New issue
Advanced search Search tips

Issue 912383 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

bad_certificate alert from peer translates to ERR_BAD_SSL_CLIENT_AUTH_CERT on SSLServerSocket

Project Member Reported by jselover@google.com, Dec 5

Issue description

If the SSLServer has an invalid certificate, and its peer (the client) alerts it with bad_certificate, the alert-mapping code assumes it is running on a client, so it translates bad_certificate to ERR_BAD_SSL_CLIENT_AUTH_CERT, which shouldn't be the error for a bad server certificate.
 
Summary: bad_certificate alert from peer translates to ERR_BAD_SSL_CLIENT_AUTH_CERT on SSLServerSocket (was: bad_certificate alert from peer translates to ERR_BAD_SSL_CLIENT_AUTH_CERT on server)

Comment 2 Deleted

Do we actually use SSLServer sockets in production?
Not really, but I think some corners of Cast and remoting do.

Sign in to add a comment