Tag: ssl

Postfix & Courier & Letsencrypt

Post author By Yeri Tiete
Post date Sunday, June 12, 2016
No Comments on Postfix & Courier & Letsencrypt

First of all, create your certificates (the regular way). I created one with multiple domains: webmail.rootspirit.com, mail.rootspirit.com, smtp.rootspirit.com.

In my case, as the mailserver and webserver are behind a proxy (postfix, imap, Roundcube Webmail), I create the certificate on the proxy (nginx) and scp the cert to the mail server. All this is automated with a tiny script.

For Postfix, edit main.cf and change/edit/add these lines (check the right path too!):

smtpd_use_tls = yes
smtpd_tls_key_file = /etc/ssl/letsencrypt/webmail.privkey.pem
smtpd_tls_cert_file = /etc/ssl/letsencrypt/webmail.fullchain.pem
smtpd_tls_received_header = yes
smtpd_tls_session_cache_timeout = 3600s
tls_random_exchange_name = /var/run/prng_exch
tls_random_source = dev:/dev/urandom
smtpd_tls_exclude_ciphers = aNULL, eNULL, EXPORT, DES, RC4, MD5, PSK, aECDH, EDH-DSS-DES-CBC3-SHA, EDH-RSA-DES-CDB3-SHA, KRB5-DES, CBC3-SHA
smtpd_tls_dh1024_param_file = /etc/ssl/postfix/dhparams.pem
smtpd_tls_auth_only = yes
smtp_tls_security_level = may
smtpd_use_tls=yes
smtpd_tls_security_level=may
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_tls_loglevel=1
smtp_tls_loglevel=1

And restart postfix: /etc/init.d/postfix restart

As for Courier you’ll need to concatenate the files (again, check the path, it’s most likely /etc/letsencrypt/live/domain/xyz.pem):

cat /etc/ssl/letsencrypt/webmail.privkey.pem /etc/ssl/letsencrypt/webmail.fullchain.pem > /etc/ssl/letsencrypt/webmail.all.pem

Then edit both /etc/courier/pop3d-ssl and /etc/courier/imapd-ssl

And add/change the path of the certificate:

TLS_CERTFILE=/etc/ssl/letsencrypt/webmail.all.pem

And restart Courier: /etc/init.d/courier-imap-ssl restart && /etc/init.d/courier-pop-ssl restart

Tags encryption, mail, rootspirit, ssl

Linux Networking Software www

Gmail & Postfix: unencrypted emails?

Post author By Yeri Tiete
Post date Monday, March 7, 2016
No Comments on Gmail & Postfix: unencrypted emails?

If you’re running Postfix, add this line to main.cf:

smtp_tls_security_level = may

Restart Postfix, and retry.

PS: You can set encrypt instead of may — but this can cause issues with Amavis and/or SpamAssassin.

Tags rootspirit, ssl

Linux Networking Software www

Belgian banks & SSL — part 5

Post author By Yeri Tiete
Post date Friday, December 18, 2015
5 Comments on Belgian banks & SSL — part 5

Minor end of year update. No big SSL exploits have been released since (bar DH, see below).

Once again, this is testing the public websites I can access. There might be other gateways, APIs, etc that are not (as) secure.

It’s worthy to note that some banks are serious about security and fixing their SSL. Most improved their rating and solved all issues (especially getting rid of SHA1 in the chain). However, a couple lowered from B to C (see below). But… No more F’s. 🙂

The noteworthy changers:

Hello Bank! went from A to B though due to weak DH,
Triodos lost their Forward Secrecy,
Optima from F to A(-) (and a bunch others from B to A, and higher),
A bunch from B to C due to SSLLabs being more severe (see below). Most did solve some of their issues,
BKCP is doing a lot wrong.

Edit: Tested wrong AXA domain; updated to A+.

Update 11 Jan 2016: ABK & BvB updated to A.

Note that not supporting TLS 1.2 or supporting RC4 capped sites to grade B about a year ago; it now caps to grade C (aka SSLLabs is more severe).

Grade A

