qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] QEMU website (wiki) improvements
Date: Sat, 1 Jul 2017 19:35:29 +0200	[thread overview]
Message-ID: <c453070d-65d5-8a23-bdef-0fefbe9eb9b0@weilnetz.de> (raw)
In-Reply-To: <20170123102810.GD29186@stefanha-x1.localdomain>

Am 23.01.2017 um 11:28 schrieb Stefan Hajnoczi:
> On Sun, Jan 22, 2017 at 04:19:43PM +0100, Stefan Weil wrote:
>> On 03/02/15 23:12, Stefan Hajnoczi wrote:
>>> On Sat, Feb 28, 2015 at 04:29:44PM +0100, Stefan Weil wrote:
>>>> * It does not support secure access (https), so each login is insecure.
>>>>   Can we get a free server certificate?
>>>
>>> This is on my todo list.  I'm travelling right now but will work on it
>>> over the coming weeks.
>>>
>>> There are some gotchas:
>>>
>>> 1. qemu.org vs qemu-project.org.  Unless we get a SNI certificate, the
>>>    certificate will only be valid for one or the other.  Users will get
>>>    an untrusted certificate message if they go to the other domain name.
>>>
>>> 2. We use subdomains, so a wildcard certificate is necessary.  That's
>>>    not always offered for free so I need to compare the certificate
>>>    vendors.
>>>
>>> Stefan
>>
>>
>> Although this discussion thread is rather old, its subject
>> still applies.
>>
>> In the meantime there are free certificates available.
>> We could add https support with a certificate from
>> https://letsencrypt.org/. As long as there is only a
>> small number of host names (*), I'd simply add them all
>> to the primary certificate. In addition, SNI certificates
>> for the different names can be installed.
> 
> Good idea, Jeff and I have discussed Let's Encrypt and have experience
> setting it up.
> 
>> I can help with the installation if that is needed.
>>
>> Stefan
>>
>> (*)
>>
>> qemu.org
>> qemu.osuosl.org
>> qemu-project.org
>> wiki.qemu.org
>> wiki.qemu-project.org
>> www.qemu.org
>> www.qemu-project.org
>>
>> Are there more host names used?
> 
> git.qemu.org
> git.qemu-project.org
> 

It looks like there were some changes since my last mail:

The official website is now again www.qemu.org instead of
qemu-project.org. Is qemu-project.org now deprecated?

Also HTTPS was enabled, but uses a self signed certificate
and does not show the correct contents, so
https://www.qemu.org/ still does not work.

Stefan

      parent reply	other threads:[~2017-07-01 17:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28 15:29 [Qemu-devel] QEMU website (wiki) improvements Stefan Weil
2015-03-02 13:36 ` Claudio Fontana
2015-03-02 14:01   ` Peter Maydell
2015-03-02 14:31     ` Claudio Fontana
2015-03-02 22:12 ` Stefan Hajnoczi
2017-01-22 15:19   ` Stefan Weil
2017-01-23 10:28     ` Stefan Hajnoczi
2017-03-28 19:37       ` Stefan Weil
2017-07-01 17:35       ` Stefan Weil [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=c453070d-65d5-8a23-bdef-0fefbe9eb9b0@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).