Talk:X.509

From Wikipedia, the free encyclopedia

Contents

[edit] Cited Reference wasn't a Reference

The only cited reference doesn't actually seem to have been a source for the article, as it is actually about a compromise of the mechanism, and, although it may cover some of the facts in passing, it certainly doesn't cover most of them.

I've moved it to external links.

It was:

Arjen Lenstra, Xiaoyun Wang and Benne de Weger, Colliding X.509 Certificates, 1 March 2005, ePrint archive, [1].

--David Woolley 11:27, 15 November 2005 (UTC)

I've added a line about the X.509 certificate collision, and so moved the citation back to the "References" section. &mdash; Matt <small>Crypto</small> 12:36, 15 November 2005 (UTC)
There is still a problem that all but one paragraph lacks sources. Unfortunately, there doesn't seem to be a template for this article's references are largely incomplete. --David Woolley 12:47, 15 November 2005 (UTC).

[edit] Sometimes I forget Wikipedia isn't necessarily for the "common man"

This article was linked from another article (the latter in "common-man's" English).

But after two quick glances my eyes just glazed over.

There's got to be a better way....

--angrykeyboarder (a/k/a:Scott) 14:03, 4 September 2006 (UTC)

[edit] CRL Validaton

As of Internet Explorer 7 CRL validation is on by default. —Preceding unsigned comment added by 24.232.96.62 (talk) 03:19, 7 October 2007 (UTC)


[edit] Not Encyclopedic

Much of this article is written in a casual style, especially this paragraph:

This is an example of a self-signed certificate; note that the issuer and subject are the same. There's no way to verify this certificate except by checking it against itself; we've reached the top of the certificate chain. So how does this certificate become trusted? Simple - it's manually configured. Thawte is one of the root certificate authorities recognized by both Microsoft and Netscape. This certificate comes with the web browser (you can probably find it listed as "Thawte Server CA" in the security settings); it's trusted by default. As a long-lived (note the expiration date), globally trusted certificate that can sign pretty much anything (note the lack of any constraints), its matching private key has to be one of the most closely guarded in the world.

I lack enough knowledge of the subject matter to rewrite it though... —Preceding unsigned comment added by 64.112.227.142 (talk) 00:50, 12 December 2007 (UTC)