Thanks Sebastien for re-assigning.
And thank you Nathan, for taking the time to report this bug and helping
to make Ubuntu better. I appreciate the quality of this bug report and
I'm sure it'll be helpful to others experiencing the same issue.
I agree to the triage made so far, but in that case that is not more or less
than an openssh upstream feature request.
You should check if that was not resolved in the meantime. Bionic is on
1:7.6p1-4ubuntu0.3 while Current Disco Development release 19.04 is already on
upstreams latest 1:7.9p1-9.
Once confirmed to be upstream bug (by checking it exists in the latest
version), the best route to getting it fixed in Ubuntu in this case
would be to file an upstream bug if you're able to do that. Otherwise,
I'm not sure what we can do directly in Ubuntu to fix the problem.
OTOH it might also be worth to check if there is some key attribute that makes
it work again.
Here my current list:
$ ssh-add -l
4096 SHA256:... /home/paelzer/.ssh/id_rsa (RSA)
2048 SHA256:... ubuntu@cpaelzer-bastion (RSA)
4096 SHA256:... paelzer@lap (RSA)
4096 SHA256:... paelzer@swarm.naarz... (RSA)
You see all but the first one have the comment listed - yet I fail to see the
difference as they keys look the same and id_rsa{.pub} has the same style of
mentioning an id like the others that work. Never the less maybe a path for you
to evaluate (or clarify with upstream).
If you do end up filing an upstream bug, please link to it from (or at
least mention it) here. Thanks!
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758924
Title:
'ssh-add -l' doesn't like the key email/comment (unlike gnome-
keyring's agent used to)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1758924/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
