unable to connect

strace output attached , username sanitized as "user"

Thank you for taking the time to report this bug and helping to make Ubuntu better.

You seem to be saying that the ssh client on 15.10 cannot read its own key file? I'm using 15.10 and reading my key file fine. If this bug were as simple as you describe then I'd expect thousands of bug reports within days of 15.10's release. Since this isn't the case, it seems likely to me that this is a local configuration issue on your system. If you disagree, then please could you provide steps to reproduce the system on a fresh Ubuntu system?

So since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

As a canonical employee I find your response rude and insulting if I was a
regular customer (i am in this case) i would feel like that too. I never
said it was all 15.10 systems, I have other 15.10 that did work.

The bug was reported accurate and due to some debugging i did find the
issue is network related as that host did have another managed switch in
its path which evidently is the cause. Moving the 15.10 node to the same
switch as the host node suceeded.I then went on travel and was unable to
update the bug. Ill take responsibility for that.

The errors were captured as output, i was not denied a connection it just
hangs, i sent an strace because i was asked in. IRC canonical channell.

So bug was reported properly, however i do think the error itself does not
accurately reflect the real problem.

If you prefer call me or ping on irc.

Doug

On Jan 20, 2016 5:41 AM, "Robie Basak" <email address hidden> wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> You seem to be saying that the ssh client on 15.10 cannot read its own
> key file? I'm using 15.10 and reading my key file fine. If this bug were
> as simple as you describe then I'd expect thousands of bug reports
> within days of 15.10's release. Since this isn't the case, it seems
> likely to me that this is a local configuration issue on your system. If
> you disagree, then please could you provide steps to reproduce the
> system on a fresh Ubuntu system?
>
> So since it seems likely to me that this is a local configuration
> problem, rather than a bug in Ubuntu, I'm marking this bug as
> Incomplete.
>
> If indeed this is a local configuration problem, you can find pointers
> to get help for this sort of problem here:
> http://www.ubuntu.com/support/community
>
> Or if you believe that this is really a bug, then you may find it
> helpful to read "How to report bugs effectively"
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
> if you would then provide a more complete description of the problem,
> explain why you believe this is a bug in Ubuntu rather than a problem
> specific to your system, and then change the bug status back to New.
>
>
> ** Changed in: openssh (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1534792
>
> Title:
> unable to connect or load identity file
>
> Status in openssh package in Ubuntu:
> Incomplete
>
> Bug description:
> 2 bugs are similar but not the same at
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1522190 and
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1497263
>
>
> host A ubuntu 14.04.3 -- running ssh-server
>
>
> client B and C
>
> client B 14.04.3 can connect no problem with ssh keys only to host A
> (to me this means openssh-server is fine on Host A)
>
>
> Client C 15.10 cannot ssh to host A, openssh cannot or refuses to
> load identity files; output of ssh -vvv below
>
> $ ssh ubuntu@172.27.20.1 -vv
> OpenSSH_6.9p1 Ubuntu-2, OpenSSL 1.0.2d 9 Jul 2015
> debug1: Reading configuration d...

The key_load_public bits are a red herring; it loads id_rsa(.pub) successfully (you can tell because it says "type 1", not "type -1"), and the immediately-subsequent error pertains to id_rsa-cert(.pub) instead. So it's successfully loaded the available identity file.

I think the next steps here should have been:

 * increase debugging to -vvv rather than just -vv (no point in messing about, might as well have the maximum debugging level)
 * see if there's any useful logging at the server end if you have root access to it, probably in /var/log/auth.log

However, it seems that the network fix was sufficient? I would say that a hang is a fairly typical response to a misconfigured network. ssh's debugging output is primarily intended for developers, and I don't think we (or upstream) would generally consider it a bug that it may require reading the source code to determine what it means.

Thanks Colin and that is a response that makes sense. I sent the stack
trace because i was asked to, i want asked for a vvv.
On Jan 20, 2016 6:20 AM, "Colin Watson" <email address hidden> wrote:

> The key_load_public bits are a red herring; it loads id_rsa(.pub)
> successfully (you can tell because it says "type 1", not "type -1"), and
> the immediately-subsequent error pertains to id_rsa-cert(.pub) instead.
> So it's successfully loaded the available identity file.
>
> I think the next steps here should have been:
>
> * increase debugging to -vvv rather than just -vv (no point in messing
> about, might as well have the maximum debugging level)
> * see if there's any useful logging at the server end if you have root
> access to it, probably in /var/log/auth.log
>
> However, it seems that the network fix was sufficient? I would say that
> a hang is a fairly typical response to a misconfigured network. ssh's
> debugging output is primarily intended for developers, and I don't think
> we (or upstream) would generally consider it a bug that it may require
> reading the source code to determine what it means.
>
> ** Summary changed:
>
> - unable to connect or load identity file
> + unable to connect
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1534792
>
> Title:
> unable to connect
>
> Status in openssh package in Ubuntu:
> Incomplete
>
> Bug description:
> 2 bugs are similar but not the same at
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1522190 and
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1497263
>
>
> host A ubuntu 14.04.3 -- running ssh-server
>
>
> client B and C
>
> client B 14.04.3 can connect no problem with ssh keys only to host A
> (to me this means openssh-server is fine on Host A)
>
>
> Client C 15.10 cannot ssh to host A, openssh cannot or refuses to
> load identity files; output of ssh -vvv below
>
> $ ssh ubuntu@172.27.20.1 -vv
> OpenSSH_6.9p1 Ubuntu-2, OpenSSL 1.0.2d 9 Jul 2015
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: Applying options for *
> debug2: ssh_connect: needpriv 0
> debug1: Connecting to 172.27.20.1 [172.27.20.1] port 22.
> debug1: Connection established.
> debug1: identity file /home/dsikora/.ssh/id_rsa type 1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/dsikora/.ssh/id_rsa-cert type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/dsikora/.ssh/id_dsa type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/dsikora/.ssh/id_dsa-cert type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/dsikora/.ssh/id_ecdsa type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/dsikora/.ssh/id_ecdsa-cert type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/dsikora/.ssh/id_ed25519 type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/dsikora...

[Expired for openssh (Ubuntu) because there has been no activity for 60 days.]