User:Zarutian/Authorization Certificates - Revision history

99.139.186.34: fix spelling and link to sturdyref

99.139.186.34 — Mon, 07 Jul 2008 14:42:32 GMT

fix spelling and link to sturdyref

New page

This is an idea I have been mulling over a bit.

An receptionist (an object), that is reachable via an [[sturdyref]],
receives an sequence of authorization certificates.

An certificate is an tuple of issuer, instructions and signature of those two by the issuer.
An issuer in above is simply an public key (or fingerprint of the key to identify it).
The private key counterpart of that key is used to sign the certificate.

The receptionist has an mapping of issuers to avatar objects.

For each certificate in an sequence
the receptionist checks the signature of the certificate
if invalid then an exception is thrown
the receptionist then checks if it has an issuer to avatar mapping
if not then an exception is thrown
then the receptionist invokes the avatar object and passes it the instructions in the cert
the avatar object then interprets those instructions as its programer sees fit.

An facet of the receptionist handles introductions of new issuers and construction of avatar
objects for those issuers. (Some such introductions wouldn't out live the session of the current
sequence).

One type of certificate would be an online challenge-response requesting certificate
where an capability to the requester would be passed to an avatar object if it succeeds.

Zarutian: added some notes

Zarutian — Sun, 06 Jul 2008 05:55:56 GMT

added some notes

←Older revision		Revision as of 05:55, 6 July 2008
Line 17:		Line 17:
	then the recieptionist invokes the avatar object and passes it the instructions in the cert		then the recieptionist invokes the avatar object and passes it the instructions in the cert
	the avatar object then interprets those instructions as its programer sees fit.		the avatar object then interprets those instructions as its programer sees fit.
		+
		+	An facet of the recieptionist handles introductions of new issuers and construction of avatar
		+	objects for those issuers. (Some such introductions wouldnt out live the session of the current
		+	sequence).
		+
		+	One type of certificate would be an online challange-response requesting certificate
		+	where an capability to the requester would be passed to an avatar object if it succeeds.

Zarutian at 01:20, 1 July 2008

Zarutian — Tue, 01 Jul 2008 01:20:13 GMT

←Older revision		Revision as of 01:20, 1 July 2008
Line 9:		Line 9:

	The recieptionist has an mapping of issuers to avatar objects.		The recieptionist has an mapping of issuers to avatar objects.
-	For each certificate in an sequence	+
-	1. the recieptionist checks the signeture of the certificate	+	For each certificate in an sequence
-	if invalid then an exception is thrown	+	the recieptionist checks the signeture of the certificate
-	3. the recieptionist then checks if it has an issuer to avatar mapping	+	if invalid then an exception is thrown
-	if not then an exception is thrown	+	the recieptionist then checks if it has an issuer to avatar mapping
-	4. then the recieptionist invokes the avatar object and passes it the instructions in the cert	+	if not then an exception is thrown
-	5. the avatar object then interprets those instructions as its programer sees fit.	+	then the recieptionist invokes the avatar object and passes it the instructions in the cert
		+	the avatar object then interprets those instructions as its programer sees fit.

Zarutian at 01:19, 1 July 2008

Zarutian — Tue, 01 Jul 2008 01:19:38 GMT

←Older revision		Revision as of 01:19, 1 July 2008
Line 10:		Line 10:
	The recieptionist has an mapping of issuers to avatar objects.		The recieptionist has an mapping of issuers to avatar objects.
	For each certificate in an sequence		For each certificate in an sequence
-	the recieptionist checks the signeture of the certificate	+	1. the recieptionist checks the signeture of the certificate
-	if invalid then an exception is thrown	+	if invalid then an exception is thrown
-	the recieptionist then checks if it has an issuer to avatar mapping	+	3. the recieptionist then checks if it has an issuer to avatar mapping
-	if not then an exception is thrown	+	if not then an exception is thrown
-	then the recieptionist invokes the avatar object and passes it the instructions in the cert	+	4. then the recieptionist invokes the avatar object and passes it the instructions in the cert
-	the avatar object ~~is free to interpret~~ those instructions as its programer sees fit.	+	5. the avatar object then interprets those instructions as its programer sees fit.

Zarutian at 01:18, 1 July 2008

Zarutian — Tue, 01 Jul 2008 01:18:43 GMT

←Older revision		Revision as of 01:18, 1 July 2008
Line 9:		Line 9:

	The recieptionist has an mapping of issuers to avatar objects.		The recieptionist has an mapping of issuers to avatar objects.
		+	For each certificate in an sequence
		+	the recieptionist checks the signeture of the certificate
		+	if invalid then an exception is thrown
		+	the recieptionist then checks if it has an issuer to avatar mapping
		+	if not then an exception is thrown
		+	then the recieptionist invokes the avatar object and passes it the instructions in the cert
		+	the avatar object is free to interpret those instructions as its programer sees fit.

Zarutian at 01:09, 1 July 2008

Zarutian — Tue, 01 Jul 2008 01:09:57 GMT

←Older revision		Revision as of 01:09, 1 July 2008
Line 1:		Line 1:
-
	This is an idea I have been mulling over a bit.		This is an idea I have been mulling over a bit.

Line 6:		Line 5:

	An certificate is an tuple of issuer, instructions and signeture of those two by the issuer.		An certificate is an tuple of issuer, instructions and signeture of those two by the issuer.
		+	An issuer in above is simply an public key (or fingerprint of the key to identify it).
		+	The private key counterpart of that key is used to sign the certificate.
		+
		+	The recieptionist has an mapping of issuers to avatar objects.

Zarutian: New page, will be editing for a while on it.

Zarutian — Tue, 01 Jul 2008 01:05:48 GMT

New page, will be editing for a while on it.

←Older revision		Revision as of 01:05, 1 July 2008
Line 1:		Line 1:
		+
	This is an idea I have been mulling over a bit.		This is an idea I have been mulling over a bit.

-	An ~~receptionist~~ (an object), that is reachable via an [[sturdyref]],	+	An recieptionist (an object), that is reachable via an sturdyref,
-	~~receives~~ an sequence of authorization certificates.	+	recivies an sequence of authorization certificates.
-		+
-	~~An certificate is an tuple of issuer, instructions and signature of those two by the issuer.~~	+
-	~~An issuer in above is simply an public key (or fingerprint of the key to identify it).~~	+
-	~~The private key counterpart of that key is used to sign the certificate.~~	+
-		+
-	~~The receptionist has an mapping of issuers to avatar objects.~~	+
-		+
-	~~For each certificate in an sequence~~	+
-	~~the receptionist checks the signature of the certificate~~	+
-	~~if invalid then an exception is thrown~~	+
-	~~the receptionist then checks if it has an issuer to avatar mapping~~	+
-	~~if not then an exception is thrown~~	+
-	~~then the receptionist invokes the avatar object and passes it the instructions in the cert~~	+
-	~~the avatar object then interprets those instructions as its programer sees fit.~~	+
-		+
-	~~An facet of the receptionist handles introductions of new issuers and construction of avatar~~	+
-	~~objects for those issuers. (Some such introductions wouldn't out live the session of the current~~	+
-	~~sequence)~~.	+

-	~~One type of~~ certificate ~~would be~~ an ~~online challenge-response requesting certificate~~	+	An certificate is an tuple of issuer, instructions and signeture of those two by the issuer.
-	~~where an capability to~~ the ~~requester would be passed to an avatar object if it succeeds~~.	+