You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently if no suitable certificate is found in a Service declaration, the first certificate is issued to the client. If the domain does not suite the certificate the client gets an certificate error in his browser.
Is there a way to disable this behavior, i.e. just cancel the SSL/HTTPS handshake?
THX, Georg
The text was updated successfully, but these errors were encountered:
gschoenberger
changed the title
Cancle SSL/HTTPS handshake if no suited cert is found
Cancel SSL/HTTPS handshake if no suited cert is found
Dec 17, 2015
Not currently. I can't think of a compelling reason to implement this. If
you think there's a compelling use case you should bring it up on the Pound
mailing list (www.apsis.ch/pound has the links)
On Thu, Dec 17, 2015 at 9:32 AM, Georg Schönberger <[email protected]
wrote:
Hi goochjj,
currently if no suitable certificate is found in a Service declaration,
the first certificate is issued to the client. If the domain does not suite
the certificate the client gets an certificate error in his browser.
Is there a way to disable this behavior, i.e. just cancle the SSL/HTTPS
handshake?
THX, Georg
—
Reply to this email directly or view it on GitHub #13.
Hi goochjj,
currently if no suitable certificate is found in a Service declaration, the first certificate is issued to the client. If the domain does not suite the certificate the client gets an certificate error in his browser.
Is there a way to disable this behavior, i.e. just cancel the SSL/HTTPS handshake?
THX, Georg
The text was updated successfully, but these errors were encountered: