X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:subject:references:date:in-reply-to :message-id:mime-version:content-type; q=dns; s=default; b=n1s2i YxCMxljQ04t9qeOG6btYuOz5RTMfoyYamSz1luZbGq0IZZPele7TT0XEvEU8u1ZL D3rLwO+RnQoRvh6IknSHowK6r3PrUzbSr066/H36yrEEFdkzImc+QPWDSj757lpO pHyGUa7vdp8mV4hKRV+P0HmXyMevDWpGFMJcxk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:subject:references:date:in-reply-to :message-id:mime-version:content-type; s=default; bh=0EvW80+69vJ TMdGFBfee70ZjlD4=; b=vt7pcF+liOmm9hZkJWbz3my3TkFGUauK7iKAX85Bsvk Th71UkQrKvEVUxeL7SIZb6h1OYK6T0InavaB+0xaU3j/PG7wgOpap1gFF/XxxLvN haFtSEevkTObVVMhnbHbPINuNbKCNIgWOUg0jBm83EqL1AbX3nSHJikuugQiaPN4 = Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-in-02.arcor-online.net X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-17.arcor-online.net 7ACD1CBC2C From: Achim Gratz To: cygwin AT cygwin DOT com Subject: Re: setup.exe bad signatures? References: <0A03B892A1F8E14C8D9E8DCB832005284FEEFF2A AT EX2010-MAIL1 DOT WIZARD DOT PVT> Date: Wed, 26 Feb 2014 20:13:57 +0100 In-Reply-To: <0A03B892A1F8E14C8D9E8DCB832005284FEEFF2A@EX2010-MAIL1.WIZARD.PVT> (Michael Ryan's message of "Wed, 26 Feb 2014 03:09:04 +0000") Message-ID: <87ppm9k7pm.fsf@Rainer.invalid> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Michael Ryan writes: > I'm trying to verify the signatures on the latest setup.exe files and I'm finding that they don't match: > > $ gpg --verify setup-x86.exe.sig > gpg: Signature made Fri 13 Dec 2013 17:24:37 GMT using DSA key ID 676041BA > gpg: BAD signature from "Cygwin " > $ gpg --verify setup-x86_64.exe.sig > gpg: Signature made Fri 13 Dec 2013 17:38:14 GMT using DSA key ID 676041BA > gpg: BAD signature from "Cygwin " > $ md5sum setup-x86* > 93ee19b4143133ec0d9462a27e5c92cb setup-x86_64.exe > 2f2d2a21916b164c9f844810ada0f5f5 setup-x86_64.exe.sig > 9b3e9b26fa040763f2673cc3dc0cf229 setup-x86.exe > 3afb815ce823e601f999de777ea72885 setup-x86.exe.sig > > Am I doing something wrong, or...? Probably not, those signatures are still referring to the previous setup.exe files if you believe the date. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple