On 1 Apr 2014, at 15:25, Stefan Winter <stefan.winter@restena.lu> wrote:
Hi,
I had the yama problem on ubuntu, and poking the relevant file in the yama subdir solved it. But if you're not running yama... hmm.
OK, someone reporting *exactly* the same problem back in 2008 on the GBD list.
Here is the fix they helpfully posted: https://www.sourceware.org/ml/gdb/2008-01/msg00246.html
Here's the original message: http://lists.gnu.org/archive/html/bug-gdb/2008-01/msg00002.html
Googlefoo!
suid? Well, worth a try, so I did - but I still get the same problem.
It's also a bit awkward: if this were a default kernel security measure, would it not *consistently* fail to work on all recent Linuxes? Am I the only one using the default "production system" panic_action?
It works fine for me on OSX (10.9.1) and the the yama detection disabled on ubuntu 13.07. We've used it at customer sites to send out automatic emails when the hosts have gone down with the backtraces, and it seems to work there too (ubuntu 12.04). Not really sure what else to suggest, sorry. -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2