b2756e3519
Fix for CVE-2018-15863, CVE-2018-15863, CVE-2018-15859, CVE-2018-15853 (bsc#1105832)
slfo-1.2
Stefan Dirsch
2025-12-10 15:48:04 +01:00
23bed497f0
Fix for CVE-2018-15863/CVE-2018-15861/CVE-2018-15859/CVE-2018-15853 (bsc#1105832)
slfo-main
Stefan Dirsch
2025-12-10 15:45:06 +01:00
f92f84bda7
- This releases contains the fixes for the issues reported in today's security advisory: https://lists.x.org/archives/xorg-announce/2025-December/003644.html * CVE-2018-15863 (bsc#1105832) * CVE-2018-15861 (bsc#1105832) * CVE-2018-15859 (bsc#1105832) * CVE-2018-15853 (bsc#1105832) Note that the year is not a typo, these CVEs have been reported previously for libxkbcommon but the same code exists in xkbcomp and required the same fixes. As a new feature in this version: xkbcomp now supports the meson build system in addition to autotools. autotools support may be removed in a future version. - switch to meson build
Stefan Dirsch2025-12-10 13:30:05 +00:00
1cdd0c606c
Accepting request 1144053 from X11:XOrg
Ana Guerrero2024-02-06 15:32:30 +00:00
3769c0b2c7
Accepting request 1144053 from X11:XOrg
Ana Guerrero2024-02-06 15:32:30 +00:00
cd93384f8c
- update to 1.4.7 * This release mainly focuses on code cleanup and improving maintainability and making static analysis work better on this code base. It also fixes a bug that could cause build failures with gcc when the -ftracer option was used.
Stefan Dirsch2024-02-04 21:08:32 +00:00
e9a1b988e7
- update to 1.4.7 * This release mainly focuses on code cleanup and improving maintainability and making static analysis work better on this code base. It also fixes a bug that could cause build failures with gcc when the -ftracer option was used.
Stefan Dirsch2024-02-04 21:08:32 +00:00
1f67e8c163
Accepting request 889729 from home:dirkmueller:Factory
Stefan Dirsch2021-05-02 20:43:14 +00:00
20b1c38527
Accepting request 889729 from home:dirkmueller:Factory
Stefan Dirsch2021-05-02 20:43:14 +00:00
8f97f0ae4a
Accepting request 879661 from X11:XOrg
Richard Brown
2021-03-19 15:40:19 +00:00
5adfa469c1
Accepting request 879661 from X11:XOrg
Richard Brown
2021-03-19 15:40:19 +00:00
fc027494f1
- Update to version 1.4.5 * Remove trailing whitespaces * gitlab CI: add basic build test * Replace WARN[1-9], ERROR[1-9], etc. with their unnumbered version * Downgrade the warning for missing symbols to info * keycodes: downgrade the >255 keycode warning to an info * keycodes: compress the high keycode warning
Stefan Dirsch2021-03-17 10:37:59 +00:00
8645cdb1e2
- Update to version 1.4.5 * Remove trailing whitespaces * gitlab CI: add basic build test * Replace WARN[1-9], ERROR[1-9], etc. with their unnumbered version * Downgrade the warning for missing symbols to info * keycodes: downgrade the >255 keycode warning to an info * keycodes: compress the high keycode warning
Stefan Dirsch2021-03-17 10:37:59 +00:00
57dca5155b
- Update to version 1.4.4 * Fix spelling/wording issues * Fix lockdevbtn to be XkbSA_LockDeviceBtn action * For -R and after chdir, add the current directory to the path * Don't pretend unresolved symbols are an error
Stefan Dirsch2020-11-05 09:52:08 +00:00
c34ded4a86
- Update to version 1.4.4 * Fix spelling/wording issues * Fix lockdevbtn to be XkbSA_LockDeviceBtn action * For -R and after chdir, add the current directory to the path * Don't pretend unresolved symbols are an error
Stefan Dirsch2020-11-05 09:52:08 +00:00
df794ccdba
- Update to version 1.4.3 * Update configure.ac bug URL for gitlab migration * configure: Remove unused AC_SUBST([REQUIRED_MODULES]) * pkgconfig: Remove unneeded Requires.private * Suppress high-keycode warnings at the default warning level * xkbcomp Fix missing support for "affect" and incorrect modifier handling for ISOLock * Don't compare with string literals * Fix invalid error report on F_Accel field * Error out if we have no default path
Stefan Dirsch2020-02-21 12:57:59 +00:00
edb7115edd
- Update to version 1.4.3 * Update configure.ac bug URL for gitlab migration * configure: Remove unused AC_SUBST([REQUIRED_MODULES]) * pkgconfig: Remove unneeded Requires.private * Suppress high-keycode warnings at the default warning level * xkbcomp Fix missing support for "affect" and incorrect modifier handling for ISOLock * Don't compare with string literals * Fix invalid error report on F_Accel field * Error out if we have no default path
Stefan Dirsch2020-02-21 12:57:59 +00:00
a83c298388
Accepting request 615212 from X11:XOrg
Yuchen Lin2018-06-15 12:33:37 +00:00
87c0a1c081
Accepting request 615212 from X11:XOrg
Yuchen Lin2018-06-15 12:33:37 +00:00
12c663642f
- Update to version 1.4.2 * Only one patch, fixing keymap compilation errors when the keycodes maximum is set to a value above the permitted X11 maximum of 255. While we already ignored keys with codes above 255, we still failed on the maximum=374; line that xkeyboard-config 2.24 produces now.
Stefan Dirsch2018-06-08 10:52:38 +00:00
563ca1acd5
- Update to version 1.4.2 * Only one patch, fixing keymap compilation errors when the keycodes maximum is set to a value above the permitted X11 maximum of 255. While we already ignored keys with codes above 255, we still failed on the maximum=374; line that xkeyboard-config 2.24 produces now.
Stefan Dirsch2018-06-08 10:52:38 +00:00
0ac3051193
- Update to version 1.4.1 * This release adds the path of the xkbcomp executable to the pkgconfig data, allowing the X server to find the right binary regardless of where its (the X servers) $prefix is pointed. Without this the X server will guess that xkbcomp is configured for the same prefix; since the default prefix is /usr/local, and your distribution certainly did not install xkbcomp there, 'make check' and 'ninja dist' for the X server build would fail because Xvfb would not start. - supersedes U_xkbcomp_pkgconfig-add-bindir.patch - refreshed xkbcomp.keyring; seems signing key changed, since this time the package has been released by Adam Jackson (before: Daniel Stone)? Hope I got this right ...
Stefan Dirsch2018-03-05 15:08:56 +00:00
c0a72cc43e
- Update to version 1.4.1 * This release adds the path of the xkbcomp executable to the pkgconfig data, allowing the X server to find the right binary regardless of where its (the X servers) $prefix is pointed. Without this the X server will guess that xkbcomp is configured for the same prefix; since the default prefix is /usr/local, and your distribution certainly did not install xkbcomp there, 'make check' and 'ninja dist' for the X server build would fail because Xvfb would not start. - supersedes U_xkbcomp_pkgconfig-add-bindir.patch - refreshed xkbcomp.keyring; seems signing key changed, since this time the package has been released by Adam Jackson (before: Daniel Stone)? Hope I got this right ...
Stefan Dirsch2018-03-05 15:08:56 +00:00
da66b4be7c
- Update to version 1.4.0 * This xkbcomp release mostly contains a couple of bugfixes and parser improvements. Notably, ignoring keycodes that X11 can never support means that we can start using those keycodes, which xkbcommon supports. - refreshed xkbcomp.keyring; seems signing key changed, since this time the package has been released by Daniel Stone (before: Peter Hutterer)? Hope I got this right ...
Stefan Dirsch2017-05-05 10:41:04 +00:00
fab4beb794
- Update to version 1.4.0 * This xkbcomp release mostly contains a couple of bugfixes and parser improvements. Notably, ignoring keycodes that X11 can never support means that we can start using those keycodes, which xkbcommon supports. - refreshed xkbcomp.keyring; seems signing key changed, since this time the package has been released by Daniel Stone (before: Peter Hutterer)? Hope I got this right ...
Stefan Dirsch2017-05-05 10:41:04 +00:00
92cd687eb4
Accepting request 344219 from home:pluskalm:branches:X11:XOrg
Stefan Dirsch2015-11-13 12:48:44 +00:00
37198c20ea
Accepting request 344219 from home:pluskalm:branches:X11:XOrg
Stefan Dirsch2015-11-13 12:48:44 +00:00
0166d4c216
- Update to version 1.3.1 * Couple of minor fixes, the only user-visible change is that the warning when a key type is shortened is now on a verbosity level above the default verbosity. This effectively removes the warning below for all users of the german keyboard layout (and others): Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
Stefan Dirsch2015-11-10 13:08:58 +00:00
237f8f4882
- Update to version 1.3.1 * Couple of minor fixes, the only user-visible change is that the warning when a key type is shortened is now on a verbosity level above the default verbosity. This effectively removes the warning below for all users of the german keyboard layout (and others): Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
Stefan Dirsch2015-11-10 13:08:58 +00:00
Ana Guerrero
Stefan Dirsch
Stefan Dirsch
Dominique Leuenberger
Richard Brown
Yuchen Lin
Stephan Kulow
Factory Maintainer