Sad state of email encryption in Serbia - or how a web based bank just does not encrypt emails
Not long ago, browsing through my received emails in my gmail, I've realized that one of the banks I use does not use TLS when sending emails to their clients. Of course, being a security aware customer of the bank, and having in mind that I am their client, I've decided to contact them with this information, pointing out the fact that Gmail, a 21st century go-to free email provider, makes this very prominent in each mail they send.
The usual ways of contacting the bank in question is either via phone, email or Twitter. Since they don't encrypt their email traffic, and I didn't have time for waiting on their staff on the phone (who does these days, right?), I've decided to use Twitter. I had previous experience with them via this channel, and a positive one. They seemed to be on top of any problems they receive via tweets, and are quite fast to reply.
Just to add a bit more context to the story (or to make things even worse), the bank in question is a first ever Web based bank (at least they market themselves this way) in Serbia. You'll notice that I've included a google support link in the tweet, just to point their support in the correct direction.
Initially, the bank support just ignored me. It didn't help that I don't have many followers, and that my tweet did not get any special attention. I am guessing that the request I made was a bit too much for an average support guy, or I just overwhelmed them with an unusual request. So, three days later I made another tweet, politely asking them to turn on TLS for their outgoing emails.
I also included a remark that I'm not getting the 'crossed out red lock' on the emails from other banks in Serbia. After that, they had finally replied:
The translated gist of their response spanning two tweets is: "we won't do it for compatibility sake". How valid is this excuse in 2017? I'll tell you: it just isn't.
NOTE: the text above was drafted during 2017. A tweet I've seen today, shaming another major provider of services in Serbia for their lack of use of the TLS, prompted me to follow up and actually publish the post. Having a lot of time passed, I am posting a screenshot of an up to date email sent to me from the bank. As you can see from the picture below, nothing had changed:
The usual ways of contacting the bank in question is either via phone, email or Twitter. Since they don't encrypt their email traffic, and I didn't have time for waiting on their staff on the phone (who does these days, right?), I've decided to use Twitter. I had previous experience with them via this channel, and a positive one. They seemed to be on top of any problems they receive via tweets, and are quite fast to reply.
 |
| Translation: "Hello @TelenorBanka, did you know that emails you're sending to your clients are not encrypted in transit? Info: support.google.com/mail/answer/63..." |
Just to add a bit more context to the story (or to make things even worse), the bank in question is a first ever Web based bank (at least they market themselves this way) in Serbia. You'll notice that I've included a google support link in the tweet, just to point their support in the correct direction.
Initially, the bank support just ignored me. It didn't help that I don't have many followers, and that my tweet did not get any special attention. I am guessing that the request I made was a bit too much for an average support guy, or I just overwhelmed them with an unusual request. So, three days later I made another tweet, politely asking them to turn on TLS for their outgoing emails.
 |
| Translation: "Hello, @TelenorBanka, could you turn on TLS for outgoing emails? I am not getting emails like this from other banks" |
 |
| Translation: "Hi Aleksandar, to make sure all of our users get our emails, we don't have the implementation of encryption algorithms to encrypt the emails in plan at the moment. Thanks for your suggestion and patience for other users' sake. :) /Dragana" |
The translated gist of their response spanning two tweets is: "we won't do it for compatibility sake". How valid is this excuse in 2017? I'll tell you: it just isn't.
NOTE: the text above was drafted during 2017. A tweet I've seen today, shaming another major provider of services in Serbia for their lack of use of the TLS, prompted me to follow up and actually publish the post. Having a lot of time passed, I am posting a screenshot of an up to date email sent to me from the bank. As you can see from the picture below, nothing had changed:
 |
As you can see, the email wasn't transferred via TLS; the subject line translates to "Transaction approved" - and the email lists my account balance, transaction amount as well as the vendor.
|
A sad state of affairs indeed.
Comments
Post a Comment