[python-committers] SSH keys and Keychain
Vinay Sajip
vinay_sajip at yahoo.co.uk
Thu Mar 4 15:16:54 CET 2010
More information about the python-committers mailing list
Thu Mar 4 15:16:54 CET 2010
- Previous message: [python-committers] SSH keys and Keychain
- Next message: [python-committers] SSH keys and Keychain
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jesus Cea <jcea <at> jcea.es> writes: > Do you have access to any other machine vía SSH?. I would try to > generate a new SSH key in Ubuntu. If that solves the issue connecting to > ther machines, I would ask python commint gatekeeper to change your SSH > commit key. Do the test against a machine you can update new SSH keys to. Well, I could use the vinay at eta-jaunty key which I generated on the machine for access to Launchpad. I was hoping to avoid having to change the key (unless they can add the key rather than replacing the old one - I may still need to access the repo from my Windows environments). > PS: Just for trying, check if your SSH key has \013 inside (Carriage > Return). If it does, *DO A COPY* and delete those special chars, just > for testing. I thought of EOLs and checked - '\r' in open('id_rsa', 'rb').read() => False :-) Regards, Vinay Sajip
- Previous message: [python-committers] SSH keys and Keychain
- Next message: [python-committers] SSH keys and Keychain
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list