#2.87 / 15 rate

FossaGuard: Encrypt Gmail with S/MIME

1,000 users

2020-01-12

https://fossa.me

[email protected]

https://fossa.me

This extension is being deprecated because it doesn't follow Chrome extension best practices.

Extension Information

5 star

4 star

36%

3 star

18%

2 star

18%

1 star

18%

Supported Languages

Permissions

Description

Fossa Guard enables end-to-end S/MIME encryption on top of Gmail® complementing it with industry standard privacy

Secure e-mailing with Gmail becomes easy on Desktop and Android. Encrypt and Sign your Gmail messages with industry standard - S/MIME using Chrome, Yandex or Firefox browsers.

Fossa Server and Fossa Guard web extension provide secure mailing solution on top of Gmail (TM) following S/MIME specification.

Fossa Guard generates key pair within your browser then Fossa Server securely supplies you with personal X.509 certificate upon Certificate Signing Request (CSR) so that your private key always stays with you.

Use Fossa Guard extension to sign or to encrypt your email with X.509 certificate. The certificate is free and stays valid for 3 months (beta phase limitation).

Fossa Guard has own autonomous Compose dialog to avoid unsecured email content auto-saving.

Your private key is protected by pass-phrase and is replicated alongside with trusted certificates via your protected local user storage. Use Fossa Guard to get details on certificates in your repository.

Please refer to Privacy policy at https://fossa.me/policy

Reviews

Franci Šacer

Worked before but now it cannot detect logged in user in gmail it seems, cause it says I am logged in with null

Carlos C.

Puedes leer la valoración en español mas abajo. [ENGLISH] The good ... -You can sign the emails with the certificate that they generate and it is well integrated into Gmail. - You can include your own certificate (I haven't tried it) The bad ... - The certificate with which it is signed is not recognized as valid by mail clients (for example Thunderbird) because it is not issued by a trusted CA. Not good not bad ... - The permits that must be given are many, but at least they seem reasonable. - I don't trust uploading my own certificate to a server. The summary... - If the certificates were issued by a trusted CA I would use it, but sending emails that carry a certificate notice seems ugly to me. I can't ask my senders to include a CA on their computers because I'm going to send them emails. [ESPAÑOL] Lo bueno ... -Puedes firmar los correos con el certificado que te generan y está bien integrado en Gmail. - Puedes incluir tu propio certificado (no lo he probado) Lo malo ... - El certificado con el que se firma no es reconocido como válido por los clientes de correo (por ejemplo Thunderbird) porque no lo emite una CA de confianza. Ni bueno ni malo ... - Los permisos que hay que darle son muchos, pero al menos parecen razonables. - No me fio de subir un certificado emitido para mi email por una CA de confianza a un servidor. Debería poder dar la opción de firmar en local. El resumen... - Si los certificados estuviesen emitidos por una CA de confianza la usaría, pero enviar emails que llevan un aviso de certificado me parece feo. No puedo pedirle a mis remitentes que incluyan una CA en sus equipos porque yo les vaya a enviar emails.

Nathan Kaiser

it just doesn't work. It's just too complicated. Tried this, tried that, free version, paid - it would just never work, always something new coming up. Not mature yet.