Mercurial > pidgin.yaz
graph
-
propagate from branch 'im.pidgin.pidgin' (head bd56a115b35ba5922e5f9c93840d0868a4978b09)Mon, 30 Nov 2009 02:44:03 +0000, by Paul Aurich
-
jabber: Use NS_XMPP_SASLFri, 27 Nov 2009 20:41:22 +0000, by Paul Aurich
-
propagate from branch 'im.pidgin.pidgin' (head 3e6ed1829a654e5c7cf286670e3adc20e6158113)Fri, 27 Nov 2009 20:36:31 +0000, by Paul Aurich
-
propagate from branch 'im.pidgin.pidgin' (head 2980a8828dae367476dcf5d8e52783fdc137d8bf)Tue, 17 Nov 2009 23:05:18 +0000, by Paul Aurich
-
jabber: Interop with Prosody (via Tobias' code). Hooray!Tue, 17 Nov 2009 21:37:14 +0000, by Paul Aurich
-
jabber: Fix up the remaining issues and add a test case that interoperates with gsasl. Woot.Tue, 17 Nov 2009 19:39:36 +0000, by Paul Aurich
-
propagate from branch 'im.pidgin.pidgin' (head d2984fa9ffdaa63b01cc1e0d94aec5622cd080c1)Tue, 17 Nov 2009 19:23:05 +0000, by Paul Aurich
-
jabber: Handle the case where the server success-with-data is sent as a challenge/response pair.Wed, 11 Nov 2009 20:32:09 +0000, by Paul Aurich
-
propagate from branch 'im.pidgin.pidgin' (head 37329f033a30f4f4f5048f9fdc86df4400e3ada5)Mon, 09 Nov 2009 04:39:40 +0000, by Paul Aurich
-
jabber: Complete (though untested) SCRAM implementation.Mon, 09 Nov 2009 03:42:26 +0000, by Paul Aurich
-
Clean up the two temporary buffers.Sun, 08 Nov 2009 18:39:30 +0000, by Paul Aurich
-
How is it that there's no programmatic way to get the output size of the hash functions without resorting to a hardcoded table? Or did I miss something?Sun, 08 Nov 2009 18:38:30 +0000, by Paul Aurich