Menu

#49 Set file permissions correctly

open
nobody
None
5
2020-07-31
2020-07-31
Brook
No

When compiling openjade 1.3.2 the permissions are not set correctly by chmod -w. Presumably the intent is to remove all write permissions. However, because nothing precedes the '-', this does not affect bits set in umask. Here is the relevant section of the chmod(1) man page:

A combination of the letters ugoa controls which users' access to the file will be changed: the user who owns it (u), other users in the file's group (g), other users not in the file's group (o), or all users (a). If none of these are given, the effect is as if a were given, but bits that are set in the umask are not affected.

The correct invocation of chmod identifies the users explicitly. The attached patches fix this.

2 Attachments

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.