IPSec/IKEv2 is not breaking anything, maybe it just won't setup a tunnel. Maybe a better analogy: We don't say the same thing about for example a piano: "it should only be able to be used correctly". You have to study and practice a bit before you can play a somewhat decent piece, without study no piano play. The same for IPSec/IKEv2, without study no tunnel. Every VPN protocol needs a bit of study, maybe some protocol a bit more than the other. We have a Dutch saying: "Als een boer niet kan zwemmen ligt het aan zijn zwembroek", which translates to something like: "If a farmer can't swim it's because of his swimming trunks".
If you want out-of-the-box VPN solutions, you go to a VPN provider and download their apps. ;-o
This comment thread is for people who don't think IPSec/IKEv2 is the worst invention on the planet and want to share life saving stories about it.
This will inevitably be downvoted, but (almost) everytime I see IPSec/IKEv2 mentioned there's a bunch of people puking all over it. Of course, it has a lot of options and configurations and you can fu*k things up, you have to study it a bit, like a brain surgeon has to read some books and do some practice. But once done that, it is a beautiful piece of protocol, excuse my language. It's fast, stable, it auto-reconnects, not to mention MOBIKE, it is simply state-of-the-art. I guess not everybody can drive the Formula 1 car of the VPN protocols. ;-o
If it's really something worth keeping I would probably print it out to keep it safe, instead of letting it disappear in a continuing chat, with the risk of losing it, because your data is on somebody else's server and you're not in control of it.
To answer your question: I don't value chat histories that much. In the early days people didn't walk around with tape recorders to record everything everybody was saying either. If there is something really important said in a chat, you could make a screenshot, the same way you would take a note on paper with a pencil in pre-digital times, but how often did that happen? To write down an address for example, but you could put that in the digital equivalent of the rolodex, like Contacts.app or Notes. You could even go as far as to save information in a personal CRM like Monica.
My theory: apparently a lot of companies use the IP-addresses internally. And apparently the intention was to sell the IP-addresses already for a long time. But buyers would be faced with a lot of traffic coming from all those companies using the ranges internally, instant DDoS. Maybe this is an attempt to "clean" the IP-addresses before selling them. It will probably only take time before most companies using the ranges internally and having problems now (or happily continuing business now with the help of Pentagon servers), to reconfigure their networks to fix it. In the meantime the Pentagon can probably collect some interesting traffic, speeding up the whole process of reconfiguration by companies who use the ranges, to prevent their secrets from falling into exactly the right hands.
"Of the seven Recovery Key Shareholders who possess the ability to restore the DNS root keys, Dan is the American representative." -https://dankaminsky.com/bio/
It doesn't appear automatically, it's programmable [1], you as a developer decide what to do with a low score, you could ask for extra verification for example. I agree with the tracking and privacy issues with ReCAPTCHA.
Not to rely on it, but I've implemented ReCAPTCHA v3 on a couple of websites and got under the impression spambots are detecting and skipping websites who have implemented it altogether.
It's like telling da Vinci, at the moment of the reveal of the Mona Lisa, he should have used more paint so it can last 100k years instead of only 98k years. We are not dealing with a 10MB website with seconds long loading time and screaming for smaller images.