--K/NRh952CO+2tg14
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Nov 13, 2004 at 01:50:29PM +0000, Hubert Feyrer wrote:
> Modified Files:
> 	htdocs/guide/en: chap-cgd.xml
>=20
> Log Message:
>  * describe the steps takein in the example
>  * more data on filling /dev/random
>  * make connection between the generated config file and /etc/cgd/cgd.conf
>    more explicit

Thanks.

This one change below seems to have broken the english..

***************
*** 396,403 ****
          Now it's time to create our <devicename>cgd</devicename>, for whi=
ch
          we'll need a passphrase.  This passphrase needs to be entered
          every time the <devicename>cgd</devicename> is opened, usually at
!         each reboot, and it is from this passphrase and the salt that
!         the encryption key used is derived.  Make sure you choose
          something you won't forget, and others won't guess.
        </para>
 =20
--- 431,439 ----
          Now it's time to create our <devicename>cgd</devicename>, for whi=
ch
          we'll need a passphrase.  This passphrase needs to be entered
          every time the <devicename>cgd</devicename> is opened, usually at
!         each reboot, and it is derived from this passphrase and the
!         salt that=20
!         the encryption key used.  Make sure you choose
          something you won't forget, and others won't guess.
        </para>


perhaps, instead, "... reboot. The encryption key used by cgd is
derived from this passphrase and the salt."

(I still need to add descriptions for some of the other keygen
methods, and for the params file in general, both of which will help
clarify this).

--
Dan.

--K/NRh952CO+2tg14
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iD8DBQFBmCADEAVxvV4N66cRAsb1AKCHvd1f2U0ygDg9SZtXptlPeFxKBQCgvDxl
96EphjlEkkaGe6BN7zzV9yQ=
=6ZPZ
-----END PGP SIGNATURE-----

--K/NRh952CO+2tg14--