8 ms·
This is something I've had the occasion to discuss before, and it's a good idea not because "it's ssh" or "it's decentralized" (those are just good benefits), b
by scrollaway 11y ago
This is something I've had the occasion to discuss before, and it's a good idea not because "it's ssh" or "it's decentralized" (those are just good benefits), but because it moves the authentication to an actual authentication protocol and, were it to catch on, would have to be done from the browser itself.
Does this ring a bell? That's right, it's BrowserID ladies & gents. I'll never let this go, Persona was a great thing for the web and its death is mourned.
I think I've seen ssh auth implemented before but this is the smoothest POC yet. Your next step: Make a firefox extension that integrates this, as a proof of concept for in-browser authentication.
- reitanqild 11y agoAgree. However I think time is working against anyone that wants to do this though. > I'll never let this go //Using this as an excuse > Your next step: Make a firefox extension that integrates this Do it while it is still possible, before Mozilla carries out their plan to lobotomize Firefox and bring it down to the level of Chrome like they have planned. :)
- scrollaway 11y agoSandboxed/restricted extensions are a good thing. AFAIK Mozilla has no plan to get rid of the "dangerous" extension api...
- detaro 11y agoTimeline for deprecating everything that isn't using the new WebExtensions API is 12 to 18 months: https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/ https://blog.mozilla.org/addons/2015/08/21/the-future-of-dev...
- rpgmaker 11y agoI'm amazed at how Chrome keeps taking market share from Mozilla. Those ads in google.com help an awful lot but still, it's kind of unnerving. I understand why your average user wouldn't mind using it but Chrome has taken a lot of power users from Firefox. Some people even seem to deem "uncool" to use Firefox instead of chrome, it's ridiculous. It's gotten to the point where some sites features don't work correctly (or at all) in Firefox but they do so in Chrome, as if we were back in the era of browser-specific sites.
- detaro 11y agoAs someone who has been switching back and forth: The ability to customize Firefox is nice, but: Chrome has most features I need and makes up for missing ones with nicer implementations of others, or has them before Firefox does. Firefox freezes regularly for seconds, feels slower in many situations and degrades quicker if you open to many tabs (Chrome just eats ton of RAM, but can deal with many hundreds of open tabs otherwise). Oh, and faulty sites crash the entire Firefox instance instead of just a tab. Firefox is about to get multiprocess feature in full releases, I hope this will fix many of these issues.
- gregmac 11y agoI switched to Chrome because its speed was a breath of fresh air compared to Firefox, and after trying it, I couldn't stand how slow Firefox was (or how one misbehaving tab could cause the whole thing to freeze). What am I missing out on in terms of plugins/extensions that Firefox can do that Chrome can't? It's been a couple years, but I don't feel like I'm missing anything in Chrome..
- reitanqild 11y agoTwo examples Tree style tabs Scrapbook extension (misleading name, dowloads pages recursively and let you search locally)
- drdaeman 11y agoI'd disagree. My personal opinion is, BrowserID/Persona was a bad thing for the web and it's a good thing it haven't hit any big. Sure, it was better than most popular protocols out there, but it was still wrong. My opinion is that BrowserID had a very flawed core concept. I firmly believe that my identity is something that I [can] naturally define and possess. But everyone since OpenID had stolen this from the end-user and identities became something that you're provided with - and I find the very term "identity provider" unnerving. With identity providers you're not you anymore, but merely your Facebook account or your email address or your domain name - a things you only temporarily lease from a third-party like an email provider or a domain registry. Sure, there's some common sense, legal protections and stuff, but I'm don't like merely relying on those. I think, in a sane world, at least personal (i.e. non-group) identities must be merely asserted, not provided - and they must originate from a person themself. On the contrary, this login-with-ssh thingy and few other schemes (gpgAuth and WebID) are much closer to what the things should be like. While they don't yet completely resolve the distinction between an identity and a credential (it's really hard), they root your identity in something that you can actually define for yourself and handle without depending on anyone else - a key pair.
- scrollaway 11y agoI agree with most of your logic but let's also be pragmatic - something that is better than everything else out there that's actually popular, and has a chance to hit big, is good for the web. Always pursuing the impossible perfection is one of the reasons we don't have ubiquitous https for example...
- drdaeman 11y agoWell, yes, you're right. Seeking a perfection usually means never releasing anything. That's spot on. Yet, I'm particularly against about the BrowserID adoption because it helps to cement the idea of leased identities. At the moment, we're still with in the "warring states" world, where no particular scheme had won. This could've changed with BrowserID embedded in the User-Agent, so I fear it would be at least a decade until we'll be able to talk about something else. WebID, being a W3C WG, could've also hit big... It's not perfect, but from my understanding of the drafts it looked better than BrowserID to me. But no luck here.
- x5n1 11y agoEach person should pay for a client SSL certificate that they use to authenticate themselves on the web.
- deleted 11y ago[deleted]
- drdaeman 11y agoI would've loved if I could just use a self-generated certificate to authenticate. Especially if they'd be on HSM like YubiKey/NitroKey. Heck, there's even <keygen> element in HTML5, so this could've been quite user-friendly hassle-free. I could consider paying someone to assert my identity, or get some assertions for free, or whatever - the possibilities could be limitless. However, there are few issues with this. 1. We're currently stuck with X.509 and those don't allow subkeys or multiple signatures. 2. Then, the problem is that, AFAIK, there's no way to tell in that we accept just anything in TLS. I think there were a lot of discussions about allowing spontaneous authentication (changing state machine to allow TLS client to send certificate without CertificateRequest) or adding hacks like DN=WebID, but none is here. My memory's blurry in this regard - I've read about this about an year or two ago, sorry. But I'm certain there were some issues here. 3. Then, the problem is, browser UI and UX for managing certificates are terrible. There weren't any changes in this area for decades, and everything about those is deep hidden. Then, there are no subkeys and no cross-browser sync or key escrow mechanisms (opt-in, absolutely), so it's very unlikely to be useable by average person. And so on. So, format is not ready, protocol is not ready and browsers are not ready. Thus, sad but no, it's not going to work.
- deleted 11y ago[deleted]
- WorldMaker 11y agoPersona is not dead, it's just open source community run and underutilized. We could still save it, we have the technology.
- dijit 11y agoAgreed, it runs on my site, but without adoption it'll never be adopted.. :(