From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/rainbowcrack/
Date: Fri, 10 Jan 2020 11:30:33 +0000 (UTC) [thread overview]
Message-ID: <1578655825.bef4fa1b5b4f3aabde456b841b5fcd2ded15f1fa.marecki@gentoo> (raw)
commit: bef4fa1b5b4f3aabde456b841b5fcd2ded15f1fa
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 10 11:27:27 2020 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Fri Jan 10 11:30:25 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bef4fa1b
app-crypt/rainbowcrack: fix typo in longdescription
Package-Manager: Portage-2.3.79, Repoman-2.3.16
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
app-crypt/rainbowcrack/metadata.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-crypt/rainbowcrack/metadata.xml b/app-crypt/rainbowcrack/metadata.xml
index 34713955e52..f4f61b37c8f 100644
--- a/app-crypt/rainbowcrack/metadata.xml
+++ b/app-crypt/rainbowcrack/metadata.xml
@@ -6,7 +6,7 @@
<name>Marek Szuba</name>
</maintainer>
<longdescription>
- RainbowCrack is a general propose implementation of Philippe Oechslin's faster time-memory trade-off technique.
+ RainbowCrack is a general-purpose implementation of Philippe Oechslin's faster time-memory trade-off technique.
In short, the RainbowCrack tool is a password cracker. A traditional brute force cracker try all possible
plaintexts one by one in cracking time. It is time consuming to break complex password in this way. The idea of
time-memory trade-off is to do all cracking time computation in advance and store the result in files so called
next reply other threads:[~2020-01-10 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 11:30 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-27 22:44 [gentoo-commits] repo/gentoo:master commit in: app-crypt/rainbowcrack/ Marek Szuba
2021-02-15 12:39 Marek Szuba
2021-01-22 16:53 Agostino Sarubbo
2020-10-07 16:16 Marek Szuba
2020-03-20 8:59 Agostino Sarubbo
2020-03-18 17:14 Marek Szuba
2020-01-10 11:30 Marek Szuba
2019-03-20 22:00 Alon Bar-Lev
2018-11-28 14:32 Alon Bar-Lev
2017-03-25 21:46 Alon Bar-Lev
2017-02-04 21:40 Alon Bar-Lev
2016-06-12 13:41 Alon Bar-Lev
2015-12-23 13:50 Alon Bar-Lev
2015-12-23 13:50 Alon Bar-Lev
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=1578655825.bef4fa1b5b4f3aabde456b841b5fcd2ded15f1fa.marecki@gentoo \
--to=marecki@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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