From: Vasiliy Kulikov <segoon@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] segoon's status report - #11 of 15
Date: Mon, 25 Jul 2011 22:53:58 +0400 [thread overview]
Message-ID: <20110725185358.GA16994@albatros> (raw)
Accomplishments:
* Posted v2 and v3 of USERCOPY RFC to LKML.
* Stated the GNU_STACK handling issue on k-h list.
* Got a new direction of work in GNU_STACK area (RHEL's exec shield
implementation).
* Summarized all accomplishments of the GSoC and posted the list on k-h
list.
* Built and posted a list of possibly dangerous kernel infoleaks.
* Reviewed PAX_MPROTECT feature and posted the summary to the list.
* Reviewed securelevel'ish Grsecurity restrictions and posted my
thoughts on k-h list.
* Started to implement more finegranted HARDEN_PROC feature.
* Got a new task from Solar: investigate differences in base addresses
for mmap areas in x86-32 and 32-bit tasks in x86-64.
Priorities:
* RLIMIT_NPROC discussion with upstream.
* USERCOPY discussion and elaboration.
* HARDEN_RPOC implementation.
* GNU_STACK issue investigation.
* Base lib address differences in x86-32 and 32-bit tasks in x86-64.
--
Vasiliy
reply other threads:[~2011-07-25 18:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110725185358.GA16994@albatros \
--to=segoon@openwall.com \
--cc=kernel-hardening@lists.openwall.com \
/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