| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
This should make us conflict less with system files named "log.h".
Yes, we shouldn't have been conflicting with those anyway, but some
people's compilers act very oddly.
The actual change was done with one "git mv", by editing
Makefile.am, and running
find . -name '*.[ch]' | xargs perl -i -pe 'if (/^#include.*\Wlog.h/) {s/log.h/torlog.h/; }'
|
|\ |
|
| |
| |
| |
| | |
Possible workaround for bug 1139, if anybody cares.
|
| | |
|
|/
|
|
|
|
|
| |
This should never happen unless openssl is buggy or some of our
assumptions are deeply wrong, but one of those might have been the
cause of the not-yet-reproducible bug 1209. If it ever happens again,
let's get some info we can use.
|
|\
| |
| |
| |
| |
| | |
Conflicts:
src/common/test.h
src/or/test.c
|
| | |
|
|\| |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In 5e4d53d535a3cc9903250b3df0caa829f1c5e4bf we made it so that
crypto_cipher_set_key cannot fail. The call will now
always succeed, to returning a boolean for success/failure makes
no sense.
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
Some *_free functions threw asserts when passed NULL. Now all of them
accept NULL as input and perform no action when called that way.
This gains us consistence for our free functions, and allows some
code simplifications where an explicit null check is no longer necessary.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In C, the code "char x[10]; if (x) {...}" always takes the true branch of
the if statement. Coverity notices this now.
In some cases, we were testing arrays to make sure that an operation
we wanted to do would suceed. Those cases are now always-true.
In some cases, we were testing arrays to see if something was _set_.
Those caes are now tests for strlen(s), or tests for
!tor_mem_is_zero(d,len).
|
| |
| |
| |
| |
| |
| |
| |
| | |
See task 1114. The most plausible explanation for someone sending us weak
DH keys is that they experiment with their Tor code or implement a new Tor
client. Usually, we don't care about such events, especially not on warn
level. If we really care about someone not following the Tor protocol, we
can set ProtocolWarnings to 1.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This patch introduces a new type called document_signature_t to represent the
signature of a consensus document. Now, each consensus document can have up
to one document signature per voter per digest algorithm. Also, each
detached-signatures document can have up to one signature per <voter,
algorithm, flavor>.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Apparently the Android developers dumped OpenSSL's support for hardware
acceleration in order to save some memory, so you can't build programs using
engines on Android.
[Patch revised by nickm]
|
| |
| |
| |
| |
| |
| |
| | |
This shouldn't be necessary, but apparently the Android cross-compiler
doesn't respect -I as well as it should. (-I is supposed to add to the
*front* of the search path. Android's gcc wrapper apparently likes to add to
the end. This is broken, but we need to work around it.)
|
| |
| |
| |
| | |
Fixes bug in f57883a39.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(This would be everywhere running OpenSSL 0.9.7x and earlier, including
all current Macintosh users.)
The code is based on Tom St Denis's LibTomCrypt implementation,
modified to be way less general and use Tor's existing facilities. I
picked this one because it was pretty fast and pretty free, and
because Python uses it too.
|
| |
| |
| |
| | |
This adds an openssl 0.9.8 dependency. Let's see if anybody cares.
|
|\ \
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
crypto_global_init gets called. Also have it be crypto_global_init
that calls crypto_seed_rng, so we are not dependent on OpenSSL's
RAND_poll in these fiddly cases.
Should fix bug 907. Bugfix on 0.0.9pre6. Backport candidate.
svn:r18210
|
|
|
|
|
|
|
|
| |
The subversion $Id$ fields made every commit force a rebuild of
whatever file got committed. They were not actually useful for
telling the version of Tor files in the wild.
svn:r17867
|
|
|
|
| |
svn:r17804
|
|
|
|
| |
svn:r17741
|
|
|
|
| |
svn:r17734
|
|
|
|
|
|
| |
comments so that they will get recognized as doxygen.
svn:r17729
|
|
|
|
|
|
| |
and isn't actually a security thing.
svn:r17685
|
|
|
|
|
|
| |
reference counts. Bugfix on 0.1.0.1-rc.
svn:r17672
|
|
|
|
|
|
| |
anywhere, and remove the ones that we really want gone.
svn:r17651
|
|
|
|
| |
svn:r16778
|
|
|
|
|
|
| |
authorization data. Tweaked a bit: see comments on or-dev.
svn:r16475
|
|
|
|
|
|
|
| |
fix for bug 704; found by sjmurdoch. Windows and recent openssl both want to define OCSP_RESPONSE; do not let them.
svn:r15533
|
|
|
|
|
|
| |
openssl uses them.
svn:r15222
|
|
|
|
| |
svn:r14950
|
|
|
|
|
|
|
| |
New (temporary) tool to dump the modulus of a key. May help with a project of weasel's.
svn:r14580
|
|
|
|
|
|
|
| |
Use RAND_poll() again: the bug that made us stop using it has been fixed.
svn:r14150
|
|
|
|
|
|
|
| |
Whitespace fixes
svn:r13700
|
|
|
|
|
|
|
| |
More 64-to-32 fixes. Partial backport candidate. still not done.
svn:r13680
|
|
|
|
|
|
|
| |
Fix all remaining shorten-64-to-32 errors in src/common. Some were genuine problems. Many were compatibility errors with libraries (openssl, zlib) that like predate size_t. Partial backport candidate.
svn:r13665
|
|
|
|
|
|
|
| |
Apply warnings about implicit 64-to-32 conversions; some from Sebastian Hahn; some not.
svn:r13664
|