From: Pavel Labushev <p.labushev@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Re: Giving a hand with docs
Date: Tue, 29 Jun 2010 15:40:10 +0800 [thread overview]
Message-ID: <4C29A35A.2020809@gmail.com> (raw)
In-Reply-To: <4C26BC6B.3080404@gmail.com>
27.06.2010 10:50, klondike пишет:
> 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.
OK, but this part brings some degree of uncertainty:
"though if you do, your system would be prone to a DOS attack if any of
your forking daemons has a memory bug."
... It sounds like if you have a single buggy daemon, it would make the
_whole_ system be prone to a DoS attack, while it's just the daemon
itself becomes at risk. Maybe change it to: "though if you do, and if
any of your forking daemons has a memory bug, that daemon would be prone
to a DOS attack ."?
next prev parent reply other threads:[~2010-06-29 8:02 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
2010-06-29 7:40 ` Pavel Labushev [this message]
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=4C29A35A.2020809@gmail.com \
--to=p.labushev@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