Summary: | dev-lisp/mzscheme-205: fails with stack smashing attack | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Philipp Kern <phil> |
Component: | Hardened | Assignee: | Hardened Gentoo <hardened> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 59507 | ||
Attachments: | portage emerge logfile |
Description
Philipp Kern
2004-05-11 13:10:13 UTC
Created attachment 31208 [details]
portage emerge logfile
well you found an overflow. I don't know lisp for dirt and thus have no idea how to fix this. It turns out that mzscheme is quite sensitive to optimization flags. Even for a fairly sane set, it can cause ill-formed code/segfaults etc. I would recommend reducing your CFLAGS, but I'm going to unset CFLAGS in the ebuild itself and let mzscheme decide what is OK. |