I hope it will be pushed upstream, I'm not in a position to do anything
about that though. I've looked for a way to modify the bug to indicate
that there are security implications to it, but haven't found anything
yet. It would be a shame if you can only state that on logging the bug.
--
You rece
Actually, to correct my previous post, ssh-keygen -R hostname is enough
to allow the v6 key to be added properly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1271183
Title:
ipv6
Thanks for the thorough investigation. Simply removing the IPv4 entry
and connecting with v6 does the trick! And no need to drop interfaces,
just using -4 works for me. It's still a bug though (different behavior
depending on v4/v6), will it be pushed upstream?
--
You received this bug notificati
I've done some investigation into this and I'm not sure that the
description is quite accurate, at least not for my situation anyway.
Having just built a new server and ssh'd into it on a non-standard port
with no problem I've done a bit of playing and found that the problem
seems to present itsel
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/12
