On Mon, 23 Jul 2012, bnewb...@robocracy.org wrote:
I should probably give the code a one-over and include a HOWTO; I'll do this
tomorrow (tuesday).
Added a HOWTO and some other improvements; updated the pull request:
https://github.com/jvasile/Plinth/pull/2
-bryan
___
On 10 July 2012 21:45, wrote:
>
> Spoke with James and a few others here at the OpenITP event, notes and a
> rought plan are below. Some of this feels like reinventing the wheel; a
> future/mature implementation might use:
>
> D-Bus for message passing, PolicyKit for access control, Augeas for
On Mon, 23 Jul 2012, Nick Daly wrote:
Does anybody have thoughts on logical error handling behavior? Some of the
existing Plinth code (eg, hostname changer) would try to revert changes when
they failed; i'm not sure if that behavior should be implemented at the
exmachina (library/wrapper) level
On Mon, Jul 23, 2012 at 8:18 AM, wrote:
>
> On Sun, 22 Jul 2012, Nick M. Daly wrote:
>
>> Bryan, is this ready for me to add to the weekly images? This might
>> solve FreedomBuddy's OpenVPN service control issues.
>
> It's waiting for review/consensus/merge, but at this point there have been
> n
On Sun, 22 Jul 2012, Nick M. Daly wrote:
Bryan, is this ready for me to add to the weekly images? This might
solve FreedomBuddy's OpenVPN service control issues.
It's waiting for review/consensus/merge, but at this point there have been
no complaints so it's probably good to go? Does Plinth
On Sun, 15 Jul 2012 00:24:45 -0400 (EDT), bnewb...@robocracy.org wrote:
>
> Forgot to update this list, but I submitted a pull request to the Plinth
> repository:
>
>https://github.com/jvasile/Plinth/pull/2
>
> The core of the changes I made are also available in a separate
> repository:
>
Forgot to update this list, but I submitted a pull request to the Plinth
repository:
https://github.com/jvasile/Plinth/pull/2
The core of the changes I made are also available in a separate
repository:
https://github.com/bnewbold/exmachina
http://git.bnewbold.net/?p=exmachina.git;a=s
Also, just to be explicit, this would provide process separation, but does
not address local user authentication or access control. Eg, in this
scheme plinth would have permissions to edit all configuration files and
would need to authenticate users for access control on it's own (it
doesn't
