Tor compiled with --enable-expensive-hardening leads to runtime errors (null pointer passing)
../src/common/crypto.c:2596:3: runtime error: null pointer passed as argument 1, which is declared to never be null
Immediately following I get
/usr/include/x86_64-linux-gnu/bits/string3.h:90:10: runtime error: null pointer passed as argument 1, which is declared to never be null
Line 90 in my string3.h is:
return __builtin___memset_chk (__dest, __ch, __len, __bos0 (__dest));
Steps to reproduce:
- Get the latest hardened Tor Browser (the same issue happens with a stable Tor Browser + a self-compiled hardened Tor)
- Start it with
./start-tor-browser.desktop --debug --log
and don't connect directly but use a pluggable transport; just using the default one is enough, there is no need to enter bridges manually - You should see the above messages in your terminal/tor-browser.log file
FWIW connecting directly does not trigger this issue.