From: Petr Baudis <pasky-AlSwsSmVLrQ@public.gmane.org>
To: Paul A Sand <pas-JNhspZqLHXk@public.gmane.org>
Cc: mtk-manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Bug in crypt(3) man page
Date: Sun, 6 Jun 2010 12:44:55 +0200 [thread overview]
Message-ID: <20100606104455.GF16800@machine.or.cz> (raw)
In-Reply-To: <20100605114404.GA30106-gUudzVX/zFgk2GylmosdeQ@public.gmane.org>
On Sat, Jun 05, 2010 at 07:44:05AM -0400, Paul A Sand wrote:
> Hi --
>
> I have version 3.23 of man-pages (Fedora 13). At the very
> end of 'Glibc Notes' of crypt(3):
>
> In the SHA implementation the entire key is significant
> (instead of only the first 8 bytes in MD5).
>
> I'm pretty sure that's incorrect. I think both MD5 and SHA implementations
> use the whole key, and the 8-byte significance restriction is
> applies to (just) the original DES.
Thanks, this shold be already fixed in the git version.
> The man page also may be incorrect with the max salt lengths.
> I think this is eight bytes for MD5, 16 for SHA-256 and SHA-512.
> (The page implies 16 for MD5 too.)
I think the manpage is not strictly wrong here, though it could be more
detailed; patches are welcome.
--
Petr "Pasky" Baudis
The true meaning of life is to plant a tree under whose shade
you will never sit.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-06-06 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 11:44 Bug in crypt(3) man page Paul A Sand
[not found] ` <20100605114404.GA30106-gUudzVX/zFgk2GylmosdeQ@public.gmane.org>
2010-06-06 10:44 ` Petr Baudis [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100606104455.GF16800@machine.or.cz \
--to=pasky-alswssmvlrq@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk-manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pas-JNhspZqLHXk@public.gmane.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;
as well as URLs for NNTP newsgroup(s).