6 ms·
Regular reminder that new users in general don't care at all about the security of your site. Most of your signups are not going to generate and store a secure
by bigiain 10y ago
Regular reminder that new users in general don't care at all about the security of your site.
Most of your signups are not going to generate and store a secure password "just to try you out", as evidenced by the most common password here "123456". If you force people to signup to try your site/app, many (most?) of them are going to use a crap password. If you're _lucky_ that'll be 123456, and not their email/facebook/internet-banking password.
The answer isn't to try and force "good passwords" from users who don't care. Remember, by definition - they don't care.
We need to start trying to not require users to come up with passwords until they do care. Maybe just cookie me and let me tromp around as an unauthenticated user until I do something that needs me to set up a password-protected account. Maybe ask for my email and send me a login link that hooks me into my account/data without me setting a password (lets face it, your password security is going to fundamentally rely on the security of my email account, 'cause your "forgot password" story says you'll happily send a password rest link there, right?
I know Start-up-de-jour desperately needs "signed up user numbers" for their investor pitch, but that's not going to motivate me to stop using 123456 or password123 as a password when startupdejour.io demands I create an account just to look around.
- grrowl 10y agoEmailing a single-use "sign in link" to a user (Slack calls these "Magic Links") is the way forward. Yes, it move the single point of failure to the user's email account, but expecting the regular user to use (and remember) unique passwords for each service is impossible -- they simply won't do it. Plus, when/if your service is breached, you won't compromise all their other accounts as well.
- jcrites 10y agoIt's really a shame that we haven't solved this problem yet as an industry. I was thinking we could build a general purpose version of "Magic Links" for logging in, where the format of the email is well-defined, and the user's browser is able to receive these messages on their behalf through some form of integration. You could imagine a webmail provider offering some kind of polling or websocket API for listening for when these messages arrive. When the site they're visiting indicates through its web page that, "I'm trying to authenticate you by email", then the browser can fetch recent incoming messages of this type, then parse them and display UI chrome like "Xyz.example.com wants to authenticate you". You click a button to log in passwordlessly, which involves sending an HTTP request to a link specified in the email. Coordination occurs on the server side and the login is allowed. There are probably some details I'm not considering, but it doesn't seem like it'd be too hard to build a prototype, and if standardized and deployed it would eliminate the need for passwords. I gather that Mozilla Persona works along similar lines, though I confess to not knowing the exact details. There would be practical difficulties integrating all of these things together, though: email, browser, and website login, and gaining adoption in the real world. There are also sites that don't require email on signup, but this feature could be supported only for people who want to supply email. The email address used for this feature could also be a different technical address unrelated to the primary mailbox, where only login requests are sent. This could also help expedite the email traffic to ensure it's real-time. The browser could automatically fill in the email address when challenged by a website supporting this login method. Alternatively, perhaps a browser vendor could introduce a de facto standard where sites can integrate via an API with the browser's password safe features. Chrome can save passwords and synchronize them across devices. Maybe it wouldn't be too hard for sites to comply with a microformat that helps the browser understand when to generate a password on signup, and when to provide it, etc.
- kodfodrasz 10y agoYou seem obsessed with one implementation. Passwords themselves are obsolete. Actually the problem is already solved for at least a decade: Certificate based authentication. Browsers support it. Try StartSSl registration, for example.
- bigiain 10y agoYeah - but that's like saying "email security and integrity has been solved for two decades", while _technically_ true, how many of you have talked your mom through setting up PGP and had her then "just use it"? (or tried to handhold a less-than-technical colleague through getting a StartSSL account?) I'm pretty sure if any service less-technical than a CA authority starts pushing wide-spread user-driven in-browser certificate-based authentication, within days there'll be scammers and phishers faking the setup process to install untrustworthy ssl root certs so they can mitm Paypal/Facebook/everybody... How would _you_ explain to your mom the difference between installing Pinterest's new authentication certificate, and installing, say, the Charles Proxy ssl MITM cert?
- drdaeman 10y ago> How would _you_ explain to your mom the difference between installing Pinterest's new authentication certificate Actually, even with current terrible UIs, there's a reasonably big difference between installing client certificate (there even used to be a <keygen> HTML tag for those - although it's unsurprisingly marked as "deprecated" now) and trusted CAs.
- theandrewbailey 10y ago> (or tried to handhold a less-than-technical colleague through getting a StartSSL account?) I tried getting one myself a few years ago, and I couldn't. The process was too obtuse and obscure for me to follow along the entire way.
- drdaeman 10y agoSadly, it's only theoretically solved. Browser vendors have refused to touch that for years, so everything PKI-related has a cryptic UI hidden beneath 3+ clicks deep in the most obscure settings dialog areas. And some pieces are completely missing, like session state management (it's just like with HTTP auth - there are hacks to implement it, but they're hacks). Another issue is, with current implementations not really fancying the idea of CA-less self-signed client certificates, so you'll most probably need a certificate-per-site approach. And with a ton of certificates (even if they all for the same public key), you'll need to automatically sync them to another devices somehow. (The usual reasoning for not doing anything I saw was "no one uses this". Sure thing, given it's barely usable.)
- camtarn 10y agoIt's worth pointing out that in this particular case, some people will have created their Last.fm accounts more or less solely for use with Audioscrobbler, a protocol which allows them to track music listens through various third-party music players. The important bit about that is that the Last.fm/Audioscrobbler account credentials get typed directly into the third-party players - usually there's no browser involved in authentication, and in some cases the players will also be on a mobile device. There's a definite incentive for passwords to be simple (if you're going to type them in on a mobile keyboard) and weak (because it's just music metadata). So, a 'magic link' style of logging in might work here, but it would have to be complemented by an easy way of generating auth tokens for player apps - for instance, short one-time-use codes that expire quickly.
- flushandforget 10y agoI wrote a simple web app to work with last.fm's api. A little fiddly, but in essense it worked. Somewhere buried in settings were all the apps that have access to my account. I then went back to Spotify and noticed it wanted my username and password. And ever since, I just haven't been bothered. I'd rather some throwaway autogenerated app linking passwords and authenticating consistency. Copying and pasting links isn't that hard. Go to last.fm, generate OTP token/link, paste into Spotify. Done. I should have some easy way to identify authenticated apps under my account and kick them out, or reset all. Not all of us use Web mail. And I might not want a link automagically opened there and then, under a browser.
- wepple 10y ago> Yes, it move the single point of failure to the user's email account This isn't even that greater of a concern; it currently is in 99% of cases the method for password reset anyhow.
- Nadya 10y ago>Yes, it move the single point of failure to the user's email account That is already the case for the supermajority of people. They use one email account for everything and you can simply "Recover Password" on various services once you gain access to their email account. Not many people purposefully use unique, individual email addresses for every single service they sign up for...
- ryan-c 10y ago> Not many people purposefully use unique, individual email addresses for every single service they sign up for... When they do, generally email for all of them ends up in the same account anyway.
- discordance 10y agoIf you're going to recommend emailed 'magic links', then might as well use Google/Facebook/etc as an SSO indentity provider
- tudorw 10y agowhy should users care ? what makes you think it's our job to make them care, we built another shitty system, it's not the users fault, asking them repeatedly to do something proven by cognitive science to be very challenging for most is just dumbness incarnate....
- bigiain 10y agoExactly - why should they? So why are we pretending they do - and requiring them to give us email addresses and set up secure passwords? (Especially when the "upgrade password storage to something more secure than plain text or MD5" is constantly being deprioritised below "add features X, Y, and Z that the product owner claims our next three investors on our pitch schedule have Tweeted about in the last month"... "We'll 100% definitely get to it once Series A comes in. for sure! Except perhaps for the 7 million 'legacy users' we signed up with plaintext passwords during our growth hacking private investor and seed round stages...")
- zer0gravity 10y agoThe security model based on passwords kept by site provider is totally broken. I, as a user, don't want to keep 20 different passwords for 20 different sites. What I want, is host my own security agent through which I can talk with any site. If I want to authenticate with site x, I simply point it to my security agent url and that's that. Open ID was/is an idea. This approach will drastically lower the incentive for an attacker. Each attack will only get the data of one user, not millions.
- toyg 10y ago... Until the openid provider is breached, like LinkedIn was. Then you get access to everything for everyone. Decentralized schemes are safer overall. Ideally you want something like what LastPass does: local credentials replicated on the network in encrypted form. This way you take away responsibility for safe storage from unreliable websites, but you don't place the whole burden on the user (as the data is replicated and locked by a single password).
- zer0gravity 10y ago> What I want, is host my own security agent I don't trust third parties, no matter who they are. Technology can be developed so that the burden on the user is reduced, but nodoby wants to go there, because after all companies do want to have as many data about the user as they can...
- andybak 10y agoI don't trust 3rd parties but I do evaluate the threat that comes directly from large companies to be lower than the threat that comes from criminal hackers.
- theandrewbailey 10y agoThat's the idea behind cloud free password managers (like KeePass) and their browser plugins.
- witty_username 10y agoOpenID registration is the solution to this problem.
- type0 10y agoOpenID is dead thanks to OAuth. I hope IndieAuth could get some traction but the problem with it is that every user needs to have their own tld domain but many registrars and dns services don't even use two factor authentication.
- user5994461 10y agoActually, it's now called "OpenID Connect" and it's a profile of the OAuth spec.
- ultramancool 10y agoWhat on last.fm ever needs a secure password though? Maybe someone can listen to my premium radio if I paid for it, or scrobble as me, but I really don't care about either of those. As a user, a less secure password for sites that need less security just makes sense.
- donatj 10y agoSee, I disagree. I think scrobbling is Last.fm's biggest feature and it's important for them to keep it accurate. I would be devastated if someone messed up my scrobbles, I've been scrolling for 10 years and have amassed very nice statistics about my listening habits. On top of that I have to imagine they sell this data to record companies and the less accurate the data the less valuable.
- zodPod 10y agoThis SO MUCH. I can't stand when I get an email, from some service that I haven't used in 10 years and that I have no recollection of actually signing up for, saying "Oh sorry we had a hackings. You need to change your password." This happened with Yahoo's weird online publishing service thing. I don't even remember the name of it but one of my passwords was in their service and, at the time, I was using the same password everywhere. By the time I got the "Oh we got hacked" email, my twitter account was compromised as well as a few other sites. I didn't even remember signing up for their service let alone having an account. I feel like some sort of regular clean out should also be standard. If I haven't looked at your site in 5 years, why would my account still be available? I know there are situations where that could cause problems but I'd rather lose an account for (random forum that I signed up for in 2008) than possibly have a breech that could, somehow, lead to my information getting stolen...