You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your blog, it is very useful to help us understand this vulnerability. But there is a question about your comments mentioned in the blog.
In your comments, does the comment (Even with newer syscalls like openat2() you still need to mount(/proc/self/fd/X, /proc/self/fd/Y) to be race free, not sure how useful having a new mount flag to fail when one of the params is a symlink would be, but this is a huge footgun.) mean that some mount flags will be invalid if using '/proc/self/fd/X' as the parameter in the mount command?
Thanks!
The text was updated successfully, but these errors were encountered:
Greetings,
Thanks for your blog, it is very useful to help us understand this vulnerability. But there is a question about your comments mentioned in the blog.
In your comments, does the comment (
Even with newer syscalls like openat2() you still need to mount(/proc/self/fd/X, /proc/self/fd/Y) to be race free, not sure how useful having a new mount flag to fail when one of the params is a symlink would be, but this is a huge footgun.
) mean that some mount flags will be invalid if using '/proc/self/fd/X' as the parameter in the mount command?Thanks!
The text was updated successfully, but these errors were encountered: