[ https://issues.apache.org/jira/browse/THRIFT-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891189#comment-13891189 ]
Jens Geyer edited comment on THRIFT-2347 at 2/4/14 8:54 PM: ------------------------------------------------------------ A few questions: (1) Why are the RemoteCertificateChainErrors and the RemoteCertificateNameMismatch removed and ignored in CertificateValidator()? (2) Same question with checkCertificateRevocation flag at the AuthenticateAsXxx() calls? If this would be some kind of optional thing (a flag or so), I could agree, but do we really intentionally weaken the secure connection? was (Author: jensg): A few questions: (1) Why are the RemoteCertificateChainErrors and the RemoteCertificateNameMismatch removed in CertificateValidator()? (2) Same question with checkCertificateRevocation flag at the AuthenticateAsXxx() calls? If this would be some kind of optional thing (a flag or so), I could agree, but do we really intentionally weaken the secure connection? > C# TLS Transport based on THRIFT-181 > ------------------------------------ > > Key: THRIFT-2347 > URL: https://issues.apache.org/jira/browse/THRIFT-2347 > Project: Thrift > Issue Type: New Feature > Components: C# - Library > Reporter: Beat Kaeslin > Priority: Minor > Attachments: > 0001-THRIFT-181-c-add-TTLSServerSocket.cs-and-TTLSSocket..patch > > Original Estimate: 24h > Remaining Estimate: 24h > > New secure Transport Layer (TLS). Implementation from THRIFT-181 Issue > without Log dependencie. -- This message was sent by Atlassian JIRA (v6.1.5#6160)