FYI, I removed the code because it seemed arbitrary. It would reject some,
but not all combinations of:
west.ipsec.secrets
westipsec.secrets
west.secrets
ipsec.secrets
I figured reducing this list to just:
west.ipsec.secrets
ipsec.secrets
(and perhaps only allowing one) + logging the result was for a later pass.
On Mon, 21 Sep 2020 at 11:34, Antony Antony <[email protected]>
wrote:
> New commits:
> commit eff59a46350f2e638f1ef5051ab6f7a29033e5cf
> Author: Antony Antony <[email protected]>
> Date: Mon Sep 21 15:24:13 2020 +0000
>
> testing: swan-prep break on conflicting config files
>
> fix 1e0b14ec0b20c3 this is a nice improvement, however, allowing
> conflicting files and picking the first one is less than ideal.
> We would end up with test cases with reduntant config files and endless
> confusion. Even with this fix I suspect 1e0b14ec0b20c3 would allow more
> config files than what a test would use.
>
> This is a first step to refuse to copy config file when there are
> conflicting files. The checks could stricter than this.
>
> _______________________________________________
> Swan-commit mailing list
> [email protected]
> https://lists.libreswan.org/mailman/listinfo/swan-commit
>
_______________________________________________
Swan-dev mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan-dev
