On 2026/10/28 21:37, Stuart Henderson wrote: > On 2026/10/28 21:18, Jeremie Courreges-Anglas wrote: > > On Wed, Oct 28, 2026 at 12:14:29PM +0100, Matthieu Herrb wrote: > > > On Wed, Oct 28, 2026 at 10:22:00AM +0100, Dirk-Wilhelm Peters wrote: > > > > I have just found out by accident that xlock leaves its door slightly > > > > ajar when using the marquee mode with a custom message: > > > > > > > > xlock -mode marquee -message "hack me" > > > > > > > > Simply type a few random characters to get back in. > > > > > > > > Abort trap > > > > > > > > This worked on several amd64 machines running 8.0 and 8.0-current. > > > > > > > > > > This is a undefined behaviour of memcpy() on overlapping buffers. This > > > patch should fix it. > > > > I'm not a fan of memcpy aborting... I strongly suspect that everybody > > else has a lenient memcpy (read: that behaves like memmove). > > AFAIK glibc (after some version) on x86-64 doesn't handle overlaps.
... https://www.man7.org/linux/man-pages/man3/memcpy.3.html
