Hacker News new | ask | show | jobs
by ndhlms 1402 days ago
I don't see that any of those reasons are relevant, in all honesty.

1. This is not even a moderate ask; using ssh for git transactions is no more or less burdensome than https

2. As has been pointed out, there is no reason or reliable way to verify the identity of a creator's SSH key

3. Real-world example of such a project, or why this matters in the context of (2)?
1 comments
cmroanirgo 1402 days ago
> there is no ...reliable way to verify the identity of a creator's SSH key

GitHub exposes your public key via it's API. (Why? I have no idea. I call it a privacy violation) So, you need to create new github identity for every SSH identity that you wish to remain anonymous for, otherwise they just get tied together & one aspect of anonymity is lost.

link
ndhlms 1402 days ago
All that does is associate an arbitrary SSH key with a GitHub account. There is still no reliable way to verify the identity of the GitHub account owner, or the SSH key that account holder generated.

How does that expose any more information than you do by pushing a commit with a GitHub account?

link