March 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 536564] New: Packages creating user accounts do not select UID
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

http://bugzilla.novell.com/show_bug.cgi?id=536564 Summary: Packages creating user accounts do not select UID Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Some packages, such as openssh, do explicitly specify a UID/GID when creating its users/groups: /usr/sbin/groupadd -g 65 -o -r sshd 2>/dev/null || :; On the other hand, the hal package does not: /usr/sbin/groupadd -r haldaemon 2>/dev/null || : So, which is correct? Should not hal also use a fixed ID? There are many packages belonging to the latter category. -- 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 8

[Bug 518238] New: openSSH chroot security settings faulty
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

http://bugzilla.novell.com/show_bug.cgi?id=518238 Summary: openSSH chroot security settings faulty Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: marcus(a)swedcore.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11 Whenever i tried to setup a chroot environment with OpenSSH the security settings for the user folder must be root or OpenSSH doesn't work, the only solution for now is to either create subfolders in the users chroot folder where the user can have write permissions or land them one step up in the hierarchy and thus making them see other chroot folder which is not good. I followed this Wiki page to the letter: http://en.opensuse.org/Openssh#SFTP_chroot_with_ChrootDirectory I have Swedish community users trying to set this up to with same result as me. This thread takes up the same issue: http://marc.info/?l=openssh-unix-dev&m=122640731518850&w=2 But the solution mentioned there is not acceptable because as it stats on the Wiki you make one folder the chroot folder and then mapping the users home folder relative to the chroot folder, in this scenario the users should get write permissions to his own folder, but that is not possible, thus breaking the functionality intended. So the question is, is this a bug or is it designed to act like this? Reproducible: Always Steps to Reproduce: Done accordingly to this wiki entry: http://en.opensuse.org/OpenSSH Actual Results: Gets a read only home folder root Expected Results: Getting a writable home folder, where they can create on folder and upload files directly to the root of their home folder. -- 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 6

[Bug 530885] New: sshd fails to honour /etc/nologin presence when ssh keys used during login
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

http://bugzilla.novell.com/show_bug.cgi?id=530885 Summary: sshd fails to honour /etc/nologin presence when ssh keys used during login Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: liam.gretton(a)leicester.ac.uk QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 With the pam module pam_nologin in use, all non-root logins are supposed to be prevented if the file /etc/nologin exists. SSH fails to prevent user logins if /etc/nologin exists and the user authenticates with a key. Authentications with a password are successfully prevented, as expected. Reproducible: Always Steps to Reproduce: 1. Add pam_nologin to /etc/pam.d/login: auth requisite pam_nologin.so 2. Create /etc/nologin 3. Log in via SSH with a password. Login will be correctly prevented. 4. Log in via SSH with a key. Login is successful. Actual Results: SSH login with a key is not prevented by pam_nologin. Expected Results: SSH login with a key should be prevented by pam_nologin when /etc/nologin is present. openssh-5.1p1-40.15 pam-1.0.2-13.4 -- 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 12

[Bug 506831] New: /etc/init.d/sshd: incorrect usage of daemonstartproc ?
by bugzilla_noreply＠novell.com 26 Dec '19

26 Dec '19

http://bugzilla.novell.com/show_bug.cgi?id=506831 Summary: /etc/init.d/sshd: incorrect usage of daemonstartproc ? Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: anicka(a)novell.com ReportedBy: puzel(a)novell.com QAContact: qa(a)suse.de Found By: Development # /etc/init.d/sshd restart Shutting down SSH daemon Starting SSH daemonstartproc: option -p does not work in force mode sshd daemon seems to work OK, though. reproducible: always -- 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 2

[Bug 536505] New: rrdtool graph has some problems with vertical auto-scaling
by bugzilla_noreply＠novell.com 09 Dec '19

09 Dec '19

http://bugzilla.novell.com/show_bug.cgi?id=536505 Summary: rrdtool graph has some problems with vertical auto-scaling Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: SLES 10 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: qa(a)suse.de Found By: --- Created an attachment (id=316589) --> (http://bugzilla.novell.com/attachment.cgi?id=316589) Example with --rigid: No y scale displayed User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090410 SUSE/1.1.16-1.1.2 SeaMonkey/1.1.16 (Found in current version of SLES10 SP2, rrdtool-1.2.12-13.2) Specific values (like all between 17.7 and 17.8) cause rrdtool's graph to autoscale the values at a range of 10 to 20, making actual variations practically invisible. There are other intervals where similar problems arise, like [42.0:42.2] where the scale is [40:50]. The --alt-autoscale improves the scaling, but has a problem with not enough numeric labels for the y-axis being shown, just as --rigid does. The author of the tool said the current version is much better regarding those issues. Reproducible: Sometimes Steps to Reproduce: 1. Create graphs with automatic scaling where the values vary a little bit around some undetermined value Actual Results: Some graphs are not good enough to show the variations. Expected Results: The vertical scale should respect the range of values more that it currently does. -- 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 7

