[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: Sat, 17 Jun 2006 07:05:56 -0400
- Delivered-to: archiver@seul.org
- Delivered-to: or-dev-outgoing@seul.org
- Delivered-to: or-dev@seul.org
- Delivery-date: Sat, 17 Jun 2006 07:06:11 -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=M6Xrd9GgKAoLjGR15iBeIVN81uE9CpAPtT0sx1WbPjHg2wx6KaUNnUjrq4hlF0W9EJo5Tu0tDhmVVsYhZrZBkOPY2g7O/6X1YEUIa43FZacd5oyMLQ/Za9Ar6hBnjP2+tj1/WfQe+rhT/YKD9vU12Wg3wuVVvAeeIpoILf5Pd98=
- 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, but would l
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)
iD8DBQFEk+IWGV+aWVfIlEMRAuFvAJ0YiKLIab75ULjHrySxb50iQRj4eQCdEH/m
SWwDUeSyqG+QGBpH5bnYcrk=
=+9Em
-----END PGP SIGNATURE-----