Add ChromeKeePass to the list of allowed origins for native messaging #102
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.
ChromeKeePass is adding support for communication with KeePass via KeePassNatMsg in RoelVB/ChromeKeePass#93
In order for this to work, the extension needs to be added to the allowed hosts of the native messaging configuration file, otherwise Chrome and Edge will not open the native messaging channel.
The extension can be found in the Chrome web store (although the latest version there doesn't have the native messaging support yet).
I don't have a setup to compile these changes at the moment, so I can't actually verify that this works, but it seemed like a simple enough change. I added these lines to the extracted files on my system manually and verified that ChromeKeePass was able to communicate with KeePassNatMsg.