D-Bus service activation and access control

Thiago Macieira thiago at kde.org
Mon Jul 31 16:46:57 UTC 2017

On Monday, 31 July 2017 03:35:53 PDT you wrote:
> > Out of curiosity: is any of this needed considering NetworkManger already
> > does all of it?
> That is going to be resolved at a later stage, and we don't want to tie
> ourselves to NetworkManager alone.  I'm having systemd-networkd support
> open as well, plus we're not quite sure what will happen on *BSD (which
> we have seen have some D-Bus packages available).  So while we do
> currently target Linux, we try to not make it too difficult to at least
> enable this new code base on other *nix oriented OSes.

What problem are you trying to solve at all?

OpenVPN already works and almost all Unix systems already have a way of 
managing it. Heck, I even have it on my Android phone, even though I had to 
figure out which of the applications actually worked.

NM can manage its configuration and is rather complete. I have some weird 
settings in my VPN and I found that all settings can be properly configured in 
the UI. NM will start and stop the openvpn process just fine.

So, what problem are you trying to solve?

And while you're solving it, are you sure you're not breaking everyone else? 
You need to keep the openvpn process available and parsing both config files and 
command-line arguments as-is anyway.

Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center

More information about the dbus mailing list