Mailing List Archive

[Bug 3187] 'unknown error' reported on local network if internet not available
https://bugzilla.mindrot.org/show_bug.cgi?id=3187

--- Comment #3 from Damien Miller <djm@mindrot.org> ---
I can't replicate this with OpenSSH 8.2 or HEAD. It looks like you have
some configuration in ~/ssh/config that might be relevant - what is in
there?

--
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 3187] 'unknown error' reported on local network if internet not available [ In reply to ]
https://bugzilla.mindrot.org/show_bug.cgi?id=3187

--- Comment #4 from Craig James <cjames@emolecules.com> ---
The relevant entry from my ~/.ssh/config file is:

Host v-application.emolecules.com
User emi
IdentityFile ~/.ssh/vagrant

The file ~/.ssh/vagrant is an RSA private key file.

The host "v-application.emolecules.com" is defined in my Macintosh
/etc/hosts file as:

$ grep v-application.emolecules.com /etc/hosts
192.168.77.6 v-application.emolecules.com

Hope that helps.

--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 3187] 'unknown error' reported on local network if internet not available [ In reply to ]
https://bugzilla.mindrot.org/show_bug.cgi?id=3187

--- Comment #5 from Damien Miller <djm@mindrot.org> ---
I can't replicate this using OpenSSH 8.3p1 on my available Mac
hardware:

Darwin djm-mba 19.5.0 Darwin Kernel Version 19.5.0: Tue May 26 20:41:44
PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64 x86_64

However I don't see anything that could have caused this bug to be
fixed between 8.1 and 8.3p1. Are you using the OpenSSH that Apple ships
or one you've compiled yourself? (manually or via macports/brew etc)

If you are using the Apple version, I suggest trying to reproduce the
problem using a locally built OpenSSH to exclude any modifications they
may have made.

Otherwise, I recommend capturing a syscall trace from ssh to see where
it is going wrong. See
https://stackoverflow.com/questions/31045575/how-to-trace-system-calls-of-a-program-in-mac-os-x
for some hints here

--
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs