Add Setting To No Longer Force Lock Files to have 777 Permissions in Linux

[delvecccims]

Summary

During a scan of our Linux servers, there were some lock files that were flagged for having World Writable permissions in the temporary directory. It looks like this was changed in February as part of #11328.

There was a question about the security concerns from this change in #12665, but there hasn't been a comment yet regarding it. Would it be possible to have a setting that can be enabled to ignore this change so that umask can set the permissions appropriately so that these lock files are no longer flagged in our scans for having World Writable permissions?

Example

No response

[konstin]

This sounds like a false positive in the security scanner. We use files to coordinate between different processes, which often run with different permissions, e.g. from different containers that mount the same volume. These files are empty and uv doesn't read from them.