A truly obfuscatory browser: one in which everything sent to the server looked the same, regardless of which user, region, etc.
Ask HN: What feature would you want the web to “force” next, after HTTPS?
141–150 of 279 posts
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#142- A protocol for sites to get my public PGP key for server side use - The discontinuation of using SSL certificates for verification of website identities and a move to true fingerprinting ala SSH. - Deprecation of email or rather its insecurity. - Logins on websites with a public / private keypair ala SSH. - A resurgence in sites that let me pick my own anonymous username instead of Facebook, Google or Twitter login…
SSH-style login is still something I'd really fucking love. Much more secure way of logging in, easy protocol for storing multiple passwords, and easy authorization/deauthirzation of passwords/keys.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#143Obtrusive prompt (UAC equivalent) required to load any javascript. How the web would be so much functional, to the point and responsive. Just imagine the electricity savings. The world truly would be a better place.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#144Hard deprecation of the long tail of Javascript browser capabilities and incompatibilities. So much code and so many libraries are littered with "if (old version browser) do x, else if IE, do y, else, ..."
So IE should say "sorry I suck, switch to another browser?" Doesn't make any sense... I mean sites will already tell users they don't support older browsers.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#145Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#146Earlier quoted context omitted.
While I agree, there is definitely movement and recent movement [0][1] , I just wish I had the knowledge to contribute. I am great and figuring out how things work, breaking them and understanding them. Building from scratch is a bit above my head, albeit I have a few ideas.... [0] https://news.ycombinator.com/item?id=14708783 [1] https://magmadaemon.org/
We already have standards for encrypting/authenticating email transfer between mail servers and between the server and user agent. This doesn't solve the problem of mail being encrypted in transit. As far as I can tell the server operator can still read the user's mail. What we need is end-to-end encryption, lack of support in MUAs (iphone mail app, thunderbird etc.) is the problem here, it has really nothing to do w…
Thunderbird supports S/MIME out of the box and PGP through an addon, so I'm not sure what other kinds of end-to-end encryption you'd want to see. Not sure about the iPhone mail app.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#147Earlier quoted context omitted.
> And, with federated identity, you can also run your own, if you don’t trust Google or Facebook login. Sounds like OpenID...which was kind of a train wreck. One middle ground could be tighter integration between browsers, sites and password managers. With the right specification, sites could offer a "register with [1Password,KeePass,LastPass,etc]" button which would open the password manager and pre-fill all the fie…
That’s another one of these half-assed solutions that the world has too many of, just like credit cards or using SSN as auth. No. We’ve solved all these issues before, OpenID was a good solution, and OpenID Connect – a complete rewrite – can be used to replace it, and is used already for Google and Facebook login. Just use OIDC, on every page, and allow users to choose an identity provider. Problem solved.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#148SSL was forced by Google single-handedly. Developers scared that https might provide ranking factor, quickly moved to SSL. As for topic, I would like to see all mails clients rendering emails same god damn way.
>hello
>>my name is bill
>>>i'd like to have a meeting
>>>>please provide your availability
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#149I think this is only really worth the headache for security issues. That said: - HSTS - DNSSEC - IPv6 in that order. I think for a long time, governments had no interest in pushing security and encryption because that would prevent them from mass data collection. I think minds are starting to change around that: poor security is much more likely to be exploited against a government rather than used in its favor (plus…
Anyone here have any recommendations on a book, course, etc. that covers IPv6 readiness?
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#150I think this is only really worth the headache for security issues. That said: - HSTS - DNSSEC - IPv6 in that order. I think for a long time, governments had no interest in pushing security and encryption because that would prevent them from mass data collection. I think minds are starting to change around that: poor security is much more likely to be exploited against a government rather than used in its favor (plus…