On Aug 19, 2014, at 5:43 PM, Paul Wouters <[email protected]> wrote: > On Tue, 19 Aug 2014, Les Leposo wrote: > >>> the entire ipsec system is brought down/up, eg racoon is completely >>> killed and restarted all the time. >> Sounds like a totally reproducible crash/signal. >> >> I'm sure if you file a radar with the procedure of how to reproduce >> (including connection duration & user activity), may be even a test account >> on your server, a developer on that end can gdb their way to the fix. >> >> You would also have to indicate how long this problem has been happening >> e.g. years/months, ios versions (to identify regressions). > > Years ago I tried to file bug reports for IPsec to Apple. No feedback > ever, and lots of "developer" spam email. > > If Apple cares, they can contact me to convince me the process changed. > But from what I'm hearing, if you're not doing millions in revenue, you > don't really get their attention whatsoever. > That's an interesting take.
Imho, generally, part of the issue with ikev2 (circa 2011-2012), no one really knew where ike/ipsec it was going in enterprise (aside from the 3GPP area which was considered niche and not worthy of the attention it deserved). Back then, SSL VPN was the shiny toy that dev managers & customers wanted, especially because it was easy to develop, a new opportunity for revenue stream, and the enterprise server vendors had made it so easy to deploy (e.g. you install the app and go to a webpage to log in and download your configs); completely overlooking significant weaknesses (and those of its library implementations). > Paul _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
