Comment 3 for bug 1770305
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Verification completed, I tested this version:
$ dpkg-query -W ssh-import-id
ssh-import-id 5.7-0ubuntu1.1
on my bionic install, I tested importing keys from an non-existing username
$ ssh-import-id mwhudso
2018-05-20 22:17:21,328 ERROR Launchpad user not found. status_code=404 user=mwhudso
and existing
$ ssh-import-id mwhudson
2018-05-20 22:17:24,662 INFO Already authorized ['2048', 'SHA256:
2018-05-20 22:17:24,663 INFO [1] SSH keys [Authorized]
and even set up a container to that thought launchpad.net was served by another container to test the "other status code" code path (complete with self-signed certificate fiddling):
root@mitm-victim:~# ssh-import-id lp:mwhudson
2018-05-20 10:14:06,089 ERROR Requesting Launchpad keys failed. status_code=403 user=mwhudson
And everything behaved as expected.