> libc.so.0 => ...
> ld64-uClibc.so.0 => ...
Samples from systems for developing pattern matches
should not be truncated... if the data is sensitive or very long,
it can be obfuscated or have its char class substrings shortened.
Some forums and mail can mangle chars classes outside isalnum(3),
ta
> and about windows,
> it is a requirement for my situation , but i just saw some build scripts
> regarding windows in the tbb repo you mentioned; i would be happy to
> hear from you about tips and tricks regarding windows!
So tor-browser-build lets us make all our build targets (windows, mac,
and
George Kadianakis:
> An unfortunate exception here is v3 onion services: v3 onion services
> only tolerate skews of maximum ±3 hours [1] but in most cases even
> tighter than that. This is to assure that v3 clients and services have a
> recent and accurate view of the network. In theory all of Tor
Hi Richard, this is great!
I appreciate all the insights you gave me.
about the build setup i would definitely go with your suggestion. maybe it
would be possible to also use these build scripts inside a docker composer
for a reload on demand during development. and about windows, it is a
requirem
In torsocks' configure.ac, libc_name is determined by means of ldd /usr/bin/yes
which is then grepped for libc.
On a uClibc system I use, ldd /usr/bin/yes yields two entries, namely
libc.so.0 => ...
ld64-uClibc.so.0 => ...
The resulting string begins with quotation mark, ends with quotation mar
