ChangeLog 3.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  1. - NCD: fix regex_replace() semantics. It was very broken because it did a complete replacement pass for every regex on the list, so it would match parts that have already been replaced, producing unexpected results.
  2. - NCD: small performance improvement
  3. Version 1.999.121:
  4. - NCD: improve error handling semantics; see http://code.google.com/p/badvpn/source/detail?r=1376
  5. - NCD: fix assertion failure in sys.evdev() if a device error occurs (e.g. device unplugged) while an event is being processed. Similar fix in some other modules, but these may not be reproducable.
  6. - NCD: some more performance improvements
  7. - NCD: some performance improvements (~30% faster interpretation of cpu-bound code)
  8. - NCD: implemented If..elif..else clause.
  9. - NCD: net.backend.wpa_supplicant: fix to work with wpa_supplicant>=1.0
  10. Version 1.999.115:
  11. - NCD: Many improvements; new statements, including call(), alias(), foreach(), choose().
  12. Version 1.999.113:
  13. - NCD: when starting child processes, make sure that file descriptors for standard
  14. streams are always open in the child, by opening /dev/null if they are not.
  15. - Improve build system to allow selective building of components.
  16. By default, everything is built, unless -DBUILD_NOTHING_BY_DEFAULT=1 is given.
  17. Individual components can then be enabled or disabled using -DBUILD_COMPONENT=1
  18. and -DBUILD_COMPONENT=0.
  19. - When starting any BadVPN program, make sure that file descriptors for standard
  20. streams are always open in the child, by opening /dev/null if they are not.
  21. - NCD: net.backend.wpa_supplicant(): add 'bssid' and 'ssid' variables to allow
  22. determining what wireless network wpa_supplicant connected to.
  23. - NCD: net.backend.wpa_supplicant(): do not require the user to start wpa_supplicant via
  24. stdbuf, but do it automatically.
  25. Version 1.999.111:
  26. - Improved protocol such that peers can use SSL when comminicating via the server. This
  27. improves security, as compromising the server will not allow the attacker to see secret
  28. data shared by peers (in particular, encryption keys and OTP seeds when in UDP mode).
  29. Compatibility is preserved if an only if the following conditions are met:
  30. - The server is using the latest version.
  31. - If the network is using SSL, all clients using the new version are using the
  32. "--allow-peer-talk-without-ssl" command line option.
  33. Be aware, however, that using the "--allow-peer-talk-without-ssl" option negates the
  34. security benefits of the new SSL support - not only between pairs of peers where one
  35. peer is using the old version, but also between pairs where both peers are capable
  36. of SSL. This is because the server can re-initialize the pair, telling them not to use
  37. SSL.
  38. Version 1.999.107:
  39. - Added Windows IOCP support, removing the limitation on ~64 connections. This is important
  40. for tun2socks, which may have to handle several hundred connections.
  41. Version 1.999.105.2:
  42. - Fixed an assertion failure in tun2socks related to sending data to SOCKS.
  43. Version 1.999.101.3:
  44. - Fixed UDP transport on Windows 7 which didn't work (was only tested on XP).
  45. Version 1.999.101:
  46. - Fixed a protocol issue present in versions <=1.999.100.3. Compatibility is preserved in
  47. case of a new server and old clients, but it is not possible to connect to an old server
  48. with a new client.