Skip to content

Conversation

dcacklam
Copy link

@dcacklam dcacklam commented Jun 21, 2021

If server-messages were sent back to the client, the 'Otp:' prompt would be overwritten, resulting in no actual request for user action.
This results in:
bash$ sudo -i
[sudo] password for a_unixuser:
e-mail sent successfully

The system would then hang at the end of 'successfully' waiting for unprompted input. If the user does not know to type their OTP, or presses 'enter' to see if the system is hung, auth fails.

This change re-appends said prompt to the end of the challenge message, before it is sent back to PAM.

[sudo] password for a_unixuser:
e-mail sent successfully - OTP:

Closes #2
Closes #3

dcacklam added 2 commits June 21, 2021 12:32
If server-messages were sent back to the client, the 'Otp:' prompt would be overwritten, resulting in no actual request for user action.
This results in:
bash$ sudo -i
[sudo] password for a_unixuser:
e-mail sent successfully

The system would then hang at the end of 'successfully' waiting for unprompted input. If the user does not know to type their OTP, or presses 'enter' to see if the system is hung, auth fails. 

This change re-appends said prompt to the end of the challenge message, before it is sent back to PAM.

[sudo] password for a_unixuser:
e-mail sent successfully - OTP:
Adds the ability to use self-signed certs via a 'nosslcertverify' parameter. 

Default behavior remains 'verify all ssl certificates'.
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

Successfully merging this pull request may close these issues.

nosslverify keyword not working Prompt to enter OTP not displayed when using email authentication

1 participant