Re: [PATCH v4 1/1] exec: seal system mappings

2025-01-02 Thread Andrei Vagin
On Tue, Dec 17, 2024 at 2:18 PM Kees Cook wrote: > > Also from discussions it sounds like there may need to be even finer-gain > control, likely via prctl, for dealing with the CRIU case. The proposal > is to provide an opt-out prctl with CAP_CHECKPOINT_RESTORE? I think this > is reasonable a

Re: [PATCH v4 1/1] exec: seal system mappings

2024-12-12 Thread Andrei Vagin
On Wed, Dec 11, 2024 at 2:47 PM Jeff Xu wrote: > > Hi Andrei > > Thanks for your email. > I was hoping to get some feedback from CRIU devs, and happy to see you > reaching out.. > ... > I have been thinking of other alternatives, but those would require > more understanding on CRIU use cases. > On

Re: [PATCH v4 1/1] exec: seal system mappings

2024-12-09 Thread Andrei Vagin
On Mon, Nov 25, 2024 at 12:49 PM wrote: > > From: Jeff Xu > > Seal vdso, vvar, sigpage, uprobes and vsyscall. > > Those mappings are readonly or executable only, sealing can protect > them from ever changing or unmapped during the life time of the process. > For complete descriptions of memory se