| Age | Commit message (Collapse) | Author |
|---|
|
|
|
1.0.3 but stubbing out.
|
|
affect existing clients.
|
|
This stuff is called all over the place.
|
|
link, porting over core loop code from old Node.cpp to new CAPI version, etc.
|
|
trusted peers, and also rename ExternalSurface to SelfAwareness because lulz.
|
|
Switch.
|
|
out, redo COM serialization, etc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
refactoring, and a few other things related to multicast.
|
|
multicast for debugging purposes.
|
|
of certificates of membership.
|
|
frames in new way.
|
|
|
|
cipher suite enum.
|
|
to some shortsighted design early-on. In the future this can die once there are no old peers.
|
|
AES256-GCM which might be added in the future.
|
|
|
|
Network to remove redundant code and bug-proneness, more work on IncomingPacket...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
size thinko.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
protocol.
|
|
|
|
(1) The changes to path learning in the two previous releases were poorly thought out,
and this version should remedy that by introducing PROBE. This is basically a kind of
ECHO request and is used to authenticate endpoints that are not learned via a valid
request/response pair. Thus we will still passively learn endpoints, but securely.
(2) Turns out there was a security oversight in _doHELLO() that could have permitted...
well... I'm not sure it was exploitable to do anything particularly interesting since
a bad identity would be discarded anyway, but fix it just the same.
|
|
|
|
that updates for some platforms are big enough and there are enough reliability concerns that just using TCP/HTTP is safer and easier.
|
|
|
|
|
|
|
|
|
