3 ms·
Yeah, it was a wild guess. I just looked over all the new bug tracker entries in Tor since Oct 28th, but none of them seem particularly critical. Our best bet
by sillysaurus3 9y ago
Yeah, it was a wild guess. I just looked over all the new bug tracker entries in Tor since Oct 28th, but none of them seem particularly critical.
Our best bet would be to look at Firefox's commit history since the 28th.
One crafty way to determine the exploit would be to bindiff the hotfix'd firefox binary vs the previous release and examine the diffs in a disassembler to see what code changed. Non-deterministic builds make that tricky, but it's a neat technique to be aware of.
- qeternity 9y agoIsn't this pretty standard practice?
- sillysaurus3 9y agoIt is. But no one has posted details of the exploit yet. I was hoping someone would go find that out. (I can't right now else I would.)