On Sat, Apr 11, 2015 at 01:07:24PM -0400, Paul Wouters wrote:
> So the patch that switched it between add and update got quite a history
> behind it. And a reverted revert commit.
>
> Part of the problem is https://bugs.libreswan.org/show_bug.cgi?id=75
>
> Some history can be seen in the git commits:
>
> https://github.com/libreswan/libreswan/commit/b5fa5eb1033ee3b73f7121a8ba3e593be21f8226
> https://github.com/libreswan/libreswan/commit/f81203faff29490157c6ef1cbc75d476a902bb63
> https://github.com/libreswan/libreswan/commit/15d27b8ad4a2f0d1fb252e608cfeafe6b7121773
> https://github.com/libreswan/libreswan/commit/39b7891e50fae053e8acebdc1f55af6408f8fdad
>
> So first, the b5 commit changed from add to update:
No these are talking about updating policies, I'm talking about
updating states which are totally different.
The commit that should be reverted (assuming libreswan really
sticks to the 30s timeout) is
70566d65065aabd9fc968edd7d0c94e0d6c29902
Cheers,
--
Email: Herbert Xu <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
_______________________________________________
Swan-dev mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan-dev
