From: Vasiliy Kulikov <segoon@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] segoon's status report - #13 of 15
Date: Tue, 9 Aug 2011 11:30:37 +0400 [thread overview]
Message-ID: <20110809073037.GA3767@albatros> (raw)
Not too many accomplishments this time - I was interrupted by unexrected
university occasions.
Accomplishments:
* Addressed a kernel oops on ARM/MIPS/UML.
* Posted a next procfs patch version to k-h.
* Found a race in /proc/PID/fd{,info}/ handling, sent a patch to LKML.
* Posted a basic patch to lock pid namespace to 32 or 64 bit
syscalls/ELFs.
Priorities:
* Push USERCOPY, RLIMIT_NPROC, a.out patches as soon as 3.1-rc1 is out.
* Finish procfs and bitness locking patches.
* Discuss base address for libs, ASLR, GNU_STACK.
--
Vasiliy
reply other threads:[~2011-08-09 7:30 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=20110809073037.GA3767@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