August 2008 - YaST Development - openSUSE Mailing Lists

[yast-devel] Czech YaST2 team (Prague) meeting 2008-08-05
by Jiří Suchomel 06 Aug '08

06 Aug '08

Czech YaST2 team (Prague) meeting 2008-08-05 ============================================ Present: jsrain, jsuchome, juhliarik, kmachalkova, locilka, lslezak, mvidner, mzugec Absent: jkupec, jreidinger Minutes: jsuchome Next Minutes: juhliarik Bootloader Several features implemented, e.g.: - support for ordering disks in device.map for GRUB (fate#303964) - support for reducing devices from device.map to 8 devices (fate #303548) LDAP LDAP object names are not transferred to lowercase any more (fate#303596). LDAP Browser can store configured connections (fate#302858). DNS Server Added support for IPv6 reverse zones (fate #304401). Added support for automatic generation of connected reverse zones (fate #304401). Added support for TXT and SRV records (fate #206, #120040). Added support for AAAA (IPv6) records (fate #304401). pkg-bindings Published generated documentation: http://forgeftp.novell.com/yast/doc/SL11.1/pkg-bindings/ Fixed selecting package from multi-arch repository (prefer architecture to version, bnc#413150). yastdoc New documentation tool, still WIP, see http://en.opensuse.org/YaST/yastdoc Network Added support for tunnel devices in NetworkInterfaces (fate#302184). Fixed writing udev rules in installation: http://mzugec.blogspot.com/2008/07/autoyast-network-device-names.html http://en.opensuse.org/YaST/installation-network#Device_names_in_AutoYaST -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome(a)suse.cz 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(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] Replacepoints with python-yui
by Jan-Simon Möller 05 Aug '08

05 Aug '08

Hi ! I wonder if/how i can use Replacepoints in python-yui ... createReplacePoint is there, but the ReplaceWidget call seems not implemented in python-yui. And btw: where can i post examples for inclusion into libyui-bindings ? here ? best regards Jan-Simon -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 5

[yast-devel] Re: [opensuse-factory] DBus/PolicyKit support in Yast in openSUSE-11.1-Alpha1
by Ladislav Slezak 05 Aug '08

05 Aug '08

Vincent Untz wrote: [...] > Is the second step to use a dbus service ("You have to enable PolicyKit > actions performed by a particular Yast module to the relevant users.") a > temporary one or will it stay this way? I'd like to enhance policy checks for generic agents. The problem is that some agents are generic (like .target.bash or .process) and the current policy checks on the common SCR level are not sufficient for them. (The check is performed before calling an SCR agent.) For example .target.bash agent is a generic agent for starting _any_ shell command as root. For security reasons the command is now part of the policy ID but due to the PolicyKit limitations the mapping is not one to one. PolicyKit permits only [0-9], [a-z] and _. (underscore and dot) characters only, yast replaces all invalid characters by underscore. The problem is that potentially the user could call the agent with different command which encodes to the same policy ID. Imagine hypothetic /bin/Date binary for setting the system time (in addition to the usual /bin/date which reads time). If an user is allowed to do org.opensuse.yast.scr.execute.target.bash-output-bin-date action (which allows to execute /bin/date) he is also allowed to execute /bin/Date which should be forbidden. Another problem is the the policy ID cannot be longer than 255 characters. So "/bin/myprogram --option1 .... -option200" and "/bin/myprogram --option1 .... --option200 -option201" might be truncated to same ID which means that the user could add extra options which might completely change the meaning of the command. The solution is that there should be a mapping file which would map "complete SCR command" to "unique actionID". Example: SCR::Execute + .target.bash_output + "/bin/date" -> org.opensuse.yast.scr.action.readtime. The result is that you will need to change some policies in the future (if the yast module uses a generic agent). I'll open a bug for that, this a security problem which must be solved in 11.1. Another required change will be needed when we introduce DBus/PolicyKit in the logic layer later. But this will be done probably after 11.1. -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Czech YaST2 team (Prague) meeting 2008-07-29
by Jiri Srain 05 Aug '08

05 Aug '08

Czech YaST2 team (Prague) meeting 2008-07-29 ============================================ Present: aschnell, jkupec, jsrain, juhliarik, lslezak Absent: jreidinger, jsuchome, kmachalkova, locilka, mvidner, mzugec Minutes: jsrain Partitioner redesign - libstorage part has already been merged to trunk, the rest prepared to be merged after SLE11 Alpha1 Bootloader features - uEFI is mostly in stuck; we do not have hardware which we could use for testing; related packages should be ready soon - progress in other areas: - fate #301994: Correct device mapping in case windows is installed on the second HD - limiting the size of device map (fate #303548) Service support - zypper being adapted to support services handling - YaST (repository manager) not yet started YaST via DBus and PolicyKit - has been documented on openSUSE wiki - has been announced on Factory: http://lists.opensuse.org/opensuse-factory/2008-07/msg00164.html

1 0

[yast-devel] Wizard module: Dropping deprecated functions
by Lukas Ocilka 04 Aug '08

04 Aug '08

Hi, I've just dropped these deprecated functions from Wizard YCP module: * /ReplaceNextButton/ - replaced with *SetNextButton* * /ReplaceBackButton/ - replaced with *SetBackButton* * /ReplaceAbortButton/ - replaced with *SetAbortButton* These functions have been reporting a warning for a very long time and except one module /yast2-drbd version 2.13/, it is not in use anymore. This hasn't been done just for fun but because of using UI::WizardCommand in there instead of UI::ReplaceWidget. Have a nice day Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

2 1

[yast-devel] EVMS and YaST
by Arvin Schnell 04 Aug '08

04 Aug '08

Hi Hackers, as you might have heard EVMS will no longer be supported by yast2-storage in SLE11. So I will remove huge amounts of obsolete code from yast2-storage, among them the functions ActivateEvms(), CreateEvmsCo(), ExtendEvmsCo(), CreateEvmsVolume() and ChangeEvmsStripeSize() in Storage.ycp used by update and autoinstallation. Please remove these function calls. ciao Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] announce: API changes in yast2-users and yast2-ldap
by Jiří Suchomel 04 Aug '08

