[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: rules for SPKI <auth> field comparisons
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Carl" == Carl Ellison <cme@cybercash.com> writes:
Carl> We need to define a mechanism to be used by those who define
Carl> new <auth> fields so that they can describe the sorting
Carl> order for their fields. We could fall back on the
I must admit that I don't understand this requirement.
At first I thought this was so that we could have a canonical order
for the auth fields for signature.
Now, I think (based on your "checking" example) that this has
more to do with interpretation of the auth field. This confuses me,
because I thought this was necessarily application specific.
[I'm willing to write my cooked-ascii format up in an id if there is interest]
] Temporarily located in balmy Helsinki, Finland, at SSH | one quark [
] Michael Richardson, Sandelman Software Works, Ottawa, ON | two quark [
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ | red q blue q[
] panic("Just another NetBSD/notebook using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQB1AwUBMyac1cmxxiPyUBAxAQENBgMArBDuWpjuLXCcx1vVDMWcKoovs7dzhEAS
KYWq5piv7jyEbcTlq5Na6P2KpcEWfbPQgMdNB54juU/on1eEGucU573py9bADZaW
hvuGU7oUHBhOq4nVSUEFv0lFLliKmpqh
=8hXo
-----END PGP SIGNATURE-----
Follow-Ups:
References: