[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240715233232.pwHkh7Qt@steffen%sdaoden.eu>
Date: Tue, 16 Jul 2024 01:32:32 +0200
From: Steffen Nurpmeso <steffen@...oden.eu>
To: oss-security@...ts.openwall.com
Subject: Re: ASLRn't is still alive and well on x86
kernels, despite CVE-2024-26621 patch
Demi Marie Obenour wrote in
<ZpRSEWkkG6hmNhNo@...-email>:
|On Sat, Jul 13, 2024 at 10:58:58PM +0200, Steffen Nurpmeso wrote:
|> Jacob Bachmeyer wrote in
|> <6691E39C.8090600@...il.com>:
|>|Steffen Nurpmeso wrote:
|>|> [...]
...
|> Some findings:
...
|> . I always whimper when i have to rm(1) a running executable before
|> placing an updated variant on Linux, on BSDs i simply over-cp(1)
|> (and i do not understand as long as one gets either the one or
|> the other when executing the path).
...
|> But it is ok to me, Linux is as it is[.]
|
|Executable files and shared libraries should _never_ be modified
|in-place. They should _always_ be renamed over. Otherwise, a program
|might be a mixture of the old and new version, with completely undefined
|results when the program is run.
So i am thankful i get this translucent impression of my Linux box
and henceforth always use cp -f there, and cp on BSDs.
Or is this a hint to GNU coreutils?
(I rather would prefer either the one or the other, but not
a messed up copy. Is that what they are doing?)
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
