delete some unused starter stuff
testing: Added AES default key size tests

IKEv1: ike-algo-02-aes-default (ike-algo-02 testwas was obsoleted and removed)
IKEv2: ikev2-algo-05-aes-default

The interop test interop-ikev2-strongswan-05-psk-aes was modified to include
unspecified "aes" (as opposed to "aes128")
tidy parts of addconn
(add a snipit from  Wolfgang Nothdurft)
pluto: Ensure we send/require KEY_LENGTH attributes for some ciphers

This continues the work in commit b12823df59768b

- Remove unused 3rd argument of kernel_alg_esp_enc_ok()
- Remove obsoleted kernel_alg_policy_algorithms()
  (obsoleted by crypto_req_keysize() and some other checks)
- Removed some #ifdef'ed out ESP attributes we don't support
  (and one listed as unsupported but handled earlier)
- Use kernel_alg_esp_enc_ok() to check if we support the received ESP transform
  (this should be extended with the functionality of crypto_req_keysize()
   regarding valid key sizes)

The function kernel_alg_policy_algorithms() used to add ESP KEY_LENGTH
attributes for algo ESP_AES and newer if the user did not specify these
(eg user specified "aes" and not "aes128"). It used the maximum key length
instead of the default only mandatory to implement key length (usually
128). The new crypto_req_keysize() uses the mandatory to implement
key length. This means a difference in interpretation of esp=aes-sha1
(formarly we would send AES256, now we send AES128). Ideally this is
changed to send all valid AES key sizes instead (128, 192 and 256)
although in Aggressive Mode we can only send one proposal. If the
receive has esp=aes-sha1, it will accept any of the three key sizes,
so the only configuration that would break is initiator with esp=aes-sha1
and responder with esp=aes128-sha1.

There was no similar function for IKE, so we could send OKALEY_ENCRYPTION
proposals with missing OAKLEY_KEY_LENGTH attributes (violating RFC 3602).
Commit b12823df59768b already introduced the code to add the default only
mandatory to implement key sizes to insert this attribute when missing.
Interop with older functions should be verified using a new impair function.
delte empty line
eliminate stutter
addconn: only try to resolve %defaultroute using the main routing table
Forgive NUL at end of XAUTH User Password.
Android bug https://code.google.com/p/android/issues/detail?id=36879
Wolfgang Nothdurft diagnosed this problem.
Merge branch 'master' of vault.libreswan.org:/srv/src/libreswan
fix 17f61d28e1d4778 - only the table 254 check was meant to go in
IKEv1: ignore incoming ISAKMP_NEXT_SAK (AKA ISAKMP_NEXT_NATD_BADDRAFTS)

We don't support SAK (group doi) and this VID is used by old cisco
devies as a NAT traversal payload. However, the method does not support
NAT-OA and we do not support that anymore. It is recommended to update
the Cisco firmware or device that sent this.

(It this turns out to be a bigger issue, we will need to re-instate a lot
 of complexity with NAT_T_WITH_NATD_BADDRAFT_VALUES)
Merge branch 'master' into hugh-2014may

Conflicts:
	programs/addconn/addconn.c
fix resolve_defaultroute_one in non-verbose mode
addconn: move table test out of conditional
KLIPS: updown was missing NETKEY commit f58b4a322c540
addconn: ignore routes over ipsecX or mastX devices for defaultroute calc
addconn: Another fix from Wolfgang

You need to dump the whole table when searching for the gateway
route, otherwise if the destination is known, you get only the first
matching route, which is not necessarily the gateway route.

You only interested in the default routes gateway, so skip all other
routes here.
Otherwise the first route which has a gateway will wrongly taken to set
the nexthop.

The return after resolve_ppp_peer has to be removed, because this skips
all following routes. (paul: and I made it return void)
addconn.c: remove redundant help text lines and cleanup coding style
testing: added basic-pluto-02 testing some addconn orienting
testing: fix OUTPUT.enumcheck.txt for new output of fixed enum