3 ms·
Why is that a security hole? I suppose it might make it harder to detect an existing one, but it doesn't add a security hole in it's own right.
by ars 17y ago
Why is that a security hole? I suppose it might make it harder to detect an existing one, but it doesn't add a security hole in it's own right.
- humbledrone 17y agoAccording to POSIX, after a SIGSEGV, the state of the program is undefined. This is the reason that a SIGSEGV usually causes an immediate abort. Allowing a program to execute when its state is undefined is a huge security hole.