FS#15749 - [namcap] Check for static library permissions is too strict

Attached to Project: Arch Linux
Opened by Jan de Groot (JGC) - Saturday, 01 August 2009, 13:21 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 24 February 2010, 04:08 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Hugo Doria (hdoria)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When namcapping e2fsprogs, it complains that the library permissions for *.a are not 644. The library permissions are 444, which does not look wrong to me. I think the check should test for both 444 and 644. The file should always be readable to everyone, and should never have execute permissions.
This task depends upon

Closed by  Dan McGee (toofishes)
Wednesday, 24 February 2010, 04:08 GMT
Reason for closing:  Implemented
Additional comments about closing:  Implemented in git, coming your way soon
Comment by Abhishek Dasgupta (abhidg) - Sunday, 02 August 2009, 10:16 GMT
I suppose 444 is okay, but any particular reason for not making it writable by root?
Comment by Jan de Groot (JGC) - Sunday, 02 August 2009, 10:28 GMT
That's how upstream installs it, you should ask them for reasoning. Root will be able to write it anyways though.

Loading...