In theory I agree Dan. However even in dbus-daemon man page it says:
"SIGHUP will cause the D-Bus daemon to PARTIALLY reload its configuration
file..."
Partially? Interesting.
But anyway, what I've outlined above are my observations. The comment in
NetworkManager's dbus configuration is still va
On Tue, 2013-04-02 at 01:33 -0400, Pavel Simerda wrote:
> > From: "Dan Fruehauf"
> > My findings so far about that matter, regarding VPN plugins for
> > NetworkManager and their dbus policies.
> > 1. Vanilla /etc/dbus-1/system.d (without the SSH rules)
> > 2. Things don't work
> > 3. Adding the nm
On Tue, 2013-04-02 at 11:53 +1100, Dan Fruehauf wrote:
> My findings so far about that matter, regarding VPN plugins for
> NetworkManager and their dbus policies.
> 1. Vanilla /etc/dbus-1/system.d (without the SSH rules)
> 2. Things don't work
> 3. Adding the nm-ssh-service.conf file (to allow SSH
> From: "Dan Fruehauf"
> My findings so far about that matter, regarding VPN plugins for
> NetworkManager and their dbus policies.
> 1. Vanilla /etc/dbus-1/system.d (without the SSH rules)
> 2. Things don't work
> 3. Adding the nm-ssh-service.conf file (to allow SSH access)
> 4. Still things won't
My findings so far about that matter, regarding VPN plugins for
NetworkManager and their dbus policies.
1. Vanilla /etc/dbus-1/system.d (without the SSH rules)
2. Things don't work
3. Adding the nm-ssh-service.conf file (to allow SSH access)
4. Still things won't work
5. pgrep dbus-daemon | xargs k
Hey guys,
I'm sorry for the unnecessary patch, but apparently it is unneeded. Just
checked it without it (before submitting a bug to fedora to backport that
patch) and things work smoothly without it, so I guess it is not needed.
That goes I guess for the rest of the VPN modules out there, so I'l
On Thu, 2013-03-21 at 12:05 -0500, Robby Workman wrote:
> On Thu, 21 Mar 2013 10:54:59 -0500
> Dan Williams wrote:
>
> > On Thu, 2013-03-21 at 11:13 +1100, Dan Fruehauf wrote:
> > > Thanks for that guys.
> > >
> > > Sounds like the best thing to do is to actually allow the installed
> > > VPN pl
On Thu, 21 Mar 2013 10:54:59 -0500
Dan Williams wrote:
> On Thu, 2013-03-21 at 11:13 +1100, Dan Fruehauf wrote:
> > Thanks for that guys.
> >
> > Sounds like the best thing to do is to actually allow the installed
> > VPN plugins to control that configuration. i.e. every VPN plugin
> > can provi
On Thu, 2013-03-21 at 11:13 +1100, Dan Fruehauf wrote:
> Thanks for that guys.
>
> Sounds like the best thing to do is to actually allow the installed VPN
> plugins to control that configuration. i.e. every VPN plugin can provide a
> DBUS file that will allow itself to communicate with NetworkMana
Thanks for that guys.
Sounds like the best thing to do is to actually allow the installed VPN
plugins to control that configuration. i.e. every VPN plugin can provide a
DBUS file that will allow itself to communicate with NetworkManager.
However with the one file - one policy type of configuration
- Original Message -
> From: "Dan Fruehauf"
> Hey there,
>
> I'm planning to submit NetworkManager-SSH to Fedora (hopefully) and
> would like to submit that patch that just allows also the SSH plugin
> to coexist with NetworkManager.
I see no reply on the mailing list but I see your patc
On Wed, 2013-03-20 at 15:23 +1100, Dan Fruehauf wrote:
> Hey there,
>
> I'm planning to submit NetworkManager-SSH to Fedora (hopefully) and would
> like to submit that patch that just allows also the SSH plugin to coexist
> with NetworkManager.
>
> If you haven't look at NetworkManager-SSH, it's
Hey there,
I'm planning to submit NetworkManager-SSH to Fedora (hopefully) and would
like to submit that patch that just allows also the SSH plugin to coexist
with NetworkManager.
If you haven't look at NetworkManager-SSH, it's here:
https://github.com/danfruehauf/NetworkManager-ssh
Builds easily
13 matches
Mail list logo
