Your message dated Mon, 16 Jul 2007 15:34:40 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closing freeswan bugs - superseded by openswan
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: freeswan
Version: 2.04-11.3
Severity: wishlist
Tags: l10n, patch
While translating the file freeswan, I encountered the following
typos, which I thought you might like to eliminate in a future release.
_________________
1.
po:2
auto: ⑤ Type: select
auto: ⑤ Choices
reference: ⑤ ../freeswan.templates.master:3
Original: ⌘0 earliest, \"after NFS\", \"after PCMCIA\"
("a.s.a.p" [as soon as possible] is more natural English than
"earliest" in this context.)
2.
.po:4
auto: ⑤ Type: select
auto: ⑤ Description
reference: ⑤ ../freeswan.templates.master:5
Original: ⌘0
With the current Debian startup levels (nearly everything starting in
level
20), **it is impossible for FreeS/WAN to always start at the correct
time. **
There are three possibilities when FreeS/WAN can start: before or
after the
NFS services and after the PCMCIA services. The correct answer
depends on
your specific setup.
("FreeS/WAN can't always start at the correct time." is more natural
English here.)
3.
po:6
auto: ⑤ Type: select
auto: ⑤ Description
reference: ⑤ ../freeswan.templates.master:5
Original: ⌘0
If you have your /usr tree mounted via NFS and don't use a PCMCIA
network
card, then you will need to start FreeS/WAN 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.
(there is currently a double space between these two words)
4.
po:7
auto: ⑤ Type: select
auto: ⑤ Description
reference: ⑤ ../freeswan.templates.master:5
Original: ⌘0
If you use a PCMCIA network card for your IPSec connections, **then
you only
have to choice 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.
(Here, you need to use "choose" [the verb], not "choice" [the noun].
However, in this case it would be better English to say that clause as:
"then your only choice is to start it after the PCMCIA services."
5.
.po:11
auto: ⑤ Type: boolean
auto: ⑤ Description
reference: ⑤ ../freeswan.templates.master:42
Original: ⌘0
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 administrate** and more secure.
("at both ends of the tunnel"
"to administer" is the verb.
Where the noun [administration] has been constructed from the verb,
as here, the noun is longer and more complex. Where the verb has been
constructed from the noun [less common], it's the other way around:
table (noun), to tabulate (verb))
6.
po:14
auto: ⑤ Type: select
auto: ⑤ Description
reference: ⑤ ../freeswan.templates.master:55
Original: ⌘0
It is possible to create a plain RSA public/private keypair **for the
use with**
FreeS/WAN or to create a X509 certificate file which contains the RSA
public
key **and additionally store** the corresponding private key.
("to use with"
"and additionally stores" since the certificate is doing the storing:
it stores)
7.
po:17
auto: ⑤ Type: boolean
auto: ⑤ Description
reference: ⑤ ../freeswan.templates.master:74
Original: ⌘0
Do you have an existing X509 certificate file that you want to **use
for FreeS/WAN** ?
("use with FreeS/WAN")
8.
po:23
auto: ⑤ Type: string
auto: ⑤ Description
reference: ⑤ ../freeswan.templates.master:97
Original: ⌘0 Which length should the created RSA key have ?
and
po:24
auto: ⑤ Type: string
auto: ⑤ Description
reference: ⑤ ../freeswan.templates.master:97
Original: ⌘0
Please enter the length of **the created RSA key**.
("How long should the the newly-created RSA key be?")
("the newly-created RSA key")
9.
po:50
auto: ⑤ Type: boolean
auto: ⑤ Description
reference: ⑤ ../freeswan.templates.master:193
Original: ⌘0
FreeS/WAN comes with support for opportunistic encryption (OE), which
stores
IPSec authentication information (i.e. RSA public keys) in
(**preferrably**
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, FreeS/WAN upstream comes with OE enabled by default and is thus
likely
**to break you existing connection** to the Internet (i.e. your
default route)
as soon as pluto (the FreeS/WAN keying daemon) is started.
((a) "preferably", no double letter because that short-vowel-sound
syllable is not stressed Compare:
happily
opportunity
tennis
belittle
rebuttal)
((b) "to break your existing connection")
_________________
submitted by:
Clytie Siddall, Vietnamese localization team / nhóm Việt hóa
our mailing list / hộp thư chung của nhóm chúng tôi:
[EMAIL PROTECTED]
--- End Message ---
--- Begin Message ---
Hello,
This mail closes all the bugs reported against freeswan (I had two bugs in that
set so I decided to do this) (closing via BCC since 41 bugs are concerned).
As indicated by the description of the freeswan package, freeswan is dead
and superseded by openswan. If your problem still exists with openswan,
either reopen and reassign this bug or file a new one.
Description: IPSEC utilities transition package to Openswan
FreeSWan is no longer maintained upstream and has been superseded by
Openswan. This is a transition package which depends on openswan. It may be
safely removed when openswan has been installed.
Thanks in advance.
--
Raphaël Hertzog
Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/
--- End Message ---
