FossaGuard: Encrypt Gmail with S/MIME
Fossa Guard enables end-to-end S/MIME encryption on top of Gmail® complementing it with industry standard privacy
Total ratings
2.79
(Rating count:
14)Review summary
These summaries are automatically generated weekly using AI based on recent user reviews.
Chrome Web Store does not verify user reviews, so some user reviews may be inaccurate,
spammy, or outdated. Pros
- Well integrated into Gmail
- Ability to sign emails with generated certificates
- Offers support for attachments
- Seamless integration
- Free S/MIME implementation for Gmail
Cons
- Certificates not recognized as valid by other email clients
- Complex setup with issues in detecting logged in users
- Short certificate lifespan and attachment size limitations
- Lacks functionality for verifying received email signatures
- Concerns about uploading personal certificates to a server
Most mentioned
- Issues with certificate validity
- Integration with Gmail
- Complexity and instability of the extension
- Problems with entering email addresses
- Short certificate lifespan
Upgrade to see all 22 reviews
Recent reviews
Recent rating average:
2.20
All time rating average:
2.79
Upgrade to see all 22 reviews
Rating filters
5 star 4 star
3 star
2 star
1 star
| Date | Author | Rating | Lang | Comment |
|---|---|---|---|---|
| 2022-06-10 |  | | Worked before but now it cannot detect logged in user in gmail it seems, cause it says I am logged in with null | |
| 2022-06-10 |  | | en | Worked before but now it cannot detect logged in user in gmail it seems, cause it says I am logged in with null |
| 2021-01-19 |  | | 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. | |
| 2021-01-19 |  | | es | 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. |
| 2018-07-28 |  | | 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. | |
| 2018-07-28 |  | | en | 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. |
| 2018-04-12 |  | | beim schreiben der Empfänger-Email ploppt nur kurz ein Fenster auf um das Konto auszuwählen. So kann man keine Mail schreiben. | |
| 2018-04-12 |  | | de | beim schreiben der Empfänger-Email ploppt nur kurz ein Fenster auf um das Konto auszuwählen. So kann man keine Mail schreiben. |
| 2017-11-01 |  | | I had high hopes for this but entering email addresses by hand (instead of them popping up as they do in Gmail) was an issue, complicated by the email address always showing one less letter than I actually typed. That was quite annoying. ***UPDATE: This aspect suddenly started working properly after exiting my browser and restarting it, and logging in to Chrome again. *** I then attempted to send an email from within the extension, and it warned me that it would be sent unencrypted and asked me if I wanted to continue. I chose to continue but it then failed telling me that the recipient wasn't secure (diff wording). So it could not even send an email out insecurely. This has proven to be frustrating and a waste of my time. Too bad. | |
| 2017-11-01 |  | | en | I had high hopes for this but entering email addresses by hand (instead of them popping up as they do in Gmail) was an issue, complicated by the email address always showing one less letter than I actually typed. That was quite annoying. ***UPDATE: This aspect suddenly started working properly after exiting my browser and restarting it, and logging in to Chrome again. *** I then attempted to send an email from within the extension, and it warned me that it would be sent unencrypted and asked me if I wanted to continue. I chose to continue but it then failed telling me that the recipient wasn't secure (diff wording). So it could not even send an email out insecurely. This has proven to be frustrating and a waste of my time. Too bad. |
Upgrade to see all 22 reviews