Sadegh Ismael Nattaj wrote:
> Hi all,
>
> I am working with a clustered software that needs to rsh as "root" into
> every nodes of cluster (before advising on ssh or something else, I must
> say that all machines are in an isolated network and there is no
> security risk at all).
>
> I added "mac
* Victory ([EMAIL PROTECTED]) [030908 14:03]:
> I know that BUT one of the Old install program using rsh-server
> and the programmer refused to change it. Sorry
>
> BTW . I put entry in to /etc/host.allow ALL: ALL: ALLOW
> but when i try "rlogin temp1 -l root" it still won't let me in.
> OR "rsh
ck with Permission denied.
Regards,
Victor,
- Original Message -
From: "Stefan Waidele jun." <[EMAIL PROTECTED]>
To: "Victory" <[EMAIL PROTECTED]>
Cc: "Debian-User" <[EMAIL PROTECTED]>
Sent: Monday, September 08, 2003 3:26 PM
Subject: Re: rsh-serv
"Victory" <[EMAIL PROTECTED]> writes:
> I just installed rsh-server and don't know how to set it up so that
> I can do "rlogin temp1 -l root" from remote machine.
You almost certainly don't want to, unless you *want* your root
password passing across the network in the clear. Better:
(1) Remov
Victory wrote:
[...]
I just installed rsh-server and don't know how to set it up so that
I can do "rlogin temp1 -l root" from remote machine.
rsh (along with the other r-commands) should not be used for security
reasons. (Except rsync over a ssh-connection)
Why don't you use ssh?.
If you cannot
* FU ([EMAIL PROTECTED]) [020228 12:10]:
> Setting up exim (3.33-1.1) ...
> Error: system's FQDN hostname
> (pa1_2.mildred.cpsc.ucalgary.ca) doesn't
> match
> RFC1035 syntax; cannot configure the mail system.
> dpkg: error processing exim (--configure):
> subprocess post-installation script retur
[EMAIL PROTECTED] writes:
> While I was installing the rsh-server, I encountered
> the following problems.
> Setting up exim (3.33-1.1) ...
> Error: system's FQDN hostname (pa1_2.mildred.cpsc.ucalgary.ca) doesn't match
> RFC1035 syntax; cannot configure the mail system.
> dpkg: error processing
On Sun, Oct 21, 2001 at 01:20:28PM +0200, Raffaele Sandrini wrote:
> I'd like to use rsh. Yes my network is 100% secure cause its not
> connected to anything insecure.
> But i think there is no rsh in Debian. If i type "man rsh" i get the
> manpage of ssh. If i execute "rsh" i get ssh...
Sounds li
> "Paul" == Paul McAvoy <[EMAIL PROTECTED]> writes:
Paul> Don't know too much about rsh, but you would probably be
Paul> better off with SSH as it is (more) secure and offers the
Paul> same functionality.
... or the Kerberos version of rsh (eg in heimdal-clients in potato) ...
(
"Christopher S. Swingley" wrote:
>
> > rsh a redhat linux server from my debian server...and i have no idea how to
> > get it to work.
>
> To do this you need four things on your Red Hat system (or any UNIX for
> that matter):
>
> * The user's home directory on the remote machine must have a
Don't know too much about rsh, but you would probably be better off with SSH
as it is (more) secure and offers the same functionality.
- Paul
On Thu, Jan 13, 2000 at 04:07:10PM +1300, [EMAIL PROTECTED] wrote:
> hi
>
> i asked this question before but no one answered... not too sure why as it
> i
> rsh a redhat linux server from my debian server...and i have no idea how to
> get it to work.
To do this you need four things on your Red Hat system (or any UNIX for
that matter):
* The user's home directory on the remote machine must have a
~/.rhosts file with the address of the l
As an afterthought: don't forget to use the FQDN in your .rhosts (it
didn't work without it in my setup)
Ph. A.
Philippe Andersson wrote:
>
> Hello,
>
> Edit /etc/inetd.conf, look for the line that invoque rshd and modify it
> as follows:
>
> shell stream tcp nowait root/usr/sbin/
Hello,
Edit /etc/inetd.conf, look for the line that invoque rshd and modify it
as follows:
shell stream tcp nowait root/usr/sbin/tcpd in.rshd -hlL
^^
This disables the use of ~/.rhosts *except for root* (-l) and allows
On Wed, 5 Nov 1997, m* wrote:
> Syd Alsobrook wrote:
> >
> > Help,
> > What do I need to do to get rsh to work without passwords on a
> > closed network?
>
> see "man rhosts".
>
> m*
also see ssh - just because your network is 'closed' is no reason to
take risksone day your network
Syd Alsobrook wrote:
>
> Help,
> What do I need to do to get rsh to work without passwords on a
> closed network?
see "man rhosts".
m*
--
"The Shining One"
--
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PR
M. Hegbloom" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: debian-user@lists.debian.org
> Subject: Re: rsh authentication ...
>
> >>>>> "Richard" == Richard G Roberto <[EMAIL PROTECTED]> writes:
>
> Richard> I have (after some fr
> "Richard" == Richard G Roberto <[EMAIL PROTECTED]> writes:
Richard> I have (after some frustration with explicit entries, as
Richard> well as ALL: ALL) removed hosts.deny and hosts.allow on
Richard> both machines.
The solution is to ditch `inetd' and tcpwrappers, and install
`
Quoting Karl M. Hegbloom ([EMAIL PROTECTED]):
> On a related note, is there any way to make rdist use ssh?
man rdist, look at the option for rsh path; replace the path
to rsh with the path to ssh--they're functionally equivalent
(although you might want to add parameters for compression,
etc.)
-
On a related note, is there any way to make rdist use ssh?
--
Karl M. Hegbloom <[EMAIL PROTECTED]>
http://www.inetarena.com/~karlheg
Portland, OR USA
Debian GNU 1.3 Linux 2.1.36 AMD K5 PR-133
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trou
Christoph Lameter <[EMAIL PROTECTED]> writes:
> You can simply decrypt the private key and then no passwords are required.
I couldn't figure out how to do that, but isn't that a little unsafe?
After some more investigation, it looks like the way ssh wants you to
do this is with ssh-agent and ssh
On 9 Jun 1997, Rob Browning wrote:
>Christoph Lameter <[EMAIL PROTECTED]> writes:
>
>> You need to run keygen and then put your public key on the host you
>> want to reach. Get rid of the .shosts file and the pain of
>> passwords is gone. You can put your private key on any account you
>> want to
Christoph Lameter <[EMAIL PROTECTED]> writes:
> You need to run keygen and then put your public key on the host you
> want to reach. Get rid of the .shosts file and the pain of
> passwords is gone. You can put your private key on any account you
> want to use to connect from.
I had tried that, b
Use RSA User authentication instead of RSA Host authentication.
You need to run keygen and then put your public key on the host you want to
reach.
Get rid of the .shosts file and the pain of passwords is gone. You can put your
private
key on any account you want to use to connect from.
In artic
: Hi,
:
: I don't have access to a Linux machine from where I work so I can't
: check on this advice, but see if there is a man page for
: "hosts.equiv". On Solaris machines, /etc/hosts.equiv is the other
^^^
: piece that controls remote access via rsh, rlogin, etc.
:
: Good luck,
: R
"Eloy A. Paris" <[EMAIL PROTECTED]> writes:
> Can you send the .rhosts in both hosts to the list?
>
> As I remember it, the rshd is very picky about the way you specify
> the hpost name in .rhosts. I think is has to be the same string
> the gethostbyaddr() (the resolver) returns.
Also, check /et
Can you send the .rhosts in both hosts to the list?
As I remember it, the rshd is very picky about the way you specify
the hpost name in .rhosts. I think is has to be the same string
the gethostbyaddr() (the resolver) returns.
I hope this helps.
E.-
>
> Hello,
>
> does someone know any pecu
On Apr 2, Nathan O. Siemers wrote
>Hello all:
>
>I'm having trouble telling linux to allow rsh's to work as root from
>remote machines. Root's .rhosts, /etc/hosts.equiv, and
>/etc/hosts.allow don't seem to affect the "permission denied"
>result. Solution?
Change the command in.rshd in your /etc/in
Andrea Arcangeli wrote:
>
> I want to use rsh, but I found:
>
> $ rsh localhost ls
> Permission denied.
>
> What I must change (for example in hosts.allow) to run it?
>
Hi Andrea,
you have to create the file .rhosts in the users home directory on the
remote host (with permission rw-). Thi
> I want to use rsh, but I found:
>
> $ rsh localhost ls
> Permission denied.
>
> What I must change (for example in hosts.allow) to run it?
Add your hostname to the file /etc/hosts.equiv and this will work.
--
Michel Beland [EMAIL PROTECTED]
professionnel de recherchetel: (
I think this is what Andrea was trying to do:
#rsh localhost ls
permission denied
#echo "localhost hessu" >> .rhosts
#rsh localhost ls
Mail
News
bin
[rest of the listing cut]
Andrea, you need at least a 'hostname user' line in $HOME/.rhosts on the
computer you want to remotely log in to. See rlo
You don't need the 'ls' at the end for rsh. I don't know what options
you were trying to obtain from using it, but I didn't find anything about
it in the man page. I tried the same thing you did and received the same
results. However, you can see if you omit the 'ls' it works just fine.
<1
32 matches
Mail list logo
