user/sven/linux.git/include/net/flow.h, branch stable/2.6.16.y

[LSM-IPSec]: Security association restriction.

2006-01-03T21:10:24Z

This patch series implements per packet access control via the extension of the Linux Security Modules (LSM) interface by hooks in the XFRM and pfkey subsystems that leverage IPSec security associations to label packets. Extensions to the SELinux LSM are included that leverage the patch for this purpose. This patch implements the changes necessary to the XFRM subsystem, pfkey interface, ipv4/ipv6, and xfrm_user interface to restrict a socket to use only authorized security associations (or no security association) to send/receive network packets. Patch purpose: The patch is designed to enable access control per packets based on the strongly authenticated IPSec security association. Such access controls augment the existing ones based on network interface and IP address. The former are very coarse-grained, and the latter can be spoofed. By using IPSec, the system can control access to remote hosts based on cryptographic keys generated using the IPSec mechanism. This enables access control on a per-machine basis or per-application if the remote machine is running the same mechanism and trusted to enforce the access control policy. Patch design approach: The overall approach is that policy (xfrm_policy) entries set by user-level programs (e.g., setkey for ipsec-tools) are extended with a security context that is used at policy selection time in the XFRM subsystem to restrict the sockets that can send/receive packets via security associations (xfrm_states) that are built from those policies. A presentation available at www.selinux-symposium.org/2005/presentations/session2/2-3-jaeger.pdf from the SELinux symposium describes the overall approach. Patch implementation details: On output, the policy retrieved (via xfrm_policy_lookup or xfrm_sk_policy_lookup) must be authorized for the security context of the socket and the same security context is required for resultant security association (retrieved or negotiated via racoon in ipsec-tools). This is enforced in xfrm_state_find. On input, the policy retrieved must also be authorized for the socket (at __xfrm_policy_check), and the security context of the policy must also match the security association being used. The patch has virtually no impact on packets that do not use IPSec. The existing Netfilter (outgoing) and LSM rcv_skb hooks are used as before. Also, if IPSec is used without security contexts, the impact is minimal. The LSM must allow such policies to be selected for the combination of socket and remote machine, but subsequent IPSec processing proceeds as in the original case. Testing: The pfkey interface is tested using the ipsec-tools. ipsec-tools have been modified (a separate ipsec-tools patch is available for version 0.5) that supports assignment of xfrm_policy entries and security associations with security contexts via setkey and the negotiation using the security contexts via racoon. The xfrm_user interface is tested via ad hoc programs that set security contexts. These programs are also available from me, and contain programs for setting, getting, and deleting policy for testing this interface. Testing of sa functions was done by tracing kernel behavior. Signed-off-by: Trent Jaeger Signed-off-by: Herbert Xu Signed-off-by: David S. Miller

[IPV4]: Multipath cache algorithm support.

2005-03-17T07:58:54Z

Signed-off-by: David S. Miller

[NET]: Give struct flowi explicit alignment, with help from yoshfuji.

2004-03-18T12:23:46Z

[NET]: net/flow.h needs asm/atomic.h

2004-01-14T16:19:07Z

[IPSEC]: Kill object argument from flow_cache_flush.

2003-06-12T10:29:33Z

[IPSEC]: Zap killed policies from the flow cache properly.

2003-06-09T02:20:58Z

[IPV6]: Dont store pointers to in6_addrs in struct flowi.

2003-05-22T11:42:28Z

[NET]: Split out policy flow cache to be a generic facility.

2003-05-15T14:05:28Z

[DECNET]: DECnet routing fixes etc.

2003-04-18T03:43:09Z

o As requested, macros in dn_fib.h changed to decnet specific names o Two bugs fixed (only in 2.5 decnet stack) relating to bind and connection states. o Numerous style changes: using C99 initialisers and inline rather than __inline__ o Use struct flowi as routing key (for forthcoming flow cache) o Add metrics to routing table o Many routing table bug fixes o New wait code to improve efficiency o We use real device MTUs now rather than saying "hmm... looks like ethernet must be 1500" as we used to (still one or two places to fix, but its mostly correct in this patch) o Tidy up in af_decnet.c:dn_sendmsg() in preparation for zerocopy o Updates to rtnetlink code to return more information o Removed ioctl() for decnet fib. It never did anything and rtnetlink is a far better interface anyway. o Converted /proc/decnet_neigh to seq_file (other /proc files to follow) o DECnet route cache now uses RCU like the ipv4 route cache o Misc bug fixes wherever I found them o SO_BINDTODEVICE works for outgoing connections

[NET]: Actually apply Yoshfuji's fl6_{src,dst} patch.

2003-04-17T11:57:09Z