🚀 go-pugleaf

On Sun, 13 Jun 1999 08:31:26 GMT, jbrough@melbpc.org.au <jbrough@melbpc.org.au> wrote:
|After upgrading from RH5.2 to RH6.0 I can't login any more. Previously
|I was using no password on root, done by deleting the password info in
|/etc/passwd (not good security but its a stand alone for playing
|with). Now after the upgrade, it asks for a password, and won't accept
|anything I type in.
|
|Thanks in advance
|John 


You may have to boot into single user mode ( type 'linux single'
at the boot prompt ) and set a password there.

The PAM security modules on RH generally treat a null/empty
password as a locked account. Try going to /etc/pam.d and edit
the login file. Add the parameter nullok to the authentication
and authorisation lines.

Did you need to do something to RH5.2 to get the null password
working on that system?


-- 
Reverend Paul Colquhoun,      postmaster@andor.dropbear.id.au
Universal Life Church    http://andor.dropbear.id.au/~paulcol
-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-
xenaphobia: The fear of being beaten to a pulp by
            a leather-clad, New Zealand woman.

On Sun, 13 Jun 1999 11:07:14 GMT, postmaster@andor.dropbear.id.au
(Paul Colquhoun) wrote:

>On Sun, 13 Jun 1999 08:31:26 GMT, jbrough@melbpc.org.au <jbrough@melbpc.org.au> wrote:
>|After upgrading from RH5.2 to RH6.0 I can't login any more. Previously
>|I was using no password on root, done by deleting the password info in
>|/etc/passwd (not good security but its a stand alone for playing
>|with). Now after the upgrade, it asks for a password, and won't accept
>|anything I type in.
>|
>|Thanks in advance
>|John 
>
>
>You may have to boot into single user mode ( type 'linux single'
>at the boot prompt ) and set a password there.
>
>The PAM security modules on RH generally treat a null/empty
>password as a locked account. Try going to /etc/pam.d and edit
>the login file. Add the parameter nullok to the authentication
>and authorisation lines.
>
>Did you need to do something to RH5.2 to get the null password
>working on that system?
>
>
>-- 
>Reverend Paul Colquhoun,      postmaster@andor.dropbear.id.au
>Universal Life Church    http://andor.dropbear.id.au/~paulcol
>-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-
>xenaphobia: The fear of being beaten to a pulp by
>            a leather-clad, New Zealand woman.

What I did was to get the encrypted password info from a RH5.2 machine
that I use as a SMB server when I boot the RH6 machine as DOS, and
using the boot/rescue disks edit /etc/passwd and insert the info. This
allowed me to login OK.
What is bugging me now is that I can't telnet into the RH6 machine
like I used to. It seems that RH6 may tighten up security or something

On Mon, 14 Jun 1999 05:36:32 GMT, jbrough@melbpc.org.au <jbrough@melbpc.org.au> wrote:
|On Sun, 13 Jun 1999 11:07:14 GMT, postmaster@andor.dropbear.id.au
|(Paul Colquhoun) wrote:
|
|>On Sun, 13 Jun 1999 08:31:26 GMT, jbrough@melbpc.org.au <jbrough@melbpc.org.au> wrote:
|>|After upgrading from RH5.2 to RH6.0 I can't login any more. Previously
|>|I was using no password on root, done by deleting the password info in
|>|/etc/passwd (not good security but its a stand alone for playing
|>|with). Now after the upgrade, it asks for a password, and won't accept
|>|anything I type in.
|>|
|>|Thanks in advance
|>|John 
|>
|>
|>You may have to boot into single user mode ( type 'linux single'
|>at the boot prompt ) and set a password there.
|>
|>The PAM security modules on RH generally treat a null/empty
|>password as a locked account. Try going to /etc/pam.d and edit
|>the login file. Add the parameter nullok to the authentication
|>and authorisation lines.
|>
|>Did you need to do something to RH5.2 to get the null password
|>working on that system?
|
|
|What I did was to get the encrypted password info from a RH5.2 machine
|that I use as a SMB server when I boot the RH6 machine as DOS, and
|using the boot/rescue disks edit /etc/passwd and insert the info. This
|allowed me to login OK.
|What is bugging me now is that I can't telnet into the RH6 machine
|like I used to. It seems that RH6 may tighten up security or something


Most of this security stuff was the default in RH5.2 as well. Are
you sure you don't remember turning it off?

The telnet-as-root "problem" can be fixed by editing /etc/securetty
and adding some entries that correspond to telnet sessions, i.e.
pts/0
pts/1
etc...

/etc/securetty contains the list of terminals ( this includes
the virtual consoles and telnet pseudottys ) that are concidered
secure enough for root to use.

Every telnet session will use a pseudotty, and will be allocated
the smalles available number ( I think ). If you incude pts/0 and pts/1
then root can telnet directly into the box, provided that one
or the other of these pttys are free. You may need to add a few
pts/? entries if you want many simultaneous sesions.


-- 
Reverend Paul Colquhoun,      postmaster@andor.dropbear.id.au
Universal Life Church    http://andor.dropbear.id.au/~paulcol
-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-
xenaphobia: The fear of being beaten to a pulp by
            a leather-clad, New Zealand woman.

On 14 Jun 1999 07:07, Paul Colquhoun <postmaster@andor.dropbear.id.au> wrote:
>
>
>Most of this security stuff was the default in RH5.2 as well. Are
>you sure you don't remember turning it off?
>
>The telnet-as-root "problem" can be fixed by editing /etc/securetty
>and adding some entries that correspond to telnet sessions, i.e.
>pts/0
>pts/1
>etc...
>
>/etc/securetty contains the list of terminals ( this includes
>the virtual consoles and telnet pseudottys ) that are concidered
>secure enough for root to use.
>
>Every telnet session will use a pseudotty, and will be allocated
>the smalles available number ( I think ). If you incude pts/0 and pts/1
>then root can telnet directly into the box, provided that one
>or the other of these pttys are free. You may need to add a few
>pts/? entries if you want many simultaneous sesions.
>
Or, if you don't want to be limited to just a few ttys (although I think
limiting to none is a better idea!), you can just delete the file
/etc/securettys and that will disable that check and root can login from
anywhere.

OBDisclaimer:  Doing this is really not a good idea.  You're going to telnet
               into your box and send your root password as clear text for
               anybody to sniff.   Take a look at ssh and sudo!

-- 
--Tracy S. Fitch
Theatre Technical Director/Lighting Designer
Unix SysAdmin