On Tue, Oct 30, 2012 at 10:03 AM, Jakob Bohm wrote:
> On 10/29/2012 7:05 PM, Jeffrey Walton wrote:
>>
>> On Mon, Oct 29, 2012 at 11:04 AM, Jakob Bohm
>> wrote:
>>>
>>> On 10/27/2012 10:58 PM, Jeffrey Walton wrote:
On Sat, Oct 27, 2012 at 11:00 AM, Alban D. wrote:
>
>
>
On 10/29/2012 7:05 PM, Jeffrey Walton wrote:
On Mon, Oct 29, 2012 at 11:04 AM, Jakob Bohm wrote:
On 10/27/2012 10:58 PM, Jeffrey Walton wrote:
On Sat, Oct 27, 2012 at 11:00 AM, Alban D. wrote:
Hi everyone,
iSEC Partners just released a paper that provides detailed guidelines
and sample co
Sorry for the confusion.
We initially uploaded the wrong version of the paper and that's
something I noticed yesterday.
The code was out of sync with the repo on Github. I also changed a few
other things while I was at it.
Thanks for all the feedback.
2012/10/30 Jeffrey Walton :
> On Mon, Oct 29,
On Mon, Oct 29, 2012 at 4:02 PM, Erwann Abalea
wrote:
> Where's the failure here?
> hostname_matched is set to HOSTNAME_VALIDATION_ERR at initialization, and in
> case of a NULL hostname or certificate it is returned by the function,
> unmodified.
My bad - you were right. I fetched the document ag
On Mon, Oct 29, 2012 at 4:02 PM, Erwann Abalea
wrote:
> Where's the failure here?
> hostname_matched is set to HOSTNAME_VALIDATION_ERR at initialization, and in
> case of a NULL hostname or certificate it is returned by the function,
> unmodified.
HOSTNAME_VALIDATION_ERR is not mentioned in
https:
Bonjour,
In the 4.2 paragraph, talking about revocation, you explicitely write
that your code examples don't check for revocation. Depending on your
target audience, this might not be a wise choice.
In the same part, you're referring to a post by Ben Laurie about how
hard it is to detect revok
Where's the failure here?
hostname_matched is set to HOSTNAME_VALIDATION_ERR at initialization,
and in case of a NULL hostname or certificate it is returned by the
function, unmodified.
--
Erwann ABALEA
Le 27/10/2012 21:00, Jeffrey Walton a écrit :
On Sat, Oct 27, 2012 at 11:00 AM, Alban D.
On Mon, Oct 29, 2012 at 11:04 AM, Jakob Bohm wrote:
> On 10/27/2012 10:58 PM, Jeffrey Walton wrote:
>>
>> On Sat, Oct 27, 2012 at 11:00 AM, Alban D. wrote:
>>>
>>> Hi everyone,
>>>
>>> iSEC Partners just released a paper that provides detailed guidelines
>>> and sample code on how to properly do
On 10/27/2012 10:58 PM, Jeffrey Walton wrote:
On Sat, Oct 27, 2012 at 11:00 AM, Alban D. wrote:
Hi everyone,
iSEC Partners just released a paper that provides detailed guidelines
and sample code on how to properly do certificate validation with
OpenSSL:
http://www.isecpartners.com/blog/2012/10
Thanks,
Also it can be usefull to go back to the book 'Network Security with
OpenSSL', pages 128 to 138.
Michel.
Le 27/10/2012 17:00, Alban D. a écrit :
Hi everyone,
iSEC Partners just released a paper that provides detailed guidelines
and sample code on how to properly do certificate valid
On Sat, Oct 27, 2012 at 11:00 AM, Alban D. wrote:
> Hi everyone,
>
> iSEC Partners just released a paper that provides detailed guidelines
> and sample code on how to properly do certificate validation with
> OpenSSL:
> http://www.isecpartners.com/blog/2012/10/14/the-lurking-menace-of-broken-tls-v
The way how common names are verified in
The Most Dangerous Code in the World:
Validating SSL Certificates in Non-Browser Software
is not correct.
It gives a false match when there is more than one common name ava
__
OpenSSL Pr
On Sat, Oct 27, 2012 at 11:00 AM, Alban D. wrote:
> Hi everyone,
>
> iSEC Partners just released a paper that provides detailed guidelines
> and sample code on how to properly do certificate validation with
> OpenSSL:
> http://www.isecpartners.com/blog/2012/10/14/the-lurking-menace-of-broken-tls-v
On Sat, Oct 27, 2012 at 11:00 AM, Alban D. wrote:
> Hi everyone,
>
> iSEC Partners just released a paper that provides detailed guidelines
> and sample code on how to properly do certificate validation with
> OpenSSL:
> http://www.isecpartners.com/blog/2012/10/14/the-lurking-menace-of-broken-tls-v
On Sat, Oct 27, 2012 at 11:00 AM, Alban D. wrote:
> Hi everyone,
>
> iSEC Partners just released a paper that provides detailed guidelines
> and sample code on how to properly do certificate validation with
> OpenSSL:
> http://www.isecpartners.com/blog/2012/10/14/the-lurking-menace-of-broken-tls-v
Hi everyone,
iSEC Partners just released a paper that provides detailed guidelines
and sample code on how to properly do certificate validation with
OpenSSL:
http://www.isecpartners.com/blog/2012/10/14/the-lurking-menace-of-broken-tls-validation.html
It is not trivial and so I thought this refere
16 matches
Mail list logo
