Mercurial > pidgin
view doc/certificate-signals.dox @ 32796:5ae7e1f36b43
Fix a possible XMPP remote crash
A series of specially crafted file transfer requests can cause clients
to reference invalid memory. The user must have accepted one of the
file transfer requests.
The fix is to correctly cancel and free a SOCKS5 connection attempt so
that it does not trigger an attempt to access invalid memory later.
This was reported to us by Jos«± Valent«żn Guti«±rrez and this patch is
written by Paul Aurich.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Mon, 07 May 2012 03:16:31 +0000 |
parents | e0613cf8c493 |
children |
line wrap: on
line source
/** @page certificate-signals Certificate Signals @signals @signal certificate-stored @signal certificate-deleted @endsignals @see certificate.h <hr> @signaldef certificate-stored @signalproto void (*certificate_stored)(PurpleCertificatePool *pool, const gchar *id, gpointer data); @endsignalproto @signaldesc Emitted when a pool stores a certificate. Connect to the pool instance. @param pool Pool the certificate has been stored into @param id Key the certificate was stored under @endsignaldef @signaldef certificate-deleted @signalproto void (*certificate_deleted)(PurpleCertificatePool *pool, const gchar *id, gpointer data); @endsignalproto @signaldesc Emitted when a pool deletes a certificate. Connect to the pool instance. @param pool Pool the certificate was deleted from @param id Key that was deleted @endsignaldef */ // vim: syntax=c.doxygen tw=75 et