Ask HN: Secure messaging to solve phishing scams

2 pointsby helghardtvor 3 Jahren4 comments

Let’s use banks as an example, but it applies to other services too. Why do banks rely on emails and sms to communicate login alerts, password changes, transaction confirmations and even promotional alerts?

It is sooo prone for phishing attacks! HTTPS helped us confirm the website we visit is legit along with being confident the data transmission is encrypted. Everyone managed to fall in line adopting this standard and relying on a certificate authority sitting in the middle.

Taking this one step further, why have banks not tried to create a secure messaging service where there is a certificate issued and associated with your website to validate authenticity.

Furthermore, the messaging service could be opt-in only, more accurate labelling of incoming messages, etc.

So my question is why does such a messaging standard/service not exist, has anyone tried but failed?

3 comments

na4ma4vor 3 Jahren

Because it would be fragmented and have 1000 incompatible implementations if it ever got that far.

Large institutions would prefer something they control 100%, email and SMS are only used because they became ubiquitous first.

But some companies use their apps as a secure alternative.

dave4420vor 3 Jahren

Banks who create a secure messaging service build it into their app and website. There’s no incentive to create a generic service.

helghardtvor 3 Jahren

The problem with in-app messaging is that they still fall back to sms and email MFA.

helghardtvor 3 Jahren

Another benefit that comes to mind is the cost saving of not having to send SMS’es. In some regions SMS’es go up to $0.25/SMS via services like Twilio/local variations.