From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: Jack Hill <jackhill@jackhill.us>
Cc: 40203@debbugs.gnu.org
Subject: [bug#40203] [PATCH] gnu: Add ROPgadget.
Date: Tue, 24 Mar 2020 17:34:48 +0100 [thread overview]
Message-ID: <20200324163448.fhjxatikhb7yovj2@gravity> (raw)
In-Reply-To: <alpine.DEB.2.20.2003241115350.5735@marsh.hcoop.net>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
On Tue, Mar 24, 2020 at 11:18:05AM -0400, Jack Hill wrote:
> On Tue, 24 Mar 2020, Jakub Kądziołka wrote:
>
> [snip]
>
> > + (description
> > + "This tool lets you search for gadgets in binaries to help with ROP
> > +chain construction.")
>
> Perhaps we should expand what ROP means here. I as able to figure it out
> with some searching, but it would probably help non-domain experts know what
> this package is for.
Thanks, I totally forgot about non-domain experts when writing that
description. What do you think about this revised version?
(synopsis "Semiautomatic return oriented programming")
(description
"This tool lets you search for @acronym{ROP, Return Oriented Programming}
gadgets in binaries. Some facilities are included for automatically generating
chains of gadgets to execute system calls.")
Also, is the file in which I've put this package right? I choose that
place because that's where radare2 is, and it has a relatively
similar purpose. However, radare2 is a loose fit already, so ROPgadget
would be two steps removed from the original purpose of the file...
Regards,
Jakub Kądziołka
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-03-24 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 23:52 [bug#40203] [PATCH] gnu: Add ROPgadget Jakub Kądziołka
2020-03-24 15:18 ` Jack Hill
2020-03-24 16:34 ` Jakub Kądziołka [this message]
2020-03-24 16:53 ` Jack Hill
2020-03-26 21:55 ` [bug#40203] [PATCH v2] " Jakub Kądziołka
2020-03-26 22:26 ` bug#40203: Done: " Jakub Kądziołka
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200324163448.fhjxatikhb7yovj2@gravity \
--to=kuba@kadziolka.net \
--cc=40203@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).