From: pageexec@freemail.hu
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] 2.6.27-hardened-r8: assassination
Date: Fri, 06 Mar 2009 19:28:17 +0200 [thread overview]
Message-ID: <49B16B41.31874.18849D3B@pageexec.freemail.hu> (raw)
In-Reply-To: <20090306151313.GB1926@home.power>
On 6 Mar 2009 at 17:13, Alex Efros wrote:
> Two questions:
> 1) Is "2.6.28.7 and PaX alone" mean hardened-sources-2.6.28 with
> everything except PaX switched off, or vanilla-sources-2.6.28.7 manually
> patched with latests PaX?
it's always the latter ;), i need to make sure it's a PaX problem.
> 2) I'm perl programmer, not C. So I need more detailed instructions (list
> of commands to run) how to "get coredumps and analyze them for the usual
> things". Probably this info already available somewhere, so url to this
> doc will be enough.
i mentioned them quite a few times on the list and bugzilla and the grsec forums,
here it is again. first, the coredump: you enable coredumps in your shell
(ulimit -c unlimited) then run your program that crashes. this will produce
a coredump file that you load into gdb and then issue the following gdb commands:
bt
x/8i $pc
x/8x $sp
info reg
> As for strace - did that, it helps me detect .so libraries (Ioncube and
> ZendOptimizer) because of which apache was killed.
on a second thought, i'd need the strace output regardless of the gdb analysis,
just to see how text relocations went as that's where the problem is probably.
next prev parent reply other threads:[~2009-03-06 18:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 3:57 [gentoo-hardened] 2.6.27-hardened-r8: assassination Alex Efros
2009-03-06 7:11 ` Alex Efros
2009-03-06 7:15 ` pageexec
2009-03-06 15:13 ` Alex Efros
2009-03-06 17:28 ` pageexec [this message]
2009-03-06 21:51 ` Alex Efros
2009-03-06 21:12 ` pageexec
2009-03-06 22:57 ` Alex Efros
2009-03-06 23:25 ` Ned Ludd
2009-03-06 23:46 ` Alex Efros
2009-03-19 14:50 ` pageexec
2009-03-19 16:46 ` John Eckhart
2009-03-20 22:31 ` pageexec
2009-03-21 15:12 ` atoth
2011-03-08 18:40 ` Alex Efros
2011-03-08 19:05 ` Mike Frysinger
2011-03-08 19:52 ` Alex Efros
2011-03-08 20:01 ` Mike Frysinger
2011-03-08 20:48 ` klondike
2011-03-08 20:49 ` Anthony G. Basile
2011-03-08 20:55 ` Mike Frysinger
2011-03-09 9:03 ` pageexec
2011-03-10 20:30 ` Anthony G. Basile
2011-03-10 20:39 ` Anthony G. Basile
2011-03-08 21:07 ` Alex Efros
2011-03-09 13:07 ` med
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49B16B41.31874.18849D3B@pageexec.freemail.hu \
--to=pageexec@freemail.hu \
--cc=gentoo-hardened@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox