←back to thread

85 points behnamoh | 3 comments | | HN request time: 0s | source
Show context
HPMOR ◴[] No.46340199[source]
Why is this the case? I don't understand, can somebody explain the logic to me here?
replies(6): >>46340207 #>>46340237 #>>46340299 #>>46340414 #>>46340431 #>>46340585 #
ares623 ◴[] No.46340237[source]
Maybe used the email address as a primary key. Ask me how I know.
replies(4): >>46340307 #>>46340346 #>>46340384 #>>46340390 #
blitzegg ◴[] No.46340307[source]
Well it does eliminate a whole list of problems related to account takeover, account recovery workflows, legal questions regarding which email owns the data, etc. Sometimes less is more. Secure, reliable, simple.
replies(2): >>46340382 #>>46340567 #
prmph ◴[] No.46340382[source]
I fail to see how preventing email changes solves the issues you listed, or how allowing it necessarily makes them worse.
replies(1): >>46340753 #
blitzegg ◴[] No.46340753[source]
That's pretty obvious to anyone who had to maintain a high traffic site. Just the tip of the iceberg (I haven't included additional legal issues and other):

1.1 Strong protection against account takeover

Email change is one of the most abused recovery vectors in account takeover (ATO).

Eliminating email changes removes:

Social-engineering attacks on support

SIM-swap → email-change chains

Phished session → email swap → lockout of real user

Attacker must compromise the original inbox permanently, which is much harder.

1.2 No “high-risk” flows

Email change flows are among the highest-risk product flows:

Dual confirmation emails

Cooldown periods

Rollback windows

Manual reviews

Fixed email removes an entire class of security-critical code paths.

1.3 Fewer recovery attack surfaces No need for:

“I lost access to my email” flows

Identity verification uploads

Support-driven ownership disputes

Every recovery mechanism is an attack surface; removing them reduces risk.

replies(1): >>46343231 #
1. MattJ100 ◴[] No.46343231[source]
You're very wrong, because account takeover can still happen due to a compromised email account. People can and do permanently lose access to their email account to a third party.
replies(2): >>46344293 #>>46345641 #
2. cromka ◴[] No.46344293[source]
This is a logical fallacy. That's like saying security of the website is not important because someone can still steal your laptop.
3. TheNewsIsHere ◴[] No.46345641[source]
Having worked in security on a fairly high profile, highly visible, largely used product — one of the fundamental decisions that paid off very well was intentionally including mechanisms to prevent issues with other businesses (like Google) from impacting user abilities for us.

Not having email change functionality would have been a huge usability, security, and customer service nightmare for us.

Regardless of anything else, not enabling users to change their email address effectively binds them to business with a single organization. It also ignores the fact that people can and do change emails for entirely opaque reasons from the banal to the authentically emergent.

ATO attacks are a fig leaf for such concerns, because you, as an organization, always have the power to revert a change to contact information. You just need to establish a process. It takes some consideration and table topping, but it’s not rocket science for a competent team.