Add profile for checksum tools

[rusty-snake]

Someone told me that md5 is insecure, so I decided it is better to sandbox it so that is can be used securely. 🙃

---

hasher-common.profile is based on archiver-common.profile.

[glitsj16]

Just a few occurences of archiver-common.local that need changing to hasher-common.local and this is good to go. Very nice additions!

[netblue30]

What if we put "quiet" at the top of all of them and add them to firecfg.config?

[rusty-snake]

quiet should be added in any way. I am unsure about firecfg, @glitsj16 what's your opinion?

[netblue30]

I am unsure about firecfg

It could be a problem when they run it from scripts. It will slow down if they do it in a loop on large number of files, for example a package manager comparing checksums - we introduce about 50 ms to start each sandbox.

[glitsj16]

I am unsure about firecfg

It could be a problem when they run it from scripts. It will slow down if they do it in a loop on large number of files, for example a package manager comparing checksums - we introduce about 50 ms to start each sandbox.

Package management indeed poses a bit of a problem for these checksum tools, as do archivers (see #3095). I guess not all firejail users do a lot of manual/scripted package building, activities where this inherent slowing down factor quickly turns into a nuissance. Those that do are probably more aware of this and have the skills to work around it. By leaving them out of firecfg we tend to disfavour the first set of users. For the occasional checksumming outside of package management it would be nice to add them. What about adding a setting in firejail.config so users can have more control over their preference. That setting would have to be tied into firecfg to keep things from breaking, and in all honesty I haven't looked into the feasibility of doing that.

[glitsj16]

Oops, I didn't want to close this!

[netblue30]

OK, let's grab it as is, I'll put quiet in all of them. Thanks!

[netblue30]

sorry, quiet was already there!