Talk:Authorization certificate

From Wikipedia, the free encyclopedia

This article may be too technical for a general audience. Please help improve this article by providing more context and better explanations of technical details to make it more accessible, without removing technical details.

Not much activity here even when I did put delibrate spelling errors like they recomended in the stub tutorial —Zarutian

[edit] Can anyone clean this up

I couldn't make head nor tail of this addition; can anyone clean it up?

basicly and raughly: Authorization Certificate ~= sign(Kself, "Authorize <Ksubject> to access <resource> [, <resource> [...]]")

resource can be anything you want, from a file path to a password capability to service name.

Kerberos is also an ?good? way to control access in distrubated resources.

— Matt Crypto 08:08, 23 Feb 2005 (UTC)

I see I got caried away a little. That happens ;-)

What I meant that a authorization certificate is like a chitty or statement saying that an x party may access y and z resources.

This chitty or statement is cryptographicly signed with the certificate's issuer's private key.

Another good way to control access to distrubated resources is Kerberos.

Hope this cleans this up a bit

—Zarutian 18:28, 18 Jun 2005 (UTC)