Comment 6 for bug 455636

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

anatoly techtonik wrote:
> Even though I am a little bit puzzled how encrypted SSH access can
> produce less overhead than HTTP I won't ask about that, because it
> doesn't solve my problem.

It is more efficient because bzr+ssh protocol supports high-level bzr
operations, whereas http supports only low-level file operations.

> I still can't see why should it ask for my private key of I am
> requesting read-only access for the branch I do not have commit
> privilege anyway.

It asks for your private key because you have told it to use SSH when
doing lp resolution, and SSH always requires authentication. If you
would like to stop bzr from using SSH when you use lp: names, you can
delete the "launchpad_username" setting from bazaar.conf and the
[Launchpad] section from authentication.conf

You can also directly use http access by supplying the full http
location, such as "http://bazaar.launchpad.net/~bzr-pqm/bzr/bzr.dev"
rather than lp:bzr.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrepIQACgkQ0F+nu1YWqI1tgACbBkiLvYYIDbkOPSxvFNsjBrTZ
0A4AniBnXwQkLRX4rlY8Y7gOqvhD37b1
=GOw9
-----END PGP SIGNATURE-----