X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ian/git?p=secnet.git;a=blobdiff_plain;f=NEWS;h=ac1bf83ec30a78c86aca455cbd240f512bf68312;hp=c26e086b55834ec383f74ba80318a24e1f39b6b4;hb=4f5e39ecfaa49376b0a5c3a4c384e91a828c1105;hpb=8dea8d37a13fcc615daba3375809900f04a2e5a2 diff --git a/NEWS b/NEWS index c26e086..ac1bf83 100644 --- a/NEWS +++ b/NEWS @@ -1,13 +1,229 @@ * Planned for the future -New configuration syntax for netlinks: basic 'netlink' closure yields -a pure closure that can be applied in each site() to generate a -netlink for that site (with routes, options, etc.). Works well for -point-to-point: that netlink can be used directly by just one site. -Much cleaner separation between site() and netlink code this way. +Netlink device that implements an Ethernet bridge. -(Backward compatibility will be kept for a while.) +Modular transform code: choice of block ciphers, modes, sequence +numbers / timestamps, etc. similar to IWJ's udptunnel +Path-MTU discovery for each tunnel, and fragmentation/DF support in +netlink code. + +Separation of device drivers from IP router code - driver produces a +stream of packets (which has a tag indicating type and parameters). +Router module can be connected to stream to multiplex it between +different tunnels. + +Support for dynamic creation of streams/tunnels to cope with laptops, +etc. + +See also file "TODO". + +* New in version 0.1.14 + +The --help and --version options now send their output to stdout. + +Bugfix: TUN flavour "BSD" no longer implies a BSD-style ifconfig and +route command invocation. Instead "ioctl"-style is used, which should +work on both BSD and linux-2.2 systems. + +If no "networks" parameter is specified for a netlink device then it +is assumed to be 0.0.0.0/0 rather than the empty set. So, by default +there is a default route from each netlink device to the host machine. +The "networks" parameter can be used to implement a primitive +firewall, restricting the destination addresses of packets received +through tunnels; if a more complex firewall is required then implement +it on the host. + +* New in version 0.1.13 + +site.c code cleaned up; no externally visible changes + +secnet now calls setsid() after becoming a daemon. + +secnet now supports TUN on Solaris 2.5 and above (and possibly other +STREAMS-based systems as well). + +The TUN code now tries to auto-detect the type of "TUN" in use +(BSD-style, Linux-style or STREAMS-style). If your configuration file +specifies "tun-old" then it defaults to BSD-style; however, since +"tun-old" will be removed in a future release, you should change your +configuration file to specify "tun" and if there's a problem also +specify the flavour in use. + +Example: +netlink tun-old { + ... +}; +should be rewritten as +netlink tun { + flavour "bsd"; + ... +}; + +The flavours currently defined are "bsd", "linux" and "streams". + +The TUN code can now be configured to configure interfaces and +add/delete routes using one of several methods: invoking a +"linux"-style ifconfig/route command, a "bsd"-style ifconfig/route +command, "solaris-2.5"-style ifconfig/route command or calling ioctl() +directly. These methods can be selected using the "ifconfig-type" and +"route-type" options. + +Example: +netlink tun { + ifconfig-type "ioctl"; + route-type "ioctl"; + ... +}; + +The ioctl-based method is now the default for Linux systems. + +Magic numbers used within secnet are now collected in the header file +"magic.h". + +netlink now uses ICMP type=0 code=13 for 'administratively prohibited' +instead of code 9. See RFC1812 section 5.2.7.1. + +The UDP comm module now supports a proxy server, "udpforward". This +runs on a machine which is directly accessible by secnet and which can +send packets to appropriate destinations. It's useful when the proxy +machine doesn't support source- and destination-NAT. The proxy server +is specified using the "proxy" key in the UDP module configuration; +parameters are IP address (string) and port number. + +Bugfix: ipset_to_subnet_list() in ipaddr.c now believed to work in all +cases, including 0.0.0.0/0 + +* New in version 0.1.12 + +IMPORTANT: fix calculation of 'now' in secnet.c; necessary for correct +operation. + +(Only interesting for people building and modifying secnet by hand: +the Makefile now works out most dependencies automatically.) + +The netlink code no longer produces an internal routing table sorted +by netmask length. Instead, netlink instances have a 'priority'; the +table of routes is sorted by priority. Devices like laptops that have +tunnels that must sometimes 'mask' parts of other tunnels should be +given higher priorities. If a priority is not specified it is assumed +to be zero. + +Example usage: +site laptop { ... + link netlink { + route "192.168.73.74/31"; + priority 10; + }; +}; + +* New in version 0.1.11 + +Lists of IP addresses in the configuration file can now include +exclusions as well as inclusions. For example, you can specify all +the hosts on a subnet except one as follows: + +networks "192.168.73.0/24","!192.168.73.70"; + +(If you were only allowed inclusions, you'd have to specify that like +this: +networks "192.168.73.71/32","192.168.73.68/31","192.168.73.64/30", + "192.168.73.72/29","192.168.73.80/28","192.168.73.96/27", + "192.168.73.0/26","192.168.73.128/25"; +) + +secnet now ensures that it invokes userv-ipif with a non-overlapping +list of subnets. + +There is a new command-line option, --sites-key or -s, that enables +the configuration file key that's checked to determine the list of +active sites (default "sites") to be changed. This enables a single +configuration file to contain multiple cofigurations conveniently. + +NAKs are now sent when packets arrive that are not understood. The +tunnel code initiates a key setup if it sees a NAK. Future +developments should include configuration options that control this. + +The tunnel code notifies its peer when secnet is terminating, so the +peer can close the session. + +The netlink "exclude-remote-networks" option has now been replaced by +a "remote-networks" option; instead of specifying networks that no +site may access, you specify the set of networks that remote sites are +allowed to access. A sensible example: "192.168.0.0/16", +"172.16.0.0/12", "10.0.0.0/8", "!your-local-network" + +* New in version 0.1.10 + +WARNING: THIS VERSION MAKES A CHANGE TO THE CONFIGURATION FILE FORMAT +THAT IS NOT BACKWARD COMPATIBLE. However, in most configurations the +change only affects the sites.conf file, which is generated by the +make-secnet-sites script; after you regenerate your sites.conf using +version 0.1.10, everything should continue to work. + +Netlink devices now interact slightly differently with the 'site' +code. When you invoke a netlink closure like 'tun' or 'userv-ipif', +you get another closure back. You then invoke this closure (usually +in the site definitions) to specify things like routes and options. +The result of this invocation should be used as the 'link' option in +site configurations. + +All this really means is that instead of site configurations looking +like this: + +foo { + name "foo"; + networks "a", "b", "c"; + etc. +}; + +...they look like this: + +foo { + name "foo"; + link netlink { routes "a", "b", "c"; }; + etc. +}; + +This change was made to enable the 'site' code to be completely free +of any knowledge of the contents of the packets it transmits. It +should now be possible in the future to tunnel other protocols like +IPv6, IPX, raw Ethernet frames, etc. without changing the 'site' code +at all. + +Point-to-point netlink devices work slightly differently; when you +apply the 'tun', 'userv-ipif', etc. closure and specify the +ptp-address option, you must also specify the 'routes' option. The +result of this invocation should be passed directly to the 'link' +option of the site configuration. You can do things like this: + +sites site { + name "foo"; + link tun { + networks "192.168.73.76/32"; + local-address "192.168.73.76"; # IP address of interface + ptp-address "192.168.73.75"; # IP address of other end of link + routes "192.168.73.74/32"; + mtu 1400; + buffer sysbuffer(); + }; + etc. +}; + +The route dump obtained by sending SIGUSR1 to secnet now includes +packet counts. + +Point-to-point mode has now been tested. + +tun-old has now been tested, and the annoying 'untested' message has +been removed. Thanks to SGT and JDA. + +secnet now closes its stdin, stdout and stderr just after +backgrounding. + +Bugfix: specifying network "0.0.0.0/0" (or "default") now works +correctly. + * New in version 0.1.9 The netlink code may now generate ICMP responses to ICMP messages that