From: atoth@atoth.sote.hu
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] persistent paxctl -m?
Date: Fri, 10 Apr 2009 20:08:45 +0200 (CEST) [thread overview]
Message-ID: <c252fe43260946d69f179a226c1bfa1e.squirrel@atoth.sote.hu> (raw)
In-Reply-To: <49bf44f10904100929p4ec6e29bpc74f9a92a5fed916@mail.gmail.com>
Don't agree.
If you employ GRsecurity's RBAC, you can use PAX flags, like
"PAX_MPROTECT" on a given subject (binary). Take a look at on the example
policy file.
Regards:
Dw.
--
dr Tóth Attila, Radiológus, 06-20-825-8057, 06-30-5962-962
Attila Toth MD, Radiologist, +36-20-825-8057, +36-30-5962-962
On Pén, Április 10, 2009 18:29, Grant wrote:
>>>> and create executable shell script in that dir:
>>>> mozilla-firefox-bin.postinst
>>>> ---cut---
>>>> #!/bin/bash
>>>> ewarn "Running chpax -m /opt/firefox/firefox-bin to avoid crash on
>>>> flash!"
>>>> chpax -m /opt/firefox/firefox-bin
>>>> ---cut---
>>>>
>>>
>>> Of course, if you compile firefox instead of using firefox-bin, then
>>> file
>>> should be named mozilla-firefox.postinst and you should use there
>>> paxctl
>>> instead of chpax.
>>>
>> A simple cron job or slightly-less-simple RBAC policy can do the trick.
>> There's no need to mess with portage, imho.
>
> Thanks for the suggestions everyone. I think this type of persistence
> should be built into portage. Maybe /etc/portage/package.nomprotect.
> Do you agree? Should I file a bug?
>
> - Grant
>
next prev parent reply other threads:[~2009-04-10 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 16:07 [gentoo-hardened] persistent paxctl -m? Grant
2009-04-09 16:10 ` klondike
2009-04-09 17:37 ` Ned Ludd
2009-04-09 20:59 ` [gentoo-hardened] " 7v5w7go9ub0o
2009-04-09 16:13 ` [gentoo-hardened] " Thomas Sachau
2009-04-09 16:14 ` Alex Efros
2009-04-09 16:21 ` Alex Efros
2009-04-10 3:35 ` Pavel Labushev
2009-04-10 16:29 ` Grant
2009-04-10 18:08 ` atoth [this message]
2009-04-12 0:03 ` Grant
2009-04-12 6:49 ` atoth
2009-04-10 18:52 ` Ned Ludd
2009-04-11 13:06 ` Alex Efros
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=c252fe43260946d69f179a226c1bfa1e.squirrel@atoth.sote.hu \
--to=atoth@atoth.sote.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