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

James Clampffer updated HDFS-13666:
-----------------------------------
    Description: At one point there were plans to implement SASL support from 
scratch inside of libhdfs+\+. Since then we added added Kerberos support 
through Cyrus SASL and GSasl. I propose removing the partial implementation 
from libhdfs++ since doing the secure handshake and encryption are still marked 
TODO but it's unclear what getting that done involves. That way we can focus 
time on using Cyrus (GSasl uses GPL) to support DIGEST-MD5 auth and wire 
encryption.  (was: At one point there were plans to implement SASL support from 
scratch inside of libhdfs++. Since then we added added Kerberos support through 
Cyrus SASL and GSasl.  I propose removing the partial implementation from 
libhdfs++ since doing the secure handshake and encryption are still marked TODO 
but it's unclear what getting that done involves.  That way we can focus time 
on using Cyrus (GSasl uses GPL) to support DIGEST-MD5 auth and wire encryption.)

> Only use existing SASL libraries in libhdfs++
> ---------------------------------------------
>
>                 Key: HDFS-13666
>                 URL: https://issues.apache.org/jira/browse/HDFS-13666
>             Project: Hadoop HDFS
>          Issue Type: Task
>            Reporter: James Clampffer
>            Priority: Major
>
> At one point there were plans to implement SASL support from scratch inside 
> of libhdfs+\+. Since then we added added Kerberos support through Cyrus SASL 
> and GSasl. I propose removing the partial implementation from libhdfs++ since 
> doing the secure handshake and encryption are still marked TODO but it's 
> unclear what getting that done involves. That way we can focus time on using 
> Cyrus (GSasl uses GPL) to support DIGEST-MD5 auth and wire encryption.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to