memfd_secret() in 5.14
memfd_secret() in 5.14
Posted Aug 7, 2021 10:23 UTC (Sat) by khim (subscriber, #9252)In reply to: memfd_secret() in 5.14 by mb
Parent article: memfd_secret() in 5.14
> They also will press the "more security" button 0 times out of 10.
Indeed. That's why the only way to introduce new security feature is with “more security” choice being the only option. Users pick “more security” option quite easily if the alternative is not mere knob, but patch to the kernel, recompilation and other hassle of such level.
> This feature won't experience widespread use.Why do you think so? I would expect that DRM-providers would adopt it quickly. Then VPNs and remote access apps would demand it. Then, eventually, Chrome and Firefox would join the crowd.
At that point it would become a moot point if you want to use hibernation or not: you system wouldn't be much useful if you would choose the hibernation. Although I expect that the ability to empty that security memory before hibernation would be adopted instead, but maybe not. I'm not really sure how useful hibernation is today. I don't use it thus I don't care.
> I don't care, if there are keys in kernel memory.But I do care, if hibernation stops working as soon as some random app starts using memfd_secret().
And that's exactly and precisely why hibernation shouldn't be allowed to be used when memfd_secret is used. You don't care about security of memfd_secret() — and other users feel the same. Which means application developers couldn't rely on it. And if application developers couldn't rely on it then why is it there in the first place?
