Mercurial > pidgin.yaz
changeset 17317:c76bee45540a
propagate from branch 'im.pidgin.pidgin' (head dc4f2ee34039521ae6a198fe7d62f4dca8a84589)
to branch 'im.pidgin.soc.2007.certmgr' (head 9a820d4262a69cde7e03915f22c234b75f54cf5c)
| author | William Ehlhardt <williamehlhardt@gmail.com> |
|---|---|
| date | Fri, 25 May 2007 17:56:39 +0000 |
| parents | a2edef5eb1b1 (diff) 42c2d75b3d3e (current diff) |
| children | d5f07d1e37e6 |
| files | |
| diffstat | 2 files changed, 13 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/libpurple/plugins/ssl/ssl-gnutls.c Fri May 25 16:17:50 2007 +0000 +++ b/libpurple/plugins/ssl/ssl-gnutls.c Fri May 25 17:56:39 2007 +0000 @@ -123,6 +123,18 @@ gnutls_data->handshake_handler = purple_input_add(gsc->fd, PURPLE_INPUT_READ, ssl_gnutls_handshake_cb, gsc); + /* Orborde asks: Why are we configuring a callback, then + immediately calling it? + + Answer: gnutls_handshake (up in handshake_cb) needs to be called + once in order to get the ball rolling on the SSL connection. + Once it has done so, only then will the server reply, triggering + the callback. + + Since the logic driving gnutls_handshake is the same with the first + and subsequent calls, we'll just fire the callback immediately to + accomplish this. + */ ssl_gnutls_handshake_cb(gsc, gsc->fd, PURPLE_INPUT_READ); }
--- a/libpurple/sslconn.h Fri May 25 16:17:50 2007 +0000 +++ b/libpurple/sslconn.h Fri May 25 17:56:39 2007 +0000 @@ -170,6 +170,7 @@ /** * Adds an input watcher for the specified SSL connection. + * Once the SSL handshake is complete, use this to watch for actual data across it. * * @param gsc The SSL connection handle. * @param func The callback function.