Bazaar

ssh usernames specified in .ssh/config are not honoured for bzr+ssh connections

Bug #367726 reported by Michael Hudson-Doyle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
Critical
Vincent Ladeuil
Bazaar 1.15rc1

Bug Description

Hacking a bit suggests that ssh is being launched like this:

['ssh', '-oForwardX11=no', '-oForwardAgent=no', '-oClearAllForwardings=yes', '-oProtocol=2', '-oNoHostAuthenticationForLocalhost=yes',
'-l', 'mwh', 'bazaar.launchpad.dev', 'bzr', 'serve', '--inet', '--directory=/', '--allow-writes']

I have a ~/.bazaar/authentication.conf but it doesn't specify anything for this host, nor does it specify 'mwh' as a user for the hosts it does specify.

Related branches

lp:~vila/bzr/367726-ssh-default-user (Merged)
lp:~vila/bzr/integration
Vincent Ladeuil: Approve
Diff: 31 lines (+4/-4)
2 files modified
bzrlib/lazy_regex.py (+3/-3)
doc/en/release-notes/bzr-2.7.txt (+1/-1)
Revision history for this message
Robert Collins (lifeless) wrote :

Yup, already tracked to that - see the details in the mailing list thread. (remote.py grew authconf support and that broke stuff).

Changed in bzr:
assignee: nobody → Vincent Ladeuil (vila)
importance: Undecided → Critical
status: New → Confirmed
Revision history for this message
Vincent Ladeuil (vila) wrote :

remote.py got authconf support long ago, what broke stuff is the auth.get_user() defaulting to getpass.getuser().

I missed the behavior change while reviewing Jelmer's patch for bug #256612.

Changed in bzr:
status: Confirmed → In Progress
Vincent Ladeuil (vila)
Changed in bzr:
status: In Progress → Fix Committed
Vincent Ladeuil (vila)
Changed in bzr:
milestone: none → 1.15rc1
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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