[haiku-commits] Re: haiku: hrev53362 - src/add-ons/kernel/drivers/graphics/radeon src/add-ons/kernel/drivers/graphics/3dfx src/add-ons/kernel/drivers/graphics/radeon_hd src/add-ons/kernel/drivers/graphics/neomagic headers/private/system
- From: waddlesplash <waddlesplash@xxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Tue, 13 Aug 2019 08:06:51 -0400
On Tue, Aug 13, 2019, 4:20 AM Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> wrote:
Am 10/08/2019 um 21:54 schrieb waddlesplash:
8a0c9d52c629: OS: Rename B_USER_CLONEABLE_AREA to B_CLONEABLE_AREA.
It now lives in OS.h. The idea is that this will now be
accessible to userland applications, so userland memory
is protected from access by other processes, just as
kernel memory is.
What's the point of this? For shared memory you now need this flag, but
it doesn't really improve security at all.
This makes it impossible for e.g. an application to clone the heap areas of
another application and, say, steal passwords, among many other things. So
I'm not sure what you mean here
What we'd need is to specify who can clone this area -- but doing so
would already imply that one wants it cloneable in the first place.
Yes, that would be the next step; but it would be pretty involved so I have
no plans to do it in the near future; the syscalls audit is probably more
significant for now.
Other related posts: