llback decides a peer is bad, it
>>>> shall return 0 and return 1 otherwise. If 0 is returned, this
>>>> warning is produced:
>>>>
>>>> ssl3_get_client_certificate: no certificate returned
[...]
>>> The warning isn't printed by OpenSSL
cation callback decides a peer is bad, it
>>>> shall return 0 and return 1 otherwise. If 0 is returned, this
>>>> warning is produced:
>>>>
>>>> ssl3_get_client_certificate: no certificate returned
[...]
>>> The warning isn't printed by O
shall
> >> return 0 and return 1 otherwise. If 0 is returned, this warning is
> >> produced:
> >>
> >> ssl3_get_client_certificate: no certificate returned
> >>
> >> It's only a warning which does not seem to impair functionality; no
> >> warning is printed
Here's an
>> example (keys included):
>>
>> http://paste.scsys.co.uk/159837
>>
>> If the custom verification callback decides a peer is bad, it shall
>> return 0 and return 1 otherwise. If 0 is returned, this warning is
>> produced:
>>
>>
> included):
>
> http://paste.scsys.co.uk/159837
>
> If the custom verification callback decides a peer is bad, it shall
> return 0 and return 1 otherwise. If 0 is returned, this warning is
> produced:
>
> ssl3_get_client_certificate: no certificate returned
&g
n callback decides a peer is bad, it shall
return 0 and return 1 otherwise. If 0 is returned, this warning is
produced:
ssl3_get_client_certificate: no certificate returned
It's only a warning which does not seem to impair functionality; no
warning is printed if 1 is returned.
I've
