5 ms·
> Often this will be combined with fallacious notions such as “remember this device”, the idea being you only have to go through all this the first time when lo
by lolinder 3y ago
> Often this will be combined with fallacious notions such as “remember this device”, the idea being you only have to go through all this the first time when logging in from a particular device. This idea is fallacious because the web has no notion of a “device”, and this is a very intentional design choice made for privacy purposes. We are literally living through the gradual phase-out of third-party cookies, amongst other functionality, specifically to try and prevent this sort of thing, so why do web developers persist in believing in this fiction of a “device”? My own browser erases all cookies from an origin immediately after the last tab from that origin is closed, so these sites are convinced I am logging in from a new “device” every single time, and then demand I respond to one of these challenge emails.
The phasing out of third-party cookies has nothing to do with the "remember this device" functionality, because those are almost always powered by first-party cookies, which are not being phased out.
The author has configured their browser to throw away cookies when the last tab closes, and that's their prerogative, but anyone who is savvy enough to configure that setting is also savvy enough to understand that that will break "remember this device". For everyone else, that phrasing is a perfectly reasonable abstraction on what is actually happening.
- londons_explore 3y agoI kinda wish there was something like cookies, but even more persistent. Lets call them permacookies. I want to "remember my device", and have that keep me logged in forever with a permacookie. I don't even want to have a username and password. I want to create an account and be forever logged in. There would be mechanisms to backup my permacookies, or transfer them to other devices. I'd have control of which sites could set permacookies for when I didn't want to be tracked too.
- eternityforest 3y agoCookies already last months or years, I don't think the tech limits duration so much as the sites explicitly set a time, or clear the token on the backend. What I'd really like is to just be able to use the native filesystem. But Firefox doesn't like that, and people apparently use that, so it's not a real standard. At the very least, they should make the origin private filesystem user-visible with a flag. Don't allow everything, just ~/WebData/default/DOMAIN_NAME
- notpushkin 3y agoSo, like Passkeys / WebAuthn?
- QhwyF3AxE 3y agopasskeys is a common noun (like the word “password”) and therefore should always be lowercase unless it’s the first word in the sentence.
- simonw 3y agoHonestly that feels like what apps are. One of the most compelling reasons to install an iOS app for something like an online bank is so that I won't have to worry about my cookies expiring and forcing me to login again.
- samwillis 3y agoThis is why I hope PWAs take off more. If there is an implicit "save first party cookies forever" for PWAs that have been "installed" and we make them discoverable it's a net win.
- londons_explore 3y agoApple will make sure PWA's aren't successful. They can't risk their control over the app ecosystem.
- j5155 3y agoAre you aware that iOS supports PWAs, and recently implemented notifications for them?
- samwillis 3y agoExactly, they are in recent years moving to address these previous issues, I applaud them. I would like it if they were more discoverable, but not necessarily with the obnoxious pop ups. It would be awesome if they let you list a PWA in the App Store for a fee or the 30% cut.
- londons_explore 3y agoOnly 8 years late: https://developer.chrome.com/blog/push-notifications-on-the-open-web/ https://developer.chrome.com/blog/push-notifications-on-the-... Besides - there are plenty of other things Apple can do to ensure PWA's don't take off. For example, there is no ability for a web-app to have a "click here to install to desktop" button - the website must try to guide the user into clicking the share button and then creating a desktop icon - which most users don't associate with 'installing' something. Also, the 50Mb limit on PWA's prevents a lot of usecases - like photo/video editors, and even most messaging apps.
- deleted 3y ago[deleted]
- hanniabu 3y agoAnd then the credentials get stolen through phishing
- hkt 3y agoThe idea with client certificates is that they'll live in a secure keychain and never leave it. The API exposed by whatever manages them will expose functions of the key (authenticate, encrypt) but not the key itself. If the implementation is decent, you'll authenticate every request, so it isn't possible for requests to be forged or credentials stolen unless you've got a vector to attack the OS's keychain.
- Pxtl 3y agoI saw this pattern done on a forum. You just provided your email, and it would set a super-long-lived cookie. There was a button for "recreate my cookie" which sent you an email - like a password reset function without a password. It was surprising the first time I used it but now I wish everything that didn't handle cash worked that way.
- jaredhallen 3y agoSounds like certificates. You can use ssh this way, for example.
- justsomeadvice0 3y agoYou can use mTLS client certificates (kept in the system key store) in browsers this way; but the UX is pretty hard to get right, and certificates nearly always have to have an expiry date to deal with the compromise-able nature of keys imported into the system key store.
- hkt 3y agoWhat you're looking for is client certificates. This has existed for years but webby people think users are too stupid to use them, so we get the menagerie of half baked trash we have now instead.
- sublinear 3y ago> What you're looking for is client certificates. I agree with this, but... > users are too stupid to use them they are. Key management is not trivial.
- SoftTalker 3y agoYes, if you've ever managed a shared unix system that uses ssh keys for login, you know that a large fraction of users cannot manage them. Among the steps of generating a key pair, getting the public key (not the private one) into their authorized_keys file (which is in a hidden directory, for pete's sake) without introducing any extra characters or line breaks or getting the wrong permissions on the file, getting their ssh client programs to use the proper private key for the host they are trying to log in to, or figuring out ssh-agent, there are just way too many opportunities to screw up or get confused.
- hkt 3y agoIt seems a little bit uncharitable to assume the UX on client certs has to be as bad as the UX on SSH keys, although I'll concede the point that historically it has been.
- hinkley 3y agoWhen I worked on a code signing app, I had front row seats to how magical everyone thinks certificates are. It took me several years to convince the group that they aren't that complicated. I think the world would be a better place if LetsEncrypt had come into being about five years earlier.
- drdaeman 3y agoIt's a myth, they are not. They are uneducated and lazy¹, not stupid. Save for minorities with genuine learning disorders, people can learn how to click/tap a bunch of buttons in a sequence. They aren't running a PKI (that's on platform/browser vendor), they are just picking an identity from the list after all. They learn how to click the right buttons all the time, as UI designers' managers decide it's time for a new bonus and swing things around with a "new graphic language". Basic certificate management (from end-user perspective) is not harder than password management. Passkeys are conceptually the exact same thing² as TLS client certificates, just without a purposefully neglected UI and a DIY attitude³ (TLS is supported by nearly anything, barely anything knows about WebAuthn JS shenanigans). 1) Not in a bad way. "Lazy" as in "lazy evaluation", not "lazy ass". Maybe there's a better word for this. 2) Save for some technical details, both are essentially keypair management. 3) There is almost no UI, it's just an API then all the visual bits are left out as an exercise to individual app designers (partially on platform/browser developers, partially on website developers). Browser vendors just hated those areas because they weren't deemed cool and fancy ([un]like some JS framework of the day) and shoved them under the rug as deep as they could. And unlike TLS, there is no standard how to pass data around, everyone invents their own `POST /login/webauthn` semantics.
- seiferteric 3y agoMight as well use client certificates at that point. Along with TFA, if we don't have users choose passwords, then just issue a client cert and have it installed in the browser, would probably require some new web standard.
- amadeuspagel 3y agoThe max age of a cookie is a little more then a year, meaning that as long as you visit a site more then once per year, this is possible.
- charcircuit 3y agoCoookies can live longer than a year. Making it no longer possible to make them "permanent" is a browser specific thing.
- fooker 3y ago>There would be mechanisms to backup my permacookies, or transfer them to other devices. There would also be intentional and unintentional mechanisms for stealing these permacookies.
- ballenf 3y agoPassword managers could take over and manage cookie storage/retrieval. Or browsers could treat cookies more like passwords and have a user-controllable flow on each new session: "Here's this site's cookies from your last session, do you want to place these back in the browser storage?" The fundamental issue is that browser cookies and password managers have an overlap in their usage domain.
- kwhitefoot 3y agoFirefox remembers my passwords for me already. Why would I need an extra tool to do it? And so does Android.
- bazzargh 3y agonot all of my passwords are for browser-based services, not all of my secrets are passwords, and I have several devices with different operating systems. (eg, my password manager includes github recovery tokens, ssh keys and passphrases, recovery questions, my tax and health service identifiers, wifi passwords and the admin passwords)
- Brian_K_White 3y agoI think SQRL does this. But since no one can own it or sell it, it will never be adopted by anything that matters.
- CoastalCoder 3y ago> I kinda wish there was something like cookies, but even more persistent. Fruitcakes.
- AndrewOMartin 3y agoMy first thought was "ship's biscuits".
- zuppy 3y agowe already do have that and needs no certificates or other complex things for the end user: https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage https://developer.mozilla.org/en-US/docs/Web/API/Window/loca... is it secure? hell no, but it can be used.
- hinkley 3y ago[citation needed] on local storage being more durable than cookies.
- ozim 3y agoWebauthn should allow use of private key authentication stored on external hardware key or in device. You really want support for key authentication just like ssh. You shouldn’t move private keys between devices, you should have easy way to add new public keys to a service when you setu new device. Problem is permacookies or private keys don’t really allow ad-hoc access but maybe nowadays people don’t need to login to their accounts from cyber cafes :)
- axelthegerman 3y agoHow about local storage? Only downside is that this data isn't sent automatically on ever request (unlike cookies). It would be possible though to send this secret from local storage via a separate request and receive a session cookie that then let's you be logged in automatically
- hinkley 3y agoMaybe shared local storage should be a browser standard. Let me keep track of my own data, but also share it with my tablet and phone by clicking a bunch of buttons.
- thelastparadise 3y agoEven better: shared storage where every website has access to the same storage data. Log in once, on one website, then be logged in on all websites forever.
- hinkley 3y agoIsn't that basically third party cookies all over again? If you work for advertisers this sounds like a great idea. Better than eating babies.
- danShumway 3y agoThis is circling around Native File Access, which is absolutely something the web needs and if handled correctly would be a huge improvement for user privacy and user autonomy. It would open the door for fully offline webapps with no accounts or serverside components, with much better sandboxing than native apps, and with full user control over app data using just a file browser. And it would allow for app data that could be easily shared between apps when necessary without compromising user privacy or security because the app data would just be a directory with files. BUT... the problem is that if handled incorrectly it would be a disaster for web security, would open up tons of holes for user tracking and data theft, and would basically be a horror show. There are a dozen things that could go wrong with the spec, and all of them would be serious problems if they did go wrong. And Chrome is heavily involved in the spec. So it's a tough position to be in to try and figure out whether it's worth advocating for. Mozilla currently considers native filesystem access to be harmful, and I don't know whether or not I agree with them. I wish Mozilla would propose an alternative spec developed entirely internally without interaction from Google.
- kmeisthax 3y agoThis is what HTTP auth headers are for, but the UX for using header authentication on modern browsers is utter garbage. There's no way to present a themed login form, no way to log the user out at all, and all sorts of weird papercut bugs[0] in between. [0] My favorite: opening DevTools triggers a second credential prompt because the DevTools session wants to download some mapfiles or something. No infrastructure exists to make that HTTP request in the context of the current tab, apparently.
- freeone3000 3y agoYou can log the user out by changing the “realm” parameter, which is a freeform string and can be quite long. As well, setting realm will cause devtools to use cached credentials similar to a new tab. “No themed login form” oh no! Anyway. (I really think that the “theming” on login and sign-up forms breaches which bits are done by the browser and which bits are not. We’ve had to kludge back support)
- codazoda 3y agoI wish there was better browser support for this but I still use it for pet projects. Last year I wrote about why I’m still using HTTP Basic Auth. https://joeldare.com/why-im-using-http-basic-auth-in-2022 https://joeldare.com/why-im-using-http-basic-auth-in-2022
- herewulf 3y agoMaybe you don't listen on port 80 but I can imagine a standard web server using Let's Encrypt, for example, that could suffer from a user leaking credentials by inadvertently using HTTP rather than HTTPS. I have to look into some protections to this. I recently did a project and used Basic Auth for expediency thinking that later I would replace with a "proper" auth form. My theory was that this was better because sending cookies is based on the protocol also not just the domain.
- simfree 3y agoSafari on iOS does not play nice with Basic Auth. No credential saving, re-promting you for credentials on each page you navigate to. non-iOS browsers seem to handle HTTP basic auth gracefully.
- ec109685 3y agoThat’s what Passkeys are supposed to do. You have an identity tied to that website, shared across all your devices.
- hinkley 3y agoPulling on this thread a bit, when I get a new set top box, most of the apps have a url or a QR code you can use to copy your session to a new machine. You could just do that for all machines and have no cookies at all. iOS even has some ways to make that a bit easier. For some apps this would suffice. But for apps we use to live our lives, what do you do when someone has no access to their devices and they need to log in to a fresh device? Some apps will need passwords, or some other mechanism to prove you are who you say you are. But then you can leverage those apps to get back into your other apps in the case of, say, a fire.
- novok 3y agoMany websites and apps can do this, but explicitly do not in the interest of 'security' and 'anti-fraud'. Discord is a pretty bad offender of this.
- bobbylarrybobby 3y agoPasskeys?
- technimad 3y agoPasskeys are what you describe here.
- NoMoreNicksLeft 3y agoIsn't such a thing called a crypto key? And if you had such a thing, why in the hell would anyone sensible ever use browser cookie functionality to store that? Learn to use a password manager.
- danShumway 3y agoI'm sure I'm missing something, but... isn't that cookies? I think expiration fields on cookies are optional (correct me if I'm wrong), you just can't rely on them sticking around because the user might clear them (I'd have control of which sites could set permacookies for when I didn't want to be tracked too). Which is honestly desired behavior, I'm assuming you would want the ability to delete a permacookie. Cookies can't be synced through Firefox sync (I thought they could but just checked and my bad, they can't) -- but there's nothing preventing browser sync from handling that, and Firefox sync is E2EE so it would as secure as any other transfer method. It wouldn't be too hard to build a browser extension to allow exporting them or importing them manually; cookies are just text content so they're trivial to inspect and manipulate and even manually copy and paste into new browsers through the dev tools. As a login mechanism, having a permacookie is somewhat insecure so most sites use expiration dates. I'm sympathetic to the desire to be able to override that, but... the mechanisms most sites use are things like signed tokens with expiration dates checked serverside, so there's not much a browser can do about blocking a website from doing that. Short of using stateless key-based authentication I'm not sure how it would be technically possible to get rid of that behavior. ---- I'm being a little bit disingenuous here in the sense that... yeah I want native file access too. I understand that cookies are not the same as native file access and the controls aren't really the same. But that's a much larger conversation with much larger scope and with more implications for browser security. But if you're talking specifically about login, it does seem like cookies are mostly doing everything you want and your bigger problem is just that websites time-out logins? And that Firefox sync doesn't currently sync them, which... an extension could handle that. What is the non-permanent part of a cookie, is it just that user controls for clearing cookies aren't granular enough and they're too easy for the user to accidentally delete? I guess mobile too, iOS safari will clear localstorage sometimes. That's a very real issue (and a big reason why I want native file access), but it's less of an issue for login since occasionally losing your login permacookie isn't a big deal, it's only a big deal if you lose offline serverless webapp data.
- Modified3019 3y agoThat basically sounds like what yubikey’s and the like try to do.
- deleted 3y ago[deleted]
- anderspitman 3y agoI read OP's mention of third party cookies as an example of browsers supposedly moving in a more privacy focused direction, not as being related to authentication.
- lolinder 3y agoWell, the weird thing about the phrasing is the claim that third-party cookies are being phased out to "prevent this sort of thing"—where "this sort of thing" is "remember this device". This is... sorta true? Insofar as creepy advertisers also "remember this device". But a first-party site storing a cookie to remember a login session is not at all in the same category for me.
- deleted 3y ago[deleted]
- robobro 3y ago> My own browser erases all cookies from an origin immediately after the last tab from that origin is closed, Sounds like a you problem, dude. You have to go out of your way to force this behavior with any mainstream browser.
- ricree 3y agoThe text you're replying to is part of a long quote from the linked article, not a statement by the person you replied to.
- deleted 3y ago[deleted]
- ozim 3y agoAuthor is wrong in many ways. All post reads like Dunning-Kruger case, he seems to know quite some stuff but also misses 3rd party cookies. Overly focuses on weak passwords completely skipping password leaks or just mentioning password reuse. Ignoring that TOTP is actually decent interface for getting non technical and not caring at all users use random high entropy secrets. Getting regular people to keep some generated random strings won’t work. In the end ignoring all experience of industry which is: leaked passwords and email lists can be used in password spraying attacks where specific user is not targeted it is just opportunistic low hanging fruit automated exploitation. Then those easy exploitable accounts in services can be used to ask connected users for loans or financial help as a scam.
- waynesonfire 3y agoI dont agree with you that it's the user's fault. The issue isn't understanding of remember this device feature. The issue is it's a fundamentally broken design. One, because users have multiple devices and second, the feature is crippled when employing privacy preserving behavior. I should be able to authenticate by proving access to a device such as a yubikey, as an example. Now, the site can properly remember the user. This missing feature is the fault of crummy UX, not the user.
- hinkley 3y agoWhen I think 'multiple devices' I think 'multiple devices'. Yubikey is a solution for multiple computers but I don't see how something 'such as a yubikey' solves this problem for devices.
- hn_throwaway_99 3y agoI see nothing about the design that is broken. Most websites have implemented "remember this device" functionality in a way that 99% of users understand fine how to use. Some people have specifically implemented an option that says "Completely erase any potential for sites to remember this device", and then start bitching about poor design?? Queen, please. I have no objection for people choosing the "forget my device" option, but the nonsensical whining about explicitly choosing this option and then bemoaning that a website doesn't remember you is absurd.
- brasic 3y ago“Please read my rant about how this useless hair-shirt I wear to clear first party cookies too often breaks the web (for me)” > the web has no notion of a “device”, and this is a very intentional design choice made for privacy purposes [...] why do web developers persist in believing in this fiction of a “device”? Cookies are a core part of the web which enable the construction of stateful applications on top of a stateless protocol. “Remembered device” is usually just an extra cookie set on login, or a row in a backend database. It’s no more fictional than the web itself, which is after all just a series of electrical impulses over wires. Whether a device (however you build that abstraction) has previously logged in is a high-signal data point that meaningfully increases account security at login time and all serious web security teams use it to protect their users.
- deleted 3y ago[deleted]
- rjh29 3y agoThank you for teaching me the word hair-shirt. These kind of blog posts come up often on HN and it's good to have a word to describe them.
- Pesthuf 3y agoImagine if these people made posts like "I edited user32.dll to dummy out random functions I deem unnecessary like RegisterClass or CreateWindowEx and now nothing works! This is proof that Windows is broken!" It will forever be a mystery for me why people deliberately make their browsers work in ways that contradict the standards the web is built on and then manage to find blame in others when stuff doesn't work. It's already difficult enough to support all major browsers when their interpretations of the standards differ very slightly.
- naikrovek 3y agothis happens a lot. A LOT. not this exactly, but I know a lot of people who keep .reg files for "fixing Windows bullshit" on a new system, which they built up when Windows XP or Windows 2000 was new. Of course, a lot of those "fixes" now break things, because the underlying workings of windows changes a lot, but every last person I know who uses these has very odd problems with Windows that I have never once seen myself. a lot of these things that only experts knew how to do 20 years ago are now the causes of very odd problems, because these folks don't bother to verify that these registry settings are still the correct way to make the intended changes.
- littlestymaar 3y agoThe author is Hugo Landau, so of course it is a bad take, how else could it be. The real question at this point is why his terrible takes reach the front page every two weeks…
- hn_throwaway_99 3y agoSeriously, reading this article made me wish for a downvote option on submissions. I'm glad the top comment is pointing out the nonsense of this argument, but then I'm just left wondering how this made it to the top of HN in the first place. The author's diatribe about "remember device" functionality is just flat out silly, for all the reasons other commenters have pointed out.
- littlestymaar 3y ago> I'm glad the top comment is pointing out the nonsense of this argument, but then I'm just left wondering how this made it to the top of HN in the first place. The last two posts from the same author[1][2], in the past month, where of the same kind and got the same kind of reception (except that for the fediverse blog post, the top comments were either discussing about the topic of the title without addressing the (dumb) content of the article). So yeah, the mystery is why it keeps coming back. [1]: https://news.ycombinator.com/item?id=36549218 https://news.ycombinator.com/item?id=36549218 [2]: https://news.ycombinator.com/item?id=36466133 https://news.ycombinator.com/item?id=36466133
- hinkley 3y agoYeah I don't think he has adequately explored what happens when the website gives him a giant token to enter and then it can't be stored in a cookie. What does he think is going to happen next?
- knodi123 3y agoHe's right that it's a him problem- but my bank and my HR website both have "Remember this device" placebo checkboxes that do absolutely nothing. The feature is broken way too often even on stock browsers.
- wizofaus 3y agoI thought "remember this device" more typically worked via a combination of browser fingerprinting (which can be pretty sophisticated, e.g. even relying on rendering behaviours) and local storage, which may or may not involve cookies.
- Ferret7446 3y ago> anyone who is savvy enough to configure that setting is also savvy enough to understand that that will break "remember this device" I don't think so. Most people who understand that that will break "remember this device" also understand that clearing cookies doesn't help much with privacy. So the people who do enable that setting generally only know that cookies == tracking and do not understand that that will break "remember this device" ("Dunning-Kruger").
- ponorin 3y ago> The phasing out of third-party cookies has nothing to do with the "remember this device" functionality, because those are almost always powered by first-party cookies, which are not being phased out. Cookies are cookies, not a "device". You could theoretically copy whatever cookies they put in to authenticate in other place and get automatically logged in. > The author has configured their browser to throw away cookies when the last tab closes If web was supposed to be stateful, this would be a bug, and the author would have had to dig through experimental or advanced settings to enable it. But because web(HTTP) is fundamentally stateless, it is a feature, and it's a feature that every browser exposes to normal user. Your browser is not expected to keep your cookies, just like your browser isn't expected to support javascript to access a website, or that you should enable them even if you could.