SSL certificate chain validation issues

[Eion Robb]

> I think we shouldn't utilize the last plugin slot. Instead, it should
> be a link to PurpleCertificateSchemeMore (or somethink like that)
> struct, which could hold more slots for future use.
Or use it as a sizeof() and expand the struct like we do for the
PurplePluginProtocolInfo struct?

On 20 April 2014 03:32, Tomasz Wasilczyk <twasilczyk at pidgin.im> wrote:

> W dniu 19.04.2014 16:21, Daniel Atallah pisze:
>
>  I don't think there's a way to fix this without API addition - we need
>> to get more information about each cert to be able to check the usage
>> constraints. Fortunately, there are 3 SSL plugin slots available, so
>> API addition is possible.
>>
>
> I think we shouldn't utilize the last plugin slot. Instead, it should be a
> link to PurpleCertificateSchemeMore (or somethink like that) struct, which
> could hold more slots for future use.
>
> Your patch leaves the last slot free, so it's not a problem yet.
>
> Tomek
>
>
> _______________________________________________
> security mailing list
> security at pidgin.im
> https://pidgin.im/cgi-bin/mailman/listinfo/security
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pidgin.im/cgi-bin/mailman/private/security/attachments/20140420/2dc529b9/attachment.html>