mirror of
https://github.com/servalproject/serval-dna.git
synced 2025-02-21 01:42:18 +00:00
e015f0670b
at the end, and log2(filesize) instead of filesize. Equally importantly BAR construction and parsing now uses #defines for field sizes and offsets instead of it being hardwired without meaningful documentation. WILL BREAK BACKWARD COMPATIBILITY WITH PREVIOUS BUILDS. YOU MUST DELETE AND REBUILD YOUR RHIZOME DATABASE AS OLD-FORMAT BIDs WILL BE IN THERE AND GET SENT, AND STRANGE THINGS WILL HAPPEN. This break with backwards compatibility is only reasonable to consider because we have not yet had an official build using the new Rhizome with old BAR format. 0.08 uses old Rhizome. #9
When we were looking at implementing secure calls for OpenBTS it was suggested that we configure Asterisk to use SIPS/ZRTP. This would have been relatively easy to setup, however there are a few problems. Number one is that when Asterisk checks the certificates it will either validate the certificate (checking the chain of trust and so on) and then check that the common name attribute on the certificate matches the hostname of the peer, or it will do none of these checks. This code is in main/tcptls.c line 206 (in version 1.8.14.1). This is undesirable in a setup where there is limited or no infrastructure as there is not likely to be a DNS server setup, or even rigid IP assignments that would allow a static hosts file based setup. This situation would force the administrator to disable the checks completely which would allow a trivial man in the middle attack. It would be possible to modify Asterisk to have a third way where it validates the certificate and checks the chain of trust but does not look at the common name. We decided against this approach as the VOMP channel driver was written in time to avoid it.