6 ms·
A few solutions: - Create a font such that every character shows up as a * and use it for a text input. - make the input field use white text on a white backg
by dheera 10y ago
A few solutions:
- Create a font such that every character shows up as a * and use it for a text input.
- make the input field use white text on a white background using a fixed-width font, monitor length, and display the correct number of *'s above it using a div.
- implement the text box ground up from scratch using div's and JS, like google docs does.
- implement a HTTPS password field in an iframe and communicate with it over post messages.
- Moru 10y agoBut what do you do when you have a page with form data that isn't sensitive and has no password on it and the users can't care less about the content of the form but chrome still warns about unsecure page?
- kevin_thibedeau 10y agoWhy would such a form need a password field?
- Moru 10y agoWell, that is the whole point I'm trying to make. Why does chrome think I'm using a password on the page when there is no password? Anyway, Chrome will mark all http as insecure sooner or later so will just have to force https on all connections... There seems to be many people with similar problems of false positives for nonexistant passwords so I guess it's a bug.
- Piskvorrr 10y agoWell...HTTP is insecure. That's what S in HTTPS stands for.
- comex 10y agoI haven't heard of this bug, but regarding the decision to mark all HTTP as insecure: Remember, HTTPS isn't just for security, but also privacy. And even if your site is such that there is no privacy advantage in hiding the exact URL you visited (as opposed to the hostname, which unfortunately must leak for now), even if there are no cookies sent to your site, or to any iframes it uses, which can be used for identification or profiling… Even then, there are the benefits that only accrue if a user's entire browsing session is HTTP-free, including hiding the user agent from a network attacker and preventing injection of everything from tracking cookies to DDOS scripts (China's Great Cannon) to zero-day attacks.
- Symbiote 10y ago> Remember, HTTPS isn't just for security, but also privacy. And the third thing: authenticity. No-one has modified the page, for example to insert or change advertisements
- the_duke 10y agoI don't really know what your point is. This will mark pages as insecure that have a '<input type="password">' field on your page. If you don't have that, you are fine. I don't know of any reasons to have a password field if it's not actually sensitive information that's being entered.
- Piskvorrr 10y ago...for now. Marking all non-secured HTTP as insecure (duh) is in the pipeline - it seems. This is actually a Good Thing - with HTTPS-friendly CDN and/or Letsencrypt, rolling out sites that are secure-by-default is now easier and cheaper than ever before.
- detaro 10y agoThen that's a bug you should report, and let the Chrome team fix it.
- nsgi 10y agoThe last one won't work. The parent frame has to be HTTPS as well.
- deleted 10y ago[deleted]
- nawitus 10y agoYou can implement a custom element which shows the characters as dots (essentially your third suggestion).
- nkkollaw 10y agoHonestly, why would you do any of those things, now that installing a certificate takes 5 minutes and is free, with Let's Encrypt? I know that you're just exploring solutions because it's interesting, but all those things take longer than Let's Encrypt.
- PretzelFisch 10y agoBecause that is just not true in many cases. And let's encrypt is a big hassle if you can't automate the cert replacement.
- sgk284 10y agoHave you ever been on a team at a large company? Tons of bureaucracy. You're correct that Let's Encrypt is the path of least resistance in a shop where you control everything. In many large companies the path of least resistance is tweaking whatever is in your immediate control (e.g. the text inputs / javascript you're writing).
- michaelmior 10y ago> takes 5 minutes This is entirely dependent on how your site is hosted. For some shared hosting platforms, it may not be possible at all.
- disiplus 10y agoalso u have to do the request over port 443, and the alternative dns validation is not supported in in the official client. so its 5 min only in ideal case.
- ocdtrekkie 10y agoLet's Encrypt is great, but completely useless for... Actually every single website I host. No wildcard certs, the rapid rotation that requires software to renew it regularly, etc. The cost of implementing HTTPS for dozens of sites with no sensitive data is simply not worth it. When companies like Google and Mozilla decided how to handle HTTPS, they decided based on their needs and their perception of everyone else's needs, like banks and major corporations. This led, IMHO, to a complete failure to recognize a lot of other uses for the Internet, and so their solutions fail to adequately account for them.
- detaro 10y ago> - implement a HTTPS password field in an iframe and communicate with it over post messages. The top-level page also has to be served over HTTPS for the warning to not appear. (source https://developers.google.com/web/updates/2016/10/avoid-not-secure-warn https://developers.google.com/web/updates/2016/10/avoid-not-...)