Rabobank (A+): no known issues.
Evi (A+): no known issues.
Crelan (A+): no known issues.
Binck (A+): no known issues.
ING (A+): no known issues.
Keytrade Bank (A+): no known issues.
CPH (A+): no known issues.
NIBC Direct (A+): no known issues.
AXA (A+): no known issues.
Delta Lloyd Bank (A): no known issues.
Deutsche Bank (A): weak signature (SHA1).
MeDirect Bank (A): no known issues.
Monte Paschi (A): no known issues.
Belfius (A): no known issues.
BNP Paribas Fortis (A): no known issues.
bpost bank (A): no known issues.
Argenta (A): no known issues.
Fortuneo (A): invalid HSTS policy.
Fintro (A): no known issues.
DHB Bank (A): no known issues.
VDK (A): no known issues.
ABK: (A): no known issues.
Bank Van Breda (A): no known issues.
Ogone (payment facilitator — A): no known issues.
Moneyou (A-): no Forward Secrecy.
Record Bank (A-): no Forward Secrecy.
Triodos (A-): no Forward Secrecy.
Optima Bank (A-): no Forward Secrecy.
KBC (A-): no Forward Secrecy.
Isabel (banking tool for corps — A-): no Forward Secrecy.

Grade B

Hello bank!: Weak Diffie-Hell (aka DH) (info).

Grade C

PSA Bank: weak signature (SHA1), no TLS 1.2, no Forward Secrecy.
beobank: weak DH, no TLS 1.2, RC4 (insecure), no Forward Secrecy, no secure renegotiation.
BKCP: weak signature (SHA1), no TLS 1.2, RC4 (insecure), no Forward Secrecy, weak DH.

Grade D

Grade E

Grade F

Tags belgium, ssl

Misc

Belgian bank & SSL slashdot effect

Post author By Yeri Tiete
Post date Saturday, February 28, 2015
No Comments on Belgian bank & SSL slashdot effect

Quick wrap up of the slashdot effect 10 days ago.

A peak of 12k views on Monday 16/02, with a small buildup on Sunday (15/02).

The top pages were Part 3, Part 1, Part 4 and Part 2 respectively.

De Redactie is the highest referrer, surpassing De Morgen (first to publish in printed media, front page) & Datanews (first to publish online):

Second highest, after Twitter (t.co), was Tweakers (Dutch website, oddly enough).

OS wise, about 60% is Windows, 12% of OSX and 10% of iOS; 79% desktop, 15% phones, 6% tablets. Way more mobile than I expected to be honest.

This was easily handled on a Debian virtual machine: running a dual core Xeon vCPU (3.2Ghz) with 2Gb of RAM. Nginx as webserver. No slowdown was noticed. Google Analytics reported peaks of ~100 concurrent users (but not sure what timeframe they consider “concurrent”).

There was, what looks like, a DoS on Monday around 12h00 for about 30 minutes causing a 100% load (2.00 linux load, on 2 vCPUs), however there was no out of the ordinary traffic data peak — but I didn’t have time to look into it, and by the time I had notice it was already long over.

Interesting networks:

