https://bugzilla.redhat.com/show_bug.cgi?id=2093731
Bug ID: 2093731
Summary: zbarimg does not read a Code 128 barcode
Product: Fedora
Version: 36
Status: NEW
Component: zbar
Severity: high
Assignee: gwync(a)protonmail.com
Reporter: cristian.ciupitu(a)yahoo.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dougsland(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
gwync(a)protonmail.com, mchehab(a)infradead.org,
mr.marcelo.barbosa(a)gmail.com, negativo17(a)gmail.com
Target Milestone: ---
Classification: Fedora
Created attachment 1886898
--> https://bugzilla.redhat.com/attachment.cgi?id=1886898&action=edit
Code 128 barcode
Description of problem:
zbarimg does not read a Code 128 barcode
Version-Release number of selected component (if applicable):
zbar-0.23.90-1.fc36.x86_64
How reproducible:
Every time
Steps to Reproduce:
1. zbarimg barcode.png
Actual results:
scanned 0 barcode symbols from 1 images in 0 seconds
WARNING: barcode data was not detected in some image(s)
Things to check:
- is the barcode type supported? Currently supported symbologies are:
. EAN/UPC (EAN-13, EAN-8, EAN-2, EAN-5, UPC-A, UPC-E, ISBN-10, ISBN-13)
. DataBar, DataBar Expanded
. Code 128
. Code 93
. Code 39
. Codabar
. Interleaved 2 of 5
. QR code
. SQ code
. PDF 417
- is the barcode large enough in the image?
- is the barcode mostly in focus?
- is there sufficient contrast/illumination?
- If the symbol is split in several barcodes, are they combined in one image?
- Did you enable the barcode type?
some EAN/UPC codes are disabled by default. To enable all, use:
$ zbarimg -S*.enable <files>
Please also notice that some variants take precedence over others.
Due to that, if you want, for example, ISBN-10, you should do:
$ zbarimg -Sisbn10.enable <files>
Expected results:
(Code 128) 755897201062022179.73
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2093731
https://bugzilla.redhat.com/show_bug.cgi?id=2093305
Bug ID: 2093305
Summary: CVE-2022-30783 ntfs-3g: invalid return code in
fuse_kern_mount enables intercepting of libfuse-lite
protocol traffic
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: gsuckevi(a)redhat.com
CC: ddepaula(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
jferlan(a)redhat.com, kparal(a)redhat.com,
ngompa13(a)gmail.com, rjones(a)redhat.com,
spotrh(a)gmail.com, virt-maint(a)redhat.com
Target Milestone: ---
Classification: Other
An invalid return code in fuse_kern_mount enables intercepting of libfuse-lite
protocol traffic between NTFS-3G and the kernel in NTFS-3G through 2021.8.22
when using libfuse-lite.
References:
https://github.com/tuxera/ntfs-3g/security/advisories/GHSA-6mv4-4v73-xw58https://github.com/tuxera/ntfs-3g/releases
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2093305
https://bugzilla.redhat.com/show_bug.cgi?id=2093308
Bug ID: 2093308
Summary: CVE-2022-30783 ntfs-3g-system-compression: ntfs-3g:
invalid return code in fuse_kern_mount enables
intercepting of libfuse-lite protocol traffic
[epel-all]
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: ntfs-3g-system-compression
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: kparal(a)redhat.com
Reporter: gsuckevi(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
kparal(a)redhat.com, ngompa13(a)gmail.com
Target Milestone: ---
Classification: Fedora
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora EPEL. While
only one tracking bug has been filed, please correct all affected versions
at the same time. If you need to fix the versions independent of each
other, you may clone this bug as appropriate.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2093308
https://bugzilla.redhat.com/show_bug.cgi?id=2093333
Bug ID: 2093333
Summary: CVE-2022-30787 ntfs-3g: integer underflow in
fuse_lib_readdir enables arbitrary memory read
operations
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: gsuckevi(a)redhat.com
CC: ddepaula(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
jferlan(a)redhat.com, kparal(a)redhat.com,
ngompa13(a)gmail.com, rjones(a)redhat.com,
spotrh(a)gmail.com, virt-maint(a)redhat.com
Target Milestone: ---
Classification: Other
An integer underflow in fuse_lib_readdir enables arbitrary memory read
operations in NTFS-3G through 2021.8.22 when using libfuse-lite.
References:
https://github.com/tuxera/ntfs-3g/security/advisories/GHSA-6mv4-4v73-xw58https://github.com/tuxera/ntfs-3g/releases
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2093333
https://bugzilla.redhat.com/show_bug.cgi?id=2093336
Bug ID: 2093336
Summary: CVE-2022-30787 ntfs-3g-system-compression: ntfs-3g:
integer underflow in fuse_lib_readdir enables
arbitrary memory read operations [epel-all]
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: ntfs-3g-system-compression
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: kparal(a)redhat.com
Reporter: gsuckevi(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
kparal(a)redhat.com, ngompa13(a)gmail.com
Target Milestone: ---
Classification: Fedora
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora EPEL. While
only one tracking bug has been filed, please correct all affected versions
at the same time. If you need to fix the versions independent of each
other, you may clone this bug as appropriate.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2093336
https://bugzilla.redhat.com/show_bug.cgi?id=2093323
Bug ID: 2093323
Summary: CVE-2022-30785 ntfs-3g-system-compression: ntfs-3g: a
file handle created in fuse_lib_opendir, and later
used in fuse_lib_readdir, enables arbitrary memory
read and write operations [epel-all]
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: ntfs-3g-system-compression
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: kparal(a)redhat.com
Reporter: gsuckevi(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
kparal(a)redhat.com, ngompa13(a)gmail.com
Target Milestone: ---
Classification: Fedora
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora EPEL. While
only one tracking bug has been filed, please correct all affected versions
at the same time. If you need to fix the versions independent of each
other, you may clone this bug as appropriate.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2093323
https://bugzilla.redhat.com/show_bug.cgi?id=2093320
Bug ID: 2093320
Summary: CVE-2022-30785 ntfs-3g: a file handle created in
fuse_lib_opendir, and later used in fuse_lib_readdir,
enables arbitrary memory read and write operations
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: gsuckevi(a)redhat.com
CC: ddepaula(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
jferlan(a)redhat.com, kparal(a)redhat.com,
ngompa13(a)gmail.com, rjones(a)redhat.com,
spotrh(a)gmail.com, virt-maint(a)redhat.com
Target Milestone: ---
Classification: Other
A file handle created in fuse_lib_opendir, and later used in fuse_lib_readdir,
enables arbitrary memory read and write operations in NTFS-3G through 2021.8.22
when using libfuse-lite.
References:
https://github.com/tuxera/ntfs-3g/security/advisories/GHSA-6mv4-4v73-xw58https://github.com/tuxera/ntfs-3g/releases
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2093320
https://bugzilla.redhat.com/show_bug.cgi?id=2097004
Bug ID: 2097004
Summary: stalonetray-0.8.4 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: stalonetray
Keywords: FutureFeature, Triaged
Assignee: fedora(a)me.benboeckel.net
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
fedora(a)me.benboeckel.net
Target Milestone: ---
Classification: Fedora
Releases retrieved: 0.8.4
Upstream release that is considered latest: 0.8.4
Current version/release in rawhide: 0.8.3-16.fc36
URL: https://github.com/kolbusa/stalonetray
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from Anitya:
https://release-monitoring.org/project/5713/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/stalonetray
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2097004
https://bugzilla.redhat.com/show_bug.cgi?id=2121894
Bug ID: 2121894
Summary: builtins.h requires mpc.h from libmpc-devel
Product: Fedora
Version: 36
Hardware: x86_64
OS: Linux
Status: NEW
Component: cross-gcc
Severity: medium
Assignee: dhowells(a)redhat.com
Reporter: elliott(a)hpe.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dan(a)danny.cz, dhowells(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
lkundrak(a)v3.sk
Target Milestone: ---
Classification: Fedora
Description of problem:
Cross compiles of the linux kernel 6.0-rc1 allmodconfig fail for arm, arm64,
mips, powerpc, and s390.
This originates in scripts/gcc-plugins/Kconfig, which has this entry:
menuconfig GCC_PLUGINS
bool "GCC plugins"
depends on HAVE_GCC_PLUGINS
depends on CC_IS_GCC
depends on $(success,test -e $(shell,$(CC)
-print-file-name=plugin)/include/plugin-version.h)
default y
depends on $(success,test -e $(shell,$(CC)
-print-file-name=plugin)/include/plugin-version.h)
arch/sparc/Kconfig does not include
select HAVE_GCC_PLUGINS
but all the others do.
The -print-file-name tests passes for all the cross-compilers, but does not
for native x86:
$ gcc -print-file-name=plugin
plugin
$ powerpc64-linux-gnu-gcc -print-file-name=plugin
/usr/lib/gcc/powerpc64-linux-gnu/12/plugin
$ aarch64-linux-gnu-gcc -print-file-name=plugin
/usr/lib/gcc/aarch64-linux-gnu/12/plugin
$ find /usr/lib/gcc -name plugin-version.h
/usr/lib/gcc/s390x-linux-gnu/12/plugin/include/plugin-version.h
/usr/lib/gcc/aarch64-linux-gnu/12/plugin/include/plugin-version.h
/usr/lib/gcc/powerpc64-linux-gnu/12/plugin/include/plugin-version.h
/usr/lib/gcc/sparc64-linux-gnu/12/plugin/include/plugin-version.h
/usr/lib/gcc/arm-linux-gnueabi/12/plugin/include/plugin-version.h
/usr/lib/gcc/mips64-linux-gnu/12/plugin/include/plugin-version.h
so the .x86 .config file only gets:
CONFIG_HAVE_GCC_PLUGINS=y
while the others get that, CONFIG_GCC_PLUGINS, and a several
specific plugins:
build-arm64/.config:CONFIG_HAVE_GCC_PLUGINS=y
build-arm64/.config:CONFIG_GCC_PLUGINS=y
build-arm64/.config:CONFIG_GCC_PLUGIN_LATENT_ENTROPY=y
build-arm64/.config:CONFIG_GCC_PLUGIN_STACKLEAK=y
build-arm64/.config:CONFIG_GCC_PLUGIN_RANDSTRUCT=y
build-arm/.config:CONFIG_HAVE_GCC_PLUGINS=y
build-arm/.config:CONFIG_GCC_PLUGINS=y
build-arm/.config:CONFIG_GCC_PLUGIN_LATENT_ENTROPY=y
build-arm/.config:CONFIG_GCC_PLUGIN_RANDSTRUCT=y
build-mips/.config:CONFIG_HAVE_GCC_PLUGINS=y
build-mips/.config:CONFIG_GCC_PLUGINS=y
build-mips/.config:CONFIG_GCC_PLUGIN_LATENT_ENTROPY=y
build-mips/.config:CONFIG_GCC_PLUGIN_RANDSTRUCT=y
build-powerpc/.config:CONFIG_HAVE_GCC_PLUGINS=y
build-powerpc/.config:CONFIG_GCC_PLUGINS=y
build-powerpc/.config:CONFIG_GCC_PLUGIN_LATENT_ENTROPY=y
build-powerpc/.config:CONFIG_GCC_PLUGIN_RANDSTRUCT=y
build-s390/.config:CONFIG_HAVE_GCC_PLUGINS=y
build-s390/.config:CONFIG_GCC_PLUGINS=y
build-s390/.config:CONFIG_GCC_PLUGIN_LATENT_ENTROPY=y
build-s390/.config:CONFIG_GCC_PLUGIN_RANDSTRUCT=y
build-x86/.config:CONFIG_HAVE_GCC_PLUGINS=y
A header included by each of the plugins, scripts/gcc-plugins/gcc-common.h,
includes a GCC header file called builtins.h that includes <mpc.h>, which
does not exist anywhere on my system. That causes errors early in the build on
all of those architectures.
Version-Release number of selected component (if applicable):
gcc-[each architecture]-linux-gnu 12.1.1
How reproducible:
100%
Steps to Reproduce:
Example for arm 32-bit:
1. make ARCH=arm O=build-arm CROSS_COMPILE=arm-linux-gnu- allmodconfig
2. make ARCH=arm O=build-arm CROSS_COMPILE=arm-linux-gnu- -j 55
Actual results:
For each "GCC plugin", an error like this terminates the make:
In file included from ../scripts/gcc-plugins/gcc-common.h:95,
from ../scripts/gcc-plugins/latent_entropy_plugin.c:78:
/usr/lib/gcc/aarch64-linux-gnu/12/plugin/include/builtins.h:23:10: fatal error:
mpc.h: No such file or directory
23 | #include <mpc.h>
| ^~~~~~~
compilation terminated.
Expected results:
no errors
Additional info:
That mpc.h file is provided by the libmpc-devel package.
1. Please add a dependency for the libmpc-devel package from each gcc
cross-compiler package that includes a builtins.h file
2. Please investigate whether the native gcc package not having plugins is
correct, despite the kernel x86 allmodconfig expecting them by specifying
CONFIG_HAVE_GCC_PLUGINS=y
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2121894
https://bugzilla.redhat.com/show_bug.cgi?id=2052682
Bug ID: 2052682
Summary: CVE-2022-24303 python-pillow: temporary directory with
a space character allows removal of unrelated file
after im.show() and related action
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: gsuckevi(a)redhat.com
CC: bdettelb(a)redhat.com, cstratak(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
infra-sig(a)lists.fedoraproject.org,
manisandro(a)gmail.com, miminar(a)redhat.com,
orion(a)nwra.com, python-maint(a)redhat.com,
python-sig(a)lists.fedoraproject.org, torsava(a)redhat.com
Target Milestone: ---
Classification: Other
If the path to the temporary directory on Linux or macOS contained a space,
this would break removal of the temporary image file after im.show() (and
related actions), and potentially remove an unrelated file. This been present
since PIL.
Reference:
https://pillow.readthedocs.io/en/stable/releasenotes/9.0.1.html
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2052682
https://bugzilla.redhat.com/show_bug.cgi?id=2042527
Bug ID: 2042527
Summary: CVE-2022-22817 python-pillow: PIL.ImageMath.eval
allows evaluation of arbitrary expressions
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: high
Priority: high
Assignee: security-response-team(a)redhat.com
Reporter: gsuckevi(a)redhat.com
CC: bdettelb(a)redhat.com, cstratak(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
infra-sig(a)lists.fedoraproject.org,
manisandro(a)gmail.com, miminar(a)redhat.com,
orion(a)nwra.com, python-maint(a)redhat.com,
python-sig(a)lists.fedoraproject.org, torsava(a)redhat.com
Target Milestone: ---
Classification: Other
PIL.ImageMath.eval in Pillow before 9.0.0 allows evaluation of arbitrary
expressions, such as ones that use the Python exec method.
Reference:
https://pillow.readthedocs.io/en/stable/releasenotes/9.0.0.html#restrict-bu…
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2042527
https://bugzilla.redhat.com/show_bug.cgi?id=2042522
Bug ID: 2042522
Summary: CVE-2022-22816 python-pillow: buffer over-read during
initialization of ImagePath.Path in path_getbbox() in
path.c
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: high
Priority: high
Assignee: security-response-team(a)redhat.com
Reporter: gsuckevi(a)redhat.com
CC: bdettelb(a)redhat.com, cstratak(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
infra-sig(a)lists.fedoraproject.org,
manisandro(a)gmail.com, miminar(a)redhat.com,
orion(a)nwra.com, python-maint(a)redhat.com,
python-sig(a)lists.fedoraproject.org, torsava(a)redhat.com
Target Milestone: ---
Classification: Other
path_getbbox in path.c in Pillow before 9.0.0 has a buffer over-read during
initialization of ImagePath.Path.
References:
https://github.com/python-pillow/Pillow/blob/c5d9223a8b5e9295d15b5a9b1ef1da…https://pillow.readthedocs.io/en/stable/releasenotes/9.0.0.html#fixed-image…
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2042522
https://bugzilla.redhat.com/show_bug.cgi?id=2042511
Bug ID: 2042511
Summary: CVE-2022-22815 python-pillow: improperly initializes
ImagePath.Path in path_getbbox() in path.c
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: gsuckevi(a)redhat.com
CC: bdettelb(a)redhat.com, cstratak(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
infra-sig(a)lists.fedoraproject.org,
manisandro(a)gmail.com, miminar(a)redhat.com,
orion(a)nwra.com, python-maint(a)redhat.com,
python-sig(a)lists.fedoraproject.org, torsava(a)redhat.com
Target Milestone: ---
Classification: Other
path_getbbox in path.c in Pillow before 9.0.0 improperly initializes
ImagePath.Path.
References:
https://github.com/python-pillow/Pillow/blob/c5d9223a8b5e9295d15b5a9b1ef1da…https://pillow.readthedocs.io/en/stable/releasenotes/9.0.0.html#fixed-image…
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2042511
https://bugzilla.redhat.com/show_bug.cgi?id=2120537
Bug ID: 2120537
Summary: 'bodhi updates new' does not report error/warning when
setting karma limit below minimal value for package in
critical path
Product: Fedora
Version: rawhide
Status: NEW
Component: bodhi-client
Assignee: thrcka(a)redhat.com
Reporter: zdohnal(a)redhat.com
CC: aurelien(a)bompard.org,
epel-packagers-sig(a)lists.fedoraproject.org,
lenka(a)sepu.cz, thrcka(a)redhat.com
Target Milestone: ---
Classification: Fedora
Hi,
I was surprised why my bodhi update (
https://bodhi.fedoraproject.org/updates/FEDORA-2022-6f5e420e52 ) doesn't show
an option for pushing into stable or why the update is not in stable already,
because the positive karma limit (1) is reached.
On #fedora-devel IRC channel kalev answered:
(09:34:34 AM) zdohnal: Hi all, do you have an idea what blocks this update
https://bodhi.fedoraproject.org/updates/FEDORA-2022-6f5e420e52 from being
pushed to the stable?
(09:38:32 AM) kalev: zdohnal: looks like it's marked as critical path and
because of that, it needs minimum of +2 karma to be pushed to stable
(09:40:19 AM) GrannyGoose left the room (quit: Quit: Going offline, see ya!
(www.adiirc.com))
(09:41:00 AM) zdohnal: kalev: aha - good to know. However bodhi-client should
give me error when I set karma below this limit...
According to the conversation, there is karma limit for components in critical
path and it is higher - 2 - than the limit set by me - 1, which causes
confusion.
I use 'bodhi updates new' CLI command for creating updates, and I didn't see
any error/warning regarding setting the karma limit too low.
IMHO CLI command has to fail if user tries to set the limit too low, and bodhi
web UI should handle this in some way as well.
Would you mind looking into it?
Version-Release number of selected component (if applicable):
bodhi-client-6.0.1-4.fc37
How reproducible:
always
Steps to Reproduce:
1. $ bodhi updates new --type bugfix --close-bugs --request testing --autokarma
--autotime --stable-karma 1 --unstable-karma -1 --notes "Update for component
in critical path" <critical-component-1.2.3-1.fc37>
Actual results:
No error or warning, bodhi web ui shows user defined limit and the update has
karma to fulfill the limit, but the update is not pushed into stable.
Expected results:
Give error (in both interfaces - CLI and Web UI) if user wants to set lower
karma limit than it is required on the package.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2120537
https://bugzilla.redhat.com/show_bug.cgi?id=2065645
Bug ID: 2065645
Summary: Gmime 3.2.9 is available
Product: Fedora
Version: rawhide
Hardware: All
Status: NEW
Component: gmime30
Severity: medium
Assignee: klember(a)redhat.com
Reporter: mjg(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
klember(a)redhat.com
Target Milestone: ---
Link ID: Github jstedfast/gmime/releases/tag/3.2.9
Classification: Fedora
Description of problem:
Gmime 3.2.7 as packaged is outdated (Mar 2020).
Version-Release number of selected component (if applicable):
3.2.7-5
How reproducible:
always
Steps to Reproduce:
1. dnf list gmime30
Actual results:
gmime30-3.2.7
Expected results:
gmime30-3.2.9
Additional info:
The real upstream has been at https://github.com/jstedfast/gmime/ for quite
some time now (not on gnome any more, and never on gitlab).
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2065645
https://bugzilla.redhat.com/show_bug.cgi?id=2078238
Bug ID: 2078238
Summary: gssdp-1.5.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: gssdp
Keywords: FutureFeature, Triaged
Assignee: klember(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dcavalca(a)fb.com,
epel-packagers-sig(a)lists.fedoraproject.org,
klember(a)redhat.com, zeenix(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 1.5.0
Current version/release in rawhide: 1.4.0.1-2.fc36
URL: https://developer.gnome.org/gssdp/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from Anitya:
https://release-monitoring.org/project/1262/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2078238
https://bugzilla.redhat.com/show_bug.cgi?id=2081494
Bug ID: 2081494
Summary: CVE-2022-1292 openssl: c_rehash script allows command
injection
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: pdelbell(a)redhat.com
CC: aos-bugs(a)redhat.com, asoldano(a)redhat.com,
bbaranow(a)redhat.com, bdettelb(a)redhat.com,
berrange(a)redhat.com, bmaxwell(a)redhat.com,
bootloader-eng-team(a)redhat.com,
brian.stansberry(a)redhat.com, caswilli(a)redhat.com,
cdewolf(a)redhat.com, cfergeau(a)redhat.com,
chazlett(a)redhat.com, crobinso(a)redhat.com,
crypto-team(a)lists.fedoraproject.org,
csutherl(a)redhat.com, darran.lofthouse(a)redhat.com,
dbelyavs(a)redhat.com, ddepaula(a)redhat.com,
dhalasz(a)redhat.com, dkreling(a)redhat.com,
dkuc(a)redhat.com, dosoudil(a)redhat.com,
dueno(a)redhat.com, elima(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
erik-fedora(a)vanpienbroek.nl, f4bug(a)amsat.org,
fjansen(a)redhat.com, fjuma(a)redhat.com,
fmartine(a)redhat.com, gparvin(a)redhat.com,
gzaronik(a)redhat.com, iweiss(a)redhat.com,
jburrell(a)redhat.com, jclere(a)redhat.com,
jferlan(a)redhat.com, jkoehler(a)redhat.com,
jochrist(a)redhat.com, jramanat(a)redhat.com,
jwong(a)redhat.com, jwon(a)redhat.com, kaycoth(a)redhat.com,
krathod(a)redhat.com, kraxel(a)redhat.com,
ktietz(a)redhat.com, lgao(a)redhat.com,
marcandre.lureau(a)redhat.com,
michal.skrivanek(a)redhat.com, michel(a)michel-slm.name,
micjohns(a)redhat.com, mjg59(a)srcf.ucam.org,
mosmerov(a)redhat.com, mperina(a)redhat.com,
msochure(a)redhat.com, mspacek(a)redhat.com,
msvehla(a)redhat.com, mturk(a)redhat.com,
njean(a)redhat.com, nwallace(a)redhat.com,
pahickey(a)redhat.com, pbonzini(a)redhat.com,
pjindal(a)redhat.com, pjones(a)redhat.com,
pmackay(a)redhat.com, redhat-bugzilla(a)linuxnetz.de,
rfreiman(a)redhat.com, rharwood(a)redhat.com,
rh-spice-bugs(a)redhat.com, rjones(a)redhat.com,
rstancel(a)redhat.com, rsvoboda(a)redhat.com,
sahana(a)redhat.com, sbonazzo(a)redhat.com,
smaestri(a)redhat.com, stcannon(a)redhat.com,
sthirugn(a)redhat.com, szappis(a)redhat.com,
tmeszaro(a)redhat.com, tm(a)t8m.info,
tom.jenkinson(a)redhat.com,
virt-maint(a)lists.fedoraproject.org,
virt-maint(a)redhat.com, vkrizan(a)redhat.com,
vkumar(a)redhat.com, vmugicag(a)redhat.com
Target Milestone: ---
Classification: Other
The c_rehash script does not properly sanitise shell metacharacters to
prevent command injection. This script is distributed by some operating
systems in a manner where it is automatically executed. On such operating
systems, an attacker could execute arbitrary commands with the privileges
of the script.
Use of the c_rehash script is considered obsolete and should be replaced
by the OpenSSL rehash command line tool.
This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0.
OpenSSL 1.0.2 users should upgrade to 1.0.2ze
OpenSSL 1.1.1 users should upgrade to 1.1.1o
OpenSSL 3.0 users should upgrade to 3.0.3
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2081494
https://bugzilla.redhat.com/show_bug.cgi?id=2090572
Bug ID: 2090572
Summary: CVE-2022-21680 thrift: marked: regular expression
block.def may lead Denial of Service [epel-all]
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: thrift
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: ctubbsii(a)fedoraproject.org
Reporter: saroy(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ctubbsii(a)fedoraproject.org,
epel-packagers-sig(a)lists.fedoraproject.org,
milleruntime(a)gmail.com, orion(a)nwra.com,
willb(a)redhat.com
Target Milestone: ---
Classification: Fedora
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora EPEL. While
only one tracking bug has been filed, please correct all affected versions
at the same time. If you need to fix the versions independent of each
other, you may clone this bug as appropriate.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2090572
https://bugzilla.redhat.com/show_bug.cgi?id=2092715
Bug ID: 2092715
Summary: CVE-2022-21681 thrift: marked: regular expression
inline.reflinkSearch may lead Denial of Service
[epel-all]
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: thrift
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: ctubbsii(a)fedoraproject.org
Reporter: trathi(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ctubbsii(a)fedoraproject.org,
epel-packagers-sig(a)lists.fedoraproject.org,
milleruntime(a)gmail.com, orion(a)nwra.com,
willb(a)redhat.com
Target Milestone: ---
Classification: Fedora
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora EPEL. While
only one tracking bug has been filed, please correct all affected versions
at the same time. If you need to fix the versions independent of each
other, you may clone this bug as appropriate.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2092715
https://bugzilla.redhat.com/show_bug.cgi?id=2094052
Bug ID: 2094052
Summary: CVE-2021-4231 angular: XSS vulnerability
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: low
Priority: low
Assignee: security-response-team(a)redhat.com
Reporter: gsuckevi(a)redhat.com
CC: aileenc(a)redhat.com, amctagga(a)redhat.com,
amurdaca(a)redhat.com, andrew.slice(a)redhat.com,
aoconnor(a)redhat.com, asm(a)redhat.com,
bniver(a)redhat.com, bodavis(a)redhat.com,
branto(a)redhat.com, chazlett(a)redhat.com,
danmick(a)gmail.com, david(a)gnsa.us, dbhole(a)redhat.com,
decathorpe(a)gmail.com, deparker(a)redhat.com,
dwd(a)fedoraproject.org, eduardo.ramalho(a)gmail.com,
epel-packagers-sig(a)lists.fedoraproject.org,
erack(a)redhat.com, fedora(a)zaniyah.org,
flucifre(a)redhat.com, fmuellner(a)redhat.com,
fzatlouk(a)redhat.com,
gecko-bugs-nobody(a)fedoraproject.org,
gmalinko(a)redhat.com, gmeno(a)redhat.com,
go-sig(a)lists.fedoraproject.org, i(a)stingr.net,
janstey(a)redhat.com, jcajka(a)cajka.dev,
jhorak(a)redhat.com, jochrist(a)redhat.com,
josef(a)toxicpanda.com, jwon(a)redhat.com,
kai-engert-fedora(a)kuix.de, kanderso(a)redhat.com,
kkeithle(a)redhat.com, klaas(a)demter.de,
klember(a)redhat.com, lemenkov(a)gmail.com,
loic(a)dachary.org, lvaleeva(a)redhat.com,
madam(a)redhat.com, mbenjamin(a)redhat.com,
mhackett(a)redhat.com, muagarwa(a)redhat.com,
ngompa13(a)gmail.com, ocs-bugs(a)redhat.com,
omajid(a)redhat.com, pdelbell(a)redhat.com,
pjasicek(a)redhat.com, polkit-devel(a)redhat.com,
ramkrsna(a)gmail.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, rwagner(a)redhat.com,
sandmann(a)redhat.com, sostapov(a)redhat.com,
steve(a)silug.org, stransky(a)redhat.com,
thofmann(a)fedoraproject.org, tpopela(a)redhat.com,
trpost(a)rocketmail.com, vereddy(a)redhat.com,
zebob.m(a)gmail.com, zsvetlik(a)redhat.com
Blocks: 2094048
Target Milestone: ---
Classification: Other
A vulnerability was found in Angular up to 11.0.4/11.1.0-next.2. It has been
classified as problematic. Affected is the handling of comments. The
manipulation leads to cross site scripting. It is possible to launch the attack
remotely but it might require an authentication first. Upgrading to version
11.0.5 and 11.1.0-next.3 is able to address this issue. The name of the patch
is ba8da742e3b243e8f43d4c63aa842b44e14f2b09. It is recommended to upgrade the
affected component.
References:
https://vuldb.com/?id.181356https://github.com/angular/angular/issues/40136https://security.snyk.io/vuln/SNYK-JS-ANGULARCORE-1070902https://github.com/angular/angular/commit/ba8da742e3b243e8f43d4c63aa842b44e…
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2094052
https://bugzilla.redhat.com/show_bug.cgi?id=2032607
Bug ID: 2032607
Summary: F36FailsToInstall: hyperkitty
Product: Fedora
Version: rawhide
Status: NEW
Component: python-hyperkitty
Assignee: michel(a)michel-slm.name
Reporter: mhroncok(a)redhat.com
CC: epel-packagers-sig(a)lists.fedoraproject.org,
infra-sig(a)lists.fedoraproject.org,
michel(a)michel-slm.name, ngompa13(a)gmail.com,
python-sig(a)lists.fedoraproject.org
Blocks: 1992487 (F36FailsToInstall,RAWHIDEFailsToInstall)
Target Milestone: ---
Classification: Fedora
Hello,
Please note that this comment was generated automatically. If you feel that
this output has mistakes, please contact me via email (mhroncok(a)redhat.com)
Your package (python-hyperkitty) Fails To Install in Fedora 36:
can't install hyperkitty:
- nothing provides python3.10dist(flufl-lock) >= 4 needed by
hyperkitty-1.3.5-1.fc36.noarch
- nothing provides python3.10dist(mistune) >= 2~rc1 needed by
hyperkitty-1.3.5-1.fc36.noarch
If you know about this problem and are planning on fixing it, please
acknowledge so by setting the bug status to ASSIGNED. If you don't have time to
maintain this package, consider orphaning it, so maintainers of dependent
packages realize the problem.
If you don't react accordingly to the policy for FTBFS/FTI bugs
(https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails…)
your package may be orphaned in 8+ weeks.
P.S. The data was generated solely from koji buildroot, so it might be newer
than the latest compose or the content on mirrors.
P.P.S. If this bug has been reported in the middle of upgrading multiple
dependent packages, please consider using side tags:
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-d…
Thanks!
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1992487
[Bug 1992487] Fedora 36 Fails To install Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2032607
https://bugzilla.redhat.com/show_bug.cgi?id=2063508
Bug ID: 2063508
Summary: authentication recquired The password you use does not
match
Product: Fedora
Version: 36
OS: Linux
Status: NEW
Component: keyrings-filesystem
Severity: high
Assignee: manisandro(a)gmail.com
Reporter: jjb(a)xs4all.nl
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
manisandro(a)gmail.com, sergio(a)serjux.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Keyring is locked. (in Passwords and Keys, Seahorse)
try to solve error message "authentication required, the password you use to
log in to your computer no longer match that of your login keyring"
The known password is not accepted.
Version-Release number of selected component (if applicable):
How reproducible:
try to Get Geary (email program) at work.
At login to the computer the password is working all right.
Steps to Reproduce:
1.
2.
3.
Actual results:
cannot authenticate password.
Expected results:
no question of authentication
Additional info:
do not know how to solve this problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2063508
https://bugzilla.redhat.com/show_bug.cgi?id=2107574
Bug ID: 2107574
Summary: fortune(6) man page indentation is messed up for -o
and -s options
Product: Fedora
Version: 36
Status: NEW
Component: fortune-mod
Severity: low
Assignee: sheltren(a)fedoraproject.org
Reporter: rhbugs(a)n-dimensional.de
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
sergio(a)serjux.com, sheltren(a)fedoraproject.org,
shlomif(a)shlomifish.org
Target Milestone: ---
Classification: Fedora
Created attachment 1897376
--> https://bugzilla.redhat.com/attachment.cgi?id=1897376&action=edit
Quick fix patch to the fortune.6 file, copying the formatting -i and -n
Description of problem:
In the fortune(6) man page, the indentation for the description
of the options -o and -s is wrong.
Version-Release number of selected component (if applicable):
fortune-mod-3.12.0-2.fc36.x86_64
How reproducible:
100%
Steps to Reproduce:
1. man fortune
2. type /record or scroll down
Actual results:
filename-record will precede the records from the file it names.
-n length
Set the longest fortune length (in characters) considered to be
“short” (the default is 160). All fortunes longer than this are
considered “long”. Be careful! If you set the length too short and
ask for short fortunes, or too long and ask for long ones, fortune
goes into a never-ending thrash loop.
-o Choose only from potentially offensive aphorisms. The -o option
is ignored if a fortune directory is specified.
Please, please, please request a potentially offensive fortune if
and only if you believe, deep in your heart, that you are willing
to be offended. (And that you'll just quit using -o rather than
give us grief about it, okay?)
... let us keep in mind the basic governing philosophy of The
Brotherhood, as handsomely summarized in these words: we believe in
healthy, hearty laughter -- at the expense of the whole human race,
if needs be. Needs be.
--H. Allen Smith, "Rude Jokes"
-s Short apothegms only. See -n on which fortunes are considered
“short”.
-i
Ignore case for -m patterns.
Expected results:
filename-record will precede the records from the file it names.
-n length
Set the longest fortune length (in characters) considered to be
“short” (the default is 160). All fortunes longer than this are
considered “long”. Be careful! If you set the length too short and
ask for short fortunes, or too long and ask for long ones, fortune
goes into a never-ending thrash loop.
-o
Choose only from potentially offensive aphorisms. The -o option is
ignored if a fortune directory is specified.
Please, please, please request a potentially offensive fortune if
and only if you believe, deep in your heart, that you are willing
to be offended. (And that you'll just quit using -o rather than
give us grief about it, okay?)
... let us keep in mind the basic governing philosophy of The
Brotherhood, as handsomely summarized in these words: we believe in
healthy, hearty laughter -- at the expense of the whole human race,
if needs be. Needs be.
--H. Allen Smith, "Rude Jokes"
-s
Short apothegms only. See -n on which fortunes are considered
“short”.
-i
Ignore case for -m patterns.
Additional info:
The attached patch only fixes the symptoms, not the root cause.
This should probably be fixed somewhere upstream deep inside the mass of perl
scripts building the man pages.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2107574