From: boris brezillon <b.brezillon.musl@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Help-wanted tasks for musl
Date: Sun, 19 Aug 2012 10:44:13 +0200 [thread overview]
Message-ID: <CAKAk8dbt6SG-0QdB0V6OrqWt_CyrZ_OL5CaN+1egzUind=5mCQ@mail.gmail.com> (raw)
In-Reply-To: <20120819042611.GA8731@brightrain.aerifal.cx>
2012/8/19 Rich Felker <dalias@aerifal.cx>:
> Hi all,
> Here are some tasks I could really use some help on, based on current
> topics and requests that have come up on the list and IRC. Any
> volunteers? See below...
>
> Rich
>
>
>
> Research on NSCD protocol
>
> Interfacing with a proxy/cache daemon using nscd protocol is one of
> the proposed options for allowing musl to deal with NIS/LDAP/etc. user
> databases. In order to evaluate the option, we need to know how the
> protocol works and what's involved in making queries and receiving
> responses. Documenting how it works would be really helpful. I'm not
> looking for big, complete protocol documentation, just simple
> descriptions and examples of how queries are conducted.
>
>
> Analysis of Gregor's pkgsrc failure results
>
> Gregor Richards has run the whole NetBSD pkgsrc build (over 10k
> packages) against musl and posted reports to the mailing list and
> wiki. Some analysis on the most frequent causes of failure could be
> extremely helpful to improving compatibility. It would also be nice to
> identify major dependency failures that can be fixed (either in the
> upstream package if it's buggy, or in musl if it's due to missing
> features) so that the packages which depend on them can be tested too.
> I'm looking to get results in the form of "we should fix X and Y and Z
> and then lots more packages will work".
>
>
> Preparing MD5 and SHA crypt for integration
>
> See the threads on the list. Basically we need source with appropriate
> license status (MIT/BSD/permissive or public domain) that's optimized
> for size.
Did you take a look at tropicssl? It's an ssl lib (BSD license) used
in embedded systems.
But I'm not sure it's optimized for size.
>
>
> Regression testing
>
> This is a big project, but there are lots of things that can be done
> to contribute without doing it all. Basically it entails reading the
> git log, identifying all bugs fixed, and for each bug, formulating a
> test that reflects whether the bug exists or not.
next prev parent reply other threads:[~2012-08-19 8:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 4:26 Rich Felker
2012-08-19 8:10 ` idunham
2012-08-19 16:18 ` William Haddon
2012-08-19 8:44 ` boris brezillon [this message]
2012-08-19 11:49 ` Szabolcs Nagy
2012-08-19 16:56 ` Szabolcs Nagy
2012-08-19 17:29 ` Szabolcs Nagy
2012-08-20 0:51 ` Rich Felker
2012-08-20 1:35 ` Szabolcs Nagy
2012-08-20 1:39 ` Rich Felker
2012-08-20 1:58 ` Szabolcs Nagy
2012-08-20 2:12 ` Rich Felker
2012-08-28 20:09 ` Szabolcs Nagy
2012-08-28 23:35 ` Szabolcs Nagy
2012-08-29 0:15 ` Szabolcs Nagy
2012-08-29 14:30 ` Rich Felker
2012-08-29 15:14 ` Szabolcs Nagy
2012-08-29 17:01 ` Rich Felker
2012-08-30 8:40 ` Szabolcs Nagy
2012-08-19 21:46 idunham
2012-08-19 22:19 ` Gregor Richards
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='CAKAk8dbt6SG-0QdB0V6OrqWt_CyrZ_OL5CaN+1egzUind=5mCQ@mail.gmail.com' \
--to=b.brezillon.musl@gmail.com \
--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).