News for hackers. Stuff that matters.
Re:“Invalid Username or Password”: a useless security measure by darrinmn on Wednesday November 23, 2022 @09:45AM (#33719721)
> 99.9% of websites on the Internet will only let you create one account for each email address. So if you want to see if an email address has an account, try signing up for a new account with the same email address.

This is not true if the signup flow is implemented correctly. Signing up for an account should always respond with the same message "we sent an email for you to confirm your account signup". The owner of that email address then receives an email - either 1) normal signup process, or 2) "did you just try to sign up? You already have a valid account for this email address."

This way you cannot tell via the signup web form alone whether an account exists or not. You need to have access to the email address.

Re:“Invalid Username or Password”: a useless security measure by thefreeman on Wednesday November 23, 2022 @10:20AM (#33720236)
And then what happens when the user tries to login with the password they just "created". They will get the same error message as before, but be extremely confused since they just "registered" with that password. Not to mention their browser may have prompted and stored the fake registration password, etc.
Re:“Invalid Username or Password”: a useless security measure by darrinmn on Wednesday November 23, 2022 @10:23AM (#33720293)
What do you mean login? I'm talking about the signup flow. The signin flow would be consistent with what is discussed in the article "invalid username or pw".
Re:“Invalid Username or Password”: a useless security measure by thefreeman on Wednesday November 23, 2022 @10:30AM (#33720393)
What do users usually do after registering an account? They try to login with it (assuming they aren't automatically logged in after registration which is what I would generally prefer / expect as a user).

You are giving the user so many chances to just say "forget this" and move on to a different website. Especially if they are on mobile, registering for services is a huge pain in the butt.

My basic point is you are severely impairing the UX to prevent what I think is an extremely minor and generally irrelevant piece of information leakage.

Re:“Invalid Username or Password”: a useless security measure by gchamonlive on Wednesday November 23, 2022 @10:38AM (#33720499)
The flow is

1. Sign up for an account 2. Enter the email 3. Receive a confirmation email 4. Create password 5. Sign in

This is what op means. You just ingest step 2 without confirming the email is used or not. The actual account creation should occur only after email confirmation.

Re:“Invalid Username or Password”: a useless security measure by thefreeman on Wednesday November 23, 2022 @10:43AM (#33720575)
Gotcha. That does make more sense and basically signup and reset password are essentially the same process. If the user doesn't have an account previously at that point you collect the information needed to proceed. I personally would not want to break up my onboarding experience like this but I can see other people making the trade off.
Re:“Invalid Username or Password”: a useless security measure by gondo on Wednesday November 23, 2022 @10:43AM (#33720574)
The user should be automatically logged in after successful registration if the flow is implemented correctly.
Re:“Invalid Username or Password”: a useless security measure by KMag on Wednesday November 23, 2022 @11:32AM (#33721295)
If the GP is assuming that initial password setting is done via the verification link sent in the verification email, then the workflow they're proposing won't cause the confusion you describe. In other words, the "verify my email address" link is to a form that says "Create and verify password to confirm your email address."

If you're assuming that initial password entry is done before email verification, then there's a possibility for confusion there.

Honestly, the lowest friction workflows collect information lazily. Don't require setting a password (if at all... expiring login links in emails are a nice alternative) until the email is verified. Don't require a mailing address or credit card number at all, but have a "save for later" checkbox/button as part of the checkout workflow, etc.

Re:“Invalid Username or Password”: a useless security measure by Guest9081239812 on Wednesday November 23, 2022 @01:52PM (#33723111)
On my site it works this way...

1. Choose desired plan.

2. Enter username, password, checkbox for terms of service.

3. Get prompted to enter the 6 digit confirmation code that was emailed to you (if you were already registered, it says you have an account and links to the login and password reset pages if required).

4. Registration is complete and the user is automatically signed in.

The username or email address isn't blocked until someone completes a registration with it.

Re:“Invalid Username or Password”: a useless security measure by emodendroket on Wednesday November 23, 2022 @11:15AM (#33721071)
You’d defer password setting if you were doing this I would think.
Re:“Invalid Username or Password”: a useless security measure by layer8 on Wednesday November 23, 2022 @10:09AM (#33720063)
This is bad in the case of online orders, where the order will usually go through anyway (vendors want to sell even when you don’t confirm your email address, and don’t care a lot about someone else getting the notification emails), because if by mistake you registered your email address as new although you already had an account with that address, the order won’t get associated with your account. Or if it does automatically get associated with the account (or after confirmation), then that’s bad as well if you really entered someone else’s email address, because your order will then get associated with their account.

This is the reason why attempting to sign up for an existing account generally fails right away, at least for online retailers.

Re:“Invalid Username or Password”: a useless security measure by darrinmn on Wednesday November 23, 2022 @10:31AM (#33720405)
Not sure exactly what you mean? Are you referring to a purchase flow where you are buying something and also given the option to checkout as guest or signin/signup?

I am only speaking to the typical signup flow that anyone can access signed out without putting in any information besides email/pw. If you are in a purchase flow where valid credit card info is already entered and is going to result in actual purchase $$, you've already excluded bots/hackers who would be trying to brute force account enumeration. It would be totally fine to confirm the existence of an account in a web form in this situation as it is not a flow that can be easily brute forced for free with little effort or info needed (like a credit card).

Re:“Invalid Username or Password”: a useless security measure by cryptoegorophy on Wednesday November 23, 2022 @11:01AM (#33720875)
Woocommerce plug-in of Wordpress solved that issue. You can checkout as a guest with someone else’s email, you won’t see other orders from that email and if you do want to see them then you need to sign up for an account
Re:“Invalid Username or Password”: a useless security measure by layer8 on Wednesday November 23, 2022 @11:31AM (#33721283)
What if it wasn’t someone else’s email, but your own with an existing account? Can you re-associate your order with the existing account?
Re:“Invalid Username or Password”: a useless security measure by cryptoegorophy on Wednesday November 23, 2022 @06:35PM (#33725912)
It can only be done manually by admin upon request. Otherwise if you are not logged in then you have a guest order.
Re:“Invalid Username or Password”: a useless security measure by lucideer on Wednesday November 23, 2022 @12:09PM (#33721772)
> the order will usually go through anyway

> vendors want

If security is not a priority for the vendor, then yes. Otherwise, no, the order will not go through anyway.

I'm very aware that in many many cases, the former is true in the real world, but that doesn't change the fact. This isn't a good justification for the op's dismissal of the practice.

Re:“Invalid Username or Password”: a useless security measure by Al-Khwarizmi on Wednesday November 23, 2022 @09:59AM (#33719917)
In simple registrations this is fine. In multi-page registrations with long forms, it can waste the user's time by making them input all the data again when it wasn't needed, though.

Except in really critical applications like payments, etc., as a user I'd rather have the convenience of being warned early about already having an account that the little extra security.

Re:“Invalid Username or Password”: a useless security measure by Xylakant on Wednesday November 23, 2022 @10:12AM (#33720112)
How often does it happen that you fill out a multi-page registration form just to notify you that you already have an account? I rarely bump into the issue of already having an account that I forgot.

Is saving that extra amount of work in a rare case a concern in practice? Sure, it would annoy me a bit if it happened to me, but I'd be more like "man, I'm stupid" instead of "man, this site is stupid, I'll never go there again."

Re:“Invalid Username or Password”: a useless security measure by Al-Khwarizmi on Wednesday November 23, 2022 @01:14PM (#33722618)
It has happened to me sometimes with ecommerce websites that I only use once every few years.

Only a mild annoyance, but still more annoying than it would be to have someone access my account on such websites (which would be basically negligible, as I don't store payment information there, and you have to multiply it by the also negligible probability that the information leak from the login form is key in letting the bad dudes access my account).

Re:“Invalid Username or Password”: a useless security measure by thomastjeffery on Wednesday November 23, 2022 @10:02AM (#33719956)
You shouldn't be doing long web forms before creating an account anyway.
Re:“Invalid Username or Password”: a useless security measure by layer8 on Wednesday November 23, 2022 @10:26AM (#33720335)
This is commonly the case for online shopping, where account creation is optional and may only occur after confirmation, but the order will be placed regardless.
Re:“Invalid Username or Password”: a useless security measure by darrinmn on Wednesday November 23, 2022 @10:56AM (#33720792)
Re:“Invalid Username or Password”: a useless security measure by thomastjeffery on Wednesday November 23, 2022 @10:58AM (#33720829)
But in that case, there is still an account (just without login ability), and you are probably even sending an email.

So in the email you can include a link to optional account (username/password) creation.

And if you aren't sending an email, then the user has clearly decided not to create an account.

Re:“Invalid Username or Password”: a useless security measure by layer8 on Wednesday November 23, 2022 @11:29AM (#33721246)
The problem is if an account for that email already exists, see https://news.ycombinator.com/item?id=33720063.
Re:“Invalid Username or Password”: a useless security measure by zhfliz on Wednesday November 23, 2022 @10:07AM (#33720030)
You shouldn't be taking my email just to demand lots of information from me after I already gave my email to you.

If you demand lots of information that should be clear right away.

Re:“Invalid Username or Password”: a useless security measure by thomastjeffery on Wednesday November 23, 2022 @10:23AM (#33720277)
I can sympathize with your frustration about long web forms, but that seems to me like a separate issue with a separate solution.

People shouldn't be making long forms part of account creation unless absolutely necessary; in which case it should already be obvious to the user that it is.

If it's somehow necessary but not obvious, you can put up a friendly warning. Maybe something like, "Step 1/12" or "expected registration time 15min."

Re:“Invalid Username or Password”: a useless security measure by TeMPOraL on Wednesday November 23, 2022 @11:47AM (#33721542)
So now you're saying web UX should actually improve and give up the major disadvantage it has over paper forms: hiding the full flow from the (l)users.

/s, but only slightly.

You're right, of course. The answer is the one nobody wants to hear: you can tell users what you'll want from them, then ask to create an account, and then ask them to do the things you outlined before registration.

As for multi-page forms, they make sense if you target non-JavaScript use, but if your site is already an SPA, you might as well present the form in full, and conditionally disable parts that don't apply based on earlier inputs. This is the way to improve over the paper UX.

Re:“Invalid Username or Password”: a useless security measure by metacritic12 on Wednesday November 23, 2022 @10:01AM (#33719940)
While clever, this system has UI tradeoffs, if I need to break my signup flow in order to click on a link and return to the signup page.

I believe this is also non-standard right now.

Re:“Invalid Username or Password”: a useless security measure by darrinmn on Wednesday November 23, 2022 @10:39AM (#33720522)
Are you saying your signup flow would automatically log the user in without confirming their email address (verify later)? I wouldn't suggest that for most websites as that would allow someone to signup with an email address they don't own.

For most websites transacting with potentially sensitive information, having an email sent to confirm you own the email address should already be part of the normal flow, so I'm not suggesting any extra step here. I was only suggesting an alternative email response in the situation you try to signup with an email that already exists. The normal happy path signup flow for a new account is not affected at all by my comment.

Re:“Invalid Username or Password”: a useless security measure by metacritic12 on Wednesday November 23, 2022 @01:17PM (#33722658)
I think the sibling post by samwillis explains my view the clearest.

Basically, the business case for breaking the signup flow to require users to check their email is low. It interrupts flow and reduces conversion rates.

The suggestion then is yes, you are allowed to use emails you don't own to sign up for an account. The reason this is allowable is that who would want to do it? The account would be broken and the real owner of that account can pop your password.

Re:“Invalid Username or Password”: a useless security measure by cozzyd on Wednesday November 23, 2022 @02:47PM (#33723665)
well, a user might put in the wrong email by mistake...
Re:“Invalid Username or Password”: a useless security measure by ranguna on Thursday November 24, 2022 @03:27AM (#33728962)
They can just creat another account then
Re:“Invalid Username or Password”: a useless security measure by prmph on Wednesday November 23, 2022 @10:05AM (#33719996)
Could you please elaborate? What's the standard best practice for signup now?
Re:“Invalid Username or Password”: a useless security measure by lhnz on Wednesday November 23, 2022 @09:58AM (#33719899)
If you did implement it like this it would be helpful to receive an email telling you that somebody has tried to re-register the email address you already have an account with.
Re:“Invalid Username or Password”: a useless security measure by thomastjeffery on Wednesday November 23, 2022 @10:03AM (#33719964)
That's the option #2 they described.
Re:“Invalid Username or Password”: a useless security measure by gohohn on Wednesday November 23, 2022 @10:01AM (#33719942)
Another method is to delegate the registration and login flow to external providers, using OAuth.

If you have to log in to a website via one of Microsoft, Google, Facebook, Twitter, etc. then, if implemented properly, there's no way of knowing if an account associated with this external identity exists already.

Re:“Invalid Username or Password”: a useless security measure by godshatter on Wednesday November 23, 2022 @10:21AM (#33720254)
Most of those are trying to track me around the net for their own purposes. I'm not volunteering any extra information for them to profile me with. No thanks.
Re:“Invalid Username or Password”: a useless security measure by gohohn on Wednesday November 23, 2022 @10:24AM (#33720307)
The only extra information you would be volunteering is that you signed in to a specific website. In most cases, this is not really a big deal.
Re:“Invalid Username or Password”: a useless security measure by godshatter on Wednesday November 23, 2022 @10:38AM (#33720500)
If I don't want them knowing I surfed to somewebsite.com, why would I want them to know that I actually logged in to someotherwebsite.com?

I get that people have different levels of trust for these services than I do. I'm just more cynical than most, I guess.

Re:“Invalid Username or Password”: a useless security measure by bombcar on Wednesday November 23, 2022 @10:55AM (#33720791)
You are also trusting the Oauth provider to never login as you for their own inscrutable purposes.
Re:“Invalid Username or Password”: a useless security measure by gohohn on Wednesday November 23, 2022 @12:37PM (#33722162)
That is true. But then many people put a lot of trust in the major providers in many other areas too, such as hosting their private files and email, holding card payment information, and so on.
Re:“Invalid Username or Password”: a useless security measure by bombcar on Wednesday November 23, 2022 @02:11PM (#33723329)
Yeah an email provider is basically Oauth with extra steps for ALL your accounts.
Re:“Invalid Username or Password”: a useless security measure by MichaelCollins on Wednesday November 23, 2022 @12:41PM (#33722206)
Absolutely. In the case of Facebook, it's easy to imagine them logging into websites as you to slurp up your contact list on that site. Don't worry, you agreed to it somewhere in the thousand pages of small print!

Or as the case of twitter demonstrates, you're also trusting all future owners of the Oauth provider, whoever they may be. If an erratic billionaire with a penchant for breaking the rules whenever it suits him buys your Oauth provider, who's to say what he'll do with his new access? He could treat your accounts as his personal toys.

Re:“Invalid Username or Password”: a useless security measure by another2another on Thursday November 24, 2022 @11:19AM (#33733042)
Linked in used to (maybe still does) encourage you to provide them login details to your email so that they can scan it for potential matches.
Re:“Invalid Username or Password”: a useless security measure by MichaelCollins on Wednesday November 23, 2022 @12:36PM (#33722151)
> this is not really a big deal.

If it's not a big deal, then why do they offer this service "for free"?

It's all part of their commercial panopticon. You're missing the forest for the trees.

Re:“Invalid Username or Password”: a useless security measure by mint2 on Wednesday November 23, 2022 @10:11AM (#33720092)
Giving in my Facebook that centralized view and extra data… no thanks. Same with Microsoft and google.
Re:“Invalid Username or Password”: a useless security measure by gohohn on Wednesday November 23, 2022 @10:15AM (#33720157)
The only information they would receive is that you signed in to a specific website.
Re:“Invalid Username or Password”: a useless security measure by rmbyrro on Wednesday November 23, 2022 @10:05AM (#33719990)
Author talks about that in the article
Re:“Invalid Username or Password”: a useless security measure by emodendroket on Wednesday November 23, 2022 @11:13AM (#33721045)
That exact strategy is described in the second paragraph but the author argues (and I agree) that it is so arduous it will cause you to lose many users for questionable benefit.
Re:“Invalid Username or Password”: a useless security measure by darrinmn on Wednesday November 23, 2022 @11:23AM (#33721169)
Yes but the exact quote is confusing as he specifically mentions email addresses (in bold text). I know the author mentions usernames elsewhere in the article and I agree with the author this isn't applicable to websites that allow username signup since anyone can pick any random string... But for email address signup, as the exact quote mentions, there is no additional context switching since you already need to confirm the email address regardless.
Re:“Invalid Username or Password”: a useless security measure by emodendroket on Wednesday November 23, 2022 @12:57PM (#33722398)
Often you don’t need to confirm the e-mail address to complete whatever workflow you’re doing.
Re:“Invalid Username or Password”: a useless security measure by darrinmn on Wednesday November 23, 2022 @01:30PM (#33722837)
Sure, companies are free to make their own choices based on their business incentives. But if you can create an account and be logged in without verifying an email address, then arguably the email address wasn't needed in the first place and you should just allow any type of username string. If the goal of your website is for email address to be the username, the you should confirm the user actually owns the email address they claim first - since anyone could lie and put a random email they don't own.
Re:“Invalid Username or Password”: a useless security measure by samwillis on Wednesday November 23, 2022 @11:29AM (#33721243)
The vast majority of the time the number one priority is reducing friction before a conversion. As much as a email confirmation prior to completion is more secure, the business case is far less strong.

Customers can fix their email later, they can contact customer support if they got something wrong.

Get them in the door ASAP, and either using the account, or complete an order. Don't redirect them to their email where there is a good chance they will either get distracted or the email will be delayed.

That's not to say you shouldn't also have your own measures in place to detect error, or malicious checking if email associated with account.

Re:“Invalid Username or Password”: a useless security measure by MichaelCollins on Wednesday November 23, 2022 @11:38AM (#33721392)
If reducing friction is the priority, then maybe skip email completely. Let people sign up with any username and don't require an email at all, like HN allows. Most sites that require an email don't need an email, and only ask for it so they can spam users with nonsense like product updates.
Re:“Invalid Username or Password”: a useless security measure by marcosdumay on Wednesday November 23, 2022 @12:19PM (#33721927)
Any site that requires a password will need an email for password resets.
Re:“Invalid Username or Password”: a useless security measure by MichaelCollins on Wednesday November 23, 2022 @12:24PM (#33721983)
If the site doesn't need email for anything besides that, then it doesn't need email for that either. Let the user set an email for account recovery if they want, but don't require it. If users who choose not to give an email forget their password, they can simply create another account.

This is the way HN works. It's the way most websites used to work, until maybe 15 years ago, give or take. Today almost all sites ask for verified email addresses, but this used to not be the case.

Besides the commercial value of having user email addresses, I think it's mostly done for the webdev's ego:

> Users need to hear about my new update! (Because if I don't spam their inbox, nobody will notice or care about the thing I just did.)

Re:“Invalid Username or Password”: a useless security measure by ben0x539 on Wednesday November 23, 2022 @02:50PM (#33723695)
I think the webdevs are right about this one. People lose or forget passwords all the time (in general not using password managers). Permanently losing access to an account sucks a lot. Tying account ownership to email primarily with passwords being more or less an optional convenience saving you the email roundtrip seems worth it.
Re:“Invalid Username or Password”: a useless security measure by parminya on Wednesday November 23, 2022 @03:27PM (#33724108)
> Permanently losing access to an account sucks a lot.

But mostly that's all. Usually it's a minor inconvenience. Occasionally it sucks a bit. Rarely it sucks a lot. Almost never is anything of value lost. It can be wholly eliminated by good data practices e.g. backups. (No one backs up their Amazon account data. It isn't designed for it. Because the "webdevs" think of the data as their boss's - squarequoting "webdev" because the effective decision is the CEO's and the "webdev" is just taking some abstract, ill-thought-through decision and making the ramifications concrete.)

On the other hand, it also sucks a lot when your gratuitously collected private information is taken to the darkweb. As countries become more accustomed to dealing with databreaches, they are beginning to consider legislating harsh compensation requirements and painful fines. Once that's happened, almost all of the private data that the user has in their account? Let the user keep it. We webdevs and our mortal enemies in business/sales/product will have to innovate new decentralised databases - where each node is a users' computer. And yeah, some things will be harder or not even possible (for the user). Other things will become possible that aren't at the moment (for the user). And at least you won't go bankrupt when a state level actor decides your database is valuable.

Re:“Invalid Username or Password”: a useless security measure by EamonnMR on Wednesday November 23, 2022 @05:05PM (#33725113)
Most people need to back up is a receipt for their transaction, and the main method people expect for receiving it is... email.
Re:“Invalid Username or Password”: a useless security measure by Alupis on Wednesday November 23, 2022 @05:34PM (#33725384)
There are some exceptions to this. Notably, Amazon is ruthless in enforcement of their "One Person, One Account" policy (worded not so eloquently in their official terms).

If you lose access to your Amazon account and open a new account, there's a non-trivial chance they shut it down without explanation. If your account ever participated in the marketplace from a seller side, then this policy is even more ruthlessly enforced.

Which means... email address verification is necessary for Amazon to at least guard against type-o's and other common form data-entry errors.

Re:“Invalid Username or Password”: a useless security measure by jhauris on Wednesday November 23, 2022 @11:32PM (#33727824)
Is this policy for a specific kind of Amazon account? I didn't recall seeing anything in the TOS, and they appear to have first class support for people with multiple accounts.

https://www.amazon.com/gp/help/customer/display.html%3FnodeI...

Re:“Invalid Username or Password”: a useless security measure by echelon on Wednesday November 23, 2022 @02:50PM (#33723712)
I worked for a big fintech.

- Zero email validation at signup measurably reduces friction. [1]

- Require email validation for bank deposits, once your customer is further onboarded.

- Encourage 2FA and other measures as the customer grows.

[1] (Much to the chagrin of all security-adjacent, marketing, account owning, risk, ATO prevention, etc. teams. I was directly in the path of these decisions, and it was interesting to see the various stakeholders argue their points. Growth funnel wears the pants.)

Re:“Invalid Username or Password”: a useless security measure by EamonnMR on Wednesday November 23, 2022 @05:03PM (#33725102)
Yeah you may not realize that a significant fraction of people don't remember passwords at all and need to reset on every login. If you don't allow self serve password resets you're creating a huge customer service burden.
Re:“Invalid Username or Password”: a useless security measure by fabiospampinato on Wednesday November 23, 2022 @03:43PM (#33724293)
Not true for end to end encrypted stuff, the server can't reset anything.
Re:“Invalid Username or Password”: a useless security measure by matt-attack on Thursday November 24, 2022 @10:09AM (#33732129)
I’ve had my Reddit account for 15 years. Never given them an email.
Re:“Invalid Username or Password”: a useless security measure by ruined on Wednesday November 23, 2022 @12:33PM (#33722109)
sending those messages is part of the same business case as reducing friction by not confirming the address :)
Re:“Invalid Username or Password”: a useless security measure by blacksmith_tb on Wednesday November 23, 2022 @12:36PM (#33722149)
I'd say that depends on what 'a conversion' is - if it's buying physical things (and getting shipping confirmations for them), an email is maybe not absolutely required, but most of your customers would probably still rather they got those?
Re:“Invalid Username or Password”: a useless security measure by MichaelCollins on Wednesday November 23, 2022 @12:44PM (#33722248)
Maybe they want SMS updates to their shipping, does that mean you should ask for confirmed phone numbers on signup? Of course not. Let them enter their email or phone number for shipping updates when they're confirming their purchase.

Ideally you shouldn't require users to make an account to make a purchase at all. There should be a "guest" path for purchases. Some sites still get this right. I can buy anything from plane tickets to pizzas without having an account on the company's website. Meanwhile half the "Show HN" non-commercial toy websites I come across seem to require a confirmed email for no good reason at all (probably because the webdev is hoping his little toy website somehow becomes a real business, and then he can spam my inbox with updates about this and turn me into a paying customer.)

Off the top of my head, here are some companies that don't require me to confirm my email address when making a purchase or an account: Southwest Airlines. Dominos Pizza, Hacker News, Reddit.

If those guys don't need a confirmed email address, probably your site doesn't either.

Re:“Invalid Username or Password”: a useless security measure by Alupis on Wednesday November 23, 2022 @01:52PM (#33723106)
These are not good examples of everyday websites.

Southwest Airlines knows an awful lot more information about you than you provide them. They don't need your email address because they know who you are - and they make it your responsibility to monitor changes to your schedule/flight.

Dominos Pizza allows you to monitor in real time the status of your delivery on their website after checkout. You can provide an email address to access the tracking status page again if you close it.

Hacker News is not a good representation of anything outside of a very tech-focused forum. It's designed to be anonymous, there is nothing to keep track of (order status etc) and if you lose your password to HN, you might just be SOL. That's not going to fly for the general public.

Reddit is focused on eyeballs and clicks - nothing else. You're not buying things on Reddit and waiting for them to deliver to your house or whatever. Reddit just needs you to click and look at things to make money. Reddit also requires an email address, but if you don't provide a real one then you're SOL if you lose access. Again, not going to fly for the general public.

The reality is, most regular sites do need a reliable way to contact you for business reasons. Some are even required to have your contact information (for international shipments, as one example).

Your email inbox does a good job of holding emails for you, so let's stop pretending it's a huge burden to get an email... and if you find your way onto some newsletter list just click the unsubscribe button. It's not that hard...

Re:“Invalid Username or Password”: a useless security measure by MichaelCollins on Wednesday November 23, 2022 @01:57PM (#33723165)
> The reality is, most regular sites do need a reliable way to contact you for business reasons.

In these cases, which I think are more unusual than usual, a email can be required during checkout. There's almost never a valid reason to require a confirmed email account during account creation, before the user has even decided if they want to make a purchase.

Re:“Invalid Username or Password”: a useless security measure by Alupis on Wednesday November 23, 2022 @02:11PM (#33723331)
We might be envisioning very different types of websites then. Some random dude's blog - no you don't need to enter your email address.

Buying something online or subscribing to a service? The company does need a way to contact you... which is going to be email.

Email addresses are more-or-less globally unique, which makes them very handy for identifying an individual customer. Verifying the email address is an extra step that can provide the business with more confidence when dealing with a new potential customer. Certain types of fraud vanish or are greatly impeded with email verification, such as carding attacks. Customer support tasks can be performed more reliably and with identity confidence of who they are dealing with, stopping account impersonation attacks and more.

With all that said, sites that choose not to verify email addresses put a greater burden onto the customer for support needs. Password resets, order tracking, cancelling subscriptions etc. all become more difficult if the email address entered by the customer had a type-o for example, or belongs to someone else.

That doesn't mean all sites should verify email addresses - but it does mean railing against any site that does is misguided.

Re:“Invalid Username or Password”: a useless security measure by MichaelCollins on Wednesday November 23, 2022 @02:40PM (#33723606)
Twitter or discord, why do these require me to confirm an email or phone number when reddit doesn't? Why do shop websites like Etsy require me to confirm my email address before I even decide to purchase or sell anything? If you're worried about credit card fraud, confirm my identity when I give you my payment info, not when I'm merely registering an account.
Re:“Invalid Username or Password”: a useless security measure by Alupis on Wednesday November 23, 2022 @03:06PM (#33723882)
What you propose would lead to increased cart abandonment. No business wants that.

Account registration is the perfect time to do email verification, if the business is going to do it. The user already is in that "mindset"... and clicking a link is really not very difficult. Everyone in that flow understands what is going on.

Sites like Etsy probably have a significant fraud problem... and as previously discussed verifying email addresses goes a very long way towards minimizing risk.

Companies like Twitter and Discord likely require verification for the same reasons - fraud/abuse. I am aware Twitter has had a history of abusing that data, but the initial reason for verification remains the same.

I'm actually surprised more websites don't require verification. It's easy to do, and the benefits are very obvious. Most users aren't bothered by it either...

Smaller ecommerce sites still keep the Guest Checkout flow available because they would rather not impede checkout for any reason - although that means they take on additional risk. Major ecommerce sites require accounts (think Amazon, Newegg, Etsy, Walmart, Zappos, Chewy) and some do require verification. At their scale, fraud and abuse become very difficult problems that require a lot of time/resources.

OAuth/Social Login has removed some of the need to verify email addresses at the business level. This is because a trusted 3rd party Identity Provider has already done that for you, and most OIDC IDP's already provide an "email_verified" flag of sorts. Depending on your trust level (connecting to Google's IDP vs. random IDP), you can just use this data and assume it's been verified, removing that step for the customer.

Re:“Invalid Username or Password”: a useless security measure by chongli on Wednesday November 23, 2022 @03:45PM (#33724311)
Dominos Pizza allows you to monitor in real time the status of your delivery on their website after checkout

Dominos doesn't even verify that you own an email address when you register one. I have received Dominos delivery updates sent to my email address for pizzas delivered to a person who doesn't even live in the same country as me. These updates contained a bunch of PII information about the customer including their exact home address depicted on a map inside the email.

Web developers: verify that people own the email addresses or phone numbers that they register!

Re:“Invalid Username or Password”: a useless security measure by listenallyall on Wednesday November 23, 2022 @09:31PM (#33727244)
> Dominos doesn't even verify that you own an email address when you register one

Considering that Domino's doesn't verify you're actually at the physical address you're having a pizza delivered to, I doubt they are sweating an email addy

Re:“Invalid Username or Password”: a useless security measure by quacksilver on Wednesday November 23, 2022 @03:03PM (#33723847)
Could part of the pattern for requiring an email address (or phone number) at time of purchase be reduced customer support costs for the vendor.

With an email address the customer can reset their own password for using their account with self service features - like get a duplicate invoice or view/change/cancel a reservation or similar stuff.

Without an email address / phone number / something to link a customer to their order, the customer will need to phone up a call centre or visit a store or use live chat to get what they need.

Southwest probably have a call centre or live chat anyway. Dominos have stores (and presumably a customer service department) and a pizza order is probably only interesting for a short time.

If the customer can't sort their order out or get it sorted out, they will complain or give bad feedback. Even if it was their choice not to leave an email as they were too busy.

Your business without any of these things has no incentive to get them if it can just collect emails instead and let users use self service features. Even if you already have call centers / live chat / stores then your cost of dealing with the customer via a self service portal is probably way cheaper than using them.

Re:“Invalid Username or Password”: a useless security measure by listenallyall on Wednesday November 23, 2022 @09:34PM (#33727262)
You're missing his point. He's saying that the whole point of having an "account" is often not actually necessary. Domino's and Southwest are much more focused on making it as easy as possible to buy a pizza or a plane ticket, without an account being mandatory.
Re:“Invalid Username or Password”: a useless security measure by quacksilver on Thursday November 24, 2022 @09:14AM (#33731461)
I was attempting to say it may be more convenient / less expensive for the vendor if all customers are forced to have self-service accounts rather than having to complain to manned customer service or via twitter or whatever.
Re:“Invalid Username or Password”: a useless security measure by gauravphoenix on Wednesday November 23, 2022 @01:50PM (#33723085)
>spam users with nonsense like product updates

IMHO, not all product updates are nonsense.

Re:“Invalid Username or Password”: a useless security measure by MichaelCollins on Wednesday November 23, 2022 @01:55PM (#33723139)
[x] - Send me emails about product updates.

(Receiving these emails should be opt-in. But companies often find lame excuses to ignore this preference so I prefer to not hand over my email address at all.)

Re:“Invalid Username or Password”: a useless security measure by renewiltord on Wednesday November 23, 2022 @02:27PM (#33723471)
Users are trained to put in their email. Making them choose a username increases friction if the username is non-public (i.e. it's not instagram). Ideally, using SSO speeds the whole thing up, but if not, then it's better to just use email.
Re:“Invalid Username or Password”: a useless security measure by jstarfish on Wednesday November 23, 2022 @04:13PM (#33724611)
> Most sites that require an email don't need an email, and only ask for it so they can spam users with nonsense like product updates.

Not the only reason. It adds friction for people trying to create an army of sockpuppet accounts.

Re:“Invalid Username or Password”: a useless security measure by account42 on Thursday November 24, 2022 @09:28AM (#33731613)
Not a lot of friction. Especially if you don't restrict the allowed email providers.
Re:“Invalid Username or Password”: a useless security measure by KMag on Wednesday November 23, 2022 @12:05PM (#33721733)
The lowest friction workflows make data collection/entry as lazy/delayed as possible and maximize optionality. Allow users to "save as default" as part of their normal workflows on your site, rather than demanding the information up-front at signup.

The welcome/email verification email should have an expiring passwordless sign-in link (and maybe a way to set password if you decide to support passwords). If I use your site rarely enough, I don't even save your information into my password manager. Your password reset workflow is my normal sign-in workflow. Kudos to sites that don't force me to generate a one-time random password for this sign-in workflow. In practice, I think a lot of people accidentally use this as their login procedure on rarely visited sites.

If account creation is part of the ordering workflow, make the most significant 6 (or more) digits of the order ID a secure message authentication code of the rest of the digits and delay verification of the email address. That allows you to delay email address verification and still securely correct email address typos (of recent orders) if the user records their order ID.

If your site has made birthday mandatory but you haven't demanded a government ID for verification or run a credit check, I've lied to you about my birthday.

If your site demanded a mailing address but you're not shipping anything to me, I've lied to you about my address.

If you're demanding to over-collect information, and I'm polluting your data lake, that's on you.

Side note: the McDonald's app is nice in not requiring (or apparently even allowing) passwords to log in. However, there's a problem with its state transition, where the user needs to exit from the dialog that sends the sign-in link before they go to their email and click on the sign-in link, otherwise the user gets dumped to the next step without having actually signed in.

Re:“Invalid Username or Password”: a useless security measure by ev1 on Wednesday November 23, 2022 @01:40PM (#33722972)
> Side note: the McDonald's app is nice in not requiring (or apparently even allowing) passwords to log in. However, there's a problem with its state transition, where the user needs to exit from the dialog that sends the sign-in link before they go to their email and click on the sign-in link, otherwise the user gets dumped to the next step without having actually signed in.

The mcdonalds app loads several dozen data collection sdks, pihole practically had a meltdown when it launched

Re:“Invalid Username or Password”: a useless security measure by whateveracct on Wednesday November 23, 2022 @02:36PM (#33723559)
Discussions of friction and login/signup always drive me crazy. Like I get the need to get people to sign up. But security is always an afterthought - it always loses to lower friction.

And don't get me started when the PM starts lowering friction to the point where they are basically trying to trick the user.

Re:“Invalid Username or Password”: a useless security measure by Spooky23 on Wednesday November 23, 2022 @04:33PM (#33724819)
Even an async validation would be better. I have <common name>@gmail.com, and get several newspapers and some other subscriptions for free.

In one case, a person named Mary in Australia sends their loved one a gift card every year, and the retailer doesn’t provide any information about Mary. In another case, a student missed out on their work study job and a opportunity for early class enrollment due to a bad email.

It’s sad as all of these customers don’t even know that they have a problem.

Re:“Invalid Username or Password”: a useless security measure by uxp on Wednesday November 23, 2022 @08:09PM (#33726674)
Validating any contact method that has the potential of sending PII, Health, or financial data should be mandatory by law.

At least once a year I get an automated phone call from a regional hospital letting me know some minor's test results. Calling the hospital's CS department in order to notify them or somehow get my phone number removed from the account is impossible, because I'm not this person nor their legal guardian and HIPAA regulations prevent me from instigating a change on someone else's medical records or accounts.

Re:“Invalid Username or Password”: a useless security measure by dietketchup on Thursday November 24, 2022 @08:15AM (#33730951)
Don't call CS. File a HIPAA complaint. The provider who is sharing PHI illegally will certainly care. They have no duty to validate the phone number, but they do have to respond to a complaint saying they shared PHI with a person who is not THE person.
Re:“Invalid Username or Password”: a useless security measure by yencabulator on Tuesday November 29, 2022 @12:17PM (#33790316)
An extra problem there is that phone numbers get reused. They might have verified the number at the time the previous person still had it.

I get all kinds of messages to someone called Amy from multiple sources, so I believe Amy really had my phone number earlier. No medical results yet, but healthcare appointment reminders for sure.

Re:“Invalid Username or Password”: a useless security measure by IshKebab on Wednesday November 23, 2022 @12:50PM (#33722310)
I've used exactly one site ever that had this sign-up flow, and hundreds that had the stupid "invalid username or password" error.
Re:“Invalid Username or Password”: a useless security measure by Beldin on Wednesday November 23, 2022 @01:55PM (#33723142)
True. Moreover, even if a site implemented this in a naive way, they made the UX much worse for the attacker. And that constitutes a significant issue, if we follow the reasoning of the article.

It does, actually: it hampers casual attackers -- those looking for any account in. On the other hand, attackers out to break into a specific account will not be deterred. Then again: they are not deterred in either case, so you might as well go with the version that impacts some attackers.

Re:“Invalid Username or Password”: a useless security measure by dwheeler on Wednesday November 23, 2022 @01:58PM (#33723180)
Exactly, if you reveal that an account exists when you just type in an email address, then you have a privacy failure and probably a security failure.

For example, the OpenSSF's secure software development fundamentals course <https://openssf.org/training/courses/> in its section on minimizing feedback <https://github.com/ossf/secure-sw-dev-fundamentals/blob/main...> says:

* If a user tries to create an account using an email address, don't tell the user if an account with that email address already exists. Similarly, if a user tries to do a password reset using an email address, don't tell the user if there is no account with that email address. Providing that information would allow an attacker to determine if a specific email address is being used (or not) by some existing account.

Now for the unpopular take: not everyone lives in the US. The GDPR requires protection of personally-identifying information, and in many cases that includes email addresses that identify individuals. There are exceptions, but it's typically better to keep email addresses private unless the user specifically authorizes it.

Re:“Invalid Username or Password”: a useless security measure by sbf501 on Wednesday November 23, 2022 @02:41PM (#33723616)
0.1% representing!

I got some code to fix.

Re:“Invalid Username or Password”: a useless security measure by akerl_ on Wednesday November 23, 2022 @05:16PM (#33725226)
Sure, I guess? But the overwhelming majority of sites on the internet do not do this. Primarily because their new signup flow has priorities that matter an order of magnitude higher for them than avoiding leaking whether an account already exists.
Re:“Invalid Username or Password”: a useless security measure by iudqnolq on Wednesday November 23, 2022 @09:57PM (#33727375)
By your definition almost no popular website - including Google - implements signup flow correctly.