Skip to content
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

Open
crepererum opened this issue Sep 28, 2014 · 5 comments
Open

ykchalresp: get challange from env variable #49

crepererum opened this issue Sep 28, 2014 · 5 comments
Assignees

Comments

@crepererum
Copy link

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.

@thorduri
Copy link
Contributor

Any thoughts on this @klali ?

Looking at ykchalresp.c it should be trivial to add.

@klali
Copy link
Member

klali commented Sep 30, 2016

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?

@thorduri
Copy link
Contributor

@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 YKCHAL.

@thorduri thorduri self-assigned this Sep 30, 2016
@klali
Copy link
Member

klali commented Sep 30, 2016

No objections at all.

On Sep 30, 2016 11:06, "Thordur Bjornsson" [email protected] wrote:

@klali https://github.com/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 YKCHAL.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#49 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQI3bKZYZ7tasXbjbppnkNB_AjAYBBQks5qvNEngaJpZM4CoHB0
.

@Vincent43
Copy link

Vincent43 commented Oct 23, 2020

Environment variables are considered to be safe on most Linux systems.

Environment variables definitely aren't considered safe for storing secrets as they leak as easy as command args i.e. with ps ewwax. I advice to not introduce new options that may work as footgun for inexperienced users. Using stdin should be the safe approach.

@klali

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants