Re:GitHub's email correlation for authorship
by petercooper on Wednesday May 12, 2010 @06:59PM
(#1342564)
It's on a par with using a forged From header over SMTP. You can send e-mail as pretty much anyone. (Though technologies like SPF are helping clamp down on this.)
"Joe jobbing" is when spammers use real e-mail addresses in their From headers so that that person gets the flak. In a round about way, this is the same for patches/commits :-)
Re:GitHub's email correlation for authorship
by jackowayed on Wednesday May 12, 2010 @07:06PM
(#1342587)
He changed his git config so that user.email was [email protected] (The email DHH lists on GitHub). GitHub then automatically says "oh, this is by [email protected], so let's put his avatar there and link to his profile as the author."
Changing the config is as simple as
git config user.email "[email protected]"
And you can add a --global flag if you want that to be the default for all repos instead of just the one you're on.Edit: There's also some way to do it with a --author= flag when you commit.
Re:GitHub's email correlation for authorship
by clemesha on Wednesday May 12, 2010 @06:52PM
(#1342544)
You have it correct. What you say in your second sentence is exactly the issue.
If this is "actually" a big issue or not is another question.
Re:GitHub's email correlation for authorship
by technoweenie on Thursday May 13, 2010 @02:35PM
(#1345173)
Sure, all it does is links the commit to a github login. It doesn't somehow give you access to any data that's not yours. You've just discovered another way to post spam.
So, you aren't 'dhh' but you commited using his email address and it showed up as him?