From: Vasiliy Kulikov <segoon@openwall.com>
To: musl@lists.openwall.com
Subject: Re: holywar: malloc() vs. OOM
Date: Sun, 24 Jul 2011 22:33:41 +0400 [thread overview]
Message-ID: <20110724183341.GC6429@albatros> (raw)
In-Reply-To: <20110724132704.GK132@brightrain.aerifal.cx>
On Sun, Jul 24, 2011 at 09:27 -0400, Rich Felker wrote:
> > it could "fix" deprecated/dangerous calls
> > (maybe turn them into compiletime errors)
> > and things like oom failures into runtime errors
> >
> > so bad code can be compiled against this radical extremist libc
>
> The only problem I see is that it only catches "known bad" code.
Sure, as almost any workaround of API misdesign.
> As an
> admin I would be inclined to simply look for another program that
> performs the function I need, rather than trying to compile in
> workarounds, if I knew a program had code that bad..
It depends on the requirements and level of paranoia :) It could be the
only program in the required programs class. It could be the only
program you may use for non-technical reasons. Other programs could be
not much better (re: desktop). In the ideal world any hardening would be
redundant ;)
--
Vasiliy
next prev parent reply other threads:[~2011-07-24 18:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 10:33 Vasiliy Kulikov
2011-07-24 12:40 ` Rich Felker
2011-07-24 13:29 ` Szabolcs Nagy
2011-07-24 13:27 ` Rich Felker
2011-07-24 18:33 ` Vasiliy Kulikov [this message]
2011-07-24 22:24 ` Rich Felker
2011-07-24 18:25 ` Vasiliy Kulikov
2011-07-24 22:19 ` Rich Felker
2011-07-25 17:43 ` Vasiliy Kulikov
2011-07-25 19:21 ` Rich Felker
2011-07-24 12:44 ` Szabolcs Nagy
2011-07-24 12:53 ` Szabolcs Nagy
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=20110724183341.GC6429@albatros \
--to=segoon@openwall.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).