Repository navigation
fix(fleasion): trust Fleasion's CA on 2.746 and flag missing Sober - #92
Merged
Merged
Conversation
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.
Roblox 2.746 turns on DFFlagHttpUseEmbeddedCaCerts, which makes it use its built-in CA list and ignore cacert.pem. Fleasion's certificate never gets trusted, so every asset request fails TLS and nothing is replaced. With Fleasion enabled, Nightcap now sets that flag to False (fflags.json still wins).
On Linux, Fleasion's Env Proxy mode won't start unless Sober is installed, and nothing told users that. When the proxy isn't reachable and Sober isn't installed, the startup log and the Fleasion badge in Settings now say so. Also adds a short Fleasion section to the FAQ.