Sunday, June 28, 2020

Fossa Guard Pro 1.0 improvements


Roboto font

  • Roboto font has been introduced as a default font to be aligned with the overall Gmail appearance.

Compose / View dialogs

  • Fossa Guard Compose / View dialogs can be minimized by the click on the header not to block creating and viewing other S/MIME emails.



  • Minimized Compose / View dialogs are represented as bars at the bottom of the Gmail window and can be restored by the click on the subject or closed by the click on the cross icon.

Search Index



  • Search index size is presented in the form of a bar indicating the amount of available space.


Informational warnings for error cases


  • Informational alerts and warnings have been added for extension invalidation, user authentication, authorization, and synchronization errors.

See detailed article on the point: http://fossaguard.blogspot.com/2020/03/fossa-guard-authentication-and.html

Recipient certificate details and status

Recipients are presented by the pillows indicating the status of user certificate by the color and the corresponding icon, considering:

  • Green - there is at least one valid certificate for the email address
  • Red - there is at least one invalid certificate for the email address
  • Grey - there is no certificate for the email address



Click on the recipient's pillow opens `Recipient Details` popup with the information from the Contacts (photo, name, email) and list of certificates found in the local Chrome extension storage. There are in-place options to

  • Load certificate from the file
  • Load certificate from Fossa registry


Click on the certificate info opens `Certificate Details` popup displaying the internal information of the selected certificate.


    Fossa Guard Pro 1.0 released

    27 of June 2020

    Glad to announce Fossa Guard Pro 1.0 commercial release is available at https://chrome.google.com/webstore/detail/fossaguardpro-encrypt-gma/opfepnmdnnmiiemnkhaneagicmlakdjh


    S/MIME end-to-end encryption Chrome extension for Gmail with
    • S/MIME formats supported (including attachments)
      • Sign
      • Encrypt
      • Sign-then-Encrypt
    • Constant pricing about $1.99 per month 
    • Interoperability tested with
      • Outlook
      • Thunderbird
    Release details should come in further articles on this blog.

    Future plans 

    • Triple wrapping: Sign-then-Encrypt-then-Sign considering 2 private keys
    • Firefox, Opera, Yandex browsers support  
    • Mobile Gmail web version support

    Wednesday, April 1, 2020

    S/MIME signed messages support in Gmail

    From RFC5751 

    "There are two formats for signed messages defined for S/MIME:

    • application/pkcs7-mime with SignedData
    • multipart/signed.

    In general, the multipart/signed form is preferred for sending, and receiving agents MUST be able to handle both."

    As per 1st of April, 2020 the situation with S/MIME signed messages support for free Gmail accounts is as following:

    multipart/signed

    • Gmail to Gmail: NOK  (since 2013)
    • Gmail to External Mail: NOK (since 2013)
    • External Mail to Gmail: OK 

    application/pkcs7-mime with SignedData

    • Gmail to Gmail: NOK (since 2017)
    • Gmail to External Mail: OK
    • External Mail to Gmail: OK 

    NOK means Gmail service mangles a message in transit by:
    • repacking MIME entities and changing boundaries
    • changing the content type of the message to multipart/mixed
    • restricting access to S/MIME signature for multipart/signed messages

    The history of the above points:

    Sunday, March 22, 2020

    Fossa Guard authentication and authorization error cases

    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 installation

    Sometimes 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
    The detailed information about installed extensions can be found at chrome://extensions.


    Note that Fossa Guard extensions have the following static Extension IDs (can be verified in Chrome Web Store):


    Please contact support@fossa.me if your Fossa Guard extension installation has the wrong Extension ID on your machine.

    Extension permissions 

    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.


    Extension update

    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

    Gmail tends to be a quite heavy web application and requires a remarkable time to load all installed extensions, add-ins. When User tries to invoke Fossa Guard functionality when it' snot yet loaded onto the Gmail the following notification can be displayed:

    Google identity and Private Key access

    Fossa 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 will be notified about the necessity to log and to synchronize the account.

    Chrome user vs Gmail user

    Since 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.

    Privacy policy

    Fossa Team has quite detailed and formal Fossa privacy policy with the main statement that the Fossa solution has been designed with the only main goal to supply Gmail users with privacy via industry-grade email encryption (S/MIME) integrated into the web browser.

    Friday, March 6, 2020

    Technical details about Chrome extension

    Installation 

    During the installation on Windows 10 Chrome extension artifacts are copied into the folder for default Chrome account:
    C:\Users\<Windows Login>\AppData\Local\Google\Chrome\User Data\Default

    Note that if Windows user has several Chrome accounts, each Chrome account has its own set of installed extensions with root located at
    C:\Users\<Windows Login>\AppData\Local\Google\Chrome\User Data\Profile<N>

    Source files 

    Source files of Chrome extension are stored in the sub-folder named after the id and the version of the extension:
    ...\Extensions\<Extension ID>\<Extension Version>\

    Local Storage

    Local storage of Chrome extensions is stored at the: 
    ...\Local Extension Settings\<Extension ID>\


    Note that: 

    • local storage is isolated from common Chrome storages: Local, Session or IndexedDB
    • local storage can be accessed only from the corresponding Chrome account using Developer Tools
    • local storage has levelDb format 

    State Management

    Navigate to chrome://extensions to manage extensions for the currently logged Chrome user.

    User can:

    • Enable / Disable extension
    • Update / Refresh
    • Remove
    • Navigate to Background page (Developer mode) 
    • Review Errors log (Developer mode)

    Using Developer mode one can install extensions from not only Chrome Web Store but from a local drive as well using 'Load unpacked'.

    Components


    Fossa Guard extension consists of 3 main components linked via messaging

    • Content script operates on Gmail page in the dedicated iframe, communicates with Gmail via DOM messages, observing DOM events, communicates with Background Script via Chrome messages.
    • Settings page provides user UI to manage certificates and keys
    • Background script is responsible for cryptography, uses with extension storages and communicates external services via http(s) calls.







    Monday, February 24, 2020

    Reply and Forward in S/MIME format

    From V0.1.17 Fossa Guard Pro enables Reply All, Reply and Forward for plain-text messages via the dedicated bar on top of each email.

    When clicked, it opens FossaGuard compose dialog with the content of the selected email and the options to encrypt and to sign the replied (forwarded) message.

    You should click on the email to view content to be able to access the bar and reply (or forward) the specific email from the thread.

    Auto-indexing option

    Starting from V0.1.17 Fossa Guard Pro supports the option to auto-index S/MIME emails during reading meaning that the search index is auto-updated.

    Emails that are left unread can be indexed manually by clicking `Refresh` link it actualize the index from last update time up to the current time.
    Note that the search index is limited by extension local storage size quota around 5Mb https://developer.chrome.com/apps/storage#property-local