Authenticate using enc_pass over plain text pass (fixes #121) #122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue here is that Facebook changed their authentication rules.
We've been sending the password using pass in plaintext (but over HTTPS so still secure) so far.
Facebook no longer allows this (which means it completely breaks Facebook for people using no Javascript browsers!).
Instead, Facebook is now enforcing we pass a enc_pass encrypted version of the password which they first started using around 2019 but it wasn't enforced like it is now.
Thankfully, other people like @lorenzodifuccia have already done the hard work to generate this encrypted password.
https://gist.github.com/lorenzodifuccia/c857afa47ede66db852e6a25c0a1a027