Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ...
by charleslmunger on Thursday December 08, 2016 @09:59PM
(#13136335)
If you're serving them over plaintext http, then they're already insecure. How dangerous that is might be debatable, but there's no doubt that it's insecure.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ...
by Buge on Friday December 09, 2016 @02:08AM
(#13137229)
Well China intercepts http traffic and inserts javascript malware joining users into a botnet that DDOSes github pages of human rights organizations. It depends on what you mean by insecure and dangerous.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ...
by niij on Friday December 09, 2016 @01:45PM
(#13140794)
Link?
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ...
by gruez on Thursday December 08, 2016 @11:30PM
(#13136690)
gitlab pages has https support built in
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ...
by nothrabannosir on Friday December 09, 2016 @04:15AM
(#13137624)
For custom domains? I doubt it. Op is not talking about https://<username>.github.io.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ...
by ben0x539 on Friday December 09, 2016 @05:25AM
(#13137875)
Comment you're responding to said gitlab, not github.
Maybe those code hosting sites need to become more creative in their naming...
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ...
by nothrabannosir on Friday December 09, 2016 @05:51AM
(#13137977)
The comment I was responding to was talking about gitlab having SSL on their <username>.gitlab.io pages. While correct, that is besides the point OP was making. Which was about custom domains. Gitlab doesn't offer that, either.
[edit] I'll guess I'll have to find a new host then, since Github pages doesn't support https on custom domains. Perhaps Netlify, seems to support Github hooks.