Hi Martin, > @Tobias: What do you think about reverting [1]? Could we use a less > aggressive mechanism to close these FDs for Android?
I guess we could. I don't remember what the problem was exactly, probably that charon was still attached to the shell somehow. Looking at the time stamp, this fix was for Android 2.x, so it's definitely possible that the original issue has since been fixed. > Probably we should go through a libstrongswan deinit/init cycle > after/during the fork(), so we don't share the pipe with the parent > process. Yeah, leaking those FDs to charon isn't optimal. But since we will remove starter sometime in the future, I guess reverting the patch should do it for now. Regards, Tobias _______________________________________________ Users mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/users
