[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #20100 [Applications/Tor Browser]: persistent libxul.so bug crashing TBB Linux/64 (but probably a bug in locally linked shared object)
#20100: persistent libxul.so bug crashing TBB Linux/64 (but probably a bug in
locally linked shared object)
--------------------------------------+--------------------------
Reporter: sjamaan | Owner: tbb-team
Type: defect | Status: new
Priority: High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Major | Resolution:
Keywords: tbb-crash | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+--------------------------
Comment (by ronvandaal_):
Replying to [comment:6 cypherpunks]:
> > is it normal for libxul.so binaries to change when run?
>
> On disk? No, of course.
> What hash of your libxul?
The question was for my own sanity. Thank you ;-)
See attached files:
tor-browser-linux64-6.0.6_en-libxul.so-STOCK-VALID
eaa0cb53cea58ced3a8182d81c9b48c9
tor-browser-linux64-6.0.6_en-libxul.so-POWNED
cc2fc415dda6632cf67b285ae41808b4
For records: tor-browser-linux64-6.0.6_en-US.tar.xz
e71f92bc24cc8325a328561c2f6d6aa7
These don't relate to TBB but Debian's Iceweasel (patchlevel unsure, did
reinstall after):
libxul.so-debian-jessie-amd64-STOCK cad4639bff84298c3af0340c19714e46
libxul.so-debian-jessie-amd64-POWN 3eb2b8139fd24211e5a787f2510a3aff
(changed while browsing)
I'm certain when the TBB init scripts (same goes for Tails) run a simple
hashchecker, perhaps with the option to feedback a mismatch, more
background info on the bug can be obtained. Just an idea.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20100#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs