I’m inclined to agree, as this was discussed on multiple occasions and seems to
fix a lot of the address re-use problems. With hot topics like “coin
validation”, I think it’s important to highlight the privacy that generating
fresh addresses from public extended keys grants us.
Also thinking ab
How does signing the commit message itself help at all since it just signs
the commit message, not the content of the commit. You could commit some
code then I. Then I squash my commits into yours and use your commit
message. You could also include the previous commit hash in your commit
message.
Hey Peter -
I think this is a super list. A couple of thoughts:
a) In the section on multi-sig and multi-factor, I think we can split these
apart. Multi-factor user authentication is very valuable and not the same
as multi-factor signing, which is a second level of complexity. The
multi-facto
On 19 December 2013 16:04, Amir Taaki wrote:
> About signing each commit, Linus advises against it:
>
> http://git.661346.n2.nabble.com/GPG-signing-for-git-commit-td2582986.html
Yeah, it makes no sense after reading it. Nice catch.
However, his recommendation for signing tags with `git tag -s`
4 matches
Mail list logo
