From: 1stFlight <1stflight@ameritech.net>
To: david.jay.jackson@wcox.com
Cc: Glynn Clements <glynn.clements@virgin.net>, linux-admin@vger.kernel.org
Subject: Re: RH7.2: init 1 no password?
Date: Sun, 19 May 2002 16:58:06 -0400 [thread overview]
Message-ID: <3CE811DE.FEC64260@ameritech.net> (raw)
In-Reply-To: 200205191416.AA13369654@wcox.com
Actually this is a good point, anyone know of a way to secure init 1 ?
Darryl
David Jackson wrote:
> Glynn --
> Thanks for you reply
> In my experience working in datacenters, anyone includes janitors, and
> and $10.00 secruity guards, it still doesn't explain why RedHat has this
> behavior, can you think of another Unix flavor that does this?
> Solaris, Slackware and Debain don't?
>
> Thanks again for reply,
> David
>
> >
> >Why? The root shell is only accessible from the console. Anyone who
> >has physical access to the machine can probably do whatever they want
> >with it; software security mechanisms aren't much use in that
> >situation.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
It's not that life is so short, it's that death is so long...
next prev parent reply other threads:[~2002-05-19 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-19 20:16 RH7.2: init 1 no password? David Jackson
2002-05-19 20:58 ` 1stFlight [this message]
2002-05-20 8:24 ` Anatoli Souppes
2002-05-21 14:42 ` Scott Taylor
2002-05-21 14:33 ` Scott Taylor
-- strict thread matches above, loose matches on Subject: below --
2002-05-21 17:35 David Jackson
2002-05-21 17:50 ` Glynn Clements
2002-05-21 16:47 David Jackson
2002-05-21 17:01 ` Glynn Clements
2002-05-21 14:29 Scott Taylor
[not found] <200205191355.AA10813750@wcox.com>
2002-05-19 21:08 ` David Eduardo Gomez Noguera
2002-05-19 19:35 David Jackson
2002-05-19 19:54 ` Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CE811DE.FEC64260@ameritech.net \
--to=1stflight@ameritech.net \
--cc=david.jay.jackson@wcox.com \
--cc=glynn.clements@virgin.net \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.