I seem to have found the answer to my own question.
The question was:
How do I prevent the boot2 bootstrap step from displaying a prompt
where the user can load a custom boot program and/or force booting
with options such as single user mode?
The answer that seems to work for me:
Add "-n" to /boo
Nerius Landys wrote:
Hi. I am attempting to secure some workstations in such a way that a
user would not be able gain full control of the computer (only user
access). However, they are able to see and touch the physical
workstation.
I assume that users cannot tingle with the hardware, take it
On Thu, Aug 06, 2009 at 01:35:55PM -0600, Tim Judd wrote:
> On 8/6/09, Nerius Landys wrote:
> > Hi. I am attempting to secure some workstations in such a way that a
> > user would not be able gain full control of the computer (only user
> > access). However, they are able to see and touch the phy
On 8/6/09, Nerius Landys wrote:
> Hi. I am attempting to secure some workstations in such a way that a
> user would not be able gain full control of the computer (only user
> access). However, they are able to see and touch the physical
> workstation. Things I'm trying to avoid, to list a couple
Hi. I am attempting to secure some workstations in such a way that a
user would not be able gain full control of the computer (only user
access). However, they are able to see and touch the physical
workstation. Things I'm trying to avoid, to list a couple of
examples:
1. Go to BIOS settings and
> or by setting the actual hdd to secondary and plug an other primary
> hdd
Once the hardware is compromised, it is really tricky to keep secure.
If you cannot protect your hardware (secure room) then your hard disk
has to auto protect itself: encrypt the data, and have no saved
password on the d
On Wed, Jul 13, 2005 at 01:05:43PM +0200, [EMAIL PROTECTED] wrote:
> I would like to secure my FreeBSD server.
> I don't want anyone to be able to access to the disk using a bootable
> CD (or by setting the actual hdd to secondary and plug an other
> primary hdd).
Put the machine in a locked cabi
>On 7/13/05, Greg Barniskis <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > hi guys
> >
> > I would like to secure my FreeBSD server.
> > I don't want anyone to be able to access to the disk using a bootable CD
> > (or by
> > setting the actual hdd to secondary and plug an other primary
[EMAIL PROTECTED] wrote:
hi guys
I would like to secure my FreeBSD server.
I don't want anyone to be able to access to the disk using a bootable CD (or by
setting the actual hdd to secondary and plug an other primary hdd).
I just don't want anyone to be able to hack this box nor any password.
[EMAIL PROTECTED] wrote:
hi guys
I would like to secure my FreeBSD server.
I don't want anyone to be able to access to the disk using a bootable CD (or by
setting the actual hdd to secondary and plug an other primary hdd).
I just don't want anyone to be able to hack this box nor any password.
hi guys
I would like to secure my FreeBSD server.
I don't want anyone to be able to access to the disk using a bootable CD (or by
setting the actual hdd to secondary and plug an other primary hdd).
I just don't want anyone to be able to hack this box nor any password.
Do you have a solution?
Ch
Peter Rosa wrote:
[ ... ]
I'm looking for an exact list of files, which:
1. MUST have...
2. HAVE FROM BSD INSTALLATION...
3. DO NOT NEED...
4. NEVER MAY...
...the suid-bit set.
Of course, it's no problem to find-out which files ALREADY HAS
suid-bit set. But what files REALLY MUST have it ?
The file
Matthew Graybosch wrote:
But if you're concerned with security uber alles, I'm surprised you
didn't look into OpenBSD first. According to their site
(openbsd.org), they've had "only one remote hole in the default
install, in more than 7 years!"
Caveat: the default install has almost nothing in i
t; <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, July 26, 2003 7:22 PM
Subject: Re: suid bit files and securing FreeBSD
>
> > Second question is: Has anybody an exact wizard, how to secure
> > the FreeBSD machine. Imagine the situation, the only person w
> Second question is: Has anybody an exact wizard, how to secure
> the FreeBSD machine. Imagine the situation, the only person who
> can do anything on that machine is me, and nobody other. I have
> set very restrictive firewalling, I have removed ALL tty's except
> two local tty's (I need to work
1 PM
Subject: suid bit files and securing FreeBSD
> Hello everybody,
>
> I'm a newbie in this list, so I don't know if it's the appropriate place
> for my question. Anyway, I'd be happy to find out the solution.
>
> Please, has anyone simple answer for:
>
> I&#
Hello everybody,
I'm a newbie in this list, so I don't know if it's the appropriate place
for my question. Anyway, I'd be happy to find out the solution.
Please, has anyone simple answer for:
I'm looking for an exact list of files, which:
1. MUST have...
2. HAVE FROM BSD INSTALLATION...
3. DO NO
17 matches
Mail list logo
