-
Notifications
You must be signed in to change notification settings - Fork 1.9k
env.gateway doesn't honor the content of env.passwords #884
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
Comments
Thanks for the report, I acknowledge the issue. Seems easy to fix by switching get/set_password to take explicit user/host/port arguments instead of relying on shared state. Testing that change now. |
Fixed in d41e39b (forgot the pound sign in commit msg, oops). Please reopen if that didn't do it - I don't have any good password-friendly gateways to test on right now. Key-only auth for life! ;) |
hey man, this fails again.Fabric 1.10.2 my setting is that from local -> proxy -> host fabfile.py
run |
Hi, @yupbank, @bitprophet In my case this will fix
|
Port seems to be needed after fix d41e39b. env.passwords = { That works for me. It wouldn't work without the port. Cheers |
How can I use .pem file instead of password in above case? |
The fabric.network.connect(user, host, port) function uses the function fabric.auth.get_password() to retrieve the password, and that function always return the password related to the current env.host_string.
This approach works with only one one level of connections, but when you use a env.gateway setting, the first connect host parameter will match the env.host_string content, so it will retrieve the wrong password.
Example:
This will end to a try to log on 'gwuser@gwhost' using 'pass' as password instead of 'gwpass'.
The text was updated successfully, but these errors were encountered: