Differences between version 21 and predecessor to the previous major change of RobotCA.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 21 | Last edited on Friday, June 3, 2005 6:11:23 am | by JamesHoward | Revert |
| Older page: | version 14 | Last edited on Wednesday, May 18, 2005 7:44:06 am | by JamesHoward | Revert |
@@ -9,15 +9,15 @@
A [RobotCA] also has the side effect of serving as a TimeStampServer for keys---because a time stamp is included in the signature added to the key, the signature is evidence that the key existed at a certain point in time.
[RobotCA]s include:
# http://www.toehold.com/robotca/
-# http://pgpkeys.telering.at/robotca/ (discontinued as per 25.01.2005)
+# http://pgpkeys.telering.at/robotca/ (discontinued as per 25.01.2005 "due to legal considerations"
)
# http://www.imperialviolet.org/keyverify.html
-# http
://www.
jameshoward.us/Robot_Certificate_Authority (fix as of May 17, 2005)
-# https://box.cardboard.net/robotca/
-# [PGPGlobalDirectory] (WARNING: __VERY__
low security)
+# https
://jameshoward.us/Robot_Certificate_Authority
+# https://box.cardboard.net/crypto
/robotca (up and then down again in May 2005)
+# [PGPGlobalDirectory] (low security)
The first two use the same implementation, the first three are wrappers around [GPG].
-(I've used all these [RobotCA]s -- StuartYeates)
There are some [RobotCA]s which offer a a higher level of trust than simply verifying that email sent to the address list in the uid gets delivered to a holder of the secret key. Generally these are run by organisations and require some form of identification such as a passport.
# http://cacert.org/
+# http://www.heise.de/security/dienste/pgp/keys.shtml (German language)
