summaryrefslogtreecommitdiff
path: root/debian/po/da.po
diff options
context:
space:
mode:
Diffstat (limited to 'debian/po/da.po')
-rw-r--r--debian/po/da.po138
1 files changed, 0 insertions, 138 deletions
diff --git a/debian/po/da.po b/debian/po/da.po
deleted file mode 100644
index b72b5ff24..000000000
--- a/debian/po/da.po
+++ /dev/null
@@ -1,138 +0,0 @@
1# Danish translation openssh.
2# Copyright (C) 2010 openssh & nedenstående oversættere.
3# This file is distributed under the same license as the openssh package.
4# Claus Hindsgaul <claus.hindsgaul@gmail.com>, 2006.
5# Joe Hansen (joedalton2@yahoo.dk), 2010.
6#
7msgid ""
8msgstr ""
9"Project-Id-Version: openssh\n"
10"Report-Msgid-Bugs-To: openssh@packages.debian.org\n"
11"POT-Creation-Date: 2013-05-22 00:05+0100\n"
12"PO-Revision-Date: 2010-08-12 17:30+01:00\n"
13"Last-Translator: Joe Hansen <joedalton2@yahoo.dk>\n"
14"Language-Team: Danish <debian-l10n-danish@lists.debian.org> \n"
15"Language: \n"
16"MIME-Version: 1.0\n"
17"Content-Type: text/plain; charset=UTF-8\n"
18"Content-Transfer-Encoding: 8bit\n"
19
20#. Type: note
21#. Description
22#: ../openssh-server.templates:1001
23msgid "Vulnerable host keys will be regenerated"
24msgstr "Sårbare værtsnøgler vil blive oprettet"
25
26#. Type: note
27#. Description
28#: ../openssh-server.templates:1001
29msgid ""
30"Some of the OpenSSH server host keys on this system were generated with a "
31"version of OpenSSL that had a broken random number generator. As a result, "
32"these host keys are from a well-known set, are subject to brute-force "
33"attacks, and must be regenerated."
34msgstr ""
35"Nogle af OpenSSh-serverens værtsnøgler på dette system blev oprettet med en "
36"version af OpenSSL, som havde en ødelagt tilfældighedstalgenerator. Derfor "
37"er disse værtsnøgler fra et velkendt sæt, der er sårbare over for brutale "
38"(brute-force) angreb og skal derfor genskabes."
39
40#. Type: note
41#. Description
42#: ../openssh-server.templates:1001
43msgid ""
44"Users of this system should be informed of this change, as they will be "
45"prompted about the host key change the next time they log in. Use 'ssh-"
46"keygen -l -f HOST_KEY_FILE' after the upgrade to print the fingerprints of "
47"the new host keys."
48msgstr ""
49"Brugere af dette system bør informeres om denne ændring, da de vil blive "
50"spurgt om værtsnøgleændringen den næste gang de logger ind. Brug 'ssh-keygen "
51"-l -f HOST_KEY_FILE' efter opgraderingen for at udskrive fingeraftryk på de "
52"nye værtsnøgler."
53
54#. Type: note
55#. Description
56#: ../openssh-server.templates:1001
57msgid "The affected host keys are:"
58msgstr "De påvirkede værtsnøgler er:"
59
60#. Type: note
61#. Description
62#: ../openssh-server.templates:1001
63msgid ""
64"User keys may also be affected by this problem. The 'ssh-vulnkey' command "
65"may be used as a partial test for this. See /usr/share/doc/openssh-server/"
66"README.compromised-keys.gz for more details."
67msgstr ""
68"Brugernøgler kan måske også være påvirket af dette problem. Kommandoen 'ssh-"
69"vulnkey' kan bruges som en delvis test vedrørende dette. Se /usr/share/doc/"
70"openssh-server/README.compromised-keys.gz for yderligere detaljer."
71
72#~ msgid "Disable challenge-response authentication?"
73#~ msgstr "Slå udfordrings-svar godkendelse fra?"
74
75#~ msgid ""
76#~ "Password authentication appears to be disabled in the current OpenSSH "
77#~ "server configuration. In order to prevent users from logging in using "
78#~ "passwords (perhaps using only public key authentication instead) with "
79#~ "recent versions of OpenSSH, you must disable challenge-response "
80#~ "authentication, or else ensure that your PAM configuration does not allow "
81#~ "Unix password file authentication."
82#~ msgstr ""
83#~ "Adgangskodegodkendelse ser ud til at være deaktiveret i din nuværende "
84#~ "OpenSSH-serveropsætning. For at forhindre brugere i at logge ind med "
85#~ "adgangskoder (måske kun med brug af offentlig nøglegodkendelse) med nyere "
86#~ "versioner af OpenSSH, skal du deaktivere udfordrings-svar godkendelse, "
87#~ "eller sikre at din PAM-opsætning ikke tillader godkendelse via "
88#~ "Unixadgangskodefil."
89
90#~ msgid ""
91#~ "If you disable challenge-response authentication, then users will not be "
92#~ "able to log in using passwords. If you leave it enabled (the default "
93#~ "answer), then the 'PasswordAuthentication no' option will have no useful "
94#~ "effect unless you also adjust your PAM configuration in /etc/pam.d/ssh."
95#~ msgstr ""
96#~ "Hvis du deaktiverer udfordrings-svar godkendelse, vil brugere ikke være i "
97#~ "stand til at logge ind med adgangskoder. Hvis du lader det være slået til "
98#~ "(standardsvaret), så vil indstillingen 'PasswordAuthentication no' ikke "
99#~ "have nogen effekt, medmindre du også redigerer din PAM-opsætning i /etc/"
100#~ "pam.d/ssh."
101
102#~ msgid "New host key mandatory"
103#~ msgstr "Ny værtsnøgle er krævet"
104
105#~ msgid ""
106#~ "The current host key, in /etc/ssh/ssh_host_key, is encrypted with the "
107#~ "IDEA algorithm. OpenSSH can not handle this host key file, and the ssh-"
108#~ "keygen utility from the old (non-free) SSH installation does not appear "
109#~ "to be available."
110#~ msgstr ""
111#~ "Den aktuelle værtsnøgle, i /etc/ssh/ssh_host_key, er krypteret med en "
112#~ "IDEA-algoritme. OpenSSH kan ikke håndtere en sådan værtsnøglefil, og "
113#~ "værktøjet ssh-keygen fra den gamle (ikke-frie, 'non-free') SSH-"
114#~ "installation lader ikke til at være tilgængeligt."
115
116#~ msgid "You need to manually generate a new host key."
117#~ msgstr "Du skal manuelt oprette en ny værtsnøgle."
118
119#~ msgid "Do you want to risk killing active SSH sessions?"
120#~ msgstr "Vil du risikere at afbryde aktive SSH-forbindelser?"
121
122#~ msgid ""
123#~ "The currently installed version of /etc/init.d/ssh is likely to kill all "
124#~ "running sshd instances. If you are doing this upgrade via an SSH session, "
125#~ "you're likely to be disconnected and leave the upgrade procedure "
126#~ "unfinished."
127#~ msgstr ""
128#~ "Den udgave af /etc/init.d/ssh, du har installeret, vil sandsynligvis "
129#~ "afbryde alle sshd-instanser. Hvis du foretager denne opgradering via en "
130#~ "SSH-session, vil du højst sandsynlig blive afbrudt og efterlade "
131#~ "opgraderingsproceduren uafsluttet."
132
133#~ msgid ""
134#~ "This can be fixed by manually adding \"--pidfile /var/run/sshd.pid\" to "
135#~ "the start-stop-daemon line in the stop section of the file."
136#~ msgstr ""
137#~ "Du kan afhjælpe dette ved at tilføje »--pidfile /var/run/sshd.pid« til "
138#~ "linjen start-stop-daemon i stop-afsnittet af filen."