Well said, there is no catchy name for this (virtual) security threat. We will have to let one of those that oppose this proposal to find a caching name (PATHEXIT?), maybe even build a paper explaining how to mitigate it.
I am bit disappointed because other distributions fixed it, even twice after a temporary regression due to a mistake. We never did it. Now that we have a change proposal, how to continue? To get it accepted or rejected, is there a way/process that we need to follow? Should we maybe add a section to the document with supporters and opposers where people can record themselves? Thanks Sorin
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/VXFYSGI372TMRE5YRATKR4SKV4LXOMDV/
