lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 3 Jun 2016 22:16:06 -0700
From:	Andy Lutomirski <>
To:	Kees Cook <>,
	"" <>
Subject: SIGSYS annoyance

Should SIGSYS be delivered to the handler even if blocked?  What, if
anything, does POSIX say?  All I can find is in pthread_sigmask(3p):

If any of the SIGFPE, SIGILL, SIGSEGV, or SIGBUS signals are generated
while they are blocked, the result is undefined, unless the signal was
generated by the action of another process, or by one of the functions
kill(), pthread_kill(), raise(), or sigqueue().

It would be easy enough to change our behavior so that we deliver the
signal even if it's blocked or to at least add a flag so that users
can request that behavior.

Powered by blists - more mailing lists