From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] reaver: new package
Date: Thu, 12 Apr 2018 13:32:21 +0200 [thread overview]
Message-ID: <20180412133221.2beb022e@windsurf> (raw)
In-Reply-To: <1523524619-25036-1-git-send-email-guillaume.bressaix@gmail.com>
Hello,
Thanks for this new version, looks much better. A few more comments
below, nothing major.
On Thu, 12 Apr 2018 11:16:59 +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 think it would make sense to have this explanation before the
REAVER_SITE variable in the .mk file.
> -N: Guillaume William Brs <guillaume.bressaix@gmail.com>
> +N: Guillaume W. Bres <guillaume.bressaix@gmail.com>
This change is not really related. Is it an intended change? It should
preferably be part of a separate patch.
> F: package/liquid-dsp/
> +F: package/reaver/
Indentation is wrong.
> diff --git a/package/reaver/Config.in b/package/reaver/Config.in
> new file mode 100644
> index 0000000..fed433b
> --- /dev/null
> +++ b/package/reaver/Config.in
> @@ -0,0 +1,10 @@
> +config BR2_PACKAGE_REAVER
> + bool "reaver"
> + select BR2_PACKAGE_LIBPCAP
> +
This empty line is not needed.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-12 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 9:16 [Buildroot] [PATCH 1/1] reaver: new package Guillaume W. Bres
2018-04-12 11:32 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-12 11:44 Guillaume W. Bres
2018-04-12 19:42 ` 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=20180412133221.2beb022e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox