W3C home > Mailing lists > Public > public-bpwg-comments@w3.org > July to September 2008

Re: mobile OK tests: HTTPS considerations

From: Jo Rabin <jrabin@mtld.mobi>
Date: Thu, 25 Sep 2008 10:30:45 +0100
Message-ID: <48DB5A45.1010800@mtld.mobi>
To: public-bpwg-comments@w3.org, public-wsc-wg@w3.org, tlr@w3.org

Hi Thomas

Thanks for your comment on behalf of the WSC-WG. We'd appreciate your 
further comments on our proposed text, as follows.

Many thanks
Jo

Under ACTION-841

WSC Proposal:

We propose that you update this criterion, at a minimum, as follows:

If the resource is accessed through HTTPS:

	If the certificate presented does not match the
          resource's URI, FAIL.

	If the certificate has expired or is not yet valid, warn.

	If certificate validation otherwise fails, FAIL.
	
	Checker SHOULD consider arbitrary root certificates (including
	self-signed certificates) as trusted for the purposes of
	mobileOK testing.

=====

Current Text:

Note:

To allow for self-signature of certificates during testing the signatory
of a certificate should not be checked.


...


If the response is an HTTPS response:

	If the certificate is invalid, FAIL

	If the certificate has expired, warn



=====

Proposed replacement text:

Note:

Arbitrary root certificates (including self-signed certificates) should
be regarded as trusted.


...

If the response is the result of a request for a URI which has the
scheme https:

	If the certificate presented does not match the
          requested URI, FAIL.

	If the certificate has expired or is not yet valid, warn.

	If certificate validation otherwise fails, FAIL.


On 29/08/2008 10:01, Thomas Roessler wrote:
> Hello,
> 
> this is a post last call comment concerning the mobile OK basic
> tests 1.0, on behalf of the Web Security Context Working Group.
> 
> We notice that section 2.4.3 - HTTP Response - uses the notion of an
> "HTTPS response".  There is no such thing.
> 
> We also notice that the notion of an "invalid certificate" does not
> match what we understand to be the Best Practice Working Group's
> intention with this test.
> 
> We propose that you update this criterion, at a minimum, as follows:
> 
>   If the resource is accessed through HTTPS:      
>     If the certificate presented does not match the
>         resource's URI, FAIL.
> 
>     If the certificate has expired or is not yet valid, warn.
> 
>     If certificate validation otherwise fails, FAIL.
> 
>     Checker SHOULD consider arbitrary root certificates (including
>     self-signed certificates) as trusted for the purposes of
>     mobileOK testing.
> 
> Note that there are additional error conditions that can occur
> during TLS negotiation, including a mismatch on supported algorithms
> and protocol versions.
> 
> Regards,
Received on Thursday, 25 September 2008 09:31:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:01:50 UTC