Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

drop social authentication #3837

Closed
chadwhitacre opened this issue Oct 20, 2015 · 6 comments
Closed

drop social authentication #3837

chadwhitacre opened this issue Oct 20, 2015 · 6 comments
Labels

Comments

@chadwhitacre
Copy link
Contributor

Reticketed from #1052 and #3604.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@mattbk
Copy link
Contributor

mattbk commented Oct 22, 2015

Switching to email/password or Medium authentication, or drop all social network links?

@chadwhitacre
Copy link
Contributor Author

The proposal here is that we no longer allow people to use Facebook, Twitter, etc. to sign in to Gratipay. I think it's fine to support linking social accounts to one's Gratipay profile once you're signed in, but we'd only accept email to sign in.

@ghost
Copy link

ghost commented Aug 10, 2016

Bountysource

@Changaco
Copy link
Contributor

(Anyone willing to implement password auth in Gratipay might want to take a look at how it's done in Liberapay: authentication.py, participant.py, etc.)

@EdOverflow
Copy link
Contributor

I would recommend using bcrypt instead of PBKDF2 for password hashing, because the latter can be better accelerated with GPUs. There is a well maintained implementation of bcrypt by PyCA: https://github.com/pyca/bcrypt.

@chadwhitacre
Copy link
Contributor Author

chadwhitacre commented Jun 2, 2017

@rohitpaulk is -1

I like the ease of social logins

slack

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants