September 2013 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306960] support update of systems with encrypted physical volumes
by fate_noreply＠suse.de 28 Oct '13

28 Oct '13

Feature added by: Arvin Schnell (aschnell) Feature #306960, revision 1 Title: support update of systems with encrypted physical volumes openSUSE-11.3: New Priority Requester: Mandatory Requested by: Arvin Schnell (aschnell) Description: Since openSUSE 11.2 can install systems with encrypted physical volumes (see fate #305633) openSUSE 11.3 must be able to update such systems. -- openSUSE Feature: https://features.opensuse.org/306960

1 14

[openFATE 307745] Let the admin ("root") download and install untrusted third-party RPMs from known URLs guided via YaST
by fate_noreply＠suse.de 24 Oct '13

24 Oct '13

Feature added by: Johannes Meixner (jsmeix) Feature #307745, revision 1 Title: Let the admin ("root") download and install untrusted third-party RPMs from known URLs guided via YaST openSUSE-11.3: New Priority Requester: Neutral Requested by: Johannes Meixner (jsmeix) Description: I would like to have it evaluated whether or not it is allowed to implement a dialog in YaST which lets the system admin (i.e. "root") download and install untrusted third-party RPMs from known URLs. In any case "root" can download and install any software manually. This reques is about to provide a guided and restricted way for some particular cases. My current use-case are the printer driver packages which are available via OpenPrinting at the Linux Foundation: http://www.openprinting.org/driver_list.cgi where LSB compliant driver RPM packages are available. >From my point of view those packages are on the one hand untrusted third-party RPMs but on the other hand their download location is "well known" which makes those packages "well known third-party packages". I assume that from a strict security point of view any kind of third party software is "strictly forbidden" but I like to propose a more useful way here: The system adminj (i.e. "root") can in any case download and install whatever software he likes. This man invalidate e.g. whatever support contract but it is up to the admin to know what he does. Currently we have no idea at all which third-party printer drivers an admin may download an install on his own. When he has a printer for which there is no driver provided by us, the admin may download whatever driver software from any totally unknown location and install it with any unknown consequences. (E.g. some time ago there was a printer driver from a printer manufacturer where its installation script set setuid root bits on various user application programs to mak it "just work".) Currently we even do not tell the admin about the well known printer driver locations at OpenPrinting. >From my point of view it would be a big improvement when I could implement a dialog in the YaST printer module which shows a very explicite text that this is about untrusted unsupported third-party software. This text would require explicite confirmation by the admin. Then it downloads RPMs only from hardcoded URLs from OpenPrinting and inspects the downloaded RPM whether it overwrites already installed files on the system and if not, it installs it without running any RPM scripts because normal printer drivers do not need to run RPM scripts during installation. If the above conditions are not fulfilled it shows a very explicite warning text and does not install anything. In contrast to now where we leave the admin totally on its own how to get a driver for a printer for which we do not provide a driver, the above described guided and restricted way to download and install drivers via YaST would help both the admin and us because in many cases we could make sure this way that we know at least which third-party driver the admin has installed. Please do not confuse this request with the different request how a third-party (e.g. OpenPrinting or a printer manufacturer) could provide software packages in a way which is in full compliance to our package installation and management tools (i.e. via a repository which provides also updates and so on). This request is meant for third-party RPMs "as is" where the vendor/provider simply does not want (because of whatever reason which is beyond our control) to provide his RPMs in compliance to our package installation and management tools. -- openSUSE Feature: https://features.opensuse.org/307745

1 9

[New: openFATE 313496] get rid of world writable directories
by fate_noreply＠suse.de 23 Oct '13

23 Oct '13

Feature added by: Ludwig Nussel (lnussel) Feature #313496, revision 1 Title: get rid of world writable directories openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: We should get rid of all /tmp like world writable directores besides /tmp and /var/tmp themselves. This reduces the number of places where users could store extra files that don't belong there. Also reduces security risks caused by programs operating on such insecure directories. Candidates: /var/lib/xemacs/lock/ /var/run/uscreens/ /var/spool/uucppublic/ /var/tmp/vi.recover/ /var/spool/mail/ /var/cache/fonts/ -- openSUSE Feature: https://features.opensuse.org/313496

1 1

[New: openFATE 311338] YaST debconf Module
by fate_noreply＠suse.de 13 Oct '13