[Bug 500134] New: on checksumm errors yast2 software management produces non-informative message
by bugzilla_noreply＠novell.com 14 Feb '19

14 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=500134 Summary: on checksumm errors yast2 software management produces non-informative message Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: grey-olli(a)ya.ru QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=289482) --> (http://bugzilla.novell.com/attachment.cgi?id=289482) 1st time the problem found User-Agent: Opera/9.64 (X11; Linux i686; U; en) Presto/2.1.1 On start of software management repository refresh is started. If checksumm is wrong for a file related to the repository the resulting message doesn't inform to which repository it relates. So if you've a few repositories installed the message is non-informative. Reproducible: Always Expected Results: Should at least tell to which repository the problem relates. -- 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 536846] New: rebuild RPM DB automatically and silently when necessary
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=536846 Summary: rebuild RPM DB automatically and silently when necessary Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: urwald(a)gmx-topmail.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-2.4 Firefox/3.5.2 Sometimes, the RPM database is broken. Than, when you try to install packages with YaST, you get some complicate error messages like Subprocess failed. Error: RPM fallido: error: db4 error(-30987) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found error: error(-30987) setting "System/Libraries" records from Group index error: db4 error(-30987) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found error: error(-30987) getting "System/Libraries" records from Group index or Subprocess failed. Error: RPM fallido: error: db4 error(-30987) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found error: error(-30987) getting "" records from Requireversion index Executing 'rpm --rebuilddb' fixes the problem, but that's not user friendly. It would be great if libzypper could the this automatically when it notices that there are problems with the RPM database. Reproducible: Always -- 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 4

[Bug 546594] New: zypper ignores lock while update
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=546594 Summary: zypper ignores lock while update Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 8 Platform: All OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: lmuelle(a)novell.com QAContact: qa(a)suse.de Found By: --- zypper ignores existing locks while perfoming an upgrade. -- 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 5

[Bug 509945] New: Enforce packaging of static libraries by rpmlint check
by bugzilla_noreply＠novell.com 09 Dec '17

09 Dec '17

http://bugzilla.novell.com/show_bug.cgi?id=509945 Summary: Enforce packaging of static libraries by rpmlint check Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: dmueller(a)novell.com ReportedBy: prusnak(a)novell.com QAContact: qa(a)suse.de CC: ro(a)novell.com, mrueckert(a)novell.com, crrodriguez(a)novell.com Found By: Development We are trying to adopt the static libraries packaging scheme described on http://en.opensuse.org/Packaging/Guidelines#Packaging_Static_Libraries By adding rpmlint check we will enforce the correct packaging. rpmlint should check whether the package contains *.{a,la} files and perform these steps: a) package contains *.la files, does not contain *.a files -> throw error suggesting the packager to remove *.la files in %install phase b) package contains only *.la and *.a files -> check if the name ends with "-devel-static", throw error otherwise, suggesting the rename c) package contains *.la, *.a files AND *.so files (and probably some includes) -> check if the name ends with "-devel" AND package also provides "-devel-static" symbol, throw error otherwise, suggesting the addition of symbol -> also point out that packager has to be sure that static libraries are absolutely needed in the system. If not the package should be built with --disable-static and *.la files removed in %install phase -- 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 8

[Bug 584970] New: Yast gives error -4017 when trying to partition using LVM
by bugzilla_noreply＠novell.com 22 Dec '16

22 Dec '16

http://bugzilla.novell.com/show_bug.cgi?id=584970 http://bugzilla.novell.com/show_bug.cgi?id=584970#c0 Summary: Yast gives error -4017 when trying to partition using LVM Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: HP OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: p.c.manning(a)swansea.ac.uk QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.89 Safari/532.5 Hardware: HP ML115 with E200 SmartArray card. 4 250GB drives built as raid 5. Use OpenSUSE DVD installer, select LVM partitioning scheme, installation dies when preparing disks with error -4017 Reproducible: Always Steps to Reproduce: 1.Use OpenSUSE 11.2 DVD 64bit to Install OS 2.Get to partitioning scheme - select LVM 3.Continue through installation, installation dies at preparing disks stage Actual Results: Retried this with text mode installer which enabled me to switch to a working shell console, I could see that the installer had created a boot partition, an LVM partition and an LVM group. But had failed to create any logical volumes Expected Results: A properly partitioned disk! http://forums.opensuse.org/install-boot-login/433990-yast-partitioning-erro… Workround was to partition manually via a shell console. -- 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 4