public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: pageexec@freemail.hu
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] hardened workstation - is that worth it?
Date: Fri, 05 Dec 2008 19:22:59 +0200	[thread overview]
Message-ID: <49397183.5209.9BEB5B0@pageexec.freemail.hu> (raw)
In-Reply-To: <897813410812050921k1985ae7ar7caf712993423bc3@mail.gmail.com>

On 5 Dec 2008 at 18:21, Javier Martínez wrote:

> Have you said me that I'm obsoleted?, ok, I agreed with you... o:),
> but since I don't use xorg in servers... no problem. You still having
> the other problems I commented.

if you mean the /dev/mem issue, it's been solved to an extent in grsec
for a long time now as it restricts what range in that device you can
actually access - no physical memory for a start, so your trick of patching
anything in kernel memory wouldn't fly. current 2.6 series also try to offer
something like that (CONFIG_STRICT_DEVMEM) but as usual it's somewhat broken.

> One question, somebody knows what made
> xorg incompatible with pax mprotect restrictions in earlier versions?.

it was the so-called elfloader, which was the X module loader supported
and used by most distros back in the day. it handled .o files (ET_REL type
in ELF terms) and performed relocation and symbol resolution itself.

> I put you a link that is newer than the link that Brian Kroth posted
> and still having the incompatibilities on:
> http://www.gentoo.org/proj/en/hardened/pax-quickstart.xml, maybe a
> mistake?

yes, from a quick glance, many of these hardened docs could do with a
little update ;).




  reply	other threads:[~2008-12-05 18:23 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 [this message]
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 ` [gentoo-hardened] " 7v5w7go9ub0o
2008-11-26  2:34   ` 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=49397183.5209.9BEB5B0@pageexec.freemail.hu \
    --to=pageexec@freemail.hu \
    --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