[Openswan dev] patch regarding bug #0000558

[Ken Bantoft]

Thanks, merged into git - #kb tree as 6cbe6ad4d809cab121d71078b082f09fa1b38e5a

On Tue, 17 Jan 2006, Matthias Haas wrote:

> Hello Paul,
>
> I have added a little patch to this issue. This fixes the behavior of not
> being strict in case ike or esp proposals are set.
>
> <----------------------snip--------------------->
>
> diff -Naur openswan-2.4.5rc3/lib/libopenswan/alg_info.c
> openswan-2.4.5rc3-devel/lib/libopenswan/alg_info.c
> --- openswan-2.4.5rc3/lib/libopenswan/alg_info.c        Mon Mar 21 04:58:10
> 2005
> +++ openswan-2.4.5rc3-devel/lib/libopenswan/alg_info.c  Wed Jan 11 08:00:28
> 2006
> @@ -568,6 +568,10 @@
>        /* use default if nul esp string */
>        if (!*alg_str) {
>            (*alg_info_add)(alg_info, 0, 0, 0, 0, 0, 0);
> +       } else {
> +           // MH: as this is necessary to have mandatory proposals
> +           // add the flag as soon as an explicit proposal is set
> +           alg_info->alg_info_flags |= ALG_INFO_F_STRICT;
>        }
>
> <----------------------snap------------------------>
>
> It keeps up the old behavior of the ! setting and also sets the strict flag,
> as soon as the proposals are defined without the !. I hope this helps to
> solve that problem. Atleast it works for me :-) .
>
> Matthias
>