Second patch for proposal 121

[Karsten Loesing]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Nick,

this is the second patch to implement proposal 121. I switched patches 2
and 3 as compared to my original plan, so that all configuration options
can be used (however, without having an effect). The current plan for
the remaining 121 patches is as follows:

2. This second patch enables users to configure authorization data for
hidden services on client side.

3. The third patch will use authorization data on server side to
advertise hidden services and restrict access to authorized clients only.

4. Finally, the fourth patch uses authorization data to access a hidden
service.

Thanks!
- --Karsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFInhxp0M+WPffBEmURAohAAKCF5wUfuRiKmqgvHZMgZ9mdz85vDACgtJ4l
HcIn1sFkzQqBEbOrNxHRY00=
=mpqv
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch-121-2.txt
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20080810/0e81786c/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch-121-2.txt.sig
Type: application/octet-stream
Size: 65 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20080810/0e81786c/attachment.obj>