I totally agree on the ssh documentation, it's awful for the most
part.. I've used it for years and am not sure how to do what I talked
about before. And I HAVE read the man pages many times.
Oh and to compile ssh 2.1 with TCP_WRAPPER support do this:
./configure --with-libwrap
And you can add in /etc/hosts.allow or /etc/hosts.deny
sshd2: whatever.ip
sshd2fwd-X11: whatever.ip
of course replacing "whatever.ip" with the IP you want to allow/deny
Matt
On Tue, May 30, 2000 at 02:29:52PM -0500, Alan Mead wrote:
> At 02:17 PM 5/30/00 , [EMAIL PROTECTED] wrote:
>
> >This brings up a question I've always wondered but never asked, how does
> >ssh work with .rhosts like functionality? For example, rsh lets you
>
> I had assumed it used the .rhosts authentication means. I find that
> documentation of ssh is pretty poor for a psuedo- (soon-to-be?)
> standard. Or I'm just hopelessly dull. Like where is it documented how to
> use tcp_wrappers to limit/allow ssh? (Or is this a problem with
> tcp_wrappers docs?).
>
> Anyway, Carey Cox nailed it when he mentioned permissions. When I changed
> them to 600 it worked. /etc/hosts.equiv did not need to be modified.
>
> -Alan
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
>
--
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
