Below the list of hints and tricks related to privacy which help you to start using Fossa Guard:
- understanding authentication and authorization details
- avoid common issues and misunderstandings
Chrome extension isolation
During installation, a dedicated copy of a Chrome extension for each Google user is copied into the corresponding Operating System (OS) user's space including a dedicated storage instance. Please refer to Technical details about Chrome extension.
Extension installationSometimes the extension is installed with incorrect Extension ID which is used as a credential to access Google APIs, so that User can get the following error
Note that Fossa Guard extensions have the following static Extension IDs (can be verified in Chrome Web Store):
Please contact firstname.lastname@example.org if your Fossa Guard extension installation has the wrong Extension ID on your machine.
At first usage time, Fossa Guard requests a formal user's approval to use permissions needed to call Google APIs on a user's behalf.
If User didn't give the permissions requested the following error will be displayed:
The given permissions can be reviewed and revoked (if necessary) via Google Account portal.
From time to time a new version of the extension is being released and automatically updated by Chrome. Once the extension updated User has to refresh the Gmail page to continue with a new version of the extension.
Extension not yet loaded
Google identity and Private Key accessFossa Guard uses the current Chrome logged user as a primary Google identity to authorize the private key access and certificate management following the extension isolation approach defined in the previous chapter meaning that each extension instance operates with the private key related to the single Google account.
It means that the Chrome user should be logged in and synchronization should be turned on to make Fossa Guard extension to grant access to the private key and certificates.
Chrome user vs Gmail userSince Fossa Guard uses the identity of the currently logged Chrome user it considers that User should operate within the corresponding Gmail mailbox. If a User would try to use different Gmail mailbox Fossa Guard notifies about it.
To use a particular mailbox, the User has to login to Chrome with the corresponding account so that Chrome's extension isolation mechanism will be applied to establish the private key security.