On Wed, Jun 19, 2024 at 1:41 PM Kees Cook wrote:
>
> On Tue, Jun 18, 2024 at 03:39:44PM -0700, Jeff Xu wrote:
> > Hi
> >
> > Thanks for the patch !
> >
> > On Thu, Jun 13, 2024 at 6:40 AM Adrian Ratiu
> > wrote:
> > >
> > > Prior to v2.6.39 write access to /proc//mem was restricted,
> > > after
On Wednesday, June 19, 2024 23:41 EEST, Kees Cook wrote:
> On Tue, Jun 18, 2024 at 03:39:44PM -0700, Jeff Xu wrote:
> > Hi
> >
> > Thanks for the patch !
> >
> > On Thu, Jun 13, 2024 at 6:40 AM Adrian Ratiu
> > wrote:
> > >
> > > Prior to v2.6.39 write access to /proc//mem was restricted,
> >
On Tue, Jun 18, 2024 at 03:39:44PM -0700, Jeff Xu wrote:
> Hi
>
> Thanks for the patch !
>
> On Thu, Jun 13, 2024 at 6:40 AM Adrian Ratiu
> wrote:
> >
> > Prior to v2.6.39 write access to /proc//mem was restricted,
> > after which it got allowed in commit 198214a7ee50 ("proc: enable
> > writing
Hi
Thanks for the patch !
On Thu, Jun 13, 2024 at 6:40 AM Adrian Ratiu wrote:
>
> Prior to v2.6.39 write access to /proc//mem was restricted,
> after which it got allowed in commit 198214a7ee50 ("proc: enable
> writing to /proc/pid/mem"). Famous last words from that patch:
> "no longer a securit
On Thu, Jun 13, 2024 at 04:39:37PM +0300, Adrian Ratiu wrote:
> Prior to v2.6.39 write access to /proc//mem was restricted,
> after which it got allowed in commit 198214a7ee50 ("proc: enable
> writing to /proc/pid/mem"). Famous last words from that patch:
> "no longer a security hazard". :)
This v
Prior to v2.6.39 write access to /proc//mem was restricted,
after which it got allowed in commit 198214a7ee50 ("proc: enable
writing to /proc/pid/mem"). Famous last words from that patch:
"no longer a security hazard". :)
Afterwards exploits started causing drama like [1]. The exploits
using /proc
