From: Andrey Repin <anrdaemon@yandex.ru>
To: Zdzislaw Meglicki <zdzisiekm@sbcglobal.net>, cygwin@cygwin.com
Subject: Re: Sshd behaving strangely...
Date: Sun, 06 Sep 2015 21:50:00 -0000 [thread overview]
Message-ID: <741476330.20150907004005@yandex.ru> (raw)
In-Reply-To: <1536135967.1623711.1441554363665.JavaMail.yahoo@mail.yahoo.com>
Greetings, Zdzislaw Meglicki!
Please teach your mail agent to not break threading. Thank you in advance.
>> OpenSSH 7.0 (and thus the current 7.1) deprecated a couple
>> of old and insecure ciphers. Probably that's the reason.
> Well, what I mean is that it is strange that sshd-7.1p1-1 accepts
> a connection from ssh-3.9p1, upon announcing that the "key type ssh-dss
> [is] not in PubkeyAcceptedKeyTypes," and lets the user in having accepted
> the password,
Likely explanation is that you've tried to connect using private DSA key,
which server rejected and subsequently asked for a password.
> yet rejects connection from ssh-6.8p1-1 not even allowing
> for the presentation of a password, and claims that "seteuid operation
> [is] not permitted."
This is a different issue, judging from the error message.
Without more data from both sides it is impossible to tell for certain, whats
going on.
A verbose log of the same connection from both server and client may help.
> Why was the operation permitted when the key was not in
> PubkeyAcceptedKeyTypes?
> This seems to me to be a security bug.
More like you are not telling us a whole story.
> And I still wonder how to configure sshd to allow normal connections
> with accepted key types, any documentation out there that would help?
Sorry, what? It do work like that out of the box.
--
With best regards,
Andrey Repin
Monday, September 7, 2015 00:33:31
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-09-06 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 15:46 Zdzislaw Meglicki
2015-09-06 21:50 ` Andrey Repin [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-07 12:46 Zdzislaw Meglicki
2015-09-05 21:03 Zdzislaw Meglicki
2015-09-06 12:00 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=741476330.20150907004005@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=zdzisiekm@sbcglobal.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).