News for hackers. Stuff that matters.
Re:Lastpass Security Incident by danenania on Wednesday November 30, 2022 @11:53PM (#33812495)
Considering that 99% of web app password authentication reduces to email authentication via ‘forgot password’, a good first step would be dropping the password and just using emailed tokens (or links) directly.
Re:Lastpass Security Incident by mccorrinall on Thursday December 01, 2022 @12:39AM (#33812766)
When I was studying we had to use the computers in uni when presenting homework.

It gets really annoying when you want to sign into $service on those machines, but you need to use a magic link. Because the you need to login into your gmail, which requires an additional 2fa (and you can’t receive sms in a building that has 6 stories but no femto cells).

Unfortunately google requires either their app or SMS. They dropped pure totp for some reason.

Awful experience.

Re:Lastpass Security Incident by tpxl on Thursday December 01, 2022 @03:38AM (#33813799)
> Unfortunately google requires either their app or SMS. They dropped pure totp for some reason.

Gmail TOTP still works fine?

Re:Lastpass Security Incident by richrichardsson on Thursday December 01, 2022 @05:31AM (#33814531)
Yup, but it seems it will default to "click the notification on your phone" as soon as you've signed in on a phone. You need to click "try another way", even if you've explicitly told them that TOTP is your preferred default.
Re:Lastpass Security Incident by CorrectHorseBat on Thursday December 01, 2022 @04:59AM (#33814336)
If you first enable app or sms then you can add totp (that was my experience at least)
Re:Lastpass Security Incident by FeistySkink on Thursday December 01, 2022 @05:09AM (#33814400)
Also hardware keys work just fine with Google.
Re:Lastpass Security Incident by cyphar on Thursday December 01, 2022 @05:39AM (#33814587)
> Unfortunately google requires either their app or SMS. They dropped pure totp for some reason.

I use TOTP with my Google Account all the time. If you have a phone registered with that Google Account it will default to the push notification system first (it might even be possible to make this no longer the default, I'm not sure), but you can always click the button to switch to alternative 2FA options.

Re:Lastpass Security Incident by goosesanta on Thursday December 01, 2022 @02:18PM (#33821233)
> for some reason

Google plainly dropped totp wherever possible in order to confirm everyone's identity.

Totp was an open standard that didn't help them spy on anyone, and they regret releasing it bigtime.

Re:Lastpass Security Incident by RulerOf on Friday December 02, 2022 @11:52AM (#33833018)
>Unfortunately google requires either their app or SMS. They dropped pure totp for some reason.

You have to add a phone number, turn that on for 2fa.

Then you can add TOTP.

Then you can disable SMS.

SMS will still work for at least a week because fuck you.

Re:Lastpass Security Incident by heleninboodler on Thursday December 01, 2022 @01:11AM (#33812941)
I hope not. Not only is this often frustratingly slow, it really complicates things for people who use devices where they don't receive email. Myself, I only receive email on my computer and one mobile device. I have several devices where having to click a link in an email to log into a site means annoying gyrations trying to transfer links from one device to the next. This is especially annoying when whatever mechanism you use to transfer the link does link previews and the login link is one-time-use. :D
Re:Lastpass Security Incident by dspillett on Thursday December 01, 2022 @06:39AM (#33815009)
> means annoying gyrations trying to transfer links from one device to the next

There are alternatives to this, such as typing a code into the login prompt instead of following a link (which will be submitting that code). This does limit the size of token that can be used because it needs to not be too inconvenient for the user to type, but if the code's validity is sufficiently short-lived, and properly unguessable, this can be done without compromising security any more than it already is by involving SMTP in the process.

Of course the other problem with email-only password resets is that users often receive email on the same device they are trying to authenticate – so if someone has left a machine unlocked with their mail account logged in, an attacker can gain access to any site/app that uses this password reset mechanism. One of the reasons that email and SMS are not great choices for a second factor, and even less good choices for what is sometimes effectively the only factor.

Re:Lastpass Security Incident by heleninboodler on Thursday December 01, 2022 @05:52PM (#33824141)
Agreed. This is one reason I limit the number of devices that have my email credentials. Using 2FA everywhere is sadly not practical yet, so there are a nontrivial number of accounts that are, as you point out, effectively owned by anyone who can access my email.

I actually occasionally fantasize about implementing a mechanism that I could use from my desktop (where my password manager is) to send passwords as needed (e.g. one at a time) to my devices (I really like not worrying about syncing whole vaults). Encrypt the password using an epehemeral key (gets deleted after 60 seconds, for example) on the transfer service and a local key derived from a random six digit number. Display the number, send a url to the device, and anyone hitting that URL has 60 seconds to enter the six digit code and it decrypts the password and drops it on the device clipboard. This is about 1000 times better (and over-engineered, naturally) than my current practice of "paste it in a slack message to myself."

Re:Lastpass Security Incident by swyx on Thursday December 01, 2022 @06:32AM (#33814970)
except this is not good UX when sometimes the email links take minutes to arrive, if they arrive at all.
Re:Lastpass Security Incident by msielski on Thursday December 01, 2022 @09:02AM (#33816301)
This does seem to be the latest trend - passswordless authentication or "magic links."