public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] 'paxctl -m bin' everything that complains?
Date: Thu, 22 Jan 2009 19:07:55 -0800	[thread overview]
Message-ID: <49bf44f10901221907ie90aaa7rc87fe6bd5b160b97@mail.gmail.com> (raw)
In-Reply-To: <4255c2570901221308y37ee8f26i11f33c9e3bbf5626@mail.gmail.com>

>>> Check out 'ulimit -a' or search for 'ulimit' in bash(1).
>>
>> I read about ulimit and I'm wondering if I need to worry about
>> increasing that coredump size from zero.  Can I just ignore those
>> grsec messages without causing a problem?
>
> Allowing core dumps will enable failed applications to dump a copy of
> their memory to disk; generally this only causes issues if you're
> disk-space sensitive.  It can also be an issue for applications that
> hold sensitive data (like passwords) in-memory.
>
> If you can, yes - just ignore the RLIMIT_CORE ones.  You probably want
> to find out why applications are trying to dump, but the messages are
> a symptom rather than the cause.

It turns out I need to issue 'paxctl -m
/usr/lib64/mozilla-firefox/firefox' to prevent firefox from crashing
when watching a cnn.com video.  Is that a huge security issue?

- Grant



  reply	other threads:[~2009-01-23  3:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 19:06 [gentoo-hardened] 'paxctl -m bin' everything that complains? Grant
2009-01-22 19:26 ` RB
2009-01-22 20:21   ` Grant
2009-01-22 21:01   ` Grant
2009-01-22 21:08     ` RB
2009-01-23  3:07       ` Grant [this message]
2009-01-23  4:12         ` RB

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=49bf44f10901221907ie90aaa7rc87fe6bd5b160b97@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