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] foldingathome and PAX
Date: Mon, 20 Apr 2009 21:13:16 +0200	[thread overview]
Message-ID: <49ECC94C.31865.4D050A8@pageexec.freemail.hu> (raw)
In-Reply-To: <1240254225.12686.8.camel@lillen.dodi>

On 20 Apr 2009 at 21:03, Peter Hjalmarsson wrote:

> I realised earlier today that foldingathome (installed with the help of
> portage) had not started a new WU since 5 of april, and when I started
> to investigate I found out that the "cores" had problem running. 
> 
> cd /opt/foldingathome &&
> paxctl -c FahCore_*.exe &&
> paxctl -PEMrXS FahCore_*.exe
> 
> makes it work again.
> foldingathome has worked in the past without problems, and I do not
> really know what have changed more then some kernel-upgrades (but
> booting the last kept 2.6.27-hardened did not help either) and keeping
> the userland up to stable x86.
> What can I do to not have to do this dance?

can you re-enable pax on the binaries and see if they produce any logs
(pax kills)? if they do, try to remove mprotect only and see if that
helps. the other issue could be a bad glibc and lack of GNU_STACK headers,
execstack -c would fix that without having to compromise on pax.




  reply	other threads:[~2009-04-20 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 19:03 [gentoo-hardened] foldingathome and PAX Peter Hjalmarsson
2009-04-20 19:13 ` pageexec [this message]
2009-04-20 19:53   ` [gentoo-hardened] " Peter Hjalmarsson
2009-04-20 20:02     ` pageexec
2009-04-20 20:38       ` Peter Hjalmarsson
2009-04-20 21:07         ` pageexec
2009-04-21  4:46           ` [gentoo-hardened] " Peter Hjalmarsson
2009-04-21 19:15             ` pageexec
2009-04-21 13:44 ` [gentoo-hardened] " Brian Kroth

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=49ECC94C.31865.4D050A8@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