Hi Samuel, > > > > we don't really wanna do this and that is the reason why we never > > > > exposed these information. > > > Ok. got it. > > > > > > > > > > > I prefer actually that loading configuration via D-Bus is implemented > > > > than a bunch of WPA-Enterprise parameters that we can not expose to the > > > > end user anyway. Since normal end users won't understand them. And the > > > > service API is normal end user driven. > > > > > > Do you mean some new D-Bus call that would read some provisioning > > > configuration file? > > > What would be the right place for that, the Manager interface? > > > > yes, that is what I mean. Install provision configuration via a user > > interface. > Wouldn't having inotify support for our .config directory be enough ? Whenever > someone adds a new config there or expand an existing one we would just > provision the matching existing services.
yes, the inotify support is needed as well. However I can think about use cases where the UI can download configuration files from the web or Intranet and then just install them. That way there would be an installation path of these that could also be controlled via policies or a security framework. For example PolicyKit. Regards Marcel _______________________________________________ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
