First patch for proposal 121

[Karsten Loesing]

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

Hi Nick,

as discussed on IRC I have started splitting up the implementation of
proposal 121 into smaller patches. I've come to the conclusion that four
main patches would be a good trade-off between patch size and number in
this case. There might be further, smaller patches afterwards, but these
four patches cover roughly everything to make proposal 121 work.

1. This is the first patch that includes configuration of client
authorization on hidden-service side, but without actually using that
data when advertising hidden services.

2. The second patch will use client authorization data to advertise
hidden services and restrict access to authorized clients only.

3. The third patch will enable users to configure authorization data for
hidden services on client side.

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

Let me know what parts of this first patch I should improve (or if you
want more/smaller or less/larger patches in the future).

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

iD8DBQFImayI0M+WPffBEmURAh1ZAKDN7JD41LzQSEfRO4Fi3r/7yG5oOwCfQp3G
L84XuhLl4wbaGVbmMWqmXXE=
=tbfV
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch-121-1.txt
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20080806/8fec7735/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch-121-1.txt.sig
Type: application/octet-stream
Size: 65 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20080806/8fec7735/attachment.obj>