From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.comp.encryption.gpg.gnutls.devel,gmane.emacs.devel Subject: Re: Emacs core TLS support Date: Mon, 27 Sep 2010 13:45:26 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87bp7j6n5l.fsf@lifelogs.com> References: <878wc1vfh3.fsf@lifelogs.com> <87k4v0n0m8.fsf@lifelogs.com> <87wrrvfnc4.fsf@lifelogs.com> <87r5i2d00q.fsf@lifelogs.com> <87zkwqijye.fsf@stupidchicken.com> <878w4actmg.fsf@lifelogs.com> <877hju123h.fsf@stupidchicken.com> <8762yklrdk.fsf@lifelogs.com> <87wrqzhrjv.fsf@lifelogs.com> <87fwxmihyz.fsf@lifelogs.com> <8762ycfhqo.fsf@lifelogs.com> <87d3sf9soo.fsf@lifelogs.com> <87r5gh2fzj.fsf@lifelogs.com> <877hi79rt2.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1285613150 9361 80.91.229.12 (27 Sep 2010 18:45:50 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 27 Sep 2010 18:45:50 +0000 (UTC) Cc: emacs-devel@gnu.org To: gnutls-devel@gnu.org Original-X-From: gnutls-devel-bounces+pgp-gnutls-dev=m.gmane.org@gnu.org Mon Sep 27 20:45:47 2010 Return-path: Envelope-to: pgp-gnutls-dev@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1P0Ihs-0001cY-ML for pgp-gnutls-dev@m.gmane.org; Mon, 27 Sep 2010 20:45:44 +0200 Original-Received: from localhost ([127.0.0.1]:39186 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P0Ihs-0003wc-6i for pgp-gnutls-dev@m.gmane.org; Mon, 27 Sep 2010 14:45:44 -0400 Original-Received: from [140.186.70.92] (port=36489 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P0Ihp-0003wV-CK for gnutls-devel@gnu.org; Mon, 27 Sep 2010 14:45:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1P0Iho-0006wa-30 for gnutls-devel@gnu.org; Mon, 27 Sep 2010 14:45:41 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:44878) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1P0Ihn-0006wO-TK for gnutls-devel@gnu.org; Mon, 27 Sep 2010 14:45:40 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1P0Ihl-0001aR-34 for gnutls-devel@gnu.org; Mon, 27 Sep 2010 20:45:37 +0200 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 Sep 2010 20:45:37 +0200 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 Sep 2010 20:45:37 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 16 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:mQHyB2KGlmS15JPcJz6QDRDnfUI= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: gnutls-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GnuTLS development discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: gnutls-devel-bounces+pgp-gnutls-dev=m.gmane.org@gnu.org Errors-To: gnutls-devel-bounces+pgp-gnutls-dev=m.gmane.org@gnu.org Xref: news.gmane.org gmane.comp.encryption.gpg.gnutls.devel:4554 gmane.emacs.devel:131013 Archived-At: On Mon, 27 Sep 2010 14:25:10 -0400 James Cloos wrote: >>>>>> "TZ" == Ted Zlatanov writes: TZ> It's not really helpful to me since I don't know TLS well. JC> Sorry. My point was that wireshark does a decent job of decoding the JC> TLS such that anyone should be able to follow what is happening. With Lars' latest change we found that enabling logging, in itself, will make things work (yay!). We guessed it was the delay introduced by logging but using (sit-for 0.1) in the handshake loop doesn't work like enabling logging. So it's something specific about the logging function's interaction with Emacs and looking at the wire is *probably* not going to help. But I don't know yet what's going on. Ted