Mailing-List: contact celix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: celix-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of ted.dunning@gmail.com
 designates 74.125.83.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+ULb+vved-wH=4=DKmhvWSvte5FGFSn1etgo5rMxQm8+7Obgw@mail.gmail.com>
References: 
 <CA+ULb+vved-wH=4=DKmhvWSvte5FGFSn1etgo5rMxQm8+7Obgw@mail.gmail.com>
From: Ted Dunning <ted.dunning@gmail.com>
Date: Tue, 20 Nov 2012 12:27:55 -0800
Message-ID: 
 <CAJwFCa3YMQpiWNCoOTNcH9kWgb1Vy5OKtqSDopFB2Kfhz1wnRg@mail.gmail.com>
Subject: Re: Formats of SHA/MD5 checksums
To: general@incubator.apache.org
Cc: celix-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b624940895ddd04cef3136b

--047d7b624940895ddd04cef3136b
Content-Type: text/plain; charset=UTF-8

What does gpg --verify do?

http://www.gnupg.org/download/integrity_check.en.html

On Tue, Nov 20, 2012 at 12:22 PM, Roman Shaposhnik <rvs@apache.org> wrote:

> Turns out, this is the output of gpg and it seems that
> there's no way to ask gpg to verify it (unlike -c for md5sum lets
> say). Worse yet, because of the spaces it is not
> easy to reconcile the output with the more typical
> md5sum one.
>

--047d7b624940895ddd04cef3136b--