Age | Commit message (Collapse) | Author |
|
been established
|
|
|
|
handshake finish
This ensures that the handshake is repeated in case the finish packet is lost.
|
|
|
|
by the peer
There is no reason to run through all the session establishment just to cancel
it a moment later.
|
|
|
|
|
|
|
|
This ensures that even in the unlikely case of a crossed handshake fastd will
never establish two sessions with the same encryption key
|
|
|
|
|
|
|
|
This is needed at least on FreeBSD
|
|
|
|
Everything clang and GCC warn about, except GCC's missing-field-initializers
which are just stupid as they don't allow {} syntax to zero a field.
|
|
|
|
uninitialized" warning
|
|
|
|
handling
|
|
This enforces explicit casting and thus avoids alignment problems.
|
|
|
|
Just for the sake of completeness.
|
|
readdir_r can be unsafe for very long filenames.
|
|
|
|
|
|
|
|
|
|
Unaligned access might be a problem on some architectures, so it's better to
copy it to an aligned buffer before further handling the handshake.
|
|
|
|
The NaCl implementation has a code size of more than 10KiB.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|