Sometimes, when you want to undo things (for example with reset --hard),
it's useful to have something that tells you where to go back to in
order to undo a certain action. If all messages look the same that's
harder to do.
Also, even if the user carelessly wrote a message that gives a clue
about the file content, that would be the user's fault and it would have
nothing to do with the ability to manually edit commit messages. Not to
mention that even with a clue in the commit message, a malicious party
still couldn't do much without the user's private key.
At least that's my view on this. If I'm being too disingenuous then I'm
sorry. I can live without this after all.
Kind regards,
Gianluca
On 2/29/20 5:09 PM, Tobias Girstmair wrote:
On Sat, Feb 29, 2020 at 01:28:11PM +0100, Gianluca Recchia wrote:
the default commit message is often not very descriptive of the
change I made to an entry and I often find myself having to amend the
commit in order to change the message.
What kind of information are you putting in there, that you don't want
within the encrypted file? I'm not sure it is a good idea to
encourage detailed commit messages, since they might be an information
leak.
_______________________________________________
Password-Store mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/password-store
_______________________________________________
Password-Store mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/password-store
