After launchpad-login, bzr branch lp: doesn't work without ssh keys

Bug #1049045 reported by Dražen Lučanin
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned

Bug Description

When a user issues launchpad-login to record their launchpad username, doing a bzr branch fails with an error:

    ConnectionReset reading response for 'BzrDir.open_2.1', retrying

This continues until the user registers his public SSH key, which you sometimes don't want for "read-only operations".

Expected behaviour
----------------------------
One of these two:

- allow read-only operations such as `bzr branch` or `bzr pull` without having a registered public key even after launchpad-login has been issued
- inform the user through a more informative message than the above that *he initiated registration and that he has to either finish it by registering his public ssh key or log out to do an anonymous read-only operation* and enable some easier method of erasing the user's cached identity (`bzr launchpad-logout` from Bug #349143)

I think eliminating not-so-informative errors such as this one would aid in pushing bazaar's user friendliness (for which I appreciate it so much already) even further.

Martin Packman (gz)
Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
John A Meinel (jameinel) wrote :

Are you sure this is from 'whoami' and not from 'launchpad-login'? If you do launchpad-login, we expect to be able to use ssh keys. (I believe the launchpad-login process even checks that the user you are logging in as has ssh keys associated with that account.)

If it is just 'bzr whoami' then we probably have a bug that we are registering data somewhere that makes it ok to switch from anonymous http access to authenticated ssh access.

Can you confirm if this is 'launchpad-login' vs 'whoami'?

Revision history for this message
Dražen Lučanin (kermit666) wrote : Re: [Bug 1049045] Re: After whoami, bzr branch doesn't work without complete registration

OK, yes, it's only occurring after I do a `launchpad-login`. Doing a
`whoami` is ok.

Still, I'm behind my original statement - bzr should either throw some more
friendly output with instructions on what to do after a keyless
launchpad-login or just let the anonymous pull/branch/... go through.

On Wed, Sep 12, 2012 at 11:32 AM, John A Meinel <email address hidden>wrote:

> Are you sure this is from 'whoami' and not from 'launchpad-login'? If
> you do launchpad-login, we expect to be able to use ssh keys. (I believe
> the launchpad-login process even checks that the user you are logging in
> as has ssh keys associated with that account.)
>
> If it is just 'bzr whoami' then we probably have a bug that we are
> registering data somewhere that makes it ok to switch from anonymous
> http access to authenticated ssh access.
>
> Can you confirm if this is 'launchpad-login' vs 'whoami'?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1049045
>
> Title:
> After whoami, bzr branch doesn't work without complete registration
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/bzr/+bug/1049045/+subscriptions
>

Martin Packman (gz)
description: updated
summary: - After whoami, bzr branch doesn't work without complete registration
+ After launchpad-login, bzr branch doesn't work without complete
+ registration
John A Meinel (jameinel)
summary: - After launchpad-login, bzr branch doesn't work without complete
- registration
+ After launchpad-login, bzr branch lp: doesn't work without ssh keys
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
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.