Closed Bug 1152146 Opened 10 years ago Closed 10 years ago

SafeBrowsing requests cause logspew about SHA-1 weakness

Categories

(Toolkit :: Safe Browsing, defect)

All
Android
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1181335
Tracking Status
firefox40 --- affected

People

(Reporter: rnewman, Unassigned)

References

Details

We can't migrate the endpoint, no. This is a combination of obnoxious warnings on our end and Google being slow to move away from SHA-1 (despite partially blocking it in Chrome): https://news.ycombinator.com/item?id=9333517 Note that all Google certificates in the chain use SHA-1. For some like the root, there are no plans that I know of to migrate away from SHA-1: http://googleonlinesecurity.blogspot.be/2014/09/gradually-sunsetting-sha-1.html "Note: SHA-1-based signatures for trusted root certificates are not a problem because TLS clients trust them by their identity, rather than by the signature of their hash." Not a SafeBrowsing problem as far as I'm concerned.
Blocks: 1068949
Bug 1181335 has an open ni? request, so forward duping.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.