Remove support for TLS session caches in TLSServerSocket.

This resolves #738
This commit is contained in:
wolfbeast 2018-09-01 23:45:10 +02:00 committed by Roy Tam
commit e2e197cada
10 changed files with 15 additions and 43 deletions

View file

@ -1938,20 +1938,6 @@ nsNSSComponent::InitializeNSS()
return NS_ERROR_FAILURE;
}
// TLSServerSocket may be run with the session cache enabled. It is necessary
// to call this once before that can happen. This specifies a maximum of 1000
// cache entries (the default number of cache entries is 10000, which seems a
// little excessive as there probably won't be that many clients connecting to
// any TLSServerSockets the browser runs.)
// Note that this must occur before any calls to SSL_ClearSessionCache
// (otherwise memory will leak).
if (SSL_ConfigServerSessionIDCache(1000, 0, 0, nullptr) != SECSuccess) {
#ifdef ANDROID
MOZ_RELEASE_ASSERT(false);
#endif
return NS_ERROR_FAILURE;
}
// ensure the CertBlocklist is initialised
nsCOMPtr<nsICertBlocklist> certList = do_GetService(NS_CERTBLOCKLIST_CONTRACTID);
#ifdef ANDROID