From: Boyd Roberts <boyd@strakt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] passtokey question
Date: Thu, 12 Dec 2002 11:13:54 +0100 [thread overview]
Message-ID: <3DF86162.9000900@strakt.com> (raw)
In-Reply-To: <20021212055735.A2709@unicorn.math.spbu.ru>
Roman V. Shaposhnick wrote:
>On the similar note, why did you chose to re-encode parts of t with
>a previous key, and not some other way of stuffing long passwords
>into 7bytes long DES key ?
>
This was probably done to reduce the the possibility that the
key would be limited to typeable/printable ASCII. Any limit
of the keyspace will make brute forcing easier.
next prev parent reply other threads:[~2002-12-12 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 2:57 Roman V. Shaposhnick
2002-12-12 10:13 ` Boyd Roberts [this message]
2002-12-12 3:25 presotto
2002-12-12 5:14 ` Roman V. Shaposhnick
2002-12-12 14:06 presotto
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=3DF86162.9000900@strakt.com \
--to=boyd@strakt.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).