From: 7v5w7go9ub0o <7v5w7go9ub0o@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: [gentoo-hardened] Re: hardened workstation - is that worth it?
Date: Tue, 25 Nov 2008 21:02:58 -0500 [thread overview]
Message-ID: <492CAE52.5050709@gmail.com> (raw)
In-Reply-To: <200811251700.45540.janklodvan@gmail.com>
Jan Klod wrote:
> Suppose, I want to take some extra precautions and set up PaX&co and MAC on a
> workstation with Xorg and other nice KDE apps (only some of which should be
> granted access to files in folder X). I would like to read others opinion, if
> I can get considerable security improvements or I will have to make that much
> of exceptions to those good rules, as it makes protection too useless?
>
> Regards,
> Jan
>
>
Depends upon your definition of hardening, I guess.
I run the "old" hardened toolchain, grsecurity-enhanced hardened kernel,
rbac control, and jails for anything that accesses the LAN/WAN.(heh... I
even chroot and kill dhcpcd after 5 seconds). Avira has hundreds of
Linux rootkit signatures in its database, so I run Avira and Dazuko
realtime/on-access scanning on my /home directory, the chroot jails, and
on the portage workspace used during download and compilation.
I presume that for a desktop user, most attacks come in through the
browser, and/or extensions, plugins (e.g. flash), BHO's, etc. Something
could also come through the distribution chain from a compromised or
spoofed source - therefor the signature scanning.
- I presume that pax and/or ssp will protect me against memory attacks
that may come in through a L/WAN connection.
- If the L/WAN attack comes in through, say, a browser exploit or
backdoor it will be confined by RBAC to the areas I trained it to
access, and no more. That would be the jail.
- If the browser tries to "jail break", it will run up against the anti
jailbreak hardening provided by grsecurity, and be terminated.
- grsecurity blocks writing to /dev/mem, kmem, port.
Judging by the other posts here, someone who knows what he is doing can
have my box.
Well..... yes! - nothing is 100%. But I'm not trying to protect
against him.... I'm worried about 95%: the 0-day browser bugs,
compromised extensions, etc. that may allow a Trojan to try its stuff,
or may allow an inpatient script-kiddee to have a shell on a Linux box
that doesn't have this kernel and binary hardening; that doesn't run
applications in hardened jails.
next prev parent reply other threads:[~2008-11-26 2:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 15:00 [gentoo-hardened] hardened workstation - is that worth it? Jan Klod
2008-11-25 15:56 ` Alex Efros
2008-11-25 16:39 ` Jan Klod
2008-11-25 20:40 ` Alex Efros
2008-11-25 20:51 ` Javier Martínez
2008-11-25 20:56 ` Alex Efros
2008-11-25 19:58 ` RB
2008-11-25 20:36 ` Javier Martínez
2008-11-25 21:24 ` Jan Klod
2008-12-05 15:29 ` pageexec
2008-12-05 16:38 ` Brian Kroth
2008-12-05 17:21 ` Javier Martínez
2008-12-05 17:22 ` pageexec
2008-12-05 17:31 ` Javier Martínez
2008-12-05 17:48 ` Ned Ludd
2008-12-05 17:11 ` pageexec
2008-11-25 21:12 ` Jan Klod
2008-11-25 21:47 ` RB
2008-11-25 21:58 ` Jan Klod
2008-11-25 22:11 ` atoth
2008-11-25 22:14 ` RB
2008-11-26 11:39 ` Jan Klod
2008-11-25 23:23 ` Javier Martínez
2008-11-26 2:02 ` 7v5w7go9ub0o [this message]
2008-11-26 2:34 ` [gentoo-hardened] " Alex Efros
2008-11-26 17:31 ` 7v5w7go9ub0o
2008-11-26 6:09 ` atoth
2008-11-26 17:41 ` 7v5w7go9ub0o
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=492CAE52.5050709@gmail.com \
--to=7v5w7go9ub0o@gmail.com \
--cc=gentoo-hardened@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox