Re: [sipX-dev] Input on XCF-651 implementation (Restore pagefrom sipXconfig UI)
Martin Steinmann wrote:
>
>Cc: sipx-dev@xxxxxxxxxxxxxx
>Subject: Re: [sipX-dev] Input on XCF-651 implementation (Restore
pagefrom sipXconfig UI)
>
>On Wed, 2007-04-04 at 17:00 -0400, Douglas Hubler wrote:
>
>>
>> If it helps you decide how to proceed, as project leader of web ui, I
>> would not turn down a contribution just because it prompted for root
>> password in order to restore system as you outlined in your first
>> proposal and as described in issue comments. Admins that only wanted to
>> restore from CLI can continue to do so.
>
>With a password from the user is ok - just don't configure sudo
>privileges for the process.
I might have missed this, but why do we need root access? The database
and all the config files in /etc/sipxpbx should be owned by the
sipXconfig process.
In my view, there are two reasons to integrate "restore" into sipXconfig:
a) Ease of use: Make it unnecessary for an admin to use a console
b) Being able to create a closed system, where the admin is not given
root access but can still do restore
While objective one is currently our main one, requiring a root password
for "restore" defeats objective two.
--martin
Fact: you need to restart sipXpbx after the restore
Fact: you need to be root to restart sipXpbx
Question: Would you rather not have restore feature at all if it required root
access?
To recapitulate the discussion: we talked about setuid solution, and sudo solution - both raised
security concerns. I am not an expert here: I'd say let's implement the solution with asking for
root password while waiting for a better idea to emerge.
D.
