|
|
|
|
|
by qqii
2241 days ago
|
|
I'm not endorsing keybase, in fact I have much of the same criticisms as you probably do. The fact is unlike many PGP replacements most don't attempt to solve similar ideas as the "web of trust". For those that I know do, the cryptocurrency/tokens one's don't even consider backwards compatability. As far as I know keybase are the only ones that embrace PGP and are therefore backwards compatible with git, fossil, etc's commit signing. It may be ignorance but I don't see linux, git or any other software project that "needs" both version control and verifiable commits moving from PGP signing to something else, but rather PGP signing dying out with the rise of git platforms like github, gitlab, etc. If you squint you can see that keybase provides some form of alternative. |
|
Git patch workflow doesn't support signed commits and some kernel devs explore alternative ways of signing [1].
[0]: https://mikegerwitz.com/2012/05/a-git-horror-story-repositor...
[1]: https://people.kernel.org/monsieuricon/introducing-b4-and-pa...
By "keybase providing alternative" do you mean that they have hosted, encrypted git repos?