xenocara xlock uses imsg for privsep.
What changes:
- imsg_init becomes imsgbuf_init but imsgbuf_init can now fail
- Adding imsgbuf functions to hide the msgbuf functions:
msgbuf_clear -> imsgbuf_clear
msgbuf_write -> imsgbuf_write
- Also rename imsg_read to imsgbuf_read.
- Both imsgbuf_read and imsgbuf_write have simplified error handling.
imsgbuf_write now returns 0 on success so that old wrong connection
closed check must be removed
- Remove now official ibuf_get_string()
OK tb@ matthieu@
Don't log DDC modelines (after hotplug events/xrandr) or "Using XX ranges
from config file" messages. These were printed after hotplug events which
could be frequent in some cases (I have machines where this happens every
10 seconds when the monitor is in a dpms power-saving mode resulting in a
full /var/log filesystem).
EDID vendor/product ID still logged, giving an indication that events are
happening, but reduced from ~3.5KB per event to <100 bytes.
based on a diff from / ok matthieu@
xkb: Fix buffer overflow in _XkbSetCompatMap()
The _XkbSetCompatMap() function attempts to resize the `sym_interpret`
buffer.
However, It didn't update its size properly. It updated `num_si` only,
without updating `size_si`.
CVE-2024-9632
from matthieu@
this is errata/7.5/012_xserver.patch.sig
xkb: Fix buffer overflow in _XkbSetCompatMap()
The _XkbSetCompatMap() function attempts to resize the `sym_interpret`
buffer.
However, It didn't update its size properly. It updated `num_si` only,
without updating `size_si`.
CVE-2024-9632
from matthieu@
this is errata/7.6/002_xserver.patch.sig
xkb: Fix buffer overflow in _XkbSetCompatMap()
The _XkbSetCompatMap() function attempts to resize the `sym_interpret`
buffer.
However, It didn't update its size properly. It updated `num_si` only,
without updating `size_si`.
CVE-2024-9632