Date: Sun, 30 Dec 2018 01:46:28 +0000
To: "steffen@sdaoden.eu" <steffen@sdaoden.eu>
From: Phil Hofer <phil@sunfi.sh>
Cc: "alpine-devel@lists.alpinelinux.org" <alpine-devel@lists.alpinelinux.org>
Reply-To: Phil Hofer <phil@sunfi.sh>
Subject: [alpine-devel] Re: openrc crashes
Message-ID: <F9zS9AxnlZczhqhPenmGcQsk5Kbp-FOF-1hFiyUW2Phwc4FbTe-mtNPr9KVaC8LBT2AochKodG2j5RxEO14BJAmrjxe6jR5nNcQ6FkMc__U=@sunfi.sh>
Feedback-ID: KQYgXwW95KZKFtdKXbDLp7uXG-WRoO_GBxBXScjXQTnH4hk8IX5tVgVB60E7xVGeWaFgWV0KxGB7LiMdLyDAuw==:Ext:ProtonMail
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Steffen,

I ran into some crashes in openrc recently as well.
(Once I ran my reproducer in gdb, I saw that openrc was tripping
the stack-smashing protector.)

I went through the source and made some reliability fixes,
which have now been committed upstream:

846e46 -- fix 4 out-of-bounds reads
084877 -- fix stack buffer overrun (my issue)
a9fc26 -- fix NULL dereference

Try building the latest version of openrc and see
if your issues persist. (You'll have to take some patches
from aports in order for it to build cleanly, or you
can build from my aports tree:
https://github.com/philhofer/aports/tree/master/main/openrc)

If you're able to reproduce a crash locally, run the
reproducer under gdb and see if you can at least grab
a stack trace. Building with some hardening options turned
on will help crash the program closer to the memory corruption.

- Phil


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---