Erights - User contributions [en]

Sandbox

99.139.186.34 — Tue, 12 Apr 2011 21:22:12 GMT

99.139.186.34: added Hacker News

Use this page for testing out wiki markup and categories and so on.
------------------
[http://www.example.com link title]

[http://www.ibm.com another link title]

[http://www.yahoo.com Yahoo!]

[http://www.bing.com Bing]

[http://slashdot.org Slashdot]

[http://news.ycombinator.com/news Hacker News]

Sandbox

99.139.186.34 — Thu, 17 Feb 2011 22:31:23 GMT

99.139.186.34: added slashdot to test recaptcha

Sandbox

99.139.186.34 — Sat, 05 Feb 2011 15:26:48 GMT

99.139.186.34: added bing to test recaptcha

Sandbox

99.139.186.34 — Wed, 01 Dec 2010 15:57:18 GMT

99.139.186.34: test recaptcha

Use this page for testing out wiki markup and categories and so on.
------------------
[http://www.example.com link title]

[http://www.ibm.com another link title]

[http://www.yahoo.com Yahoo!]

Sandbox

99.139.186.34 — Thu, 07 Oct 2010 15:18:12 GMT

99.139.186.34: and another recaptcha test

Use this page for testing out wiki markup and categories and so on.
------------------
[http://www.example.com link title]

[http://www.ibm.com another link title]

Sandbox

99.139.186.34 — Thu, 07 Oct 2010 15:17:21 GMT

99.139.186.34: another recaptcha test

Use this page for testing out wiki markup and categories and so on.
------------------
[http://www.example.com link title]

[http://www.example.com another link title]

Sandbox

99.139.186.34 — Mon, 04 Oct 2010 22:46:50 GMT

99.139.186.34: test recaptcha

Use this page for testing out wiki markup and categories and so on.
------------------
[http://www.example.com link title]

Sandbox

99.139.186.34 — Tue, 16 Feb 2010 17:30:53 GMT

99.139.186.34: foobar.com

[[Agoric opaque box]]
[[Capability-based Active Invocation Certificates]]
----

Walnut is here:
[[Walnut]]

<nowiki>pragma.syntax("0.9")</nowiki>

<nowiki>Using nowiki</nowiki>

<pre>Using pre instead of nowiki</pre>
normal text
<code>Using code instead of nowiki</code>
more normal text
<nowiki><pre>Using pre inside of nowiki</pre></nowiki>

<pre><nowiki>Using nowiki inside of pre</nowiki></pre>

"This is in quotes."

----

How to do interwiki links:

[[wikipedia:E_(programming_language)|'''''E''''' on Wikipedia]]

[[wiki:EeLanguage|'''''E''''' on the C2 wiki]]

----

And now for something completely different.

[[Security Shootout]]

[[Object-capability languages]]

[[Object-capability operating systems]]

[[Cryptographic-capability protocols]]

[[Distributed object-capability systems]]

[[Standard updoc prelude]]

[[Standard updoc prelude for awt and swing]]

[[Standard updoc prelude for swt]]

[[Horton]]

-----

It's that classic love triangle: [[Image:erights_send.gif]]

-----

This is just some anonymous text.

And this is an anonymous link: http://www.google.com

And logged in as 'me', this should be fine: http://www.yahoo.com

-----

And now is the time for all good men to come to the aid of their country.
------

From icanhascheezburger.com:

[[Image:4chan_shiny_device.jpg]]

-------------

foobar [http://www.example.com link title] [http://www.foobar.com link title]

Sandbox

99.139.186.34 — Tue, 16 Feb 2010 17:25:51 GMT

99.139.186.34: example.com

Sandbox

99.139.186.34 — Tue, 16 Feb 2010 15:37:32 GMT

99.139.186.34: foobar

User:Zarutian/Authorization Certificates

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

99.139.186.34: fix spelling and link to sturdyref

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.