-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passwords stored in plain text #107
Comments
raising this up again. |
I adapted the code to encrypt the entire dsn. The code is below. |
this looks promising @thaddak , we will be trying this out. have you considered a MR/PR to the main repo? or forking the repo itself if it's not maintained? |
Hi Mark,
No, I adapted the code for my own use and put it up on github to make it
easier to share. I'm not a developer and don't want the responsibility of
maintaining code :)
Hopefully that code works for you.
Regards,
Thaddaeus
|
of course. thanks so much for you contribution!
…On Wed, Mar 22, 2023 at 9:20 AM TK ***@***.***> wrote:
Hi Mark,
No, I adapted the code for my own use and put it up on github to make it
easier to share. I'm not a developer and don't want the responsibility of
maintaining code :)
Hopefully that code works for you.
Regards,
Thaddaeus
On Thu, 23 Mar 2023 at 00:04, Mark Lybarger ***@***.***>
wrote:
> this looks promising @thaddak <https://github.com/thaddak> , we will be
> trying this out. have you considered a MR/PR to the main repo? or forking
> the repo itself if it's not maintained?
>
> —
> Reply to this email directly, view it on GitHub
> <#107 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/A6VDO7PFQH6BZ54EYTECB6TW5L2HHANCNFSM5HRHRUHA
>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#107 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAL3FVVKGTBXYDJCICYZFMDW5L4B5ANCNFSM5HRHRUHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi team,
Noted that when defining the data source the username and password are being stored in clear text. Do you have any experience with pulling the username and/or password from a secure source (a Vault, for example)? There are obvious security concerns with keeping passwords in plaintext (even if it's on a yaml file on our infra)
Thanks!
The text was updated successfully, but these errors were encountered: