-
Notifications
You must be signed in to change notification settings - Fork 51
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
Challenge exposed in process list #44
Labels
Comments
BTW, this code is somewhat similar to cornelinux/yubikey-luks, and thus has this same issue. |
@HacKanCuBa great find! I'll look into it. |
@HacKanCuBa This should be fixed in 6aa15b9 . Thank you again for reporting this. |
Awesome! I checked the commit and seems fine. Thank you! |
Nice report! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello there! I was checking your scripts and I noticed that you pass the password to the
ykchalresp
bin as part of its command line, thus exposing it to the system:yubikey-full-disk-encryption/src/ykfde-enroll
Line 149 in 0e1e58b
If you run
top
orhtop
you will see the password shows up there. The same happens in the initram script, but on that scenario is not so dangerous. However, on the already booted up scenario, having the password shown as part of the command is VERY dangerous.I haven't used
ykchalresp
but a better approach would be to pass the password like:printf "%s" "$P1" | ykchalresp -2 -
or something like that (we need to test this).The text was updated successfully, but these errors were encountered: