Please confirm your message

[Daniel Cousens]

Hi (again),

Not sure if it is too late now, so I apologize in advance, but I just had
someone on IRC (finally) advise me of the following bug report:

https://bugzilla.mindrot.org/show_bug.cgi?id=1290

Which is exactly my problem (which I just reported to you via email).
It took me too long to figure out since there were no problems reported by
sshd (-ddddddd) up until it received an actual connection.
The loading sequence for sshd had reported key loading and config loading
as all completing successfully.

Maybe just some kind of warning could help to show this is indeed what is
happening would be awesome. Ah well.

Kind Regards,

On Mon, Jun 10, 2013 at 9:03 PM, Daniel Cousens <daniel210x at gmail.com>wrote:

>
>
> On Mon, Jun 10, 2013 at 9:02 PM, TMDA daemon <tmda at mindrot.org> wrote:
>
>> This message was created automatically by mail delivery software (TMDA).
>>
>> Your message attached below is being held because the address
>> <daniel210x at gmail.com> has not been verified.
>>
>> To release your message for delivery, please send an empty message
>> to the following address, or use your mailer's "Reply" feature.
>>
>>    tmda+confirm+1370862161.22465.6cc559 at mindrot.org
>>
>> This confirmation verifies that your message is legitimate and not
>> junk-mail. You should only have to confirm your address once.
>>
>> If you do not respond to this confirmation request within 14 days,
>> your message will not be delivered.
>>
>>
>> ---------- Forwarded message ----------
>> From: Daniel Cousens <daniel210x at gmail.com>
>> To: openssh-unix-dev at mindrot.org
>> Cc:
>> Date: Mon, 10 Jun 2013 21:02:13 +1000
>> Subject: SSHD relative pathing problem
>> Hi :)
>>
>> I hope this isn't just a problem in my understanding, but anyway.
>>
>> I am using `OpenSSH_6.2, OpenSSL 1.0.1e 11 Feb 2013` on an Arch Linux
>> system, and I got caught out on this error for several days, and I'm not
>> sure if its a bug for you guys or what.
>>
>> Anyway, what I noticed, was that when I specifyied a custom HostKey in
>> the host file or by relative path, that is:
>>
>> `sshd -Dd -f myconfig`
>> or
>> `sshd -Dd -h myhostkey`
>>
>> where myconfig is just:
>> ```myconfig
>> HostKey myhostkey
>> ```
>>
>> It would load the key correctly, no complaints, but when attempted to
>> connect to the server via `ssh 127.0.0.1` (or by any other means), it would
>> immediately have an `ssh_exchange_identification: read: Connection reset by
>> peer` error; and sshd would exit.
>> Changing either of the above lines to:
>>
>> `sshd -Dd -f /home/foo/bar/myconfig`
>> or
>> `sshd -Dd -h /home/foo/bar/myhostkey`
>>
>> Resolved this issue, resulting in regular sshd behaviour.
>>
>> As I said, this may actually be a problem further downstream (that is,
>> the Arch packagers), but I figured I'd ask here first. If that is the case,
>> I'm sorry for taking up your time.
>>
>> Kind Regards,
>>
>> Daniel Cousens
>>
>
>