Thanks Josh.
On Nov 28, 2017 11:24 AM, "Josh Elser" wrote:
Have you read the portion of the HBase book that I previously linked to?
This is handled by SASL and GSSAPI/Kerberos. Please use your favorite
search engine and do some reading.
SSL is just *one* library that can be used to provide priv
Have you read the portion of the HBase book that I previously linked to?
This is handled by SASL and GSSAPI/Kerberos. Please use your favorite
search engine and do some reading.
SSL is just *one* library that can be used to provide privacy of data in
motion.
On 11/27/17 7:25 AM, Ash N wrote:
Josh,
Thank you for your comment.
1.
Could you please point me to any resources around the below statement you
make?
" there are definitely the tools/configuration that exist to provide end to
end data privacy "
2.SSL is just not part of that picture :)
Above statement is contrary to my und
Thanks, Ash. Just to confirm, there are definitely the tools/configuration
that exist to provide end to end data privacy (at rest and in motion). SSL
is just not part of that picture :)
On Nov 24, 2017 12:19, "Ash N" <742...@gmail.com> wrote:
> Josh,
>
> Thank you for your quick response.
>
> The
Josh,
Thank you for your quick response.
The data is sensitive personal data of customers. Everything needs to be
encrypted and secure. In - wire, on-wire, in-motion, at rest, everything.
Our solution was to use SSL/TLS everywhere. Our development team reported
that Phoenix does not support SS
Why do you have a hard-requirement on using SSL?
HBase itself does not use SSL to provide confidentiality on its wire
communication, it relies on jGSS and SASL to implement this security.
Under the hood, this actually boils down to using GSSAPI, Kerberos
specifically, to implement privacy (e.g
