Build also fails with gcc 14 now: _ruamel_yaml.c: In function '__pyx_pf_6ruamel_4yaml_4clib_12_ruamel_yaml_8CEmitter___init__': _ruamel_yaml.c:16882:53: error: passing argument 2 of 'yaml_emitter_set_output' from incompatible pointer type [-Wincompatible-pointer-types] 16882 | yaml_emitter_set_output((&__pyx_v_self->emitter), __pyx_f_6ruamel_4yaml_4clib_12_ruamel_yaml_output_handler, ((void *)__pyx_v_self)); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | | int (*)(void *, char *,...
build failure with openssl 3.0
parallel build fatal error: soapcpp2_yacc.h: No such file or directory
Aret here any fixes for CVE-2019-12212 and CVE-2019-12214?
Thank you very much!
I am aware that there more issues. The point is that it is difficult to fix production systems at current state. Backporting patches also require some work since each commit includes changelog and version string change. Those hunks needs to be manually removed to be able to apply the patch which the actual fix. I did a handful fixes but gave up when I got to png.c. I though that it would be easier for you to tag a new release than ti would be for me to try manually backport 20-30 patches for png.c....
Please make a 1.3.27 release for security fixes
make check fails in testrsa on x86_64 alpine linux
Also, this looks like it fixes an interger overflow vulnerability (if the int is unsigned), and if that is the case, then a user with 2.8.50 may wrongly believe that he/she is not vulnerable, depending on when the 2.8.50 release was downloaded.
checksum of 2.8.50 zip changed
Better (untested) variant, without mutex, using getpwuid_r, which also deals with the situation that the euid does not exist: diff --git a/src/tspi/ps/tspps.c b/src/tspi/ps/tspps.c index b5e83d0..4874509 100644 --- a/src/tspi/ps/tspps.c +++ b/src/tspi/ps/tspps.c @@ -51,9 +51,6 @@ static int user_ps_fd = -1; static MUTEX_DECLARE_INIT(user_ps_lock); -#if (defined (__FreeBSD__) || defined (__OpenBSD__)) -static MUTEX_DECLARE_INIT(user_ps_path); -#endif static struct flock fl; @@ -66,9 +63,7 @@ get_user_ps_path(char...
Something like: diff --git a/src/tspi/ps/tspps.c b/src/tspi/ps/tspps.c index b5e83d0..838522c 100644 --- a/src/tspi/ps/tspps.c +++ b/src/tspi/ps/tspps.c @@ -51,9 +51,7 @@ static int user_ps_fd = -1; static MUTEX_DECLARE_INIT(user_ps_lock); -#if (defined (__FreeBSD__) || defined (__OpenBSD__)) static MUTEX_DECLARE_INIT(user_ps_path); -#endif static struct flock fl; @@ -66,9 +64,6 @@ get_user_ps_path(char **file) TSS_RESULT result; char *file_name = NULL, *home_dir = NULL; struct passwd *pwp; -#if...
Apparently getpwent_r is not re-entrant. From man page: The function getpwent_r() is not really reentrant since it shares the reading position in the stream with all other threads. http://man7.org/linux/man-pages/man3/getpwent_r.3.html#NOTES I think it might be wise to simply drop the #if (defined(__linux) .....) and #if (defined (__FreeBSD__) || ...) and always use the mutex and posix compatible getpwent.
Ok, i found in in NEWS: * Remove unnecessary duplicate EGifClose() in gifcolor.c....
Which version of gitlib has the fix? Do you have a link to the exact commit(s) that...
works for musl libc too. thanks!
Fix build with musl libc
Thank you for looking into it. Unfortunally it sill dont build due to the following...
I will try these steps. - read the source of musl libc and search other useful function....
aufs-utils fails to build with musl libc due to use of non-standard FTW_ACTIONRETVAL
[PATCH] fix error_at_line() support for musl libc
bad use of __LITTLE_ENDIAN macor in src/main/print-olympus.c
Create new release
unsquashfs segfaults with musl libc due to stack overflow
hwclock now sends help to stderr.
Fix autodetection of lxc
[PATCH] fails to build with musl libc due to use of non-standard u_int32_t
[PATCH] fails to build with musl libc due to use of non-standard unsigned