-
Notifications
You must be signed in to change notification settings - Fork 81
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
ykchalresp: get challange from env variable #49
Comments
Any thoughts on this @klali ? Looking at |
Yeah, it should be fairly easy to add. In #73 we added support for reading the challenge from a file (or STDIN). Maybe that solves the same usecase? |
@klali Not really. I'm a fan of the trifecta of options being available from the command line, environment and config files. So unless there are objections, I'll whip up a patch to read the challange from |
No objections at all. On Sep 30, 2016 11:06, "Thordur Bjornsson" [email protected] wrote:
|
Environment variables definitely aren't considered safe for storing secrets as they leak as easy as command args i.e. with |
Reading a secure challenge from command line arguments isn't safe, because other users and processes are able to read them. Environment variables are considered to be safe on most Linux systems. So it would be great if ykchalresp would be able to read a challenge from an environment variable (e.g. YKCHAL) instead.
The text was updated successfully, but these errors were encountered: