Feature: ability to turn off lastmodified and mac

I believe my organization's use-case is quite common: using sops to encrypt secrets to store them in git.

This poses a scalability challenge: If two PRs edit the file, the latter one will have merge conflicts.

One way to mitigate this is to split up the files. We don't want to do this!

If we had the ability to turn off lastmodified and mac, PRs would only have merge conflicts if they modified the same keys.

I think these two fields are unnecessary for our use-case:

• lastmodified can be determined in git history
• modifications are code-reviewed, so detecting fraudulent modifications feels out of scope for this use-case. There is one threat model that sticks out here: a git user who doesn't have access to the encryption key is able to create a pull request that uses old encrypted values, and can also swap values between keys.

Start by locating the handling of the lastmodified and mac fields and the existing configuration or command entry points for optional behavior. Define how users would disable each field, then verify that encrypted files omit them while still working for the stated Git merge-conflict use case and preserving the documented threat-model expectations.