13 Oct '13

Feature added by: Lars Vogdt (lrupp) Feature #311338, revision 1 Title: YaST debconf Module openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Lars Vogdt (lrupp) Partner organization: openSUSE.org Description: Currently, people installing RPM packages have no opportunity to configure the installed applications afterwards with openSUSE Tools - if there's no specialized YaST module. This is a disadvantage comparing to Debians debconf system, allowing packagers (and therefor endusers) asking the user certain configuration questions after installation. Goals * A first part will be a GUI reading currently availble debconf templates and displaying them as expected. Please have a look at the debconf specifications for this. * If this proof of concept works, there's a need for support of such templates in RPM. We need a general policy describing how RPM packagers can include such template files in their packages. This would give openSUSE the great benefit of helping Debian people to migrate to openSUSE - and (more important) allows packagers to allow users customizing their installation without writing special YaST modules. Scope Remember that debconf doesn't cover all configuration aspects of any application. It should be enough to ask some general informations so that an application is ready for usage afterwards. A fine granulary configuration should been done by hand - or the according YaST module. Related technologies Tools that interact : * libzypp * mod_ui (YaST) * rpm Typical use case In the end, a user should be able to install a package like MySQL - and configure main parts of his new application using the YaST debconf module. Also think about packages for applications using a database, such as web based applications like horde, moodle and so on - currently, the user has to create the needed database manually. The YaST debconf module could ask for the location of the database server, the database name, the username, ... - and use this informations to set everything up so a user can login to his application right afterwards. Business case (Partner benefit): openSUSE.org: debconf is a software utility for performing system-wide configuration tasks on Unix-like operating systems. It is developed for the Debian GNU/Linux distribution, and is closely integrated with Debian's package management system, dpkg. When packages are being installed, debconf asks the user questions which determine the contents of the system-wide configuration files associated with that package. After package installation, it is possible to go back and change the configuration of a package by using the dpkg-reconfigure program, or another program such as Synaptic. The design of debconf allows for front-ends for answering configuration questions to be added in a modular way, and there exist several, such as one for dialog, other for readline, one for editor, one for KDE, one for GNOME [1], a Python front-end API, etc. There are two differnent goals for openSUSE: * Add some kind of "debconf" support to RPM * Create a YaST Module as front-end -- openSUSE Feature: https://features.opensuse.org/311338

1 3

[New: openFATE 310455] list packages that trigger build
by fate_noreply＠suse.de 08 Oct '13

08 Oct '13

Feature added by: William Brenneman (eocrates) Feature #310455, revision 1 Title: list packages that trigger build Buildservice: Unconfirmed Priority Requester: Desirable Requested by: William Brenneman (eocrates) Description: I have packages that use the openSUSE_Factory repo, and periodically a required package will be updated in the repository that triggers my packages to be rebuilt. Suggection: list what package (and version # => version #) in Commit History of my package that triggered my package to rebuild. -- openSUSE Feature: https://features.opensuse.org/310455

1 10

[New: openFATE 312816] Continuous YaST Testing in Jenkins
by fate_noreply＠suse.de 04 Oct '13

04 Oct '13

Feature added by: Lukas Ocilka (locilka) Feature #312816, revision 1 Title: Continuous YaST Testing in Jenkins Hackweek VII: Unconfirmed Priority Requester: Important Requested by: Lukas Ocilka (locilka) Partner organization: openSUSE.org Description: Continuous testing in Jenkins is widely used by several projects, such as: libzypp, slms, studio... to find issues ASAP, but YaST still lacks this possibility. Jenkins URL: http://river.suse.de/ More info on the subject can be found at this thread: http://lists.opensuse.org/yast-devel/2011-06/msg00096.html -- openSUSE Feature: https://features.opensuse.org/312816

1 1

[New: openFATE 309679] YaSTroid
by fate_noreply＠suse.de 04 Oct '13

04 Oct '13

Feature added by: Jared Allen (jpallen) Feature #309679, revision 1 Title: YaSTroid Requested by: Jared Allen (jpallen) Description: YaSTroid - An Android phone application to manage your SLES server using the WebYaST back-end. -- openSUSE Feature: https://features.opensuse.org/309679

1 14

[New: openFATE 309768] Blobec: Git with GPG on FTP
by fate_noreply＠suse.de 04 Oct '13

