All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] reaver: new package
Date: Thu, 12 Apr 2018 21:42:18 +0200	[thread overview]
Message-ID: <20180412214218.3dea90d7@windsurf> (raw)
In-Reply-To: <1523533473-20081-1-git-send-email-guillaume.bressaix@gmail.com>

Hello,

On Thu, 12 Apr 2018 13:44:33 +0200, Guillaume W. Bres wrote:
> Reaver is a tool to audit networks against brute WPS pins attacks.
> 
> It is a generic autotools package, easy to build. Tests passed for the 7 default
> toolchains. 
> 
> It is mandantory to use the github.com/t6x fork that I set in reaver.mk
> at the moment because other versions/repos of this project won't cross-compile.
> Their makefiles are pretty outdated. It is the only updated and regularly maintained
> repo that I found for this project at the moment.
> 
> I added an extra mention about this in package/reaver/reaver.mk
> as suggested by Thomas. I also removed other non related modifications.

You shouldn't put the changelog inside the commit log... but rather

> 
> Signed-off-by: Guillaume W. Bres <guillaume.bressaix@gmail.com>
> ---

here, below the "---" mark.

So, I've adjusted a bit the commit log, rewrapped the Config.in help
text where the lines were too short, and applied to master.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-04-12 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 11:44 [Buildroot] [PATCH 1/1] reaver: new package Guillaume W. Bres
2018-04-12 19:42 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-12  9:16 Guillaume W. Bres
2018-04-12 11:32 ` Thomas Petazzoni

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=20180412214218.3dea90d7@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.