https://bugzilla.suse.com/show_bug.cgi?id=1183890https://bugzilla.suse.com/show_bug.cgi?id=1183890#c6
--- Comment #6 from Oliver Kurz <okurz(a)suse.com> ---
This is an autogenerated message for openQA integration by the openqa_review
script:
This bug is still referenced in a failing openQA test: create_hdd_tumbleweed
https://openqa.opensuse.org/tests/1762720
To prevent further reminder comments one of the following options should be
followed:
1. The test scenario is fixed by applying the bug fix to the tested product or
the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1120256https://bugzilla.suse.com/show_bug.cgi?id=1120256#c60
--- Comment #60 from Oliver Kurz <okurz(a)suse.com> ---
This is an autogenerated message for openQA integration by the openqa_review
script:
This bug is still referenced in a failing openQA test:
autoyast_bug-887126_autoinst
https://openqa.suse.de/tests/5990319
To prevent further reminder comments one of the following options should be
followed:
1. The test scenario is fixed by applying the bug fix to the tested product or
the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1184243https://bugzilla.suse.com/show_bug.cgi?id=1184243#c8
--- Comment #8 from openQA Review <openqa-review(a)suse.de> ---
This is an autogenerated message for openQA integration by the openqa_review
script:
This bug is still referenced in a failing openQA test: yast2_gui
https://openqa.opensuse.org/tests/1757680
To prevent further reminder comments one of the following options should be
followed:
1. The test scenario is fixed by applying the bug fix to the tested product or
the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186715
Bug ID: 1186715
Summary: [Tumbleweed][openssl][libressl] older
"/usr/bin/openssl" command gave wrong return code
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: screening-team-bugs(a)suse.de
Reporter: richard.fan(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
The issue might be a corner one.
And it might have something to do with bug
https://bugzilla.opensuse.org/show_bug.cgi?id=1186649
However, It is very strange that, when the command reports an error msg, it
still returns 0.
Here comes the reproduce steps:
1. install the older openssl cli with command "zypper in 'openssl(cli)', and
the only libressl is installed.
susetest:~ # rpm -qf /usr/bin/openssl
libressl-3.3.3-1.2.x86_64
2. I tried to run "rehash" command, it reports error
susetest:~ # /usr/bin/openssl rehash /etc/openldap
openssl:Error: 'rehash' is an invalid command.
Standard commands
asn1parse ca certhash ciphers
cms crl crl2pkcs7 dgst
dh dhparam dsa dsaparam
ec ecparam enc errstr
gendh gendsa genpkey genrsa
nseq ocsp passwd pkcs12
pkcs7 pkcs8 pkey pkeyparam
pkeyutl prime rand req
rsa rsautl s_client s_server
s_time sess_id smime speed
spkac ts verify version
x509
Message Digest commands (see the `dgst' command for more details)
gost-mac md4 md5 md_gost94
ripemd160 sha1 sha224 sha256
sha384 sha512 sm3 sm3WithRSAEncryption
streebog256 streebog512 whirlpool
Cipher commands (see the `enc' command for more details)
aes-128-cbc aes-128-ecb aes-192-cbc aes-192-ecb
aes-256-cbc aes-256-ecb base64 bf
bf-cbc bf-cfb bf-ecb bf-ofb
camellia-128-cbc camellia-128-ecb camellia-192-cbc camellia-192-ecb
camellia-256-cbc camellia-256-ecb cast cast-cbc
cast5-cbc cast5-cfb cast5-ecb cast5-ofb
chacha des des-cbc des-cfb
des-ecb des-ede des-ede-cbc des-ede-cfb
des-ede-ofb des-ede3 des-ede3-cbc des-ede3-cfb
des-ede3-ofb des-ofb des3 desx
idea idea-cbc idea-cfb idea-ecb
idea-ofb rc2 rc2-40-cbc rc2-64-cbc
rc2-cbc rc2-cfb rc2-ecb rc2-ofb
rc4 rc4-40 sm4 sm4-cbc
sm4-cfb sm4-ecb sm4-ofb
However, the return code is 0 (IMO, it should return non-zero code)
susetest:~ # echo $?
0
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182864http://bugzilla.opensuse.org/show_bug.cgi?id=1182864#c11
--- Comment #11 from Marcus R�ckert <mrueckert(a)suse.com> ---
```
#0 sljit_malloc_exec (size=1912) at src/sljit/sljitProtExecAllocator.c:338
338 header->prev_size = chunk_size;
(gdb) bt
#0 sljit_malloc_exec (size=1912) at src/sljit/sljitProtExecAllocator.c:338
#1 0x00007f5d720c711e in sljit_generate_code
(compiler=compiler@entry=0x55c954ed7c00) at
src/sljit/sljitNativeX86_common.c:509
#2 0x00007f5d720f79fb in jit_compile (code=code@entry=0x55c954ec2f40,
mode=mode@entry=1) at src/pcre2_jit_compile.c:14066
#3 0x00007f5d720fad7d in pcre2_jit_compile_8 (code=0x55c954ec2f40,
options=options@entry=1) at src/pcre2_jit_compile.c:14220
#4 0x00007f5d72fbca2d in rspamd_regexp_post_process (r=0x55c9543b9810) at
/usr/src/debug/rspamd-2.7-30.11.x86_64/src/libutil/regexp.c:184
```
after this GDB was killed for OOM
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1173619https://bugzilla.suse.com/show_bug.cgi?id=1173619#c14
--- Comment #14 from Michael Str�der <michael(a)stroeder.com> ---
(In reply to Wolfgang Frisch from comment #13)
> Michael, can you please have a look and adjust the .spec file? The attached
> patch should do the trick.
Hmm, does this affect intended usage of unbound-control? The man-page is not
clear on that.
Personally I'm in the camp to lock down everything as much as possible. That's
e.g. one reason why I object to CAP_DAC_OVERRIDE.
But for a general purpose package we unfortunately have to clarify whether
changes to the .spec file makes using some features impossible.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186692https://bugzilla.suse.com/show_bug.cgi?id=1186692#c2
Takashi Iwai <tiwai(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bon(a)elektron.ikp.physik.tu-
| |darmstadt.de,
| |oneukum(a)suse.com,
| |tiwai(a)suse.com
Flags| |needinfo?(bon(a)elektron.ikp.
| |physik.tu-darmstadt.de)
--- Comment #2 from Takashi Iwai <tiwai(a)suse.com> ---
(In reply to Uwe Bonnes from comment #1)
> Is there some archive of KOTDs or a simple way to bisect the SUSE kernel?
There is no official archive, but you can find some kernel packages in my OBS
repos, e.g. OBS home:tiwai:kernel:5.9, home:tiwai:kernel:5.10, ...
It'd be helpful if you can narrow down which kernel version starts showing the
regression.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1173619https://bugzilla.suse.com/show_bug.cgi?id=1173619#c13
--- Comment #13 from Wolfgang Frisch <wolfgang.frisch(a)suse.com> ---
Created attachment 849858
--> https://bugzilla.suse.com/attachment.cgi?id=849858&action=edit
unbound-640.patch
(In reply to Detlef Eppers from comment #5)
> This leaves us with the second issue, unrelated to the first.
> After having dropped privileges, I believe that Unbound should
> not be able to write to its configuration file any more, as this
> hands user unbound control over the Unbound server running as root
> during next start.
>
> I cannot verify at the moment if this is still the case, but
> /etc/unbound/conf.d/example.com.conf and
> /etc/unbound/local.d/block-example.com.conf used to be sourced from
> /etc/unbound/unbound.conf.
> At the same time these files used to be writable by user unbound.
Indeed, the example configs are still sourced, and I see no reason why they
would have to be writable by the `unbound` user.
Michael, can you please have a look and adjust the .spec file? The attached
patch should do the trick.
--
You are receiving this mail because:
You are on the CC list for the bug.