Leaks personal details / email addresses

[cjb]

Leaks personal details / email addresses

[cjb]

@mcorb Thanks for the report. I agree with you, so I just pushed an update that removes name/email altogether until we can think about this more. (It still publishes a mutable key, but without identifying values.)

[mcorb]

I concur that removing the code entirely is the best course of action for now. Thanks for the quick patch and point release.

[phuicy]

How about hashing them instead of removing them? so that there is the possibility of identifying pushes, but safe.

[mcorb]

@phuicy It would be prudent to first implement pushes to get a better idea of how things will fit together.

Hashes aren't a strong solution in this space. A desktop computer could hash every public committer ID known to GitHub in a matter of seconds and use that to look up the 'secret' identity trivially, so it wouldn't add much.

I think @cjb wrote about more advanced techniques of identity proof in his blog -- perhaps I'm feeling a little edgy because my details got leaked (my fault, I didn't use a sandbox or throwaway account and this is pre-alpha code), but I'm really comfortable delaying identity work a little bit and helping out with the more interesting problems that need to be solved first on the transport and pack efficiency side, after which the solutions will be clearer.

[phuicy]

That would require a publicly access-able username and email first. So whats the issue.
If you wanted to hide your id you still could!

Although, I agree it should be delayed until pushes have been sorted.