Authentication
From Erights
(Difference between revisions)
m (→Examples) |
m (typo) |
||
| Line 13: | Line 13: | ||
== Examples == | == Examples == | ||
| - | * Debian packages (objects), after they are downloaded, before they are installed, are authenticated. The authentication procedure in this case | + | * Debian packages (objects), after they are downloaded, before they are installed, are authenticated. The authentication procedure in this case establishes that given package (object) was issued by Debian community (subject). This step is useful if our trust in the Debian community is higher than to any other random subject. Genuine installation CDs contain appropriate keyring. |
* Current technology well supports authentication of e-mails (via various [http://en.wikipedia.org/wiki/MUA MUA] plugins). | * Current technology well supports authentication of e-mails (via various [http://en.wikipedia.org/wiki/MUA MUA] plugins). | ||
Revision as of 17:53, 24 July 2009
Definition
Authentication is a process of estabilishing which subject:
- created or is responsible for the contents of a given document;
- created or is responsible for the behavior of a given program.
Notes
Authentication should not be confused with the following two other concepts:
- identity checking
- authorization
Examples
- Debian packages (objects), after they are downloaded, before they are installed, are authenticated. The authentication procedure in this case establishes that given package (object) was issued by Debian community (subject). This step is useful if our trust in the Debian community is higher than to any other random subject. Genuine installation CDs contain appropriate keyring.
- Current technology well supports authentication of e-mails (via various MUA plugins).