04 Oct '13

Feature added by: Martin Vidner (mvidner) Feature #309768, revision 1 Title: Blobec: Git with GPG on FTP Requested by: Martin Vidner (mvidner) Description: Blobec is a tool to store my private information (diary, calendar) on the Net to increase its availability and redundance. * To preserve privacy it needs to be encrypted → GPG. * I want it to be versioned, with easy merging of diverged copies → Git. * The publishing part works with what my current ISP provides → FTP (with SSL). I am implementing it in Ruby, with cURL. -- openSUSE Feature: https://features.opensuse.org/309768

1 4

[New: openFATE 312825] Objects in YCP (YaST)
by fate_noreply＠suse.de 04 Oct '13

04 Oct '13

Feature added by: Martin Vidner (mvidner) Feature #312825, revision 1 Title: Objects in YCP (YaST) Hackweek VII: Unconfirmed Priority Requester: Important Requested by: Martin Vidner (mvidner) Partner organization: openSUSE.org Description: As I am thinking about refactoring the network code, not having objects in YCP is a pain. The twist is, I don't want to add YCP objects but use Ruby objects. (We can already use Perl objects, yast2-storage does it, but it's limited.) Here's sample code to show how it could look, modeled after http://www.ruby-doc.org/stdlib-1.8.7/libdoc/uri/rdoc/classes/URI.html { import "Assert"; // Yes, you can! (also in SP2) // http://svn.opensuse.org/viewvc/yast/trunk/yast2/library/modules/Assert.ycp?… // Original Ruby code: // require 'uri' import $[ "what": "uri", "language": "ruby", "namespaces": ["URI", "URI::HTTP"] ]; /* The above complicated syntax enables - loading modules from elsewhere than /usr/share/YaST2/modules - loading YCP namespaces (Ruby modules (classes)) named otherwise than the file they are in, without needing to annotate them with TYPEINFO (like perl-bindings/pluglib-bindings do) */ // uri = URI.parse("http://www.ruby-lang.org/") any uri = URI::parse("http://www.ruby-lang.org/"); // [1] // assert_equal "http", uri.scheme Assert::Equal("http", uri->scheme()); // newuri = URI::HTTP.build( {:host => 'www.example.com', :path => '/foo/bar'}) any newuri = URI::HTTP::build($[ `host: "www.example.com", `path: "/foo/bar"]); // assert_equal "http://www.example.com/foo/bar", newuri.request_uri Assert::Equal ("http://www.example.com/foo/bar", newuri->request_uri()); } Formally, whereas now YCP has NAMESPACE :: IDENTIFIER ( PARAMS ) which calls a function (a module/class method in Ruby, a class method in Perl), we add EXPRESSION -> IDENTIFIER ( PARAMS ) which calls a method (an instance method in Ruby. [1] "any" is a lie, the type is actually a distinct one, called YCPExternal in C++. We could use "extern" which is currently an unused reserved word in YCP. But URIs are not my target. I am aiming for { any eth = SUSE::Ifcfg::new("eth0"); any br = SUSE::Ifcfg::Bridge::new("br0"); br->startmode(`auto); br->add(eth); /* br->add will also set: eth->bootproto(`none); eth->startmode(br->startmode()); */ any tap = SUSE::Ifcfg::Tap::new("tap0")->tunnel_set_owner("tux"); br->add(tap); foreach(any i, [br, tap, eth], { i->save(); }); } if (you->are_interested()) { you->please()->tell(martin); } -- openSUSE Feature: https://features.opensuse.org/312825

1 3

[New: openFATE 314535] More complete theming
by fate_noreply＠suse.de 25 Sep '13

25 Sep '13

Feature added by: Gavin S (gav616) Feature #314535, revision 1 Title: More complete theming openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Gavin S (gav616) Partner organization: openSUSE.org Description: By default add a very few extra themes, maybe one dark one medium shaded. Only add tried and tested themes that are inoffensive, subtle and bug free. Add a more complete default icons in the home folder e.g. http://i.imgur.com/CKyKz.png Business case (Partner benefit): openSUSE.org: Adds a more complete feeling to the distribution, light themes and such don't work for some people. The icons in the home folder would be easier to spot what you need to click, and it looks nicer. -- openSUSE Feature: https://features.opensuse.org/314535

1 10