Control: affects -1 + security.debian.org,release.debian.org

Dear Daniel

We noticed that several iterations of NMU happened in unstable
(partially as well causing potential removal from forky). Given the
scope of libreswan, and the available alterantives, w think we need a
reliable commitment to backport/test security fixes across the typical
three year life cycle (two years of stable-security and one year of
oldstable-security).

Should libreswan be included for forky and do we have this commitment
for the lifecycle? Clearly things can happen on the way, but at least
we would like to have a start into forky with such a commitment.

strongswan itself is actively maintained by Yves-Alexis, so we would
not be left without alternatives I think.

Regards,
Salvatore