bzr unable to ask password for access over bzr+ssh:// or sftp:// when plink.exe used as SSH client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Low
|
Dmitry Vasiliev |
Bug Description
As a rule I use SSH authentication via Open SSH key. I use pageant.exe +plink.exe on win32.
Today I forgot to load my key to pageant and try to push to bzr+ssh:// location.
bzr unable to ask my password. On client side I use bzr.exe 0.15 @ win32, on server side I have bzr 0.14 installed @ FreeBSD.
C:\Temp\
Using keyboard-
bzr: ERROR: Generic bzr smart protocol error: unexpected smart server error: ('Password:\r',)
Access denied
Using keyboard-
Access denied
Using keyboard-
Access denied
Using keyboard-
Access denied
Using keyboard-
Access denied
Using keyboard-
Access denied
Using keyboard-
FATAL ERROR: Server sent disconnect message
type 2 (SSH_DISCONNECT
"Too many authentication failures for bialix"
Here is traceback from .bzr.log:
bzr arguments: [u'--no-plugins', u'push', u'bzr+ssh:
encoding stdout as sys.stdout encoding 'cp866'
got branch format Bazaar-NG branch format 5
ssh implementation is Putty's plink.
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\
SmartProtocolError: Generic bzr smart protocol error: unexpected smart server error: ('Password:\r',)
return code 3
Without plink.exe (with paramiko) all works as expected.
description: | updated |
description: | updated |
Changed in bzr: | |
milestone: | 0.9a → 1.3 |
On 4/19/07, Alexander Belchenko <email address hidden> wrote:
> Public bug reported:
>
> As a rule I use SSH authentication via Open SSH key. I use pageant.exe +plink.exe on win32.
> Today I forgot to load my key to pageant and try to push to bzr+ssh:// location.
> bzr unable to ask my password. On client side I use bzr.exe 0.15 @ win32, on server side I have bzr 0.14 installed @ FreeBSD.
This looks like perhaps the Windows ssh client is trying to read the
passphrase from stdin (connected to bzr) rather than from the tty.
--
Martin