04 Aug '08

Hi hackers, those of you who are using neither .ldap agent nor any yast2-users API may hit Delete now. For others, I would like to announce that .ldap agent now uses original LDAP names of the object keys that are returned as a result of a search. For example, the search for user object which returned $[ "uidnumber" : 1000, "homedirectory" : "/home/hh", "uid" : "hh" ] now returns $[ "uidNumber" : 1000, "homeDirectory" : "/home/hh", "uid" : "hh" ] This change (required by feature 303596) affects the return value of all .ldap.search calls, so please check your code. I tried to grep for agent usage and update yast2-mail, yast2-ldap-server and yast2-samba-server, see the attached diff. Please review, or at least test it and submit the changes. The change also affects the API of yast2-users, since the module uses for its internal user and group representation the same keys as are defined for LDAP. So if you are using the keys directly, e.g. you are changing user name in this way: Users::SelectUser (1000); Users::EditUser ($[ "uidnumber" : 1111 ]); Users::CommitUser () etc. you have to change the line where the internal key is used, i.e. Users::EditUser ($[ "uidNumber" : 1111 ]); (However, I haven't find anyone using yast2-users module to add or edit users) If anything is not clear enough, please ask. Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz

2 4

[yast-devel] DBus/PolicyKit support in Yast in openSUSE-11.1-Alpha1
by Ladislav Slezak 04 Aug '08

04 Aug '08

Hi all! I'd like to inform you about a new feature in Yast in openSUSE-11.1-Alpha1. The feature allows you to configure role based access to yast. The current implementation is limited only to some yast functionality (the SCR part), e.g. it doesn't allow to install packages by a non-root user. WARNING: the DBus support is still in development state, it may be buggy or whatever else... I ask the brave people here to give it a try. See http://en.opensuse.org/YaST/DBus_Integration for more details. There is an example how to enable "time zone change" task for a non-root user. If you find any problem with the DBus integration report it to bugzilla.novell.com and assign the bug to me. Do not forget to attach also the non-root log file (described in the link above). -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 6

[yast-devel] Important Changes to Storage
by Arvin Schnell 03 Aug '08

03 Aug '08

Hi Hackers, for fate #302971 I had to implement a lock for libstorage. This has some consequences for everyone using storage in YaST. The initialisation of libstorage fails if there is another process holding a lock. I have extended Storage::InitLibstorage to display a popup in that case (unfinished). The user can retry to initialise libstorage. The problem is that so far nobody explicitly initialises libstorage. This is more or less required now since you have to take action when locking fails (e.g. gracefully abort). So call Storage::InitLibstorage(readonly) before doing any other storage calls. You can set readonly to true if you are sure your code and no code you call modifies storage. If you do not call Storage::InitLibstorage() the first storage function will do so. But if initialisation fails all storage functions requiring libstorage return nil (if they return anything) or crash (if they don't check for proper initialisation). Comments for improvement to the situation are welcome. ciao Arvin -- Arvin Schnell, <aschnell(a)suse.de> Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 1

[yast-devel] yast from svn - libyui-bindings: how to compile standalone
by Jan-Simon Möller 01 Aug '08

01 Aug '08

Hi! How can i compile yast, especially all dependencies of libyui-bindings into an own prefix ? I don't want to break my installed yast but need a up-to-date version of python-yui for an 10.3-based host. TIA Jan-Simon -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1