unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo <sdl.web@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Bug-gnulib <bug-gnulib@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: Move sha1 to C?
Date: Tue, 24 May 2011 12:09:22 +0800	[thread overview]
Message-ID: <m1boys68p9.fsf@th041094.ip.tsinghua.edu.cn> (raw)
In-Reply-To: <4DDADB67.1090904@cs.ucla.edu> (Paul Eggert's message of "Mon, 23 May 2011 15:10:47 -0700")

On 2011-05-24 06:10 +0800, Paul Eggert wrote:
> My guess is that's due to a bit of unportable code in gnulib-tool,
> which I just fixed as follows.  Could you please try it again?  If
> that doesn't work, I can push the sha1 gnulib code into the Emacs
> trunk myself, but I'd rather get it working for everybody.  Thanks.

It works smoothly now. BTW, md5sum is not available on OSX. I alias md5
to md5sum and the script seems to run without any problem.

man md5:

----------------

SYNOPSIS
     md5 [-pqrtx] [-s string] [file ...]

DESCRIPTION
     The md5 utility takes as input a message of arbitrary length and produces
     as output a ``fingerprint'' or ``message digest'' of the input.  It is
     conjectured that it is computationally infeasible to produce two messages
     having the same message digest, or to produce any message having a given
     prespecified target message digest.  The MD5 algorithm is intended for
     digital signature applications, where a large file must be ``compressed''
     in a secure manner before being encrypted with a private (secret) key
     under a public-key cryptosystem such as RSA.

     MD5 has not yet (2001-09-03) been broken, but sufficient attacks have
     been made that its security is in some doubt.  The attacks on MD5 are in
     the nature of finding ``collisions'' -- that is, multiple inputs which
     hash to the same value; it is still unlikely for an attacker to be able
     to determine the exact original input given a hash value.

     The following options may be used in any combination and must precede any
     files named on the command line.  The hexadecimal checksum of each file
     listed on the command line is printed after the options are processed.

     -s string
             Print a checksum of the given string.

     -p      Echo stdin to stdout and append the checksum to stdout.

     -q      Quiet mode - only the checksum is printed out.  Overrides the -r
             option.

     -r      Reverses the format of the output.  This helps with visual diffs.
             Does nothing when combined with the -ptx options.

     -t      Run a built-in time trial.

     -x      Run a built-in test script.



  reply	other threads:[~2011-05-24  4:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21  6:37 Move sha1 to C? Leo
2011-05-22 19:04 ` Stefan Monnier
2011-05-22 20:02   ` Leo
2011-05-23  1:23     ` Stefan Monnier
2011-05-23  8:44       ` Leo
2011-05-23 12:04         ` Stefan Monnier
2011-05-23 13:21           ` Leo
2011-05-23 13:27             ` Stefan Monnier
2011-05-23 13:34               ` Leo
2011-05-23 13:57                 ` Stefan Monnier
2011-05-23 18:14                   ` Leo
2011-05-23 19:15                     ` Stefan Monnier
2011-05-23 22:10                     ` Paul Eggert
2011-05-24  4:09                       ` Leo [this message]
2011-05-24 10:01                         ` Eli Zaretskii
2011-05-24 14:24                           ` Leo
2011-05-24 22:01                           ` Richard Stallman
2011-05-24  5:09                       ` Thien-Thi Nguyen
2011-05-23 14:30                 ` Eli Zaretskii
2011-05-23 17:47                   ` Leo
2011-05-23 18:12                     ` Eli Zaretskii
2011-05-23 18:23                       ` Leo
2011-05-23 19:21                         ` Eli Zaretskii
2011-05-23  7:21     ` Eli Zaretskii
2011-05-23  8:30       ` Leo
2011-05-23 15:27         ` Chong Yidong
2011-05-23 17:14           ` Leo
2011-05-23 17:38       ` Leo

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1boys68p9.fsf@th041094.ip.tsinghua.edu.cn \
    --to=sdl.web@gmail.com \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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/emacs.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).