unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: phodina <phodina@protonmail.com>
Cc: 59760@debbugs.gnu.org
Subject: [bug#59760] [PATCH] gnu: Add ncrack.
Date: Mon, 16 Jan 2023 09:13:22 -0500	[thread overview]
Message-ID: <878ri2bm9p.fsf@gmail.com> (raw)
In-Reply-To: <WSgbTIT-0EVw00x79M1C4IoJnu497WH90q_x9HrwP736-BdOVcs0KaKNx9tcSaZu3u7jA6G8tnr7tsS9eUcIwrh3_DziU2imKAVbzDkx0Xo=@protonmail.com> (phodina@protonmail.com's message of "Fri, 02 Dec 2022 05:21:28 +0000")

Hi Petr,

phodina <phodina@protonmail.com> writes:

> Hi,
>
> here's another penetration testing tool - ncrack. Slowly catching up to Kali :-)
>
> ----
> Petr
> From cfcc719c2fc2e40fb2936269dc4bdbd28be5d71a Mon Sep 17 00:00:00 2001
> From: Petr Hodina <phodina@protonmail.com>
> Date: Fri, 10 Jun 2022 10:26:13 +0200
> Subject: [PATCH] gnu: Add ncrack.

Neat, thank you!

[...]

> * gnu/packages/patches/ncrack-fix-spelling-errors.patch: New file.
> * gnu/packages/patches/ncrack-nullcheck.patch: New file.
> * gnu/packages/patches/ncrack-unbundle-opensshlib.patch: New file.

The patches above have unclear upstream status; could you annotate the
files with the information?  They should be submitted upstream for
consideration.  For upstream to consider your last patch though, you'd
want to have the opensshlib patch configurable via a configure.ac check
or option.  It could for example check for a system-provided opensshlib
and use this, else fall-back to the bundled library build that it
currently does.

> diff --git a/gnu/packages/networking.scm b/gnu/packages/networking.scm
> index 3f44d082fb..ce004c52f0 100644
> --- a/gnu/packages/networking.scm
> +++ b/gnu/packages/networking.scm
> @@ -786,6 +786,35 @@ (define-public knockd
>  at the link-layer level.")
>      (license license:gpl2+)))
>  
> +(define-public ncrack
> +  (package
> +    (name "ncrack")
> +    (version "0.7")
> +    (source (origin
> +              (method url-fetch)
> +              (uri (string-append
> +                    "https://github.com/nmap/ncrack/archive/refs/tags/"
> +                    version ".tar.gz"))
> +              (patches (search-patches "ncrack-nullcheck.patch"
> +                                       "ncrack-fix-gcc-10-build.patch"
> +                                       "ncrack-fix-autotools-compat.patch"
> +                                       "ncrack-fix-spelling-errors.patch"))
> +              (sha256
> +               (base32
> +                "0jnif319rjykiphi211v1c2hblw1ql190dnbd030qjkwcz6p3ygk"))))
> +    (build-system gnu-build-system)
> +    (arguments
> +     (list #:tests? #f)) ;no test suite
> +    (native-inputs (list pkg-config))
> +    (inputs (list openssl zlib))
> +    (home-page "https://nmap.org/ncrack/man.html")
> +    (synopsis "Network authentication cracking tool")
> +    (description
> +     "@code{Ncrack} is a tool for network authentication cracking.  It was

To be more accurate, I'd use "The @command{ncrack} command is a tool for
[...]".

Otherwise, LGTM.

-- 
Thanks,
Maxim




      reply	other threads:[~2023-01-16 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02  5:21 [bug#59760] [PATCH] gnu: Add ncrack phodina via Guix-patches via
2023-01-16 14:13 ` Maxim Cournoyer [this message]

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=878ri2bm9p.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=59760@debbugs.gnu.org \
    --cc=phodina@protonmail.com \
    /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).