All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Programmingkid <programmingkidx@gmail.com>,
	Rainer M?ller <raimue@macports.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [qemu-web PATCH] download: Add instructions for MacPorts
Date: Wed, 4 Apr 2018 19:41:39 +0200	[thread overview]
Message-ID: <64bdd5df-c7c0-fe1b-4622-680cee1a13bb@weilnetz.de> (raw)
In-Reply-To: <6171cf9f-6c76-33a7-9654-c6ed78dbe02f@redhat.com>

Am 04.04.2018 um 18:11 schrieb Paolo Bonzini:
> On 04/04/2018 17:55, Stefan Weil wrote:
>> By the way: https://qemu.weilnetz.de provides https (maybe I should
>> enforce it), it includes sha512, and I also sign the binaries with my
>> key. You still have to trust me, Debian and Cygwin (which provides lots
>> of libraries used for the build).
> 
> Cool!  I had noticed sha512, but it is not very useful without https
> (except to verify bitflips).  Good news that you support https, we
> should change the website to use https links instead.
> 
> Regarding signing, there is no GPG signature.  That's okay, but we
> should document how to verify the installer signature from either Linux
> or Windows.
> 
> Thanks,
> 
> Paolo


The executables (installer, installed exe files) are signed using
osslsigncode (https://packages.debian.org/sid/otherosfs/osslsigncode)
and my personal CACert key for code signing.

The signatures can be checked on Windows (e.g. during the installation
process or from Windows Explorer with file properties) or on Linux (see
example below). That's Windows standard. The only problem is that
Windows does not automatically accept CACert keys (and that I have no
better key for code signing).

Stefan


$ osslsigncode verify /var/www/html/w32/qemu-w32-setup-20180321.exe
Current PE checksum   : 04D7CD55
Calculated PE checksum: 04D7CD55

Message digest algorithm  : SHA1
Current message digest    : B2B13EB4765B4708D999BE3E4893915BBCAB0F8E
Calculated message digest : B2B13EB4765B4708D999BE3E4893915BBCAB0F8E

Signature verification: ok

Number of signers: 1
	Signer #0:
		Subject: /CN=Stefan Weil/emailAddress=sw@weilnetz.de
		Issuer : /O=Root CA/OU=http://www.cacert.org/CN=CA Cert Signing
Authority/emailAddress=support@cacert.org
		Serial : 0D6AA6

Number of certificates: 2
	Cert #0:
		Subject: /CN=Stefan Weil/emailAddress=sw@weilnetz.de
		Issuer : /O=Root CA/OU=http://www.cacert.org/CN=CA Cert Signing
Authority/emailAddress=support@cacert.org
		Serial : 0D6AA6
	------------------
	Cert #1:
		Subject: /O=Root CA/OU=http://www.cacert.org/CN=CA Cert Signing
Authority/emailAddress=support@cacert.org
		Issuer : /O=Root CA/OU=http://www.cacert.org/CN=CA Cert Signing
Authority/emailAddress=support@cacert.org
		Serial : 0

Succeeded

  reply	other threads:[~2018-04-04 17:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.35816.1522678020.27992.qemu-devel@nongnu.org>
2018-04-02 14:13 ` [Qemu-devel] [qemu-web PATCH] download: Add instructions for MacPorts Programmingkid
2018-04-04 11:15   ` Paolo Bonzini
2018-04-04 14:24     ` Programmingkid
2018-04-04 14:38       ` Daniel P. Berrangé
2018-04-04 14:45         ` Paolo Bonzini
2018-04-04 14:58           ` Daniel P. Berrangé
2018-04-04 15:55             ` Stefan Weil
2018-04-04 16:05               ` Programmingkid
2018-04-04 16:08                 ` Paolo Bonzini
2018-04-04 16:19                   ` Programmingkid
2018-04-04 17:23                     ` Paolo Bonzini
2018-04-04 16:11               ` Paolo Bonzini
2018-04-04 17:41                 ` Stefan Weil [this message]
2018-04-05  5:56                   ` Paolo Bonzini
2018-04-01 16:22 Rainer Müller
2018-04-02  2:22 ` Paolo Bonzini

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=64bdd5df-c7c0-fe1b-4622-680cee1a13bb@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=raimue@macports.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.