Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.networking > #1470

Re: why does rsh -l ignore .rhosts?

From Chris Davies <chris-usenet@roaima.co.uk>
Newsgroups comp.os.linux.networking
Subject Re: why does rsh -l ignore .rhosts?
Date 2012-06-07 10:21 +0100
Organization Roaima. Harrogate, North Yorkshire, UK
Message-ID <0d86a9xl85.ln2@news.roaima.co.uk> (permalink)
References <4fcdf079$0$10739$5b6aafb4@news.zen.co.uk> <ee82a9xj8i.ln2@news.roaima.co.uk> <xn0hz11ic5qaxgw000@news.individual.net>

Show all headers | View raw


Ralph <ralphzodapn@ymeal.com> wrote:
> Well, it [rsh/rlogin] 's less complex, I don't mean less complex to
> use or less complex to learn. I mean less complex functionally, and
> so how it works behind the scenes, the code, is less complex.

> I also like to have some familiarity with the spring from which ssh
> sprung, the void it filled, the problems it solves.

Fair enough. I forget I've been using Unix-type systems since the mid 80s.


> Also, if I read a chapter of a book, and it talks briefly about the
> inetd super server, and rexec rlogin, and rsh and rcp.. How things
> -were done-, then the contents means more to me  having used them.

I still use inetd - it's a great piece of my toolkit. There have
been improvements and tweaks along the way, but it's a really quick
and convenient way to bring up a daemon written in nothing more than
shell script. Here's a trivial that appears to offer an FTP service but
actually doesn't:

    #!/bin/sh
    #
    echo "421-FTP not available here."
    echo "421 See http://www.example.com/no-ftp-here for alternatives"
    exit 0

If you create that as /usr/local/bin/no-ftp and make it executable,
drop the following line into inetd and send it a SIGHUP ("killall -HUP
inetd") you have a new service operational:

    ftp     stream  tcp     nowait  nobody  /usr/local/bin/no-ftp


> While I wouldn't need encryption on a private LAN, and i'm the only
> user on it, I see that rlogin and rsh etc are still functionally a bit
> naturally limited in passwordless logins. If you specify a different
> user, you must enter a password.

Yes. On one's on LAN it's not so much the encryption as the functionality
that wins. And I can use one tool family (ssh) regardless of whether
the target is on my LAN or elsewhere.

Chris

Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

why does rsh -l ignore .rhosts? "Ralph" <ralphzodapn@ymeal.com> - 2012-06-05 11:41 +0000
  Re: why does rsh -l ignore .rhosts? Chris Davies <chris-usenet@roaima.co.uk> - 2012-06-05 21:57 +0100
    Re: why does rsh -l ignore .rhosts? "Ralph" <ralphzodapn@ymeal.com> - 2012-06-06 19:39 +0000
      Re: why does rsh -l ignore .rhosts? Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-06-07 08:03 +0000
      Re: why does rsh -l ignore .rhosts? Chris Davies <chris-usenet@roaima.co.uk> - 2012-06-07 10:21 +0100
  Re: why does rsh -l ignore .rhosts? MJ <me@invalid.org> - 2012-06-17 04:00 +0000

csiph-web