May 2010 - 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 308958] Reduce size of the Minimal Install
by fate_noreply＠suse.de 22 Sep '13

22 Sep '13

Feature added by: Jan Engelhardt (jengelh) Feature #308958, revision 1 Title: Reduce size of the Minimal Install openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Jan Engelhardt (jengelh) Partner organization: openSUSE.org Description: IMHO, the text-mode minimal install without X and anything still comes with "too many" packages. I use the minimal selection whenever I need to set up a new, clean, system, as installing onto a Minimal is faster than cherry-picking every single package for deletion from a Medium or Maximum selection. This includes, but is not limited to: * documentation to magic things happening in the background: PolicyKit-doc, readline-doc * other documentation that I've probably read already; bash-doc, perl-doc * archaic systems: yp-tools ypbind yast2-nis-client * packages serving no purpose: perl-Business-ISBN (heck, not even yast needs that), perl-GD * things that make my command line slow: command-not-found scout * it so happens that eventually I can throw out the entire python stack, and the remaining Xorg libs * printing, sound, bootsplash I have here a dump file between the initial minimal install and a tailored system - some things have been removed that I would leave on the minimal install list however (e.g. yast2-sudo). So the raw contents of the diff file is [mh, FATE has no attachments - see https://bugzilla.novell.com/show_bug.cgi?id=577791 ] Business case (Partner benefit): openSUSE.org: Everytime a new system is bootstrapped, I have to (="want to") remove these first because they will never be needed -- if they will, I can reinstall them later, or pick a larger "non-minimal" text mode from yast. -- openSUSE Feature: https://features.opensuse.org/308958

1 3

[openFATE 306974] Additional columns in software management
by fate_noreply＠suse.de 03 Sep '13

03 Sep '13

Feature added by: Todd R (TheBlackCat) Feature #306974, revision 1 Title: Additional columns in software management openSUSE-11.2: Unconfirmed Priority Requester: Desirable openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Todd R (theblackcat) Description: It would be nice if there were a few additional columns in the software management interface. One specific column I am interested in would be an architecture column, to show you the architecture of an installed package or the architecture the package would have if you were to install it. The other column would show the repository of the package, either the repository of an installed package or the repository the package would be downloaded from if you were to install it. -- openSUSE Feature: https://features.opensuse.org/306974

1 6

[openFATE 306598] Sync Tomboy/Tasque with Evernote
by fate_noreply＠suse.de 13 Aug '13

13 Aug '13

Feature added by: Joe Brockmeier (jbrockmeier) Feature #306598, revision 1 Title: Sync Tomboy/Tasque with Evernote Requested by: Joe Brockmeier (jbrockmeier) Description: Evernote is a pretty cool service, but it doesn't have a Linux client. I'd like to be able to sync my Tomboy notes with Evernote and retrieve them from another machine. Same with Tasque -- I'd like to be able to save a to-do list to Evernote from tasque so I could use a mobile Evernote client to look up my to-dos. -- openSUSE Feature: https://features.opensuse.org/306598

1 4

[openFATE 306588] improve on software search
by fate_noreply＠suse.de 13 Aug '13

13 Aug '13

Feature added by: Juergen Weigert (jnweiger) Feature #306588, revision 1 Title: improve on software search Requested by: Juergen Weigert (jnweiger) Description: software.o.o/search is always a case insensitive substring search. I'd like to hack into the system and add - optional case sensitivity,- exact package name search- regexp search This is an opportunity to learn ruby on rails for me. Any takers, who want to coach me, especially with Rails welcome. -- openSUSE Feature: https://features.opensuse.org/306588

1 6

[openFate 305705] Types of installation
by fate_noreply＠suse.de 13 Aug '13

13 Aug '13

Feature added by: Agustin Chavarria (dj_ubun_1) Feature #305705, revision 1, last change by Title: Types of installation openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Agustin Chavarria (dj_ubun_1) Partner organization: openSUSE.org Description: would be good, that at the time of installation opensuse, ask what you want to install, like a template, without having to go to edit to add software. An example for that will be: Multimedia install Full install server install developer install -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305705

1 12

[New: openFATE 309614] Activator application for SUSE Studio created appliances
by fate_noreply＠suse.de 12 Aug '13

12 Aug '13

Feature added by: Christian Hueller (chuller) Feature #309614, revision 1 Title: Activator application for SUSE Studio created appliances Requested by: Christian Hueller (chuller) Partner organization: openSUSE.org Description: Basically the idea is simple: Create an application (GUI would be nice) that can 'activate' a previously SUSE Studio built appliance. 'Activate' stands here for things like o register appliance with Novell or ISV o create users and set passwords o do other security relevant things like creating keys or add own proprietary material After the activation it would be awesome to also integrate some deployment functionality to burn isos directly to CD after activation or copy disk images to a usb stick How it might work: Basically the appliance filesystem needs to be accessed in order to modify the appliance accordingly. This could be done through either loop mounting the image or by booting it inside some hypervisor. Loop mounting requires root access, so booting might be the better solution, we only need to take care the kiwi firstboot processes do net get triggered in this activation boot. Possible features: o interaction with studio itself using its API (no manual download of the appliance e.g.) Use Case: The use case is pretty clear as this would cover the gap between the simple creation of an appliance and the frist booting of it on your hardware: The user downloads a SLES11 appliance with the 'activator', then sets the root password and enters the SLES11 registration key. Now the update repositories get added to the appliance and the password is changed without being accessible on the online server. Business case (Partner benefit): openSUSE.org: This would be a great usability improvement to the whole stusio experienc -- openSUSE Feature: https://features.opensuse.org/309614

1 2

[New: openFATE 309314] Add Factory Snapshots to SUSE Studio
by fate_noreply＠suse.de 12 Aug '13

12 Aug '13

Feature added by: James Mason (bear454) Feature #309314, revision 1 Title: Add Factory Snapshots to SUSE Studio openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: James Mason (bear454) Description: SUSE Studio has base images of the current openSUSE release to use as a basis for construction custom versions or specialized appliances. It would benefit the products of those appliances to have early access to Factory snapshots (Milestones, Release Candidates) in order to be able to have updates ready at the time of release. This would also allow beta testers the opportunity to create more robust test cases based on specific configuration choices, potentially resulting in more rapid, fine grained testing of the snapshots. -- openSUSE Feature: https://features.opensuse.org/309314

1 2

[openFATE 306606] GUI client for SUSE Studio
by fate_noreply＠suse.de 12 Aug '13

12 Aug '13

Feature added by: Cornelius Schumacher (cschum) Feature #306606, revision 1 Title: GUI client for SUSE Studio Requested by: Cornelius Schumacher (cschum) Description: SUSE Studio is a fantastic web app, but sometimes it would still be more convenient to have a native client, for example when dealing with lots of overlay files, or to manage writing downloaded appliances to physical media or running and controlling them in a virtual machine. The Studio API makes it possible to write a native client. -- openSUSE Feature: https://features.opensuse.org/306606

1 7