November 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 891268] New: Squid permissions and setbadness handling
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=891268 https://bugzilla.novell.com/show_bug.cgi?id=891268#c0 Summary: Squid permissions and setbadness handling Classification: openSUSE Product: openSUSE Factory Version: 201407* Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: boris(a)steki.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Squid proxy server now has correct permissions handling and as such in this moment uses setBadness in squid-rpmlintrc, so to be able to push this change into Factory we need it to be resolved with security team. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 24

[Bug 578053] New: postgresql-plperl looks for libperl.so in the wrong place
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=578053 http://bugzilla.novell.com/show_bug.cgi?id=578053#c0 Summary: postgresql-plperl looks for libperl.so in the wrong place Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: eggyknap(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/532.8 (KHTML, like Gecko) Chrome/4.0.299.0 Safari/532.8 On a completely new openSUSE 11.3 machine, I installed the postgresql-server, postgresql, and postgresql-plperl packages. After starting PostgreSQL and letting it initialize a new database, I sudo-d to the postgres user, and tried to add the PL/Perl language, as follows, with the error below: postgres@linux-e16r:~> createlang plperl createlang: language installation failed: ERROR: could not load library "/usr/lib/postgresql/plperl.so": libperl.so: cannot open shared object file: No such file or directory libperl.so lives in /usr/lib/perl5/5.10.0/i586-linux-thread-multi/CORE/libperl.so. Creating a symlink at /usr/lib/libperl.so to the installed libperl.so binary works around the problem. This also exists in at least one of the 10.x versions, though I don't have access to the servers to know the precise version(s) As a secondary note, the description of the postgresql-plperl package, at least as it appears in YaST2, says the package also includes PL/Tcl and PL/Python. This is incorrect. Thirdly, the documentation also claims "PostgreSQL also offers the builtin procedural language PL/SQL". This is also incorrect -- PL/SQL is an Oracle-specific language. PostgreSQL offers PL/pgSQL, which fact might be worth noting in the PL/Perl documentation, or it might not. Reproducible: Always Steps to Reproduce: 1.install postgresql, postgresql-server, and postgresql-plperl 2.start postgresql (/etc/init.d/postgresql start) 3.become the postgres user (sudo su - postgres) 4.create the plperl language in the default database: createlang plperl Actual Results: # createlang plperl createlang: language installation failed: ERROR: could not load library "/usr/lib/postgresql/plperl.so": libperl.so: cannot open shared object file: No such file or directory Expected Results: createlang should have no output, and a 0 exit status I realize this is a packaging bug, and likely not something distributed by Novell directly. I saw nowhere else to file the bug. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 17

[Bug 849715] New: Chrome has been updated to 30.0.1599.114
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=849715 https://bugzilla.novell.com/show_bug.cgi?id=849715#c0 Summary: Chrome has been updated to 30.0.1599.114 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tittiatcoke(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.2 Safari/537.36 SUSE/32.0.1700.2 Chrome has been updated to 30.0.1599.114 for Windows, Mac, Linux and Chrome Frame. Security Fixes and Rewards Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. This update includes 5 security fixes. Below, we highlight fixes that were either contributed by external researchers or particularly interesting. Please see the Chromium security page for more information. [$1000][292422] High CVE-2013-2925: Use after free in XHR. Credit to Atte Kettunen of OUSPG. [$2000][294456] High CVE-2013-2926: Use after free in editing. Credit to cloudfuzzer. [$2000][297478] High CVE-2013-2927: Use after free in forms. Credit to cloudfuzzer. As usual, our ongoing internal security work responsible for a wide range of fixes: [305790] CVE-2013-2928: Various fixes from internal audits, fuzzing and other initiatives. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 16

