News for hackers. Stuff that matters.
Re:Chrome 68 will mark all HTTP sites as “not secure” by olympus on Thursday February 08, 2018 @07:45PM (#16336954)
Can you self-sign a certificate from the internal server and install it as trusted on the work computers? Or does Chrome only trust certificates that Google trusts?
Re:Chrome 68 will mark all HTTP sites as “not secure” by pfg on Thursday February 08, 2018 @07:55PM (#16337007)
Generally speaking, Chrome uses whatever is in the OS trust store, with certain exceptions for CAs that have been naughty (e.g. StartCom, WoSign, Symantec) or subCAs that were revoked via CRLSets. Private CAs present in the OS trust store will generally just work, the only exceptions being things like Superfish.
Re:Chrome 68 will mark all HTTP sites as “not secure” by ams6110 on Thursday February 08, 2018 @07:59PM (#16337031)
Not sure about Chrome, but you can absolutely install a local CA into Firefox.
Re:Chrome 68 will mark all HTTP sites as “not secure” by cheeze on Thursday February 08, 2018 @11:07PM (#16337833)
You definitely can in Chrome. Tons of corporations need the ability to trust their internal PKI.
Re:Chrome 68 will mark all HTTP sites as “not secure” by cup-of-tea on Friday February 09, 2018 @06:17AM (#16339386)
You can install your own CA, yes. But's it's easier to just use HTTP.