Server-Gated Cryptography

Server-Gated Cryptography (SGC), also known as International Step-Up by Netscape, is a defunct mechanism that was used to step up from 40-bit or 56-bit to 128-bit cipher suites with SSL. It was created in response to United States federal legislation on the export of strong cryptography in the 1990s.[1] The legislation had limited encryption to weak algorithms and shorter key lengths in software exported outside of the United States . When the legislation added an exception for financial transactions, SGC was created as an extension to SSL with the certificates being restricted to financial organisations. In 1999, this list was expanded to include online merchants, healthcare organizations, and insurance companies.[2] This legislation changed in January 2000, resulting in vendors no longer shipping export-grade browsers and SGC certificates becoming available without restriction. Internet Explorer supported SGC starting with patched versions of Internet Explorer 3. SGC became obsolete when Internet Explorer 5.01 SP1 and Internet Explorer 5.5 started supporting strong encryption without the need for a separate high encryption pack (except on Windows 2000, which needs its own high encryption pack that was included in Service Pack 2 and later).[3] "Export-grade" browsers are unusable on the modern Web due to many servers disabling export cipher suites. Additionally, these browsers are incapable of using SHA-2 family signature hash algorithms like SHA-256. Certification authorities are trying to phase out the new issuance of certificates with the older SHA-1 signature hash algorithm.

The continuing use of SGC facilitates the use of obsolete, insecure Web browsers with HTTPS.[4][5] However, while certificates that use the SHA-1 signature hash algorithm remain available, some certificate authorities continue to issue SGC certificates (often charging a premium for them) although they are obsolete. The reason certificate authorities can charge a premium for SGC certificates is that browsers only allowed a limited number of roots to support SGC.

When an SSL handshake takes place, the software (e.g. a web browser) would list the ciphers that it supports. Although the weaker exported browsers would only include weaker ciphers in its initial SSL handshake, the browser also contained stronger cryptography algorithms. There are two protocols involved to activate them. Netscape Communicator 4 used International Step-Up, which used the now obsolete insecure renegotiation to change to a stronger cipher suite. Microsoft used SGC, which sends a new Client Hello message listing the stronger cipher suites on the same connection after the certificate is determined to be SGC capable, and also supported Netscape Step-Up for compatibility (though this support in the NT 4.0 SP6 and IE 5.01 version had a bug where changing MAC algorithms during Step-Up did not work properly).[citation needed]

## See also

* FREAK

## References

1. ↑ Thawte SGC Knowledgebase , 3/12/2010
2. ↑ "Global Server ID Details". Archived on 29 February 2000. Error: If you specify `|archivedate=`, you must also specify `|archiveurl=`. http://digitalid.verisign.com/server/global/globalDetails.htm.
3. ↑ University of Cambridge page on Server Gated Cryptography, 3/12/2010[clarification needed]
4. ↑ SSLShopper.com "Say No to SGC", 3/12/2010
5. ↑ Server-Gated Cryptography (SGC) browsers pose security risks, 3/12/2010

## External links

* Microsoft's page on Server Gated Cryptography
* Old mod_ssl documentation on SGC, Step-Up and Global-ID

* v
* t
* e

TLS and SSL

Protocols and technologies|

* Transport Layer Security / Secure Sockets Layer (TLS/SSL)
* Datagram Transport Layer Security (DTLS)
* Server Name Indication (SNI)
* Application-Layer Protocol Negotiation (ALPN)
* DNS-based Authentication of Named Entities (DANE)
* DNS Certification Authority Authorization (CAA)
* HTTPS
* HTTP Strict Transport Security (HSTS)
* HTTP Public Key Pinning (HPKP)
* OCSP stapling
* Perfect forward secrecy
* STARTTLS

Public-key infrastructure|

* Automated Certificate Management Environment (ACME)
* Certificate authority (CA)
* CA/Browser Forum
* Certificate policy
* Certificate revocation list (CRL)
* Domain-validated certificate (DV)
* Extended Validation Certificate (EV)
* Online Certificate Status Protocol (OCSP)
* Public key certificate
* Public-key cryptography
* Public key infrastructure (PKI)
* Root certificate
* Self-signed certificate

See also|

* Domain Name System Security Extensions (DNSSEC)
* Internet Protocol Security (IPsec)
* Secure Shell (SSH)

History|

* Export of cryptography from the United States
* Server-Gated Cryptography

Implementations|

* Bouncy Castle
* BoringSSL
* Botan
* cryptlib
* GnuTLS
* JSSE
* LibreSSL
* MatrixSSL
* mbed TLS
* NSS
* OpenSSL
* RSA BSAFE
* S2n
* SChannel
* SSLeay
* stunnel
* wolfSSL

Notaries|

* Certificate Transparency
* Convergence
* HTTPS Everywhere
* Perspectives Project

Vulnerabilities|

| Theory|

* Man-in-the-middle attack
* Padding oracle attack

|

Cipher|

* Bar mitzvah attack

Protocol|

* BEAST
* BREACH
* CRIME
* DROWN
* Logjam
* POODLE (in regards to SSL 3.0)

Implementation|

* Certificate authority compromise
* Random number generator attacks
* FREAK
* goto fail
* Heartbleed
* Lucky Thirteen attack
* POODLE (in regards to TLS 1.0)
* Kazakhstan MITM attack

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Server-Gated Cryptography. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Server-Gated_Cryptography&oldid=194228"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template