From: Tom Syroid <tom@syroidmanor.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] OpenSSH/libwrap error RESOLVED
Date: Mon, 21 Oct 2002 17:15:37 -0600 [thread overview]
Message-ID: <18670000.1035242137@phaedrus.syroidmanor.com> (raw)
In-Reply-To: <200210211522.45911.marcc@whitepj.com>
OK, thanks to everyone -- all problems solved. Just completed a full
"unstable" tree update, and everything's working as well as the "stable"
tree I started with this morning. Nice work, Gents.
Turns out I did have tcp-wrappers installed, but it would appear it was yet
another casualty of the glibc-2.3.1 update this morning...
In summary:
- openssh 3.5 fails during config; looking for "libwrap"
- libwrap was on my system but broken, likely by my earlier glibc update
- re-emerging tcp-wrappers fixed the problem
This doesn't address the problem of SSH demanding tcp-wrappers, but at this
point in time this is a minor issue... It's Miller Time :=)
Cheers,
/tom
--On Monday, October 21, 2002 15:22:45 -0700 Marc Chabrol
<marcc@whitepj.com> wrote:
> and from /usr/portage/net-misc/openssh/openssh-3.5_p1.ebuild
> it seems this should be necessary only if USE contains tcpd :
>
> DEPEND="${RDEPEND}
> sys-devel/perl
> sys-apps/groff
> tcpd? ( >=sys-apps/tcp-wrappers-7.6 )"
next prev parent reply other threads:[~2002-10-21 23:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 15:34 [gentoo-dev] PAM appears B0rked Tom Syroid
2002-10-21 16:10 ` Stefan Jones
2002-10-21 20:37 ` Matthew J. Turk
2002-10-21 21:49 ` Spider
2002-10-21 22:12 ` Alan
2002-10-21 22:15 ` [gentoo-dev] PAM appears B0rked RESOLVED Tom Syroid
2002-10-21 22:22 ` Marc Chabrol
2002-10-21 22:43 ` Tom Syroid
2002-10-21 23:15 ` Tom Syroid [this message]
2002-10-21 23:27 ` [gentoo-dev] OpenSSH/libwrap error RESOLVED Marc Chabrol
2002-10-26 0:30 ` [gentoo-dev] PAM appears B0rked RESOLVED Martin Schlemmer
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=18670000.1035242137@phaedrus.syroidmanor.com \
--to=tom@syroidmanor.com \
--cc=gentoo-dev@gentoo.org \
/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