[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130830170356.GN20515@brightrain.aerifal.cx>
Date: Fri, 30 Aug 2013 13:03:57 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: Initial work on post-1.0 roadmap
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, ...
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
