From: Michael R. <mr...@us...> - 2004-03-13 15:54:42
|
Hi Daniel, > > I was starting to work on the config entry cleanup while I found yet > > another show stopper: There are some severe security problems related to > > config entries. Since it is possible to change any config entry by the > > MRL, all config entries which are interpreted as absolute paths to some > > file are really, really bad. My proposal would be to drop the config > > entry by MRL feature entirely. Is there any important use for it? > > if that doesn't affect the xine-ui feature i don't see any objection. It would not, but IMO that would not make much sense. If xine-ui would still be able to fill config entries with values from untrusted sources, we would not increase security at all by disabling this only in xine-lib. Another option would be to add (yet another) config entry for "implicit config changes", disabled by default, which xine-lib and xine-ui can query to determine, whether the user wants to allow config settings in MRLs. Michael -- panic("Attempted to kill the idle task!"); 2.2.16 /usr/src/linux/kernel/exit.c |