Mailinglist Archive: yast-devel (246 mails)

< Previous Next >
Re: [yast-devel] WebYaST: Vendor customization
  • From: Jiří Suchomel <jsuchome@xxxxxxx>
  • Date: Thu, 13 Aug 2009 18:37:52 +0200
  • Message-id: <200908131837.53052.jsuchome@xxxxxxx>
On Thursday 13 of August 2009 15:47:37 Klaus Kaempf wrote:
Technically, config file is parsed from YaPI which is called from
rest-service, so it is not bound to webYaST usage and theoretically
could be used together with YaPI from perl scripts.

Ruby provides nice support for yaml files, so there's no need to
involve YaPI here.

The reason to involve YaPI is different: SCR layer runs as root after
user passes the permissions checks, so it has rights to access the
scripts.

Using the YaPI where its needed is fine. But going via SCR and Perl
for a simple task easily doable within Ruby doesn't look
straightforward to me.

The scripts (either vendor specific ones or init scripts) should be called by
YaPI because of SCR running with root privilliegies. Or maybe there is some
other way, but I don't know about it.

So you mean that parsing the config file could be done on ruby level? That is
possible, but how should the results (the example of result is path to
executable script) be passed to YaPI layer? As a parameter? This is a
security risk, as the one who has the right to operate services gets the
right to execute custom script....

Jiri

--
Jiri Suchomel

SUSE LINUX, s.r.o. e-mail: jsuchome@xxxxxxx
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Praha 9, Czech Republic http://www.suse.cz
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups