Ondrej Moris
Ondrej Moris
IMO #2696 solves (2) for me. Ad (1). I am starting to realize that this might not be possible. What I am looking for is to be able to "resurrect"...
I would have to modify 'crasher' test to detect reboot and to attempt to restore the library (and then use options added in #2696) to get to 'second test'.
The current PR allows disabling FIPS but that is not really an option and should not be supported. It was possible to some extend on RHEL but it was not...
@psss Can you assign this one to me? I have a playbook ready and I am about to push it with the rest of the changes.
I can't really push into this PR since I don't have the repository write access (I guess I don't need that). So I am wondering - shall I open a...
Kernel can be configured in a way that panic is followed by a reboot. This essentially means that once TMT is able to gracefully handle unexpected/hard reboot it will be...
So assume I have a connection configured with rekey=no and it child SA lifetime expires, with libreswan-4 it was correctly not re-established but with libreswan-5 it keep re-establishing. Is that...
I am using auto=add so that is why re-establishing should not be happening (as it wasn't in libreswan-4). Here's my full config (host-to-host, both connections share the same config): ```...
Interesting - but was it supposed to be like that this in libreswan-4 too or is this semantics new to libreswan-5?
@cagney I am sorry, I simply can't reproduce it any longer, I suppose I had some kind of bogus in the policy file and I did not notice. Please feel...