public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: klondike <franxisco1988@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: [gentoo-hardened] Re: Giving a hand with docs
Date: Sun, 27 Jun 2010 04:50:19 +0200	[thread overview]
Message-ID: <4C26BC6B.3080404@gmail.com> (raw)
In-Reply-To: <4C1898D6.7030304@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1785 bytes --]

El 16/06/10 11:26, Pavel Labushev escribió:
> I think GRKERNSEC_BRUTE deserves a bit more explaination, as long as in
> some (most?) cases it seems to be the single little trick that prevents
> preforked apps to be eventually owned with no regard to ASLR, especially
> on x86.
>   
Updated the explanation a bit, I hope you find it more appropriate.
> Also, maybe a reader should be advised to develop a policy to
> autorestart preforked apps when the relevant records appear in the grsec
> log? They are "Segmentation fault" and "Illegal instruction". And maybe
> it deserves to be mentioned that SIGSEGV does not trigger the fork()
> delay, so the autorestart policy which takes frequent SIGSEGV log
> messages into account is a right thing.
>   
Updated that too, I also commented that a small edit of the patch could
also be valid to add the SIGSEGV signal to those controlled.
> Btw, it's not "some delays" but the 30 seconds hardcoded in
> grsecurity/grsec_sig.c.
>   
Added also, I wrote some delays to make it more generic and easily
accessible though I see that stating the delay helps a lot to see which
are the consequences if the bug is triggered.

Thanks for your comments :D

El 13/06/10 15:30, ascii escribió:
> seems nice to me, consider contacting someone @
> http://www.gentoo.org/proj/en/gdp/index.xml
>   
Well I won't mind converting the doc to GuideXML if this document is
interesting. All I need is a go ahead from someone on the Hardened team.
> perhaps you'll also like this project
>
> http://lollobox.org/
>   
Seems cool, but a bit left over (also I don't currently own a working
laptop) :/ It's a pity how most securization projects end up dying
because people think great technical skills are needed to contribute.

[-- Attachment #1.2: GentooHardenedWhy.odt --]
[-- Type: application/vnd.oasis.opendocument.text, Size: 23711 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2010-06-27  2:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08  0:34 [gentoo-hardened] Giving a hand with docs klondike
2010-06-13  9:15 ` [gentoo-hardened] " klondike
2010-06-13  9:33   ` klondike
2010-06-16  9:26   ` Pavel Labushev
2010-06-27  2:50     ` klondike [this message]
2010-06-29  7:40       ` Pavel Labushev
2010-06-29  8:04         ` Daniel Kuehn

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=4C26BC6B.3080404@gmail.com \
    --to=franxisco1988@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