On Wednesday 05 Jan 2011 10:03:19 Rob Stradling wrote:
On Friday 24 December 2010 16:24:03 Igor Galić wrote:
snip
If we want to see more extensive testing in the field,
then this is the right time to make 'On' the default.
Steve, has Igor persuaded you?
I was hoping to generate a bit
On Wednesday 09 Feb 2011 09:39:36 Rob Stradling wrote:
On Wednesday 05 Jan 2011 10:03:19 Rob Stradling wrote:
On Friday 24 December 2010 16:24:03 Igor Galić wrote:
snip
If we want to see more extensive testing in the field,
then this is the right time to make 'On' the default.
On Wed, Feb 09, 2011 at 09:39:36AM +, Rob Stradling wrote:
On Wednesday 05 Jan 2011 10:03:19 Rob Stradling wrote:
On Friday 24 December 2010 16:24:03 Igor Galić wrote:
snip
If we want to see more extensive testing in the field,
then this is the right time to make 'On' the
On 2/9/2011 5:15 AM, Joe Orton wrote:
On Wed, Feb 09, 2011 at 09:39:36AM +, Rob Stradling wrote:
On Wednesday 05 Jan 2011 10:03:19 Rob Stradling wrote:
On Friday 24 December 2010 16:24:03 Igor Galić wrote:
snip
If we want to see more extensive testing in the field,
then this is the
On Friday 24 December 2010 16:24:03 Igor Galić wrote:
snip
If we want to see more extensive testing in the field,
then this is the right time to make 'On' the default.
Steve, has Igor persuaded you?
Rob Stradling
Senior Research Development Scientist
COMODO - Creating Trust Online
More significantly the code hasn't been tested extensively in the
field
so there may be problems that have yet to be uncovered.
That's a fair point.
My personal opinion would be to, at least initially, require an
explicit
directive to enable it and leave the option in future to have
On Wednesday 22 December 2010 16:11:21 Dr Stephen Henson wrote:
On 22/12/2010 15:32, Rob Stradling wrote:
On Friday 03 December 2010 10:31:24 Rob Stradling wrote:
snip
Would it be possible to make OCSP Stapling enabled by default (when the
server certificate contains an OCSP Responder
On Friday 03 December 2010 10:31:24 Rob Stradling wrote:
snip
Would it be possible to make OCSP Stapling enabled by default (when the
server certificate contains an OCSP Responder URL in the AIA extension)
instead of disabled by default?
(Perhaps SSLUseStapling could be replaced by
On 22/12/2010 15:32, Rob Stradling wrote:
On Friday 03 December 2010 10:31:24 Rob Stradling wrote:
snip
Would it be possible to make OCSP Stapling enabled by default (when the
server certificate contains an OCSP Responder URL in the AIA extension)
instead of disabled by default?
(Perhaps
On Tuesday 30 November 2010 00:55:48 Dr Stephen Henson wrote:
On 30/11/2010 00:03, Dr Stephen Henson wrote:
On 29/11/2010 21:46, Guenter Knauf wrote:
snip
I think that we had some similar already in the past, and you suggested
a change which was compatible with both 0.9.8 and 1.0.0
On 29/11/2010 21:46, Guenter Knauf wrote:
Hi Steve,
ssl_util_stapling.c issues warnings / breaks when compiled with OSSL 1.0.0;
MSVC
warns:
\modules\ssl\ssl_util_stapling.c(140) : warning C4133: '=' : incompatible
types
- from 'struct stack_st_OPENSSL_STRING *' to 'struct stack_st_STRING
On 30/11/2010 00:03, Dr Stephen Henson wrote:
On 29/11/2010 21:46, Guenter Knauf wrote:
Hi Steve,
ssl_util_stapling.c issues warnings / breaks when compiled with OSSL 1.0.0;
MSVC
warns:
\modules\ssl\ssl_util_stapling.c(140) : warning C4133: '=' : incompatible
types
- from 'struct
Am 30.11.2010 01:55, schrieb Dr Stephen Henson:
See of the patch for bug #50121 resolves this for you.
There's a slightly cleaner way of doing that r1040366 in trunk fixes it for me.
thanks Steve, works fine. I've closed bug #50121.
Gün.
13 matches
Mail list logo
