From: Mills, John T (John.T.Mills@ERAC.COM)
Date: Mon Jan 06 2003 - 15:22:29 EST
Kevin,
Ouch, not what I wanted to hear, but thanks for the info.
I'll do some more checking and forward that up the chain.
Thanks,
John T. Mills
-----Original Message-----
From: Adams Kevin J [mailto:kevin.adams@PHS.COM]
Sent: Monday, January 06, 2003 2:18 PM
To: aix-l@Princeton.EDU
Subject: Re: [aix-l] ssh when rlogin=false
PermitRootLogin does not override AIX rlogin=false, at least in my
experience.
Nor does UseLogin.
You could maybe modify the OpenSSH source.
I use Kerberos telnet/rsh/rlogin from MIT. It does not honor rlogin=false.
I could never get this to work with OpenSSH and rlogin=false.
Kevin Adams
-----Original Message-----
From: Chris Gregors [mailto:Chris.Gregors@TELUS.COM]
Sent: Monday, January 06, 2003 12:08 PM
To: aix-l@Princeton.EDU
Subject: Re: [aix-l] ssh when rlogin=false
Hmmm I always thought that was the solution.
If it is root logins you are trying to stop, then set this in
/etc/sshd_config
PermitRootLogin no
Otherwise, I'm not sure anymore.
-----Original Message-----
From: Mills, John T [mailto:John.T.Mills@ERAC.COM]
Sent: Monday, January 06, 2003 12:52 PM
To: aix-l@Princeton.EDU
Subject: Re: ssh when rlogin=false
Chris,
My daemon starts on demand, so I don't have anything to restart I think.
I tried the change and it is still disallowing login with rlogin=false. Was
this a fix for ssh to honor rlogin or ignore it? I am trying to get ssh to
ignore rlogin=false.
John
-----Original Message-----
From: Chris Gregors [mailto:Chris.Gregors@TELUS.COM]
Sent: Monday, January 06, 2003 1:08 PM
To: aix-l@Princeton.EDU
Subject: Re: [aix-l] ssh when rlogin=false
In /etc/sshd_config set the following entry:
UseLogin yes
And restart sshd. This should cause it to honor rlogin=false.
Chris Gregors
Telus Enterprise Solutions
Email: chris.gregors@telus.com
Phone: (780) 493-2450
Cell: (780) 718-5917
-----Original Message-----
From: Mills, John T [mailto:John.T.Mills@ERAC.COM]
Sent: Monday, January 06, 2003 10:33 AM
To: aix-l@Princeton.EDU
Subject: Re: ssh when rlogin=false
Bill,
I don't have an sshd running. I'm using openssh,
and it starts a sshd when I connect but it doesn't
keep one running in the background. I am just doing
and 'ssh hostname' to test and a 'chuser rlogin=false
uid' to make the change.
When I set rlogin=false I get the standard:
Remote logins are not allowed for this account.
message. With rlogin=true I can ssh with no problems.
John T. Mills
-----Original Message-----
From: Bill Verzal [mailto:Bill_Verzal@BCBSIL.COM]
Sent: Monday, January 06, 2003 11:03 AM
To: aix-l@Princeton.EDU
Subject: Re: [aix-l] ssh when rlogin=false
Curious - did you refresh or stop/start sshd ?
----------------------------------------------------------------------------
----------------------------
Bill Verzal
Technical Consultant
Forbes Technical Consulting
(312) 653-3684
bill_verzal@bcbsil.com
billverzal@imcingular.com (Pager)
888-428-4025 (Pager)
MailStop: 27.202B
"Mills, John
T" To: aix-l@Princeton.EDU
<John.T.Mills@ cc:
ERAC.COM> Subject: ssh when rlogin=false
Sent by: "IBM
AIX Discussion
List"
<aix-l@Princet
on.EDU>
01/06/2003
11:00 AM
Please respond
to "IBM AIX
Discussion
List"
All,
Has anyone had any luck getting ssh to function
when rlogin=false has been set? I understand that
ssh takes rlogin=false very seriously, but I am
trying to configure ssh to function after this
change is made.
Thanks,
John T. Mills
**********
The information contained in this communication is confidential, private,
proprietary, or otherwise privileged and is intended only for the use of the
addressee. Unauthorized use, disclosure, distribution or copying is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify the sender immediately at
(312)653-6000 in Illinois; (972)766-6900 in Texas; or (800)835-8699 in New
Mexico.
**********
This electronic message transmission, including any attachments, contains
information from PacifiCare Health Systems Inc. which may be confidential or
privileged. The information is intended to be for the use of the individual
or entity named above. If you are not the intended recipient, be aware that
any disclosure, copying, distribution or use of the contents of this
information is prohibited.
If you have received this electronic transmission in error, please notify
the sender immediately by a "reply to sender only" message and destroy all
electronic and hard copies of the communication, including attachments.
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:27 EDT