[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: cookie authentication
- To: or-dev@xxxxxxxxxxxxx
- Subject: Re: cookie authentication
- From: Watson Ladd <watsonbladd@xxxxxxxxx>
- Date: Tue, 20 Jun 2006 17:53:52 -0400
- Delivered-to: archiver@seul.org
- Delivered-to: or-dev-outgoing@seul.org
- Delivered-to: or-dev@seul.org
- Delivery-date: Tue, 20 Jun 2006 17:54:04 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-pgp-agent:x-mailer; b=AB1P8LUxT0IWUynjywqxlUiu1I8o4xPu89z7MGg3vbh3DGYBWBG6tTRzrpC3YjY1T3M89kRg0+5aE8Ub7b2oikxADdT+JTSLeR/rucjzb8ZMCKx3FpSQkWWpZGYdmaN7BHBaDlexqrNnJHuZWEnXrFbFDK4vbRmb6dNdjEQL2ak=
- In-reply-to: <200606171021.40617.robert@roberthogan.net>
- References: <200606171021.40617.robert@roberthogan.net>
- Reply-to: or-dev@xxxxxxxxxxxxx
- Sender: owner-or-dev@xxxxxxxxxxxxx
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
What is this in reference to? I have no idea
On Jun 17, 2006, at 5:21 AM, Robert Hogan wrote:
this seems to be implemented a bit oddly. the controller has to
send the raw
bytes rather than hexified version to authenticate.
is there a reason for this? i.e. harder to send from a keyboard?
or was it just convenient to do it that way? if so, would a patch
be useful
for accepting an ascii version of the cookie?
thanks,
robert
Sincerely,
Watson Ladd
- ---
"Those who would give up Essential Liberty to purchase a little
Temporary Safety deserve neither Liberty nor Safety."
- -- Benjamin Franklin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFEmG5wGV+aWVfIlEMRAukqAJ0bQNMsq2NGcTb9yfOiXEekDj5uxQCgkhhz
Tl/kHG0rQEQ3MVjEVrfH6LE=
=hBDy
-----END PGP SIGNATURE-----