“Thawte”的意思、由来-开放百科全书

Thawte was originally run from Shuttleworth's parents' garage. Shuttleworth originally aimed to produce a secure server not fettered by the restrictions on the export of cryptography which had been imposed by the United States. The server, Sioux, was a fork of the Apache HTTP server; it was later integrated with the Stronghold web server as Thawte began to concentrate more on their certification activities.

Sale

In 1999, Verisign acquired Thawte in a stock purchase from Shuttleworth for US $575 million.^[2] Both Verisign and Thawte had certificates in the first Netscape browsers, and were thus "grandfathered" into all other web browsers. Before Verisign's purchase, they each had about 50% of the market. Verisign's certificate rollover was due to take place on 1 January 2000—an unfortunate choice considering the imminent Y2K bug. (Thawte had a similar rollover in July 1998.) The purchase of Thawte ensured there would be no business loss over Y2K.{{Citation needed|date=August 2010}}

Thawte certificates are also sold by retail partners with discount and installation offer.^[3]

Proceeds from the sale enabled Shuttleworth to become the second space tourist^[4] and to found the Ubuntu project.^[5]

In August 2010, Symantec acquired Verisign's security business, including Thawte.^[6]

Root Certificate Untrust

Following a dispute with Google due to the improper issuance of certificates the GeoTrust Root Certificate became untrusted.^[7] This led to the sale of Symantec's certificate business which included Thawte in August 2017 to Thoma Bravo LLC for $1 billion^[8] with the intention of merging it with DigiCert.^[9]

From the 1st December 2017 Thawte started to issue all new Certificates under the DigiCert Trusted Root TLS Certificate.^[10]

Web of Trust

The Thawte Web of Trust was discontinued on 16 November 2009.^[11] Thawte used to issue free email certificates and the Thawte Web of Trust was the optional identity verification mechanism for it. To obtain a free Thawte email certificate, a person needed to sign up for a Thawte FreeMail account which allowed a person to create as many certificates as they wanted. Although each certificate was associated with exactly one email address, multiple email addresses could have been associated with a single Thawte FreeMail account. So if a person had more than one email address, they could have created a different certificate for each of them through the same account.

Associating the Thawte FreeMail account with the real identity of the person owning was based on a Web of trust model (similar to CAcert.org). The person's identity was assured by meeting face-to-face with one or more "Thawte Notaries" who needed to see identification and keep a copy of it (for at least five years). Points were assigned by the notaries. The number of points a notary could have assigned ranges from 10 to 35. In general, the more experienced a notary was the more points they could have assigned (see table below). Notaries who were directly verified by Thawte, through events Thawte attended or held, automatically could have issued 35 points without needing to gain experience.

The number of points determined what that person's account can do. With fewer than 50 points, the certificates issued had "Thawte Freemail Member" in the name field. With 50 or more points, the certificates had the person's name in it. The presence of the person's real name in the certificate can be useful for identifying the certificate (e.g., when stored in a key store) and to help the recipient to recognise and trust the certificate. For the purposes of signing and encrypting both types of certificates could be used in the same way, because both types of certificates had the person's email address in it.

With 100 or more points, a person became a Thawte Notary. When a person becomes a notary, they were initially listed underneath their country. They could then change that location and add text to advertise the services they offer. Changes to the advertising text were approved by Thawte and the notary was placed in a pending state while it waits approval. The approval process could take several weeks, during which the person's advertisement was not published and the system did not let them access it as a notary. Cross notarisation was not allowed: a notary could not notarise a person who had notarised them.

After end of life

Thawte Notaries have been submitting minimal information to the Gossamer Spider Web of Trust ("GSWoT"; a grass-roots OpenPGP PKI) for safe-keeping in hopes to increase the longevity of their earned trust points. The collaborative effort aims to bind Thawte Notary names and email addresses to their now-existing entry on Thawte's Web of Trust Notary Map. Thawte Notaries from within and without GSWoT are performing the validations. The initiative will bear no fruit if Thawte Notaries fail to find or create a WoT that will recognise their former status as a Thawte Web of Trust Notary. The Thawte WoT Notaries List on GSWoT was maintained until 16 November 2010. CAcert, the free certification authority, took over a large part of the participants of the Thawte Web of Trust through a special programme.^[12]

See also

References

1. ^{{cite web | url=https://w3techs.com/technologies/overview/ssl_certificate/all | title=Usage of SSL certificate authorities for websites | accessdate=30 December 2016 }}
2. ^{{cite web | url=http://www.fundinguniverse.com/company-histories/verisign-inc-history/ | title=VeriSign Acquires Thawte, Signio for More Than $1.2 Billion | accessdate=30 August 2012 |date=21 December 1999 }}
3. ^{{Cite web|url=https://sslretail.com/thawte/|title=Thawte SSL Certificates|website=sslretail.com|access-date=2019-01-08}}
4. ^{{cite web | url=http://www.space.com/missionlaunches/soyuz_dock_020427.html | title=Soyuz Docks as Shuttleworth and Crew Begin Week-Long Stay at Station | accessdate=2 January 2008 | date=27 April 2002 | work=SPACE.com | deadurl=yes | archiveurl=https://web.archive.org/web/20020606141624/http://www.space.com/missionlaunches/soyuz_dock_020427.html | archivedate=6 June 2002 | df=dmy-all }}
5. ^{{cite web | url=http://www.ubuntu.com/community/ubuntustory | title=The Ubuntu Story | accessdate=21 October 2007 | deadurl=yes | archiveurl=https://www.webcitation.org/6BmUkPsXM?url=http://www.ubuntu.com/project/about-ubuntu | archivedate=29 October 2012 | df=dmy-all }}
6. ^{{cite web | url=http://www.symantec.com/content/en/us/enterprise/other_resources/b-verisign_customer_faq.en-us.pdf | title=VeriSign's Security Business is Now Part of Symantec | accessdate=9 August 2010 |date=9 August 2010 }}
7. ^{{Cite news|url=https://www.theregister.co.uk/2017/09/12/chrome_66_to_reject_symantec_certs/|title=Google to kill Symantec certs in Chrome 66, due in early 2018|access-date=2018-01-08|language=en}}
8. ^[https://www.reuters.com/article/us-symantec-divestiture-thoma-bravo/symantec-to-sell-web-certificates-business-to-thoma-bravo-sources-idUSKBN1AI2N6 Symantec to sell Web certificates business to Thoma Bravo: sources]
9. ^{{Cite news|url=https://www.digicert.com/news/digicert-completes-acquisition-of-symantec-ssl/|title=DigiCert Completes Acquisition of Symantec’s Website Security and Related PKI Solutions - DigiCert|work=DigiCert|access-date=2018-01-08|language=en-US}}
10. ^[https://www.ssltrust.com.au/thawte-ssl#about-thawte About Thawte]
11. ^{{cite web | url=https://search.thawte.com/support/ssl-digital-certificates/index?page=content&id=SO12658 | title=Frequently Asked Questions for the EOL of WOT / Class One | accessdate=24 July 2009 }}
12. ^{{Cite web|url=http://wiki.cacert.org/Tverify|title=Tverify-Programme|last=|first=|date=|website=wiki.cacert.org|access-date=2017-10-23}}