May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 934256] New: Passwords maintained by Filezilla are easily recovered in some cases
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=934256 Bug ID: 934256 Summary: Passwords maintained by Filezilla are easily recovered in some cases Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: Greg.Freemyer(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm testing with LaZagne: http://www.kitploit.com/2015/02/the-lazagne-project-recover-most-common.html Or in OBS @ home:gregfreemyer:Tools-for-forensic-boot-cd LaZagne Running LaZagne under my normal user account recovered one filezilla stored passwd. The amount of time taken was near instantaneous so I believe the password was simply decoded, not cracked in the sense of "John the ripper". The password was associated with a SFTP account, so it is a password I consider needing to be kept securely. I don't know if Filezilla simply handles passwords poorly or if it can be compiled differently to store passwords securely. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1135224] New: yast2-adsi crashes with "TypeError: Expected a string or unicode object" during auth
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1135224 Bug ID: 1135224 Summary: yast2-adsi crashes with "TypeError: Expected a string or unicode object" during auth Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: david.mulder(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- 2019-05-14 15:34:05 <3> linux-h7xz(14712) [Python] clients/adsi.py(<module>):57 Traceback (most recent call last): File "/usr/share/YaST2/clients/../include/adsi/wizards.py", line 11, in <lambda> 'adsi' : [(lambda lp, creds: ADSI(lp, creds).Show()), lp, creds], File "/usr/share/YaST2/clients/../include/adsi/dialogs.py", line 522, in Show self.conn = ConnectionSettings(self.creds, self.lp).Show() File "/usr/share/YaST2/clients/../include/adsi/dialogs.py", line 423, in Show ycred.Show(cred_valid) File "/usr/lib/python3.7/site-packages/adcommon-1.0-py3.7.egg/adcommon/creds.py", line 150, in Show got_creds = self.get_creds() File "/usr/lib/python3.7/site-packages/adcommon-1.0-py3.7.egg/adcommon/creds.py", line 182, in get_creds self.__delete_keyring() File "/usr/lib/python3.7/site-packages/adcommon-1.0-py3.7.egg/adcommon/creds.py", line 244, in __delete_keyring delete_password('adcommon', keyring_user) File "/usr/lib/python3.7/site-packages/keyring/core.py", line 69, in delete_password _keyring_backend.delete_password(service_name, username) File "/usr/lib/python3.7/site-packages/keyring/backends/SecretService.py", line 92, in delete_password for item in items: File "/usr/lib/python3.7/site-packages/secretstorage/collection.py", line 86, in search_items signature='a{ss}') File "/usr/lib/python3.7/site-packages/secretstorage/util.py", line 31, in function_out return function_in(*args, **kwargs) File "/usr/lib/python3.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python3.7/site-packages/dbus/connection.py", line 641, in call_blocking message.append(signature=signature, *args) TypeError: Expected a string or unicode object This happens when 'save creds' is unchecked, but no creds have been previously saved to the keychain. I None type is being passed into keyring.delete_password(). -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1135130] New: yast2-adsi authentication fails with "Failed to initialize ldap connection"
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1135130 Bug ID: 1135130 Summary: yast2-adsi authentication fails with "Failed to initialize ldap connection" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: david.mulder(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- adcommon/yldap.py(__ldap_connect):104 Failed to initialize ldap connection adsi/dialogs.py(cred_valid):421 Failed to initialize ldap connection The failure is actually in yast2-adcommon-python, in the kinit code. # kinit Administrator(a)FROGGY.SUSE.DE kinit: Credential cache directory /run/user/0/krb5cc does not exist while getting default ccache I can work around this by creating the /run/user/0 directory. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1133568] New: yast2-adcommon-python ldap doesn't correctly parse ldap urls for ldap.initialize()
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1133568 Bug ID: 1133568 Summary: yast2-adcommon-python ldap doesn't correctly parse ldap urls for ldap.initialize() Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: david.mulder(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Ldap urls with anything other than the scheme, host, and port crash with an LdapError and no message details. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1084864] New: YaST module names are too similar to some desktop environment configuration modules
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1084864 Bug ID: 1084864 Summary: YaST module names are too similar to some desktop environment configuration modules Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: noahadvs(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 763361 --> http://bugzilla.suse.com/attachment.cgi?id=763361&action=edit How it should look when fixed YaST, GNOME, KDE Plasma and Enlightenment all have configuration modules named "Fonts" and a YaST module with the same exact name shows up when searching for "fonts" in all 3 DEs. This is not currently too much of a problem for users because the YaST Fonts module uses an icon representing X11 instead of an icon representing fonts, but there's no way to tell the difference without the icon. This will also be a problem for me because I am working on a KDE Breeze theme for YaST and intend to change the icon of the YaST Fonts module to a proper fonts icon. Fixing this problem will require changes to the code of yast-control-center and changes to the .desktop files shown for all YaST modules. 1. Every Name field needs to be prefixed with "YaST " or something similar to show association with YaST. However, this will cause every module name shown in the YaST Control Center to also have that prefix, which doesn't look good. 2. GenericName can be the field that YaST Control Center uses for module names instead. For example, the Name field could be "YaST Fonts" and the GenericName field could be "Fonts". 3. The GenericName field is currently used as if it was the Comment field, so YaST Control Center needs to display the Comment field instead of the GenericName field for module descriptions. All descriptions in the .desktop files need to be moved to the Comment field. -- You are receiving this mail because: You are on the CC list for the bug.

2 41

[Bug 918028] New: no Grub Legacy shell history
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=918028 Bug ID: 918028 Summary: no Grub Legacy shell history Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- To reproduce: 1-login root on tty[1-6] on en_US installation 2-grub 3-find /boot/grub/stage1 4-keystroke <UP> Actual behavior: 1-^[[A appears at prompt Expected behavior: 1-find /boot/grub/stage1 appears at prompt Comments: 1-Shell cmdline history works as expected in 13.1, as in all previous openSUSE releases. 2-I recognized this problem many months ago, maybe as much as a year ago, but only just surmised it was almost certainly 13.2 and up Grub Legacy post-0.97-194.1.2 itself rather than having anything to do with kernel, framebuffer configuration, video mode, or files contained in target /boot/grub/. "Downgrading" to 13.1's 0.97-194.1.2 fixes 13.2 and Tumbleweed. 3-Nearly all my Grub stanzas include "splash=verbose vga=791 video=1024x768@60 3 " on cmdline. 4-All my openSUSE installations are on multiboot hardware (no VMs), with keyboards on PS/2 ports. 5-Plymouth is not installed in any of my openSUSE installations. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1012388] New: cmake should not set -Wl,--no-undefined for modules
by bugzilla_noreply＠novell.com 12 Mar '21

12 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1012388 Bug ID: 1012388 Summary: cmake should not set -Wl,--no-undefined for modules Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: asn(a)cryptomilk.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In the file /etc/rpm/macros.cmake -Wl,--no-undefined should not be set for CMAKE_MODULE_LINKER_FLAGS. As modules are loaded into other binaries they are allowed to have undefined functions. Normally the application loading them has the required library loaded. Please remove the flag for modules in openSUSE Leap, Tumbleweed and Factory. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1097006] New: dwz debuginfo splitting is one-thread and very very slow on packages which have too many libs
by bugzilla_noreply＠novell.com 10 Mar '21

10 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1097006 Bug ID: 1097006 Summary: dwz debuginfo splitting is one-thread and very very slow on packages which have too many libs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: pth(a)suse.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mliska(a)suse.cz Found By: --- Blocker: --- Obs generates dwz compression for all items at once to reduce space: [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_0x0100.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/adt_null.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_ed25519.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_gssapi.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_pam.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_socket.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/disks.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/client_ed25519.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/dialog_examples.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/auth_test_plugin.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_blackhole.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/file_key_management.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/example_key_management.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_connect.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_archive.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_example.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_federated.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_mroonga.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_oqgraph.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_federatedx.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_rocksdb.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_sphinx.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_spider.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/handlersocket.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/libdaemon_example.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/locales.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/ha_test_sql_discovery.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/metadata_lock_info.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/qa_auth_client.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/query_cache_info.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/mypluglib.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/qa_auth_interface.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/qa_auth_server.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/query_response_time.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/semisync_slave.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/sql_errlog.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/semisync_master.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/server_audit.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/sbin/mysqld [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/simple_password_check.so [ 209s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mariadb-10.2.15-0.x86_64/usr/lib64/mysql/plugin/wsrep_info.so [ 497s] /usr/lib/rpm/sepdebugcrcfix: Updated 80 CRC32s, 0 CRC32s did match. As you can see whole build took 209s while dwz split another 288s utilizing just one core. The -multifile mode tries to reduce the size even more, but question is if there are enough gains to justify the slowdown. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1135809] New: Udev package does not contain persistent-ifnames script any more
by bugzilla_noreply＠novell.com 08 Mar '21

08 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1135809 Bug ID: 1135809 Summary: Udev package does not contain persistent-ifnames script any more Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: sknorr(a)suse.com QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- The script mentioned in https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.1/index.html… is not available from the package `udev` anymore. IT is now packaged as `udev-persistent-interfaces`. To be able to use it at all, you need to run the following after installation: > ln -s foobar/75-rule-generator-script.rule /etc/udev/rules.d/ -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1084827] New: email links in forum "Reply to thread" notices open Corrupted Content Error page instead of forum page
by bugzilla_noreply＠novell.com 08 Mar '21

08 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1084827 Bug ID: 1084827 Summary: email links in forum "Reply to thread" notices open Corrupted Content Error page instead of forum page Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Infrastructure Assignee: mrueckert(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: lars.vogdt(a)suse.com CC: per(a)computer.org, suse-beta(a)cboltz.de Found By: --- Blocker: --- Problem: email links in forum "Reply to thread" notices open Corrupted Content Error page instead of forum page email list thread that produced no useful response: https://lists.opensuse.org/heroes/2018-02/msg00008.html error message:[quote] Corrupted Content Error The site at https://forums.opensuse.org/showthread.php/530041-Leap-42-3-nouveau-pointer… has experienced a network protocol violation that cannot be repaired. The page you are trying to view cannot be shown because an error in the data transmission was detected. Please contact the website owners to inform them of this problem.[/quote] These forums(a)microfocus.com email links always work if pasted into the urlbar and the trailing "?goto=newpost" is removed before proceeding. This highly annoying web accessibility impediment started happening routinely around the first of this year. IIRC, around that time, around 6 months after I updated from 42.1 to 42.3, there were some significant Nuremberg infrastructure changes. To cause these links to load the error page instead of the intended destination requires no particular action or inaction I've been able to pin down. It routinely happens while I have various B.O.O. bug pages loaded, among them saved searches, one or more of which have remained loaded across browser restarts, and may or may not have been used in recent hours or minutes. There may or may not be any open wiki or forum pages on restart, but there will nearly always have been at least one of them open in logged in state within the past 24 hours. I rarely have the browser closed except briefly for daily backup or when I log out for zypper system updating. I always start browser by loading previous session, which always has well over a hundred tabs. Since browser restarts usually cause logging out from login.microfocus.com, I typically switch to one of the open B.O.O. tabs to force re-logging in by clicking on a saved search link shortly after a browser reopen. Often I remember to check that I remain logged in before trying to open an emailed forum link, after which the link is less likely to produce the error page. Unless I've relatively recently been active on a forum or wiki page, the most likely result of the attempt is the corruption error, unless I have one or more open and recently touched forum or wiki page with a visible "log out" link. The browser I virtually always use for BOO, forum and Wiki Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 SeaMonkey/2.49.2 has NoScript extension set to always allow opensuse.org pages. -- You are receiving this mail because: You are on the CC list for the bug.

2 26