-
Notifications
You must be signed in to change notification settings - Fork 59
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
How to use with google-authenticator? #124
Comments
I do not think there is an easy way to do what you want with the current design of pdsh. If it is possible, switch to SSH keys. If it is impossible to use SSH keys in this instance, the only other idea I would have would be to create a custom program that implements the askpass protocol, but only asks once per pdsh invocation, returning the same answer on each subsequent run without prompting the user. It might be that you'd have to store the password in pdsh itself (you could implement a pdsh module for this) to make sure different pdsh invocations didn't reuse a password. Even if you did that, it might be prone to error since you do not know how long pdsh is going to take to contact all hosts, and a time-based password could expire in the interim. |
Thanks for the response. In fact, we intend to use SSH keys and TOTP together. I already (very briefly) tried expect + pdsh, no success. Another tool which I tried was cssh. Here, the TOTP part works. However, cssh is not a suitable replacement for pdsh (node count >>100)... |
For times where ssh keys are not allowed, but a password is, I've used the following script to do something like this. It does mean your password is stored in a file for as long as the pdsh is running, but the permissions are set so only you and root can read it, which is sufficient for some people.
|
I want to use pdsh in conjunction with Google Authenticator PAM module. All remote servers have the same TOTP secret. How to pass the TOTP value?
Currently, one askpass window per remote server is opened, which is annoying, if there are many of these.
The text was updated successfully, but these errors were encountered: