On Wed, Oct 18, 2006 at 11:26:23AM +0900, Kazunori MIYAZAWA wrote:
>
> diff --git a/net/xfrm/xfrm_algo.c b/net/xfrm/xfrm_algo.c
> index 5a0dbeb..e03eadd 100644
> --- a/net/xfrm/xfrm_algo.c
> +++ b/net/xfrm/xfrm_algo.c
> @@ -119,6 +119,24 @@ static struct xfrm_algo_desc aalg_list[]
> .sadb_alg_maxbits = 160
> }
> },
> +{
> + .name = "xcbc(aes)",
> + .compat = "aes_xcbc_128",
BTW, new algorithms should not have a compat field. The whole point
of the compat field is to allow existing users to get the correct
algorithm without updating their configuration. This does not make
sense for new algorithms as there aren't any existing configurations
for us to worry about yet.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
