summaryrefslogtreecommitdiff
path: root/debian/po/templates.pot
diff options
context:
space:
mode:
authorRene Mayrhofer <rene@mayrhofer.eu.org>2006-05-22 06:31:58 +0000
committerRene Mayrhofer <rene@mayrhofer.eu.org>2006-05-22 06:31:58 +0000
commit4769e2f961d2930ffcc6cfa5b1561548e4ea552c (patch)
tree09d7bf5ab7e542d4f909c26d57b657d3f53b5a52 /debian/po/templates.pot
parent12843c61608dfbfdd27d67d67f321e6b5b1806da (diff)
downloadvyos-strongswan-4769e2f961d2930ffcc6cfa5b1561548e4ea552c.tar.gz
vyos-strongswan-4769e2f961d2930ffcc6cfa5b1561548e4ea552c.zip
- Just copy the whole debian/ dir from my openswan packaging.
Diffstat (limited to 'debian/po/templates.pot')
-rw-r--r--debian/po/templates.pot424
1 files changed, 424 insertions, 0 deletions
diff --git a/debian/po/templates.pot b/debian/po/templates.pot
new file mode 100644
index 000000000..33c4a2acb
--- /dev/null
+++ b/debian/po/templates.pot
@@ -0,0 +1,424 @@
+#
+# Translators, if you are not familiar with the PO format, gettext
+# documentation is worth reading, especially sections dedicated to
+# this format, e.g. by running:
+# info -n '(gettext)PO Files'
+# info -n '(gettext)Header Entry'
+#
+# Some information specific to po-debconf are available at
+# /usr/share/doc/po-debconf/README-trans
+# or http://www.debian.org/intl/l10n/po-debconf/README-trans
+#
+# Developers do not need to manually edit POT or PO files.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2006-03-16 06:09+0100\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=CHARSET\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Type: select
+#. Choices
+#: ../openswan.templates.master:3
+msgid "earliest, \"after NFS\", \"after PCMCIA\""
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../openswan.templates.master:5
+msgid "At which level do you wish to start Openswan ?"
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../openswan.templates.master:5
+msgid ""
+"With the current Debian startup levels (nearly everything starting in level "
+"20), it is impossible for Openswan to always start at the correct time. "
+"There are three possibilities when Openswan can start: before or after the "
+"NFS services and after the PCMCIA services. The correct answer depends on "
+"your specific setup."
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../openswan.templates.master:5
+msgid ""
+"If you do not have your /usr tree mounted via NFS (either you only mount "
+"other, less vital trees via NFS or don't use NFS mounted trees at all) and "
+"don't use a PCMCIA network card, then it's best to start Openswan at the "
+"earliest possible time, thus allowing the NFS mounts to be secured by IPSec. "
+"In this case (or if you don't understand or care about this issue), answer "
+"\"earliest\" to this question (the default)."
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../openswan.templates.master:5
+msgid ""
+"If you have your /usr tree mounted via NFS and don't use a PCMCIA network "
+"card, then you will need to start Openswan after NFS so that all necessary "
+"files are available. In this case, answer \"after NFS\" to this question. "
+"Please note that the NFS mount of /usr can not be secured by IPSec in this "
+"case."
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../openswan.templates.master:5
+msgid ""
+"If you use a PCMCIA network card for your IPSec connections, then you only "
+"have to choose to start it after the PCMCIA services. Answer \"after PCMCIA"
+"\" in this case. This is also the correct answer if you want to fetch keys "
+"from a locally running DNS server with DNSSec support."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:33
+msgid "Do you wish to restart Openswan?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:33
+msgid ""
+"Restarting Openswan is a good idea, since if there is a security fix, it "
+"will not be fixed until the daemon restarts. Most people expect the daemon "
+"to restart, so this is generally a good idea. However this might take down "
+"existing connections and then bring them back up."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:42
+msgid "Do you want to create a RSA public/private keypair for this host ?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:42
+msgid ""
+"This installer can automatically create a RSA public/private keypair for "
+"this host. This keypair can be used to authenticate IPSec connections to "
+"other hosts and is the preferred way for building up secure IPSec "
+"connections. The other possibility would be to use shared secrets (passwords "
+"that are the same on both sides of the tunnel) for authenticating an "
+"connection, but for a larger number of connections RSA authentication is "
+"easier to administer and more secure."
+msgstr ""
+
+#. Type: select
+#. Choices
+#: ../openswan.templates.master:53
+msgid "x509, plain"
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../openswan.templates.master:55
+msgid "Which type of RSA keypair do you want to create ?"
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../openswan.templates.master:55
+msgid ""
+"It is possible to create a plain RSA public/private keypair for use with "
+"Openswan or to create a X509 certificate file which contains the RSA public "
+"key and additionally stores the corresponding private key."
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../openswan.templates.master:55
+msgid ""
+"If you only want to build up IPSec connections to hosts also running "
+"Openswan, it might be a bit easier using plain RSA keypairs. But if you want "
+"to connect to other IPSec implementations, you will need a X509 certificate. "
+"It is also possible to create a X509 certificate here and extract the RSA "
+"public key in plain format if the other side runs Openswan without X509 "
+"certificate support."
+msgstr ""
+
+#. Type: select
+#. Description
+#: ../openswan.templates.master:55
+msgid ""
+"Therefore a X509 certificate is recommended since it is more flexible and "
+"this installer should be able to hide the complex creation of the X509 "
+"certificate and its use in Openswan anyway."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:74
+msgid ""
+"Do you have an existing X509 certificate file that you want to use for "
+"Openswan ?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:74
+msgid ""
+"This installer can automatically extract the needed information from an "
+"existing X509 certificate with a matching RSA private key. Both parts can be "
+"in one file, if it is in PEM format. Do you have such an existing "
+"certificate and key file and want to use it for authenticating IPSec "
+"connections ?"
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:83
+msgid "Please enter the location of your X509 certificate in PEM format."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:83
+msgid ""
+"Please enter the location of the file containing your X509 certificate in "
+"PEM format."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:89
+msgid "Please enter the location of your X509 private key in PEM format."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:89
+msgid ""
+"Please enter the location of the file containing the private RSA key "
+"matching your X509 certificate in PEM format. This can be the same file that "
+"contains the X509 certificate."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:97
+msgid "Which length should the created RSA key have ?"
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:97
+msgid ""
+"Please enter the length of the created RSA key. it should not be less than "
+"1024 bits because this should be considered unsecure and you will probably "
+"not need anything more than 2048 bits because it only slows the "
+"authentication process down and is not needed at the moment."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:106
+msgid "Do you want to create a self-signed X509 certificate ?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:106
+msgid ""
+"This installer can only create self-signed X509 certificates automatically, "
+"because otherwise a certificate authority is needed to sign the certificate "
+"request. If you want to create a self-signed certificate, you can use it "
+"immediately to connect to other IPSec hosts that support X509 certificate "
+"for authentication of IPSec connections. However, if you want to use the new "
+"PKI features of Openswan >= 1.91, you will need to have all X509 "
+"certificates signed by a single certificate authority to create a trust path."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:106
+msgid ""
+"If you do not want to create a self-signed certificate, then this installer "
+"will only create the RSA private key and the certificate request and you "
+"will have to sign the certificate request with your certificate authority."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:124
+msgid "Please enter the country code for the X509 certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:124
+msgid ""
+"Please enter the 2 letter country code for your country. This code will be "
+"placed in the certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:124
+msgid ""
+"You really need to enter a valid country code here, because openssl will "
+"refuse to generate certificates without one. An empty field is allowed for "
+"any other field of the X.509 certificate, but not for this one."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:124
+msgid "Example: AT"
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:137
+msgid ""
+"Please enter the state or province name for the X509 certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:137
+msgid ""
+"Please enter the full name of the state or province you live in. This name "
+"will be placed in the certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:137
+msgid "Example: Upper Austria"
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:146
+msgid "Please enter the locality name for the X509 certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:146
+msgid ""
+"Please enter the locality (e.g. city) where you live. This name will be "
+"placed in the certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:146
+msgid "Example: Vienna"
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:155
+msgid "Please enter the organization name for the X509 certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:155
+msgid ""
+"Please enter the organization (e.g. company) that the X509 certificate "
+"should be created for. This name will be placed in the certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:155
+msgid "Example: Debian"
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:165
+msgid "Please enter the organizational unit for the X509 certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:165
+msgid ""
+"Please enter the organizational unit (e.g. section) that the X509 "
+"certificate should be created for. This name will be placed in the "
+"certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:165
+msgid "Example: security group"
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:175
+msgid "Please enter the common name for the X509 certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:175
+msgid ""
+"Please enter the common name (e.g. the host name of this machine) for which "
+"the X509 certificate should be created for. This name will be placed in the "
+"certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:175
+msgid "Example: gateway.debian.org"
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:185
+msgid "Please enter the email address for the X509 certificate request."
+msgstr ""
+
+#. Type: string
+#. Description
+#: ../openswan.templates.master:185
+msgid ""
+"Please enter the email address of the person or organization who is "
+"responsible for the X509 certificate, This address will be placed in the "
+"certificate request."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:193
+msgid "Do you wish to enable opportunistic encryption in Openswan?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:193
+msgid ""
+"Openswan comes with support for opportunistic encryption (OE), which stores "
+"IPSec authentication information (i.e. RSA public keys) in (preferably "
+"secure) DNS records. Until this is widely deployed, activating it will cause "
+"a significant slow-down for every new, outgoing connection. Since version "
+"2.0, Openswan upstream comes with OE enabled by default and is thus likely "
+"to break your existing connection to the Internet (i.e. your default route) "
+"as soon as pluto (the Openswan keying daemon) is started."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../openswan.templates.master:193
+msgid ""
+"Please choose whether you want to enable support for OE. If unsure, do not "
+"enable it."
+msgstr ""