Well, the main reason why we disallow email login is for mitigating spamming. GitHub account association also provides some reputation reference in R&D community. (And considering dogfooding Ethereum account login in the future)
I don’t think you can set password now. If you want to hide your main email/GitHub info, you could register a new GitHub account for ethresear.ch.
Sorry it’s not perfect, but IMO it’s not good to enable email login in ethresear.ch.
Hi, this is my first reply, hope it can be helpful.
As @hwwhww mentioned, there is no way you can set a password; but you still can recover access to the profile after cookie expiration.
The way to proceed would be creating a new GitHub account for the newly set “primary email” in your forum profile. You can access your profile using those GitHub credentials. This way you didn’t need to create an extra profile and still succeed to remove any trace of your main GitHub account.
To achieve privacy when creating a ethresear.ch profile just use a fresh email with a fresh GitHub account.
My session is still alive! Woohoo, clearly living on the edge here. Tbh, as some might have guessed, I didn’t really expect to receive a solution here. I just wanted to highlight that the current system seems inefficient.
Given how easy it is to create a separate GitHub account for registration here, what is the purpose of enforcing GitHub in the first place? If it’s for reputation purposes, then you shouldn’t be allowed to disassociate your GitHub again, and you should enforce a certain minimum GitHub account age or a certain minimum number of GitHub contributions.
The current system doesn’t protect us from anything. Instead, I only see negative outcomes:
People who don’t want all their profiles across the Internet correlated are forced to go through the extra step of setting up a throwaway GitHub account (it takes time to set up and secure) — there is a reason why people set their GitHub email to private
People who don’t have time to do that may need to unnecessarily sacrifice OpSec against their will
People who don’t know yet what they want are by default directed into a non-privacy maximizing choice and the use of single-sign on is wrongly presented to them as a best practice (by a reputable community)
Given the increasing scrutiny from all sides, we should all try to become less traceable, not more traceable. At least, you should allow the people who care to minimize their attack surface.
These topics were discussed here alongside with the EAuth implementation.
@hwwhww Are spamming and impersonator attacks the only reasons for disallowing email login? Did we have bad experiences with this before? How is ethereum-magicians managing these issues while allowing email login?
I agree on maximizing non-traceability and would like to point out two more implications of the GitHub login only: UX and security.
I believe that it is fair to say that a significant amount of potential users fall under a) don’t have an GitHub account or b) have a completely inactive GitHub account. For these users the lack of 2FA results on poor UX, of course, but also they are more likely to give up on security as they are probably less willing to set up and secure a GitHub account they don’t use.
On the other hand, in my personal experience as a GitHub user, the UX of the current system feels super smooth.
The advantages of having email login and GitHub auth would be:
Privacy for those who don’t want their profile to be associated with their GitHub.
More balanced UX.
For the current GitHub only system we have the following:
A worst UX and security for non-GitHub-users.
A better UX for GitHub users.
Protection against spam and impersonator attacks.
Is there a way to point to the GitHub account without using email as primary key? If this is non-trivial to make, we can’t enforce users to stick with one GitHub account since GitHub email can be changed.
When it comes to EAuth implementation we are still facing the same privacy issues, as the idea would be enabling to sign up with ENS but requiring to associate a GitHub account with it. (Still excited about EAuth though!)