Usually Telenet & Belgacom consumer networks are high above anything else (they were still #1 and #2 respectively, this time), but closely following up where a lot of corporate networks, as as these:
Bank van Breda (177 pageviews)
ING (167)
Fortis (125)
KBC (114)
AXA (104)
And others (< 50 pageviews) Ogone, HP, Crelan, Argenta, Infrabel, Deutsche Bank, Microsoft, Vlaamse Overheid, AGFA, Getronics, De Post, etc.

Interesting referrers:

a bunch of intranets (fedict, kbc, ing),
a bunch of bank website & mailings: updated list on part 4.

Interesting reads:

Frank,
And a few comments on part 3 and part 4.

Ripple effect:

Same tests in Norway.

Tags belgium, media, slashdot, ssl

Linux Misc Networking Software www

Belgian banks & SSL — part 4

Post author By Yeri Tiete
Post date Monday, February 16, 2015
40 Comments on Belgian banks & SSL — part 4

Because of the mediastorm it’s time for an update. The previous (1, 2, 3) blog posts are outdated!

I’ll do my usual slashdot-effect post in a couple of days (it’s already at 10k views today).

Banks that changed rank since last post (all for the better):

16/02/2015:
- Keytrade: B to A
- Hello Bank!: C to A
- ING: F to A-
- Record Bank: F to A-
17/02/2015:
- ABK: F to B
- Bank Van Breda: C to B
18/02/2015:
- MeDirect: F to A
- Added 6 new (small) banks
27/02/2015
- Ogone: C to A-
02/03/2015
- Fortuneo: C to B
03/03/2015
- Crelan: B to A

I cannot test Europabank using SSL Labs. I can only speculate they requested SSL Labs to not scan them. I have also added a couple new banks (Delta Lloyd, Deutsche Bank, Moneyou, Fortuneo, BKCP, Binck, and Isabel as bank tool).

I would like to apologise for every IT’er that had a crappy Monday morning, and thank you for fixing SSL so fast. 🙂

The entire list updated (last partial update 18/02/2015 around 20h00):

I’ve updated the sites to now correctly test the login page and not the main homepage. If that’s not the case somewhere, please tell me.

Grade A

Rabobank (A+): no known issues. Support for HTTP Strict Transport Security and prevented downgrade attacks.
Triodos (A+): no known issues. Support for HTTP Strict Transport Security and prevented downgrade attacks.
Evi (A+): no known issues.
Crelan (A): weak signature (SHA1).
Delta Lloyd Bank (A): no known issues. [news post]
Deutsche Bank (A): weak signature (SHA1).
Hello bank! (A): no known issues.
Keytrade Bank (A): weak signature (SHA1, intermediate, very very minor issue).
MeDirect Bank (A): no known issues. [newsletter: 1, 2]
Monte Paschi (A): no known issues.
Belfius (A-): weak signature (SHA1), no Forward Secrecy.
BNP Paribas Fortis (A-): weak signature (SHA1), no Forward Secrecy.
bpost bank (A-): weak signature (SHA1), no Forward Secrecy.
Binck (A-): weak signature (SHA1), no Forward Secrecy.
Fintro (A-): weak signature (SHA1), no Forward Secrecy.
ING (A-): no Forward Secrecy. [press release via Standaard]
Moneyou (A-): weak signature (SHA1), no Forward Secrecy.
Record Bank (A-): no Forward Secrecy. [news post]
Isabel (banking tool for big corps – A-): weak signature (SHA1), no Forward Secrecy.
Ogone (payment facilitator): no Forward Secrecy. [newsletter via twitter]

Grade B

Argenta: SSL3 (insecure), weak signature (SHA1), RC4 (insecure), no Forward Secrecy.
ABK: weak signature (SHA1), no TLS 1.2, no Forward Secrecy, no support for secure renegotiation. [update]
AXA: weak signature (SHA1), SSL3 (insecure), RC4 (insecure), no Forward Secrecy.
Bank Van Breda: weak signature (SHA1), no TLS 1.2, no Forward Secrecy, no support for secure renegotiation. [update]
beobank: weak signature (SHA1), no TLS 1.2, RC4 (insecure), no Forward Secrecy.
BKCP: weak signature (SHA1), no TLS 1.2, RC4 (insecure), no Forward Secrecy. [newsletter]
CPH: no TLS 1.2, RC4 (insecure), no Forward Secrecy.
DHB Bank: weak signature (SHA1), RC4 (insecure).
Fortuneo: weak signature (SHA1), no TLS 1.2, no Forward Secrecy.
KBC: weak signature (SHA1), no TLS 1.2, no Forward Secrecy.
NIBC Direct: weak signature (SHA1), RC4 (insecure), no Forward Secrecy.
VDK: SSL3 (insecure),no TLS 1.2, weak signature (SHA1), RC4 (insecure), no Forward Secrecy

Grade C

PSA Bank: weak signature (SHA1), no TLS 1.2, RC4 (insecure), no Forward Secrecy.

Grade D

Grade E

Grade F

Optima Bank: vulnerable to POODLE attack in SSL3 and TLS format, weak signature (SHA1), RC4, no Forward Secrecy.

Information about SSL Labs grading can be found here. Grade A (+) being the best possible ranking, and F the worst.

Respect to those that send a mailing list to their customers with more detailed information. Communication++

Respect to Rabobank to be the only bank that directly contacted me (officially, not hiding behind a Gmail or Hotmail address) and thanked me for the work I did, asking for more details, etc.

And thank you for an anonymous person, working for one of the big banks, to give me more details about why they are slow at patching this, how legacy works, etc. I wish he could take this discussion public, but alas.

Tags belgium, ssl