Mailinglist Archive: opensuse-buildservice (206 mails)

< Previous Next >
Re: [opensuse-buildservice] Should osc support global oscrc ?
  • From: Marcus Hüwe <suse-tux@xxxxxx>
  • Date: Mon, 28 Feb 2011 17:45:10 +0100
  • Message-id: <20110228164510.GB4461@linux>
On 2011-02-28 13:22:40 +0000, Anas Nashif wrote:

On 28 Feb 2011, at 12:59, Marcus Hüwe wrote:


On 2011-02-28 11:34:07 +0000, Anas Nashif wrote:
Actually, osc should not touch or change anything in the home directory,
if the permissions of oscrc are not right, then it should just refuse to
run and ask the user to change the permissions of .oscrc.
Hmm yes we could implement this easily.

Another thing I noticed is that it manipulates the user credentials,
removes password entries and such without asking the user, which is really
a bad behaviour IMO, such changes should be confirmed or done by the user.

This shouldn't be the case with osc from git master anymore.

What is wrong with having a system level oscrc file? For example in
/etc/oscrc? This is not less secure, since the the permissions of the file
/etc can be set to prevent other's from reading it.

There's no need for a "system level" oscrc, just tell osc which
configfile it should use: "osc --config /path/to/file" or set
the "OSC_CONFIG" environment variable.

Using environment variable for something like that really makes things harder
than they should be, especially if we are not using the command line but osc
as a module. We should be able to override the configuration when
initialising osc in some other python program for example. That should work
fine if we do not try to change the permissions mentioned above I guess..

As I said it's possible to change the code so that it raises an
exception if the permissions of the config are "wrong". If you're
writing a python module using osc you can specify a different config
with "get_config(override_conffile='/path/to/config', ...)".

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >