Update cookie_monster.c to be compatible with chrome 144+#1
Open
g-slashsec wants to merge 1 commit intortecCyberSec:mainfrom
Open
Update cookie_monster.c to be compatible with chrome 144+#1g-slashsec wants to merge 1 commit intortecCyberSec:mainfrom
g-slashsec wants to merge 1 commit intortecCyberSec:mainfrom
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
1 participant
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.
Chrome 144+ added a new COM interface to the elevator_service. Currently this is an exact copy of the old IElevetor interface but it has a new CLSID. According to relevant commit (chromium/chromium@4962049) there will be additional changes but for now using the new CLSID is sufficiant.
I quickly implemented a fallback in case the browser has been updated and is using the new implementation. This way cookie_monster should be compatible with both v127-143 and 144+.
According to the release notes of another project (https://github.com/xaitax/Chrome-App-Bound-Encryption-Decryption/releases/tag/v0.18.0), edge should remain the same, and the same changes are expected for brave as well.