my tweets are severely limited by my lack of understanding of what I am doing.
It's also not easy to see certificate information on Chrome - you have to dig into developer tools :-(
One of the dangers of Chrome writing "Not secure" on basically every large website is I suspect people will ignore it. https://twitter.com/zackwhittaker/status/886018265918713858 …
Ten tweet jest niedostępny.
-
-
Dziękujemy. Twitter skorzysta z tych informacji, aby Twoja oś czasu bardziej Ci odpowiadała. CofnijCofnij
-
-
-
I know it's naive, but I can't believe this won't get fixed, if only so some poor sod doesn't have to explain it to some exec
-
Given the choice between writing a report to explain this or working out how to use
@letsencrypt to make it go away I know which I'd choose
Koniec rozmowy
Nowa rozmowa -
-
-
I remember watching a presentation from a Google employee saying effectively the same thing
Dziękujemy. Twitter skorzysta z tych informacji, aby Twoja oś czasu bardziej Ci odpowiadała. CofnijCofnij
-
-
-
Is that a flag setting currently? That particular 'Not Secure' is only shown when you use an https URL for a site that doesn't support it..
Dziękujemy. Twitter skorzysta z tych informacji, aby Twoja oś czasu bardziej Ci odpowiadała. CofnijCofnij
-
-
-
Yes! Exactly! I'm glad someone understands it. I was trying to explain just that in a thread started by Troy Hunt.
-
Marking as "not secure" any page that has any kind of text input field (not just a password field) is stupid, overdone, cheapens the warning
- Pokaż odpowiedzi
Nowa rozmowa -
-
-
They will ignore it because it is OVERDONE. It doesn't appear only when the page requests for passwords (where it is important).
-
It appears on ANY page that has ANY kind of text entry field. This is idiocy.
Koniec rozmowy
Nowa rozmowa -
-
-
There are two main problems with HTTPS and they affect different kinds of companies. For small sites, the main problem is cert renewal.
-
Let's Encrypt has great tools for auto renewal on Linux. On Windows, you're basically on your own. There are some third party scripts.
- Pokaż odpowiedzi
Nowa rozmowa -
Wydaje się, że ładowanie zajmuje dużo czasu.
Twitter jest przeciążony lub wystąpił chwilowy problem. Spróbuj ponownie lub sprawdź status Twittera, aby uzyskać więcej informacji.