All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: linux-gcc@vger.kernel.org
Subject: Generating shellcode at compile time
Date: Wed, 15 Dec 2004 22:55:15 -0500	[thread overview]
Message-ID: <41C10723.5070604@comcast.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I need to generate some sort of strcpy()able shell code.  Probably
something to do

_exit(255);

would be quite enough; though more in-depth demonstrations would benefit
from being able to actually display a live exploit.  Something like
calling exec("/bin/bash") for example.

I'm working on an x86-64, but would like to be able to demonstrate
exploits and what PaX and the IBM stack smash protector do to stop them
on x86-64, x86, SPARC, PPC, SPARC64, and PPC64.

In the worst case, each shellcode could be individually created and
passed as a reaction to having the example daemon reveal the host type
(which may be useful in dual-host demonstrations where I could exploit a
PPC with an x86); however, I have not the time nor the need to invest my
time in generating such shellcode myself.

I'm not so sure what I want to do, but _exit(255) is fine for my
regression tests.

- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBwQcjhDd4aOud5P8RAl+vAJ40ThT0vaa3iyhCp/EgwsNhYp/8nQCfdVpU
Xv/XTZSogpCMgBI/j0mxqa8=
=5SD4
-----END PGP SIGNATURE-----

                 reply	other threads:[~2004-12-16  3:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41C10723.5070604@comcast.net \
    --to=nigelenki@comcast.net \
    --cc=linux-gcc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.