Jump to: navigation, search

Difference between revisions of "Security and Privacy"

Difference between revisions of "Security and Privacy"

(Put it more politely)
Line 26: Line 26:
  
 
== Website HTTPS ==
 
== Website HTTPS ==
Currently we have a [https://www.ssllabs.com/ssltest/analyze.html?d=mail.tolabaki.gr shitty] HTTPS setup with many problems. In this link there is how to fix everything along with all the problems. A "good" server must get an A- at least on this test.
+
Currently we have an amazingly [https://www.ssllabs.com/ssltest/analyze.html?d=mail.tolabaki.gr insecure] HTTPS setup with many security issues. In this link there is how to fix everything along with all the problems. A "good" server must get an A- at least on this test.
  
 
Additionally, our Root CA uses MD5 signatures which is long now obsolete and considered insecure.
 
Additionally, our Root CA uses MD5 signatures which is long now obsolete and considered insecure.

Revision as of 15:51, 20 April 2015

This page discusses the security mechanisms and the configurations we use to prevent malicious attacks. Note that the information here will be limited to prevent exposing possible vulnerabilities.

Intrusion Prevention Mechanisms

We use:

To Do

Encryption

TODO: use some short of encryption for the content of our users.

Suggestion: Allow users to opt-in to a service where their entire inbox is encrypted with their GPG key regardless if the sender of the original e-mail used GPG.

Configurations

TODO

  • Use non-default ports for ssh / imap? / ...
  • Block remote root login
  • Only allow ssh login using Private Keys
  • Renew (rotate) server ssh keys and use ECDHA/ECDSA
  • Automated security updates without human intervention
  • Setup reminders about expiring certificates

Website HTTPS

Currently we have an amazingly insecure HTTPS setup with many security issues. In this link there is how to fix everything along with all the problems. A "good" server must get an A- at least on this test.

Additionally, our Root CA uses MD5 signatures which is long now obsolete and considered insecure.

E-Mail

  • Prevent outbound spoofing ( check if From: matches authenticated username )
  • Notify user with the spam filter if incoming e-mail is spoofed (invalid SPF / IP not in From: domain MX)