Le vendredi 22 mai 2020 à 10:30 -0400, Steve Grubb a écrit : > The /usr/share hierarchy is for all read-only architecture > independent data > files. The important part of the FHS definition is “read-only architecture independent“. Because everything on computing storage is data depending on how you look at it. Practically, people have been putting “read-only architecture independent“ executable data in /usr/share forever. Not just javascript. Java bytecode, xslt programs, scheme programs, go code, etc (in the Java & Go cases I’ve also seen architecture dependant data leak in here, though I intend to fix the leaking oneway or another in the next generation of Go packaging). If you want to split hairs we also install fonts there, and OpenType fonts contain instructions that will be executed by the text renderer, and malicious fonts have triggered security problems in the past. So, no use looking for non-executable /usr/share. A lot of /usr/share is executable and will stay that way. Regards, -- Nicolas Mailhot _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
