From: Grant <emailgrant@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Which hardened kernel feature disables wine?
Date: Wed, 14 Jan 2009 09:49:04 -0800 [thread overview]
Message-ID: <49bf44f10901140949n1ebc71ednf7ffd8c1bac05daa@mail.gmail.com> (raw)
In-Reply-To: <1231905314.4856.11.camel@localhost>
>> >> Thanks everyone, that worked great. Is there a way to get a list of
>> >> files which have been operated on by paxctl? I didn't see anything in
>> >> man paxctl.
>> >
>> >
>> > qlist -ao | scanelf -f - -q -x
>>
>> Thanks Ned. I get the following but I've only ever issued paxctl
>> referencing /usr/bin/wine-preloader. Can you tell me why the other
>> files might be listed?
>>
>> # qlist -ao | scanelf -f - -q -x
>> --mxe- /opt/emul-linux-x86-java-1.6.0.11/bin/java
> ..
>
> portage and or the toolchain handles them.
> Packages with known problems such as wine should be pax-marked
If I'm understanding correctly, emul-linux-x86-java, VirtualBox, and
sun-jdk have known problems with pax so portage pax-marks them.
Shouldn't portage pax-mark wine too instead of me doing it manually?
- Grant
> See /usr/portage/eclass/pax-utils.eclass for more details.
>
> Finding pkgs that use these functions can be done like this.
>
> qgrep -Hvv 'pax-mark'
next prev parent reply other threads:[~2009-01-14 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 19:00 [gentoo-hardened] Which hardened kernel feature disables wine? Grant
2009-01-13 19:42 ` Javier J. Martínez Cabezón
2009-01-13 20:09 ` Ned Ludd
2009-01-13 20:16 ` Javier J. Martínez Cabezón
2009-01-13 20:27 ` Thomas Sachau
2009-01-13 21:06 ` Grant
2009-01-13 21:30 ` Ned Ludd
2009-01-14 3:19 ` Grant
2009-01-14 3:55 ` Ned Ludd
2009-01-14 17:49 ` Grant [this message]
2009-01-14 17:07 ` pageexec
2009-01-15 16:13 ` Grant
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=49bf44f10901140949n1ebc71ednf7ffd8c1bac05daa@mail.gmail.com \
--to=emailgrant@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