[
https://issues.apache.org/jira/browse/THRIFT-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Worth updated THRIFT-151:
-------------------------------
Attachment: thrift-0.6.0-cpp-ssl.patch
Uploading Ping Li's ssl-redesigned.patch updated as thrift-0.6.0-cpp-ssl.patch
so that it patches and compiles (includes Makefile stuff) against the
thrift-0.6.0 release and tests properly against a Python SSL client (using
patch in THRIFT-1068). Is there anything holding this improvement up from being
committed? This issue has been around a looong time.
> TSSLServerSocket and TSSLSocket implementation
> ----------------------------------------------
>
> Key: THRIFT-151
> URL: https://issues.apache.org/jira/browse/THRIFT-151
> Project: Thrift
> Issue Type: Improvement
> Components: C++ - Library
> Reporter: Ian Pye
> Attachments: TSSLSocket.cpp.diff, TSSLSocket.h.diff, Thrift.zip,
> ssl-pingli.patch, ssl-redesigned.patch, ssl-test-pingli.patch, ssl.patch,
> thrift-0.6.0-cpp-ssl.patch
>
> Original Estimate: 6h
> Remaining Estimate: 6h
>
> SSL Connections w/ autogenerated self signed x509 certs seem to be the state
> of the art for rpc layers.
> It would be good if there was a C++ implementation of TSocket and
> TServerSocket classes.
> This is similar to the Java issue Thrift 106.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
