linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thornton Prime <theoszi@gmail.com>
To: Ankit Jain <ankitjain1580@yahoo.com>,
	admin <linux-admin@vger.kernel.org>
Subject: Re: linuxsingle
Date: Sun, 10 Apr 2005 09:11:39 -0700	[thread overview]
Message-ID: <2d7eccf5050410091159808924@mail.gmail.com> (raw)
In-Reply-To: <20050410155037.GA26834@jbrown.mylinuxbox.org>

> On Sun, Apr 10, 2005 at 05:20:36AM +0100, Ankit Jain wrote:
> ifanybody can tell me how to make changes in linux so
> that a person cannot move to linux single mode in any
> condition . not even from bootable CD

Depending on your PC you can:

1. Set the BIOS to boot only to HD.
2. Set a BIOS password to make sure no one changes your boot preferences.

With those taken care of you can:

3. Set a password on your bootloader.

No one should be able to boot from CD or change the bootloader options
without the BIOS and/or bootloader passwords. Please keep in mind that
there are plenty of ways to circumvent these measures if anyone has
physical access to the machine (reset your bios, replace your drives,
etc.). Linux is no more or less susceptible to these issues than other
platforms.

Actually, in many ways Linux on good PC hardware is safer than other
Unix platforms. On many platforms you can boot an arbitrary kernel on
an arbitrary device if you have access to the physical console. Many
of those platforms have no BIOS restrictions or bootloader security.
Some of those platforms may have the init path hardcoded or may have
single user prompt for a password, but these are really of minimal
security if you can boot an arbitary kernel on an arbitrary device,
especially if that device is the network!

thornton

  reply	other threads:[~2005-04-10 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10  4:20 linuxsingle Ankit Jain
2005-04-10  4:47 ` linuxsingle Jeff Woods
2005-04-10 15:50 ` linuxsingle Jim C. Brown
2005-04-10 16:11   ` Thornton Prime [this message]
2005-04-10 16:32 ` linuxsingle chuck gelm
2005-04-14  2:43 ` linuxsingle Michael H. Warfield
2005-04-14 14:25   ` linuxsingle terry white
2005-04-14 14:34     ` linuxsingle Michael H. Warfield
2005-04-16  1:36       ` linuxsingle terry white
2005-04-16 22:08         ` linuxsingle markus reichelt

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=2d7eccf5050410091159808924@mail.gmail.com \
    --to=theoszi@gmail.com \
    --cc=ankitjain1580@yahoo.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=thornton@yoyoweb.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).