From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add eschalot.
Date: Tue, 6 Sep 2016 17:22:30 -0400 [thread overview]
Message-ID: <20160906212230.GA3304@jasmine> (raw)
In-Reply-To: <87y43ep034.fsf@we.make.ritual.n0.is>
On Tue, Aug 30, 2016 at 06:45:35PM +0000, ng0 wrote:
> From 5eea0ec3a7b1f94912f18e32d3e9bedff64f3ecb Mon Sep 17 00:00:00 2001
> From: ng0 <ng0@we.make.ritual.n0.is>
> Date: Fri, 26 Aug 2016 15:41:33 +0000
> Subject: [PATCH] gnu: Add eschalot.
>
> * gnu/packages/crypto.scm (eschalot): New variable.
Pushed!
> + (source
> + (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/schnabear/eschalot")
> + (commit commit)))
I added a (file-name) field.
> + (replace 'check
> + (lambda _
> + (zero? (system* "./worgen" "8-12" "top1000.txt" "3-10" "top400nouns.txt"
> + "3-6" "top150adjectives.txt" "3-6"))
> + (zero? (system* "./eschalot" "-r" "^guix|^guixsd"))
> + (zero? (system* "./eschalot" "-r" "^gnu|^free"))
> + (zero? (system* "./eschalot" "-r" "^cyber|^hack"))
> + (zero? (system* "./eschalot" "-r" "^troll"))))
I wrapped all these (zero? ...) in (and).
> + (description
> + "Eschalot is a tor hidden service name generator, it allows one to produce
> +customized vanity .onion addresses using a brute-force method.
> +Searches for valid names can be run with regular expressions and wordlists, for
> +the generation of wordlists the included tool @code{worgen} can be used.
And I split this sentence into two sentences.
prev parent reply other threads:[~2016-09-06 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 15:49 [PATCH] gnu: Add eschalot ng0
2016-08-30 7:11 ` Leo Famulari
2016-08-30 11:01 ` ng0
2016-08-30 11:09 ` ng0
2016-08-30 17:34 ` Eric Bavier
2016-08-30 18:45 ` ng0
2016-09-06 21:22 ` Leo Famulari [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=20160906212230.GA3304@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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).