nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqrsjjkguerepp3dmh7xw5rnvckvz56hseuu5444aql6d7cfmwpatqncfpdh
> I definitely wouldn't trust single file encryption too much if the threat is diffe...
@nprofile1q... @nprofile1q...
I'm not UnePorte, but wanted to say something similar in response to your original question (that the threat model matters a lot here).
Consider attackers who can modify the encrypted file. Do you want to ensure that the file is not some weird mixture of the contents you wanted and contents the attacker put there (this particular property is ensured by `age`)? Do you want to be able to ensure that the file is not wholesale replaced by the attacker in a way that allows the attacker to control its contents? If you have two such encrypted files, do you want to ensure the attacker didn't swap them?
I'm not UnePorte, but wanted to say something similar in response to your original question (that the threat model matters a lot here).
Consider attackers who can modify the encrypted file. Do you want to ensure that the file is not some weird mixture of the contents you wanted and contents the attacker put there (this particular property is ensured by `age`)? Do you want to be able to ensure that the file is not wholesale replaced by the attacker in a way that allows the attacker to control its contents? If you have two such encrypted files, do you want to ensure the attacker didn't swap them?
1