From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Cc: musl@lists.openwall.com
Subject: Re: Initial work on post-1.0 roadmap
Date: Thu, 05 Sep 2013 06:14:13 -0500 [thread overview]
Message-ID: <1378379653.1985.4@driftwood> (raw)
In-Reply-To: <20130830170356.GN20515@brightrain.aerifal.cx> (from dalias@aerifal.cx on Fri Aug 30 12:03:57 2013)
On 08/30/2013 12:03:57 PM, Rich Felker wrote:
> On Wed, Aug 28, 2013 at 01:46:30AM -0400, Rich Felker wrote:
> > This message is purely some notes for tracking and possible
> discussion
> > of things to do after musl 1.0 is released. I'm leaning towards (but
> > undecided) maintaining separate 1.0.x and 1.1.x branches after the
> 1.0
> > release, the 1.0.x being just bug-fixes and backports of
> non-invasive
> > changes, and real development taking place in the 1.1.x series. The
> > below items should probably then be arranged into a 1.1.x-series
> > roadmap based on how much seems reasonable to get done per release
> > (roughly, per month), and which features are in the highest demand.
>
> One more item (well, a big multi-part item):
>
> Security features -- RELRO processing in the dynamic linker, a
> replacement for _FORTIFY_SOURCE (as a layer on top of libc's headers
> rather than part of libc's headers), making it possible to build libc
> itself with stack-protector, possibly nonstandard interfaces needed
> for using kernel security features well, adapting malloc's footer
> bookkeeping to make it difficult to preserve footer when performing
> buffer overflows, ...
This isn't on the wiki...?
Rob
next prev parent reply other threads:[~2013-09-05 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 5:46 Rich Felker
2013-08-30 17:03 ` Rich Felker
2013-09-05 11:14 ` Rob Landley [this message]
2013-09-05 18:27 ` Rich Felker
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=1378379653.1985.4@driftwood \
--to=rob@landley.net \
--cc=musl@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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).