[Qemu-devel] QEMU website (wiki) improvements

[Qemu-devel] QEMU website (wiki) improvements

[Stefan Weil]

Hello Michael,

here are some suggestions / thoughts for the QEMU website.

* http://wiki.qemu.org/Main_Pagedoes not pass the W3C validator, see
http://validator.w3.org/check?uri=http%3A%2F%2Fwiki.qemu.org.
   They can be easily fixed, but not by normal wiki users.

* It tracks users (g+ image 
https://ssl.gstatic.com/images/icons/gplus-32.png).
   Do we need that, or could we improve privacy?

* It does not support secure access (https), so each login is insecure.
   Can we get a free server certificate?

Regards
Stefan

Re: [Qemu-devel] QEMU website (wiki) improvements

[Claudio Fontana]

On 28.02.2015 16:29, Stefan Weil wrote:
> Hello Michael,
> 
> here are some suggestions / thoughts for the QEMU website.
> 
> * http://wiki.qemu.org/Main_Pagedoes not pass the W3C validator, see
> http://validator.w3.org/check?uri=http%3A%2F%2Fwiki.qemu.org.
>   They can be easily fixed, but not by normal wiki users.
> 
> * It tracks users (g+ image https://ssl.gstatic.com/images/icons/gplus-32.png).
>   Do we need that, or could we improve privacy?
> 
> * It does not support secure access (https), so each login is insecure.
>   Can we get a free server certificate?
> 
> Regards
> Stefan

Another suggestion for the QEMU website: improve the testing page,
adding at least one ready-to-run image for smoke testing for each supported arch.

http://wiki.qemu.org/Testing

In particular I would like to see a minimal sparc64 image added, as well as a
minimal x86_64 image. It is useful for testing tcg backends to have little endian and big endian 64-bit images.

Ciao,

Claudio

-- 
Claudio Fontana
Server Virtualization Architect
Huawei Technologies Duesseldorf GmbH
Riesstraße 25 - 80992 München

office: +49 89 158834 4135
mobile: +49 15253060158

Re: [Qemu-devel] QEMU website (wiki) improvements

[Peter Maydell]

On 2 March 2015 at 22:36, Claudio Fontana <claudio.fontana@huawei.com> wrote:
> Another suggestion for the QEMU website: improve the testing page,
> adding at least one ready-to-run image for smoke testing for each supported arch.
>
> http://wiki.qemu.org/Testing

The thing about providing Linux system images is the awkwardness of
satisfying the GPL source-code-provision requirements for everything
in them... It would be nice if new images came with complete
how-to-reproduce-this-image information.

-- PMM

Re: [Qemu-devel] QEMU website (wiki) improvements

[Claudio Fontana]

On 02.03.2015 15:01, Peter Maydell wrote:
> On 2 March 2015 at 22:36, Claudio Fontana <claudio.fontana@huawei.com> wrote:
>> Another suggestion for the QEMU website: improve the testing page,
>> adding at least one ready-to-run image for smoke testing for each supported arch.
>>
>> http://wiki.qemu.org/Testing
> 
> The thing about providing Linux system images is the awkwardness of
> satisfying the GPL source-code-provision requirements for everything
> in them... It would be nice if new images came with complete
> how-to-reproduce-this-image information.
> 
> -- PMM
>

What about adding FreeBSD Sparc64 and x86_64 images, with the minimal amount of GPL packages required?
We could then add to the same testing pages the exact sources of the packages for download, which should not be that many,
according to:

https://wiki.freebsd.org/GPLinBase

just an idea...

Claudio

Re: [Qemu-devel] QEMU website (wiki) improvements

[Stefan Hajnoczi]

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

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

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

Re: [Qemu-devel] QEMU website (wiki) improvements

[Stefan Weil]

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.

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?

Re: [Qemu-devel] QEMU website (wiki) improvements

[Stefan Hajnoczi]

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

Re: [Qemu-devel] QEMU website (wiki) improvements

[Stefan Weil]

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
>

Update: Currently https://www.qemu-project.org/ supports secure
connections, but uses a self-signed certificate which was issued
for qemu.org, so it still cannot be simply used in most browsers.

Regards
Stefan

Re: [Qemu-devel] QEMU website (wiki) improvements

[Stefan Weil]

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