From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: HEADSUP: OpenSSH 6.7 drops tcpwrapper support
Date: Mon, 18 Aug 2014 11:53:00 -0000 [thread overview]
Message-ID: <20140818115352.GC2280@calimero.vinschen.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
Hi folks,
Just a HEADSUP to all of you actively using the tcp_wrappers/libwrap
functionality in sshd:
Starting with the next OpenSSH version 6.7, which will be released soon,
upstream removed support for tcp_wrappers/libwrap from the sources.
While that's bad from a compatibility point of view, the upstream
developers are adamant about this change for security reasons.
So, if you configured /etc/hosts.allow and/or /etc/hosts.deny files in
your Cygwin installation to block certain connections to your sshd
service, you will have to find other means to do that ASAP:
- Utilize the sshd_config Match rule.
- Utilize your firewall.
Hope that helps,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-08-18 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 11:53 Corinna Vinschen [this message]
2014-08-19 18:23 ` D. Boland
2014-08-19 19:10 ` Corinna Vinschen
2014-08-19 19:05 ` Andrey Repin
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=20140818115352.GC2280@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/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).