view doc/core-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.

/** @page core-signals Core Signals

 @signals
  @signal quitting
  @signal uri-handler
 @endsignals

 @see core.h

 <hr>

 @signaldef quitting
  @signalproto
void (*quitting)();
  @endsignalproto
  @signaldesc
   Emitted when libpurple is quitting.
 @endsignaldef

 @signaldef uri-handler
  @signalproto
gboolean (*uri_handler)(const gchar *proto, const gchar *cmd, GHashTable *params);
  @endsignalproto
  @signaldesc
   Emitted when handling a registered URI.
  @param proto The protocol of the URI.
  @param cmd The 'command' of the URI.
  @param params Any key/value parameters from the URI.
 @endsignaldef

 */
// vim: syntax=c.doxygen tw=75 et