Enable opportunistic TLS verification #565
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Motivation:
In some scenarios a server might want to accept connections from both, authenticated and not authenticated peers and defer decisions after the handshake. This new options allows a host to only do TLS verificaiton if the peer presents certificates and accept connections otherwise.
Modifications:
Add a new associated value to the
nonecase ofCertificationVerificationto maintain backwards compatibility. This option enables opportunistic verification.Result:
A new configuration case for TLS verification.