August 2009 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 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 529135] New: openvas-client-2.0.1-1.33: missing call to close
by bugzilla_noreply＠novell.com 19 Aug '16

19 Aug '16

http://bugzilla.novell.com/show_bug.cgi?id=529135 Summary: openvas-client-2.0.1-1.33: missing call to close Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de Found By: --- I just had a look at factory package openvas-client-2.0.1-1.33 For source code file openvas-client-2.0.1/nessus/comm.c around line 870 is the source code for the function comm_send_file. I notice the following line of code fd = open(fname, O_RDONLY); but I notice that close is only called on failure. Suggest add a call to close at the end of the routine, for the return success case. Like network_gets(context->socket, buff, sizeof(buff) - 1); fclose( fd); return 0; -- 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 3

[Bug 502531] New: bsd-games-2.17-81.44: undefined code
by bugzilla_noreply＠novell.com 19 Aug '16

19 Aug '16

http://bugzilla.novell.com/show_bug.cgi?id=502531 Summary: bsd-games-2.17-81.44: undefined code Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de Found By: --- I just tried to build Factory package bsd-games-2.17-81.44 and the build said monop/cards.c:138: warning: operation on "dp->last_card" may be undefined The source code is dp->last_card = ++(dp->last_card) % dp->num_cards; I agree with the compiler. Better code would be dp->last_card = (dp->last_card + 1) % dp->num_cards; -- 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 3

[Bug 505546] New: Grub fails to write bootrecord on dmraid disk (GPT labeled)
by bugzilla_noreply＠novell.com 16 Aug '16

16 Aug '16

http://bugzilla.novell.com/show_bug.cgi?id=505546 User Winfrid.Tschiedel(a)ts.fujitsu.com added comment http://bugzilla.novell.com/show_bug.cgi?id=505546#c500322 Summary: Grub fails to write bootrecord on dmraid disk (GPT labeled) Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Winfrid.Tschiedel(a)ts.fujitsu.com QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=293215) --> (http://bugzilla.novell.com/attachment.cgi?id=293215) saved installation logs User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Tablet PC 1.7; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; MS-RTC LM 8; InfoPath.2) I tried to install openSUSE 11.2 Milestone 1 on Fujitsu Primergy RX220 ( Promise FastTrak TX 150 S4 ), one disk with RAID0, GPT labeled ( Same problem exists also on Fujitsu Primergy rx200s4 with ESB2 (LSI Firmware) and one disk RAID0. Installation works until the boot record should be written. In case of rx220 the boot record should be written to the root partition. Beside the error 22: No such partition also the MBR was destroyed. Reproducible: Always Steps to Reproduce: 1. Installed openSUSE 11.2 on fake raid with GPT Actual Results: No boot redord was written Expected Results: Correct operation, install a system which can be booted afterwards In the latest release of fedora 11 (Preview) almost everything works out of the box, which means only manual interaction for the following items is needed : mklabel gpt (no botton for writing new partition table!) mkinitrd on distribution is in error for details please read #500322 (bugzilla.redhat.com) I tried to write a new bootrecord with fedora 11 - which worked - but openSUSE 11.2 cannot handle this bootrecord - so chainloading failed . Next I tried to load the openSUSE boot menu with configfile /boot/grub/menu.lst So I could start openSUSE 11.2, but boot fails because root partition is not found. This seems to be similar to #500979 - with one difference that at that time (SLED 11) only the problem on ESB2 occurred. There is also a second difference, in the previous edition (openSUSE 11.1,SLED 11) there was a problem with GPT and dmraid, which ended up, that the RAID information was destroyed (please see #436825 ) -- 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 13

[Bug 535752] New: xsane crashed
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=535752 Summary: xsane crashed Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 6 Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: 80classics(a)gmail.com QAContact: qa(a)suse.de Found By: --- Created an attachment (id=316068) --> (http://bugzilla.novell.com/attachment.cgi?id=316068) xsane crashed User-Agent: Mozilla/5.0 (X11; U; Linux i686; it; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-2.4 Firefox/3.5.2 I've configured my HP Scanjet 3800 scanner using YAST. I've selected the right sane backend from YAST database and the configuration has been successfully saved. xsane has always crashed with the same error (more details below) Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 33

[Bug 534909] New: ipmitool-1.8.10-109.64: missing call to close
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=534909 Summary: ipmitool-1.8.10-109.64: missing call to close Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de Found By: --- I just had a look at factory package ipmitool-1.8.10-109.64 For source code file ipmitool-1.8.10/lib/ipmi_sdradd.c around line 340, function ipmi_sdr_read_records is the following code if ((fd = open(filename, O_RDONLY)) < 0) { but I fail to find any matching call to close. This looks like a resource leak to me. Suggest add call to close. -- 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 3