[ 
https://issues.apache.org/jira/browse/THRIFT-6097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Haonan Hou updated THRIFT-6097:
-------------------------------
    Description: 
The Rust library currently provides `TTcpChannel`, but does not include an 
official TLS-capable channel or transport. Applications need to wrap a `rustls` 
or `native-tls` stream themselves and share it between the Thrift input and 
output transports.

Is official TLS support planned for the Rust library?

A possible first step could be either:
 - a backend-neutral adapter for splitting a TLS stream safely; or
 - documentation and an example showing how to use TLS with the existing
  framed/buffered transports.

  was:
The Rust library currently provides `TTcpChannel`, but does not include an
official TLS-capable channel or transport. Applications need to wrap a `rustls` 
or `native-tls` stream themselves and
share it between the Thrift input and output transports.

Is official TLS support planned for the Rust library?

A possible first step could be either:

- a backend-neutral adapter for splitting a TLS stream safely; or
- documentation and an example showing how to use TLS with the existing
  framed/buffered transports.


> Rust supports TLS
> -----------------
>
>                 Key: THRIFT-6097
>                 URL: https://issues.apache.org/jira/browse/THRIFT-6097
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Rust - Library
>            Reporter: Haonan Hou
>            Priority: Major
>
> The Rust library currently provides `TTcpChannel`, but does not include an 
> official TLS-capable channel or transport. Applications need to wrap a 
> `rustls` or `native-tls` stream themselves and share it between the Thrift 
> input and output transports.
> Is official TLS support planned for the Rust library?
> A possible first step could be either:
>  - a backend-neutral adapter for splitting a TLS stream safely; or
>  - documentation and an example showing how to use TLS with the existing
>   framed/buffered transports.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to