bzr unable to contact paramiko ssh agent when run as a different user
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Hello
I was recently using Bazaar, on Windows, and had left the command line on Admin mode. When I ran a bzr pull command, i recieved the following trace:
bzr: ERROR: paramiko.
Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "paramiko\
File "paramiko\
File "paramiko\
SSHException: lost ssh-agent
bzr 2.6b1 on python 2.6.6 (Windows-
arguments: ['C:\\Program Files (x86)\\
plugins: bzrtools[2.5.0], changelog_
explorer[
launchpad[
news_
svn[1.2.2dev], upload[1.2.0dev], xmloutput[0.8.8]
encoding: 'cp1252', fsenc: 'mbcs', lang: None
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at
https:/
including this traceback and a description of the problem.
Again, this only occurs when I am on Admin mode.
tags: | added: check-for-breezy |
I've run into this in the past. It boils down to the fact that paramiko is using a named pipe for communication and doesn't allow another user access. Which is fine, and is probably correct for security purposes. Bazaar should probably be resilient here and just fall back to ssh-without-agent.