[Swan-commit] Changes to ref refs/heads/master

[Paul Wouters]

New commits:
commit 5415077baa7d663de3bdef69c663bab473b64e75
Merge: 83f3bf3 96bf459
Author: Paul Wouters <pwouters at redhat.com>
Date:   Sat Sep 14 19:14:18 2013 -0400

    Merge branch 'master' of vault.libreswan.org:/srv/src/libreswan

commit 83f3bf35b777cc44b8608481c2f8c29e6fc2a967
Author: Paul Wouters <pwouters at redhat.com>
Date:   Sat Sep 14 19:12:57 2013 -0400

    updated TESTLIST

commit 661686a87dc3945e1a342acf27190de27b2b3312
Author: Paul Wouters <pwouters at redhat.com>
Date:   Sat Sep 14 19:11:15 2013 -0400

    testing: loopback-pluto-05 tests the XFRM/NETKEY priority fix
    
    See rhbz#742126

commit aea91afae1269822d7f7ef74d7e1107a57882514
Author: Paul Wouters <pwouters at redhat.com>
Date:   Sat Sep 14 19:10:54 2013 -0400

    testing: loopback-pluto-06 shows problem of %any causing mismatch

commit 74ea75c7658fb6947348c140dcfedb51c83da22d
Author: Paul Wouters <pwouters at redhat.com>
Date:   Sat Sep 14 15:37:40 2013 -0400

    NETKEY: rhbz#742126 Use protocol and ports for priority
    
    (fixes most of the need for lsbz#83 as well)
    
    For XFRM/NETKEY we calculate a priority and match on longest prefix
    first. This match did not take into consideration ports or protocols,
    so a two conns with the only difference of leftprotoport=17/1701 would
    not get priority. This caused passthrough routines that were only more
    narrowed by protoport to not get priority. With the same priority as
    the routed tunnel, order of loading would determine which one was picked.