[Bug 551014] New: one click install: error ccoured while initializing the software repository
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=551014 Summary: one click install: error ccoured while initializing the software repository Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: Other OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: jsrain(a)novell.com Found By: Beta-Customer Created an attachment (id=324701) --> (http://bugzilla.novell.com/attachment.cgi?id=324701) y2logs (11.2 repo from today, probably near RC2) I tried to install YaBSC from the openSUSE:Tools repo using one click install. After entering the root password, YaST showed an error dialog: An error ccoured while initializing the software repository. Details: Try again? [Ja] [Nein] (= Yes / No) Yes, the line after "Details:" was really empty. Therefore this bug has two parts: - the missing information about details in the error dialog - maybe the failure itsself is also a bug The last lines from y2log when the error dialog was open: 2009-10-29 15:48:16 <1> geeko(26435) [zypp] RepoManager.cc(init_knownRepositories):557 end construct known repos 2009-10-29 15:48:16 <3> geeko(26435) [Pkg] Source_Create.cc(RepositoryAdd):449 alias openSUSE:Tools already exists [That's probably the disabled 11.1 version of the openSUSE:tools repo] 2009-10-29 15:48:16 <1> geeko(26435) [Pkg] OneClickInstallWorkerFunctions.ycp:113 Pkg Builtin called: SourceRefreshNow 2009-10-29 15:48:16 <3> geeko(26435) [Interpreter] OneClickInstallWorkerFunctions.ycp:113 Parameter 1 is nil, Integer is required 2009-10-29 15:48:16 <1> geeko(26435) [Pkg] OneClickInstallWorkerFunctions.ycp:116 Pkg Builtin called: LastError 2009-10-29 15:48:16 <1> geeko(26435) [ui] YPushButton.cc(setFunctionKey):183 Guessing button role YOKButton for YPushButton "Ja" at 0x18fb1b8 from function key F10 2009-10-29 15:48:16 <1> geeko(26435) [ui] YPushButton.cc(setFunctionKey):183 Guessing button role YCancelButton for YPushButton "Nein" at 0x198aac 8 from function key F9 The full y2logs are attached. Search for [cb] in y2log - I have marked when the error dialog popped up. BTW: After answering the dialog with yes (= try again) and confirming the repo details, the installation worked. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 630434] New: Server refuses to boot, while used iSCSI based non "/" file system is not available.
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=630434 http://bugzilla.novell.com/show_bug.cgi?id=630434#c0 Summary: Server refuses to boot, while used iSCSI based non "/" file system is not available. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: DOlsson(a)WEB.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.1 Firefox/3.6.6 On our SLES 11 GM based "mirror" server (running as a virtual XEN guest), we are using iSCSI to attach to our NAS holding the "/data" file system, whereas all other file systems (/, /boot, /var, /home) are placed on local disk. When rebooting the server, it refuses to boot correctly, while it is not able to "fsck" the "/data" file system -- The system stops in "(repair filesystem) #" mode (after having entered the "root" password). Using the "nofail" option for the "/data" file system helps to get the system to reboot correctly, but in this case the "/data" file system is neither being checked nor mounted during the system startup, which therefore -- once again -- makes the system unusable! Using the "nofail" option is part of the "solution" listed in the SLES 11 SP1 documentation, but since the system is unusable, this is *not* the solution to the problem. The problem is that the "mkinitrd" is and the boot scripts are not capable of handling iSCSI attached file systems correctly. The correct way of handling iSCSI attached devices are: - All iSCSI devices having the "onboot" set as node startup setting must be attached during the "initrd" boot sequence (i.e. by "boot.open-iscsi") -- and this *independent* of whether the "/" (root) file system is attached via iSCSI or not, - All iSCSI devices having the "automatic" set as node startup setting need to be attached during the normal booting sequence (i.e. by "open-iscsi"), - All iSCSI devices having the "manual" set as node startup setting should be left alone. Using such a attaching schema will ensure that a server is capable of being booted with all its iSCSI file systems being attached, checked and mounted. Reproducible: Always Steps to Reproduce: 1a. Setup an iSCSI device and mount it e.g. as "/home" (no changes to "/etc/fstab"). 2a. Reboot the system 3a. System fails to boot, while "/home" is not available. 1b. Setup an iSCSI device and mount it e.g. as "/home", and add the "nofail" option in "/etc/fstab" to the "/home" mount point. 2b. Reboot system. 3b. System boots, but "/home" is neither checked nor mounted! Actual Results: When using iSCSI devices for non root file systems - the system is not able to boot, when the file system on the iSCSI device is listed in "/etc/fstab" as a file system that should be mounted or - the system boots boots, when the file system on the iSCSI device has been marked with "nofail" in "/etc/fstab", but the file is neither being checked nor it is being mounted. Expected Results: System boots with all file systems listed in "/etc/fstab" being checked and mounted independently of whether they are on local or iSCSI attached disks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 91

[Bug 832519] New: zypper --sort-by-priority does not sort numerically
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=832519 https://bugzilla.novell.com/show_bug.cgi?id=832519#c0 Summary: zypper --sort-by-priority does not sort numerically Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: alanprescott(a)yahoo.co.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 In list repos option with zypper, using the -P|--sort-by-priority does an alpha sort rather than a numeric sort - i.e. priority 21 is sorted before 3,4,5 etc. Reproducible: Always Steps to Reproduce: 1. run zypper lr -Pe file.repo ; less file.repo 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 710541] New: Zypper gives no information about where source-install downloads files
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=710541 https://bugzilla.novell.com/show_bug.cgi?id=710541#c0 Summary: Zypper gives no information about where source-install downloads files Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)damienradtke.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.107 Safari/535.1 When installing a package's source using "zypper source-install", no information can be found about where the source is actually downloaded to. "zypper help source-install" doesn't help, nor does "man zypper". The target location is /usr/src/packages/SOURCES, but those unfamiliar with RPM practices won't know that. Please provide a message, such as in the help text for source-install, that points the user to the directory the source was downloaded to. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 637791] New: libzypp log: wrong error message if gpg not installed
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637791 https://bugzilla.novell.com/show_bug.cgi?id=637791#c0 Summary: libzypp log: wrong error message if gpg not installed Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: dheidler(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- the error message tells you, that the files in the repository are not existing, but the real issue is, that gpg is not installed we should check for gpg installed and greate a more expressive message -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 755383] New: VUL-0: python: hash collision DoS
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=755383 https://bugzilla.novell.com/show_bug.cgi?id=755383#c0 Summary: VUL-0: python: hash collision DoS Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Normal Priority: P5 - None Component: Other AssignedTo: jmatejek(a)suse.com ReportedBy: mvyskocil(a)suse.com QAContact: security-team(a)suse.de CC: lnussel(a)suse.com, security-team(a)suse.de Depends on: 751718 Found By: Other Blocker: --- +++ This bug was initially created as a clone of Bug #751718 +++ Your friendly security team received the following report via oss-security. Please respond ASAP. The issue is public. CVE-2012-1150 python dictionaries are prone to hash table collision attacks. Web services for example might store parameters of a GET or POST request in a dictionary. An attacker may use this to cause high CPU load http://bugs.python.org/issue13703 http://seclists.org/fulldisclosure/2011/Dec/477 http://www.ocert.org/advisories/ocert-2011-003.html https://bugzilla.redhat.com/show_bug.cgi?id=750555 --------------------------- This one is for python3 for openSUSE 12.1 only. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 853725] New: Unable to set proxy in Yast2
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=853725 https://bugzilla.novell.com/show_bug.cgi?id=853725#c0 Summary: Unable to set proxy in Yast2 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: linxt(a)comcast.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 In OS 13.1-GA I am unable to set the proxy in Yast. In all previous versions setting proxy via Yast2 worked successfully. After entering valid proxy settings and opening the correct port on the firewall (port 17171) (also via Yast2), when I click on the "Test Proxy Settings" it returns an error popup message (see attached screenshot). I have verified the proxy settings and credentials with another distro (fedora) so know they are working. Reproducible: Always Steps to Reproduce: 1. In "Yast2 > Network Services > Proxy", enter the proxy IP information and credentials 2. Press "Test Proxy Settings" 3. An error message popup displays failure (see attached screenshot) Actual Results: Failure to set proxy data. Yast2 logs attached Expected Results: Proxy data to be accepted and test settings to show correct connection data. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14