[Pkg-privacy-commits] [vidalia] 44/160: README.Debian reviewed by l10n-English team. Thanks JustinRye!
Ximin Luo
infinity0 at moszumanska.debian.org
Sat Aug 22 13:13:59 UTC 2015
This is an automated email from the git hooks/post-receive script.
infinity0 pushed a commit to branch master
in repository vidalia.
commit 35dc3a3b71e176cc162ecf0834f0af258e496548
Author: Dererk <dererk at madap.com.ar>
Date: Thu Oct 14 20:19:06 2010 -0300
README.Debian reviewed by l10n-English team. Thanks JustinRye!
---
debian/0.2.x/README.Debian | 106 ++++++++++-----------
.../vidalia-0.2.9-1+squeeze1/debian/README.Debian | 106 ++++++++++-----------
2 files changed, 102 insertions(+), 110 deletions(-)
diff --git a/debian/0.2.x/README.Debian b/debian/0.2.x/README.Debian
index ea168c1..284851d 100644
--- a/debian/0.2.x/README.Debian
+++ b/debian/0.2.x/README.Debian
@@ -1,15 +1,15 @@
Vidalia for Debian
------------------
- For the anxious and patienceless people
- ---------------------------------------
+ For the anxious and impatient
+ -----------------------------
-3 different ways of running Vidalia:
+There are three ways of running Vidalia:
-1. Re/Configure Vidalia not to let Tor to start and simply start Vidalia.
-2. Enable CookieAuthentication at tor's config, and grab
- /var/lib/tor/control_auth_cookie (RECOMMENDED for strength security)
-3. Enable ControlPort and use HashedControlPassword got from
+1. (Re)Configure Vidalia not to let Tor start, and simply start Vidalia.
+2. Enable CookieAuthentication in Tor's config, and grab
+ /var/lib/tor/control_auth_cookie (RECOMMENDED for greater security)
+3. Enable ControlPort and use HashedControlPassword from
'tor --hash-password'.
@@ -18,46 +18,38 @@ Vidalia for Debian
Full and complete explanation
-----------------------------
+Vidalia provides a graphical graphical user interface to configure
+various aspects of the Tor Network, check its status at a glance,
+monitor its bandwidth usage, or just view logs. This means that
+Vidalia needs to talk to the Tor daemon.
-Vidalia provides a GUI for the Tor software.
-That means that Vidalia needs to talk to the Tor software for configuring
-different aspects of the Tor Network, view its status at a glance,
-monitor its bandwidth usage, or just view logs between others
-
-The component of the Tor software that Vidalia talks to is a daemon process,
-which works on background without any user interaction required.
-
-Vidalia support three different ways of talking to Tor:
-
+Vidalia supports three different ways of talking to Tor:
-
-1. Letting Vidalia start Tor process on its own.
+1. Let Vidalia start the Tor process on its own.
---------------------------------------------
------> "I want it, and I want it NOW!"
- This option is the simplest for end users.
+ This option is the simplest, but not usable on a multi-user system.
- This is default option on debconf while configuring vidalia package, handled
- in the debconf front-end to Vidalia, easily reconfigurable by running
- 'dpkg-reconfigure vidalia' at any given time.
-
+ Debconf offers this as the default option, but it can be easily
+ reconfigured at any time by running 'dpkg-reconfigure vidalia'.
*********************** FOR PARANOIDS ONLY ***************************
| |
| |
- | In the remote and unlikely event of existing a bug on the |
- | Tor routing algorithm or implementation itself, it might |
- | _relatively_ easy, or unless possible, for a remote user to |
- | access to the user's launching Vidalia information, |
- | known as "privilege escalation attacks". |
+ | In the remote and unlikely event of a bug existing in the |
+ | Tor routing algorithm or implementation itself, it might be |
+ | _relatively_ easy, or at least possible, for a remote user to |
+ | gain access to the data of the user launching Vidalia (what's |
+ | known as a "privilege escalation" attack) |
| |
| |
- | This will be much more difficult if you run Vidalia on any |
- | of the next two alternatives described below. |
+ | This will be much more difficult if you run Vidalia using |
+ | either of the two alternatives described below. |
| |
| |
- | ** Please consider using them if possible!!!! ** |
+ | ** Please consider using them if possible! ** |
| |
| |
*********************** FOR PARANOIDS ONLY ***************************
@@ -67,44 +59,46 @@ Vidalia support three different ways of talking to Tor:
2. Enable Tor to use CookieAuthentication to communicate with Vidalia.
-------------------------------------------------------------------
- * The better password is the one you don't have to know about *
+ * The best password is the one you don't have to know about *
- This method consists in a password-less authentication. This means
- you wont have to remember any password, but you'll have to grab a
- very important and *SECRET* file from your disc, called "Auth Cookie".
+ This method consists of a password-less authentication. This means
+ you won't have to remember any password, but you'll have to grab a
+ very important and *SECRET* file from your disc, called "Auth Cookie".
+
+ To enable this profile, edit Tor's configuration file, by default at
+ '/etc/tor/torrc', and add or uncomment the 'CookieAuthentication'
+ value, setting it to 1.
- To enable this profile, edit Tor configuration file, by default at
- '/etc/tor/torrc', add or uncomment the 'CookieAuthentication' value
- and setting it to 1.
You will end up having something like this:
# grep Cookie /etc/tor/torrc
CookieAuthentication 1
- Now start/restart Tor daemon and start Vidalia from your regular X user.
- Vidalia will ask you for a "cookie file" at the next run:
+ Now start/restart the Tor daemon, and start Vidalia (as a regular X
+ user). Vidalia will ask you for a "cookie file" at the next run:
------------------------------------------------------------------------
You will have to fetch the "cookie file" from your local filesystem,
- by default at '/var/lib/tor/control_auth_cookie'
+ by default at '/var/lib/tor/control_auth_cookie'
- DO NOT share this file to anyone, Tor rests on it!
+ DO NOT share this file with anyone, Tor depends on it!
------------------------------------------------------------------------
This option might be simpler than all the others, but will require you
- to grab a different cookie file every time you restart the Tor process,
- on contrast to the next methods.
+ to grab a different cookie file every time you restart the Tor process,
+ in contrast to the next methods.
- This is my prefer and recommended method, simple and easy, no passwords.
+ This is my preferred and recommended method, simple and easy, no
+ passwords.
3. Enable Tor to use a control port to communicate with Vidalia.
-------------------------------------------------------------
- Edit Tor configuration file, by default '/etc/tor/torrc', add or
- uncomment the 'ControlPort 9051' option, and adding the output
- you get from tor to 'HashedControlPassword', as shown here:
+ Edit the Tor configuration file, by default '/etc/tor/torrc', add or
+ uncomment the 'ControlPort 9051' option, and add the output you get
+ from Tor to 'HashedControlPassword', as shown here:
# tor --hash-password SOME_PASSWORD_HERE
Sep 17 18:48:49.421 [notice] Tor v0.2.0.30 (r15956). This is experimental
@@ -113,16 +107,18 @@ software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
16:167F667A98F859D2600BD708B48B95343FEF7800B479E2AA4284ACF029
- You will end having something like this:
+ You will end up with something like this:
# grep Control /etc/tor/torrc
ControlPort 9051
HashedControlPassword 16:167F667A98F...4ACF029
- Now start/restart Tor daemon and start Vidalia from your regular X user.
- Vidalia will ask you for that password at the next run, in the example,
- 'SOME_PASSWORD_HERE' (as the phrase you pass it with --hash-password,
- not the hash), an will start a secure authentication. That's all!
+ Now start/restart the Tor daemon, and start Vidalia (as a regular X
+ user). Vidalia will ask you for that password at the next run (the
+ phrase you passed it with --hash-password, not the hash - in the
+ example, 'SOME_PASSWORD_HERE'), and will start a secure
+ authentication. That's all!
+
- -- Ulises Vitulli <dererk at debian.org> Fri, 24 Sep 2010 11:18:20 -0300
+ -- Ulises Vitulli <dererk at debian.org> Thu, 14 Oct 2010 19:58:20 -0300
diff --git a/testing-proposed-updates/vidalia-0.2.9-1+squeeze1/debian/README.Debian b/testing-proposed-updates/vidalia-0.2.9-1+squeeze1/debian/README.Debian
index ea168c1..284851d 100644
--- a/testing-proposed-updates/vidalia-0.2.9-1+squeeze1/debian/README.Debian
+++ b/testing-proposed-updates/vidalia-0.2.9-1+squeeze1/debian/README.Debian
@@ -1,15 +1,15 @@
Vidalia for Debian
------------------
- For the anxious and patienceless people
- ---------------------------------------
+ For the anxious and impatient
+ -----------------------------
-3 different ways of running Vidalia:
+There are three ways of running Vidalia:
-1. Re/Configure Vidalia not to let Tor to start and simply start Vidalia.
-2. Enable CookieAuthentication at tor's config, and grab
- /var/lib/tor/control_auth_cookie (RECOMMENDED for strength security)
-3. Enable ControlPort and use HashedControlPassword got from
+1. (Re)Configure Vidalia not to let Tor start, and simply start Vidalia.
+2. Enable CookieAuthentication in Tor's config, and grab
+ /var/lib/tor/control_auth_cookie (RECOMMENDED for greater security)
+3. Enable ControlPort and use HashedControlPassword from
'tor --hash-password'.
@@ -18,46 +18,38 @@ Vidalia for Debian
Full and complete explanation
-----------------------------
+Vidalia provides a graphical graphical user interface to configure
+various aspects of the Tor Network, check its status at a glance,
+monitor its bandwidth usage, or just view logs. This means that
+Vidalia needs to talk to the Tor daemon.
-Vidalia provides a GUI for the Tor software.
-That means that Vidalia needs to talk to the Tor software for configuring
-different aspects of the Tor Network, view its status at a glance,
-monitor its bandwidth usage, or just view logs between others
-
-The component of the Tor software that Vidalia talks to is a daemon process,
-which works on background without any user interaction required.
-
-Vidalia support three different ways of talking to Tor:
-
+Vidalia supports three different ways of talking to Tor:
-
-1. Letting Vidalia start Tor process on its own.
+1. Let Vidalia start the Tor process on its own.
---------------------------------------------
------> "I want it, and I want it NOW!"
- This option is the simplest for end users.
+ This option is the simplest, but not usable on a multi-user system.
- This is default option on debconf while configuring vidalia package, handled
- in the debconf front-end to Vidalia, easily reconfigurable by running
- 'dpkg-reconfigure vidalia' at any given time.
-
+ Debconf offers this as the default option, but it can be easily
+ reconfigured at any time by running 'dpkg-reconfigure vidalia'.
*********************** FOR PARANOIDS ONLY ***************************
| |
| |
- | In the remote and unlikely event of existing a bug on the |
- | Tor routing algorithm or implementation itself, it might |
- | _relatively_ easy, or unless possible, for a remote user to |
- | access to the user's launching Vidalia information, |
- | known as "privilege escalation attacks". |
+ | In the remote and unlikely event of a bug existing in the |
+ | Tor routing algorithm or implementation itself, it might be |
+ | _relatively_ easy, or at least possible, for a remote user to |
+ | gain access to the data of the user launching Vidalia (what's |
+ | known as a "privilege escalation" attack) |
| |
| |
- | This will be much more difficult if you run Vidalia on any |
- | of the next two alternatives described below. |
+ | This will be much more difficult if you run Vidalia using |
+ | either of the two alternatives described below. |
| |
| |
- | ** Please consider using them if possible!!!! ** |
+ | ** Please consider using them if possible! ** |
| |
| |
*********************** FOR PARANOIDS ONLY ***************************
@@ -67,44 +59,46 @@ Vidalia support three different ways of talking to Tor:
2. Enable Tor to use CookieAuthentication to communicate with Vidalia.
-------------------------------------------------------------------
- * The better password is the one you don't have to know about *
+ * The best password is the one you don't have to know about *
- This method consists in a password-less authentication. This means
- you wont have to remember any password, but you'll have to grab a
- very important and *SECRET* file from your disc, called "Auth Cookie".
+ This method consists of a password-less authentication. This means
+ you won't have to remember any password, but you'll have to grab a
+ very important and *SECRET* file from your disc, called "Auth Cookie".
+
+ To enable this profile, edit Tor's configuration file, by default at
+ '/etc/tor/torrc', and add or uncomment the 'CookieAuthentication'
+ value, setting it to 1.
- To enable this profile, edit Tor configuration file, by default at
- '/etc/tor/torrc', add or uncomment the 'CookieAuthentication' value
- and setting it to 1.
You will end up having something like this:
# grep Cookie /etc/tor/torrc
CookieAuthentication 1
- Now start/restart Tor daemon and start Vidalia from your regular X user.
- Vidalia will ask you for a "cookie file" at the next run:
+ Now start/restart the Tor daemon, and start Vidalia (as a regular X
+ user). Vidalia will ask you for a "cookie file" at the next run:
------------------------------------------------------------------------
You will have to fetch the "cookie file" from your local filesystem,
- by default at '/var/lib/tor/control_auth_cookie'
+ by default at '/var/lib/tor/control_auth_cookie'
- DO NOT share this file to anyone, Tor rests on it!
+ DO NOT share this file with anyone, Tor depends on it!
------------------------------------------------------------------------
This option might be simpler than all the others, but will require you
- to grab a different cookie file every time you restart the Tor process,
- on contrast to the next methods.
+ to grab a different cookie file every time you restart the Tor process,
+ in contrast to the next methods.
- This is my prefer and recommended method, simple and easy, no passwords.
+ This is my preferred and recommended method, simple and easy, no
+ passwords.
3. Enable Tor to use a control port to communicate with Vidalia.
-------------------------------------------------------------
- Edit Tor configuration file, by default '/etc/tor/torrc', add or
- uncomment the 'ControlPort 9051' option, and adding the output
- you get from tor to 'HashedControlPassword', as shown here:
+ Edit the Tor configuration file, by default '/etc/tor/torrc', add or
+ uncomment the 'ControlPort 9051' option, and add the output you get
+ from Tor to 'HashedControlPassword', as shown here:
# tor --hash-password SOME_PASSWORD_HERE
Sep 17 18:48:49.421 [notice] Tor v0.2.0.30 (r15956). This is experimental
@@ -113,16 +107,18 @@ software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
16:167F667A98F859D2600BD708B48B95343FEF7800B479E2AA4284ACF029
- You will end having something like this:
+ You will end up with something like this:
# grep Control /etc/tor/torrc
ControlPort 9051
HashedControlPassword 16:167F667A98F...4ACF029
- Now start/restart Tor daemon and start Vidalia from your regular X user.
- Vidalia will ask you for that password at the next run, in the example,
- 'SOME_PASSWORD_HERE' (as the phrase you pass it with --hash-password,
- not the hash), an will start a secure authentication. That's all!
+ Now start/restart the Tor daemon, and start Vidalia (as a regular X
+ user). Vidalia will ask you for that password at the next run (the
+ phrase you passed it with --hash-password, not the hash - in the
+ example, 'SOME_PASSWORD_HERE'), and will start a secure
+ authentication. That's all!
+
- -- Ulises Vitulli <dererk at debian.org> Fri, 24 Sep 2010 11:18:20 -0300
+ -- Ulises Vitulli <dererk at debian.org> Thu, 14 Oct 2010 19:58:20 -0300
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-privacy/packages/vidalia.git
More information about the Pkg-privacy-commits
mailing list