Differences between version 5 and previous revision of X509.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Thursday, April 1, 2004 2:43:02 am | by StuartYeates | Revert |
| Older page: | version 4 | Last edited on Monday, March 8, 2004 9:10:56 pm | by StuartYeates | Revert |
@@ -1,19 +1,19 @@
-X509 is a standard for defining a DigitalCertificate. It is the signing system used for [SSL]. The [X509] PublicKey security model is almost completely incompatible with the OpenPGP PublicKey security model, but they serve very different purposes. [X509] is heirarchical and commerce-oriented, whereas [PGP]/[GPG] is massively distributed, very fault tolerant and works using a WebOfTrust.
+X509 is a standard for defining a DigitalCertificate. It is the signing system used for [SSL]. The [X509] PublicKey security model is almost completely incompatible with the [
OpenPGP]
PublicKey security model, but they serve very different purposes. [X509] is heirarchical and commerce-oriented, whereas [PGP]/[GPG] is massively distributed, very fault tolerant and works using a WebOfTrust.
Some useful documentation on X509 certificates: http://java.sun.com/products/jdk/1.2/docs/guide/security/cert3.html.
-Some information about how to implement X509
+Some information about how to implement [
X509]
* http://www.cs.auckland.ac.nz/~pgut001/pubs/x509guide.txt
This is also just an interesting read to find out why X509 is such a bizarre standard
Things that use X509 certificates:
-* Various code-signing schemes, such as signed Java ARchives, and Microsoft Authenticode.
-* Various secure E-Mail standards, such as PEM and S/MIME.
+* Various code-signing schemes, such as signed Java ARchives, and Microsoft Authenticode (because these things are built upon [SSL])
.
+* Various secure E-Mail standards, such as PEM and S/MIME (S/MIME can also use [OpenPGP])
.
* E-Commerce protocols, such as SET.
* MicrosoftWindows
AddToMe...
----
CategoryStandards
