You can hardcode cacerts, keys and certificates inside profiles as well.Eh, no.
That is only the case when you have a server that uses username/password (which will be hardcoded in the config file).
That's my recommended way, because OpenVPN Connect on Android and Apple requires it that way anyways, so any decent VPN solution with profile creation should support that way out of the box.
And guess what?
I've already considered the case where they are not hardcoded inside the profile but only linked.
The import process would just check for them in the same directory as the config and hardcode them during import.
... which brings us back to the reason why we need this plugin.Besides that, most people don't have a clue how to create an openvpn configuration,
Which just proves my point.And if you want to use quotes, I've got one too: "There is never time to do it right, but there is always time to do it over and over again".
You are struggling in thoughts - an employer would call them "excuses" - about things that do not matter yet and probably never will.
On the other hand - and that's just what your quote says - nothing would be carved in stone, it still could (and probably will) be changed later to further enhance things.
It's useless to spend thoughts on intermediate certs, hierarchical certs, blah bla bla.
What we have now (and as I see it here most probably will always have!) is absolutely nothing.
To everybody else reading this:
Read my lips - we won't have any decent (Open)VPN support in any Open*** for years if not never.
Make the next box you buy a Dreambox, they got an OpenVPN-Plugin in Gemini Blue Panel since 2012 or so.
There is absolutely not a single Open*** dev left who cares about real user's world problems.