Github user herval commented on the issue:
https://github.com/apache/zeppelin/pull/2145
https://github.com/herval/zeppelin/tree/encrypt-credentials
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2145
@herval
link?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user herval commented on the issue:
https://github.com/apache/zeppelin/pull/2145
I've implemented something slightly similar here, except I'm actually
encrypting the entire file using AES, using a passphrase you provide (which can
live in memory)
it's not ideal, but as
Github user dwhsys commented on the issue:
https://github.com/apache/zeppelin/pull/2145
@felixcheung @jongyoul ,
I want to discuss the problem of "false sense of security". I hope that
anyone who want to use "credentials feature" in enterprise solution will be
aware of low securit
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2145
I agree with @felixcheung.I'm not sure what the benefit is.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does no
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2145
I think zeppelin should provide a pluggable interface for password storing
and encrypting. Zeppelin could provide its default implementation for that but
allow for extension. Storing password in fi
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2145
I'm concerned that this would give people a false sense of security...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your p
