Repository navigation
Enable OpenSSL legacy provider for Pandora (refs #451) - #577
Merged
Merged
Conversation
…e server anesidora decrypts Pandora's sync time with bf-ecb, which OpenSSL 3 disables. The throw is uncaught, so the process dies and clients get an empty reply. Refs #451
This file contains hidden or 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.
anesidora decrypts Pandora's sync time with Blowfish (bf-ecb), which OpenSSL 3 puts in its legacy provider. createDecipheriv throws 'unsupported' inside a request callback, nothing catches it, and the server dies (empty reply to the client).
Sets NODE_OPTIONS=--openssl-legacy-provider. Verified in isolation on Node 24 and 26 that the Blowfish call works with the flag and fails without. Could not verify a live Pandora login (Pandora returns error 12 to a fake login before the decrypt step).
Refs #451