bzr push via sftp without username crashes on win32

Bug #139031 reported by Jonathan Roes
2
Affects Status Importance Assigned to Milestone
Bazaar
New
Undecided
Unassigned
paramiko
Invalid
Undecided
Unassigned

Bug Description

On Win32, if I bzr push without a username using the SFTP protocol, I get the following message:

D:\src\ds\firegame>bzr push sftp://jroes.net/test
bzr: ERROR: paramiko.SFTPError: Garbage packet received

Traceback (most recent call last):
  File "bzrlib\commands.pyc", line 729, in run_bzr_catch_errors
  File "bzrlib\commands.pyc", line 691, in run_bzr
  File "bzrlib\commands.pyc", line 389, in run_argv_aliases
  File "bzrlib\builtins.pyc", line 702, in run
  File "bzrlib\transport\__init__.pyc", line 1131, in get_transport
  File "bzrlib\transport\__init__.pyc", line 1189, in _try_transport_factories
  File "bzrlib\transport\sftp.pyc", line 224, in __init__
  File "bzrlib\transport\sftp.pyc", line 841, in _sftp_connect
  File "bzrlib\transport\sftp.pyc", line 1220, in _sftp_connect
  File "bzrlib\transport\sftp.pyc", line 1226, in _sftp_connect_uncached
  File "bzrlib\transport\ssh.pyc", line 343, in connect_sftp
  File "paramiko\sftp_client.pyc", line 87, in __init__
  File "paramiko\sftp.pyc", line 108, in _send_version
  File "paramiko\sftp.pyc", line 183, in _read_packet
SFTPError: Garbage packet received

bzr 0.18.0 on python 2.5.0.final.0 (win32)
arguments: ['bzr', 'push', 'sftp://jroes.net/test']

** please send this report to <email address hidden>

D:\src\ds\firegame>Access denied
Access denied
Access denied
Access denied
Access denied
FATAL ERROR: Server sent disconnect message
type 2 (protocol error):
"Too many authentication failures for "

Let me know if there is any other information I can provide to help repro this. I'm guessing this is actually an upstream bug in paramiko, but I'm not sure myself.

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 139031] bzr push via sftp without username crashes on win32

Jonathan Roes пишет:
> Let me know if there is any other information I can provide to help
> repro this. I'm guessing this is actually an upstream bug in paramiko,
> but I'm not sure myself.

Can you show output of `bzr --version`?
Also I'd like to know is you're using plink/putty or paramiko only?
Can you install 'depends' plugin and show output of `bzr depends`
command?

Revision history for this message
Alexander Belchenko (bialix) wrote :

OK, I'm able to reproduce this error when I put plink in the $PATH.
I believe it's the same error as bug #107593.

Revision history for this message
Alexander Belchenko (bialix) wrote :

I'm sure it's not paramiko bug, but Bazaar+plink specific.

Changed in paramiko:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.