From: Harald Becker <ralda@gmx.de>
To: musl@lists.openwall.com
Cc: Matt Johnston <matt@ucc.asn.au>
Subject: Re: Re: Security advisory for musl libc - stack-based buffer overflow in ipv6 literal parsing [CVE-2015-1817]
Date: Sat, 18 Apr 2015 17:49:51 +0200 [thread overview]
Message-ID: <55327D1F.5070807@gmx.de> (raw)
In-Reply-To: <20150418152542.GG6817@brightrain.aerifal.cx>
On 18.04.2015 17:25, Rich Felker wrote:
>> The server hostkey will remain in process
>> memory since it's required for rekeying - not as bad as root
>> code execution though.
>
> Ugly. I don't see how this can be solved without a more advanced
> privsep model. I agree it's lower-severity though.
IMO you may put the host keys in a file readable (not writable) with a
dropbear group, and only using that group for dropbear (no other users
or programs using that group). So you may read the keys even if not
root, if you add this dropbear group to setgroups (not setgid) before
dropping root privileges.
Harald
next prev parent reply other threads:[~2015-04-18 15:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 13:10 Matt Johnston
2015-04-17 17:23 ` Rich Felker
2015-04-17 18:03 ` Rich Felker
2015-04-17 18:09 ` Solar Designer
2015-04-18 13:32 ` Matt Johnston
2015-04-18 15:25 ` Rich Felker
2015-04-18 15:49 ` Harald Becker [this message]
2015-04-18 15:58 ` Rich Felker
2015-04-18 16:27 ` Harald Becker
2015-04-18 16:37 ` Rich Felker
2015-04-18 17:07 ` Harald Becker
2015-04-18 18:27 ` Laurent Bercot
2015-04-18 18:47 ` Harald Becker
2015-04-18 18:13 ` Harald Becker
2015-04-18 19:56 ` Rich Felker
2015-04-18 21:02 ` Laurent Bercot
2015-04-19 3:44 ` Rich Felker
2015-04-20 10:17 ` Harald Becker
2015-04-20 11:20 ` Kurt H Maier
2015-04-20 11:35 ` Harald Becker
2015-04-20 11:50 ` Harald Becker
2015-04-20 14:14 ` Kurt H Maier
2015-04-20 14:21 ` Harald Becker
2015-04-18 18:25 ` Harald Becker
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=55327D1F.5070807@gmx.de \
--to=ralda@gmx.de \
--cc=matt@ucc.asn.au \
--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).