"no such identity"
Andreas M. Kirchwitz
amk at krell.zikzak.de
Wed Apr 3 12:37:17 EST 2013
Dag-Erling Smørgrav <des at des.no> wrote:
>> Wouldn't it make sense to release a 6.2p2?
> For a (mostly) cosmetic issue?
Technically, this issue maybe is cosmetic (however, the unexpected
warning could break scripts, but that's a different story). I spent
some time to understand what this message was all about because it
didn't make much sense to me at first. Maybe the server has been
hacked or something has been compromised? Who knows these days?
Then I found two workarounds, either create all possible keys even
if you don't need them at all, or specify IdentityFile in ~/.ssh/config
for those keys that actually exist. Well, that works for me, but that's
hard to explain to regular users on my machines. ;-)
Alternatively, patch the source code and remove the message.
But is it a good thing to remove warning messages from an
application that is about security?
Maybe some admins didn't even install OpenSSH 6.2p1 because they
were wondering if more things were broken than just that.
Well, maybe it could make sense to think about a 6.2p2 release.
On the other hand, if developers already know there will be 6.3
real soon anyway, then it's better to wait for that.
More information about the openssh-unix-dev