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

OTP input is echoed in the clear #10

Open
throw1008a opened this issue Apr 20, 2020 · 3 comments
Open

OTP input is echoed in the clear #10

throw1008a opened this issue Apr 20, 2020 · 3 comments

Comments

@throw1008a
Copy link

Currently, after enter the SSH password (which is not displayed on the screen), the OTP Token Code prompt is output, and then as one types in the six digits they are printed on the display.

I know that theoretically this should not matter, because that's the entire point of 2FA, but sometimes auditors do not care about "theory".

I would like an option added to the PAM module to control echoing; the default can remain the same if that's easier. So the proposal is to add an "echo" option that takes one of the following parameters:

  • echo=yes : same as now; leave as default?
  • =no : disables any output, like OpenSSH password prompt
  • =hide : displays an asterisk ('*') for each digit
@cron2
Copy link

cron2 commented Apr 20, 2020

what you are looking for is called "hide_otp_input" (option to pam_linotp.so in the pam config). If set, it will instruct OpenSSH to not echo password prompts.

(The echoing is not done by the PAM module itself but by OpenSSH, depending on PAM flags passed "up the stack")

@throw1008a
Copy link
Author

Thanks.

This options is "documented" in the comments of src/pam_linotp.c: perhaps mentioning it in the README or something would be more helpful.

@cron2
Copy link

cron2 commented Apr 20, 2020

I agree. Having the PAM options documented in a more easy-to-find way would be good.

(I am not one of the authors and do not have write access to the repo... I just contributed before, waiting for PR#6 to be merged, since about two years. Seems this project is fairly dead... someone should fork and revive it)

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

No branches or pull requests

2 participants