gmane.emacs.jabber.bugs

[ emacs-jabber-Bugs-3531561 ] assoc.el deprecated in emacs 24.2

SourceForge.net — 2013-04-10T22:12:55

Bugs item #3531561, was opened at 2012-06-02 14:11
Message generated for change (Comment added) made by legoscia
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3531561&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Resolution: None
Priority: 5
Private: No
Submitted By: Stefan Husmann (haawda)
Assigned to: Nobody/Anonymous (nobody)
Summary: assoc.el deprecated in emacs 24.2

Initial Comment:
According to http://www.emacswiki.org/emacs-en/assoc-deprecated assoc.el will be removed in emacs 24.2. assoc.el is required in jabber-presence.el and jabber-muc-nick-coloring.el. 

----------------------------------------------------------------------

Date: 2013-04-10 15:12

Message:
This was fixed in a recent commit by Evgenii Terechkov:
http://emacs-jabber.git.sourceforge.net/git/gitweb.cgi?p=emacs-jabber/emacs-jabber;a=commitdiff;h=c98be9e194710ea6b36903ba0435450686243b10;hp=52368dc3424bc98e4abaa20df97176404b5ff98a

----------------------------------------------------------------------

Comment By: parsifal ()
Date: 2013-04-09 06:59

Message:
I tried removing the `(require 'assoc)` statements from the two files
mentioned, and that did not fix the issue.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3531561&group_id=88346

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter

[ emacs-jabber-Bugs-3531561 ] assoc.el deprecated in emacs 24.2

SourceForge.net — 2013-04-09T13:59:34

Bugs item #3531561, was opened at 2012-06-02 14:11
Message generated for change (Comment added) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3531561&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Stefan Husmann (haawda)
Assigned to: Nobody/Anonymous (nobody)
Summary: assoc.el deprecated in emacs 24.2

Initial Comment:
According to http://www.emacswiki.org/emacs-en/assoc-deprecated assoc.el will be removed in emacs 24.2. assoc.el is required in jabber-presence.el and jabber-muc-nick-coloring.el. 

----------------------------------------------------------------------

Comment By: parsifal ()
Date: 2013-04-09 06:59

Message:
I tried removing the `(require 'assoc)` statements from the two files
mentioned, and that did not fix the issue.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3531561&group_id=88346

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter

[ emacs-jabber-Patches-1773635 ] Multi-account configuration

SourceForge.net — 2013-04-02T08:45:10

Patches item #1773635, was opened at 2007-08-13 22:45
Message generated for change (Comment added) made by pipping
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586352&aid=1773635&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Pending
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Xavier Maillard (zedek)
Assigned to: Nobody/Anonymous (nobody)
Summary: Multi-account configuration

Initial Comment:
This patch implements authentication based on an external authinfo file (ala FTP).

Actually it just support a file. Future enhancements will likely add an authinfo-alist (in addition of a file).

Please review/comment/correct.

Patch made against CVS HEAD as of 2007-08-14.

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2013-04-02 01:45

Message:
Works like a charm, thanks :)

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2013-04-01 19:28

Message:
Well, here it is:
http://emacs-jabber.git.sourceforge.net/git/gitweb.cgi?p=emacs-jabber/emacs-jabber;a=commitdiff;h=5c7d80f3aa92cc5a27e3fb553ca291173516b763

Works for me, at least.

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2013-04-01 19:12

Message:
Ah, you're right, I missed that part. And just the other day I was thinking
that it would be nice if jabber.el would read authinfo files :)

I'd rather have it use the auth-source library than reading the authinfo
file directly, though. I'll see if I can come up with a patch for that...
(though feel free to beat me to it!)

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2013-03-29 14:16

Message:
If I understand correctly, only one of those two patches ever made it into
emacs-jabber.

The other adds support for ~/.authinfo; Is there still a chance for
inclusion?

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2007-08-28 18:48

Message:
Logged In: YES 
user_id=920364
Originator: NO

Thanks a lot, and sorry about the delay... I just committed a modified
version of your patch.  Let's see if this works...

----------------------------------------------------------------------

Comment By: Xavier Maillard (zedek)
Date: 2007-08-16 13:28

Message:
Logged In: YES 
user_id=597884
Originator: YES

Ok, here is my first try to implement a jabber-account-list alist.

It adds support for multiple connections or one connection (given the
account name).

Please try this.
File Added: jabber-connect.el

----------------------------------------------------------------------

Comment By: Xavier Maillard (zedek)
Date: 2007-08-15 01:12

Message:
Logged In: YES 
user_id=597884
Originator: YES

Small fix of previous commit.
File Added: jabber-core-add-authinfo-auth.patch

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586352&aid=1773635&group_id=88346

------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2

[ emacs-jabber-Patches-1773635 ] Multi-account configuration

SourceForge.net — 2013-04-02T02:28:29

Patches item #1773635, was opened at 2007-08-13 22:45
Message generated for change (Comment added) made by legoscia
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586352&aid=1773635&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Priority: 5
Private: No
Submitted By: Xavier Maillard (zedek)
Assigned to: Nobody/Anonymous (nobody)
Summary: Multi-account configuration

Initial Comment:
This patch implements authentication based on an external authinfo file (ala FTP).

Actually it just support a file. Future enhancements will likely add an authinfo-alist (in addition of a file).

Please review/comment/correct.

Patch made against CVS HEAD as of 2007-08-14.

----------------------------------------------------------------------

Date: 2013-04-01 19:28

Message:
Well, here it is:
http://emacs-jabber.git.sourceforge.net/git/gitweb.cgi?p=emacs-jabber/emacs-jabber;a=commitdiff;h=5c7d80f3aa92cc5a27e3fb553ca291173516b763

Works for me, at least.

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2013-04-01 19:12

Message:
Ah, you're right, I missed that part. And just the other day I was thinking
that it would be nice if jabber.el would read authinfo files :)

I'd rather have it use the auth-source library than reading the authinfo
file directly, though. I'll see if I can come up with a patch for that...
(though feel free to beat me to it!)

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2013-03-29 14:16

Message:
If I understand correctly, only one of those two patches ever made it into
emacs-jabber.

The other adds support for ~/.authinfo; Is there still a chance for
inclusion?

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2007-08-28 18:48

Message:
Logged In: YES 
user_id=920364
Originator: NO

Thanks a lot, and sorry about the delay... I just committed a modified
version of your patch.  Let's see if this works...

----------------------------------------------------------------------

Comment By: Xavier Maillard (zedek)
Date: 2007-08-16 13:28

Message:
Logged In: YES 
user_id=597884
Originator: YES

Ok, here is my first try to implement a jabber-account-list alist.

It adds support for multiple connections or one connection (given the
account name).

Please try this.
File Added: jabber-connect.el

----------------------------------------------------------------------

Comment By: Xavier Maillard (zedek)
Date: 2007-08-15 01:12

Message:
Logged In: YES 
user_id=597884
Originator: YES

Small fix of previous commit.
File Added: jabber-core-add-authinfo-auth.patch

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586352&aid=1773635&group_id=88346

------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2

[ emacs-jabber-Patches-1773635 ] Multi-account configuration

SourceForge.net — 2013-04-02T02:12:20

Patches item #1773635, was opened at 2007-08-13 22:45
Message generated for change (Comment added) made by legoscia
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586352&aid=1773635&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Resolution: None
Priority: 5
Private: No
Submitted By: Xavier Maillard (zedek)
Assigned to: Nobody/Anonymous (nobody)
Summary: Multi-account configuration

Initial Comment:
This patch implements authentication based on an external authinfo file (ala FTP).

Actually it just support a file. Future enhancements will likely add an authinfo-alist (in addition of a file).

Please review/comment/correct.

Patch made against CVS HEAD as of 2007-08-14.

----------------------------------------------------------------------

Date: 2013-04-01 19:12

Message:
Ah, you're right, I missed that part. And just the other day I was thinking
that it would be nice if jabber.el would read authinfo files :)

I'd rather have it use the auth-source library than reading the authinfo
file directly, though. I'll see if I can come up with a patch for that...
(though feel free to beat me to it!)

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2013-03-29 14:16

Message:
If I understand correctly, only one of those two patches ever made it into
emacs-jabber.

The other adds support for ~/.authinfo; Is there still a chance for
inclusion?

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2007-08-28 18:48

Message:
Logged In: YES 
user_id=920364
Originator: NO

Thanks a lot, and sorry about the delay... I just committed a modified
version of your patch.  Let's see if this works...

----------------------------------------------------------------------

Comment By: Xavier Maillard (zedek)
Date: 2007-08-16 13:28

Message:
Logged In: YES 
user_id=597884
Originator: YES

Ok, here is my first try to implement a jabber-account-list alist.

It adds support for multiple connections or one connection (given the
account name).

Please try this.
File Added: jabber-connect.el

----------------------------------------------------------------------

Comment By: Xavier Maillard (zedek)
Date: 2007-08-15 01:12

Message:
Logged In: YES 
user_id=597884
Originator: YES

Small fix of previous commit.
File Added: jabber-core-add-authinfo-auth.patch

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586352&aid=1773635&group_id=88346

------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2

[ emacs-jabber-Bugs-3423554 ] Contact list is empty in gmail

SourceForge.net — 2013-04-02T00:54:17

Bugs item #3423554, was opened at 2011-10-14 02:30
Message generated for change (Comment added) made by legoscia
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3423554&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: v0.8
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Contact list is empty in gmail

Initial Comment:
In the roster buffer for gmail accounts after authentication the contact list is empty. 
But the messaging function works well. For example, I can use jabber-connect-with
to send messages, and receiving works fine as well. Changing presence works too

emacs-jabber versions tried: 0.8.0, git(oct14,2011)

----------------------------------------------------------------------

Date: 2013-04-01 17:54

Message:
Could you try the 0.8.91 version, or the git version? There is a problem
with Google
Talk when using jabber.el 0.8.0, that should be fixed now.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3423554&group_id=88346

------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2

[ emacs-jabber-Patches-1773635 ] Multi-account configuration

SourceForge.net — 2013-03-29T21:16:17

Patches item #1773635, was opened at 2007-08-13 22:45
Message generated for change (Comment added) made by pipping
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586352&aid=1773635&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Xavier Maillard (zedek)
Assigned to: Nobody/Anonymous (nobody)
Summary: Multi-account configuration

Initial Comment:
This patch implements authentication based on an external authinfo file (ala FTP).

Actually it just support a file. Future enhancements will likely add an authinfo-alist (in addition of a file).

Please review/comment/correct.

Patch made against CVS HEAD as of 2007-08-14.

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2013-03-29 14:16

Message:
If I understand correctly, only one of those two patches ever made it into
emacs-jabber.

The other adds support for ~/.authinfo; Is there still a chance for
inclusion?

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2007-08-28 18:48

Message:
Logged In: YES 
user_id=920364
Originator: NO

Thanks a lot, and sorry about the delay... I just committed a modified
version of your patch.  Let's see if this works...

----------------------------------------------------------------------

Comment By: Xavier Maillard (zedek)
Date: 2007-08-16 13:28

Message:
Logged In: YES 
user_id=597884
Originator: YES

Ok, here is my first try to implement a jabber-account-list alist.

It adds support for multiple connections or one connection (given the
account name).

Please try this.
File Added: jabber-connect.el

----------------------------------------------------------------------

Comment By: Xavier Maillard (zedek)
Date: 2007-08-15 01:12

Message:
Logged In: YES 
user_id=597884
Originator: YES

Small fix of previous commit.
File Added: jabber-core-add-authinfo-auth.patch

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586352&aid=1773635&group_id=88346

------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2

[ emacs-jabber-Bugs-2833220 ] undo erases messages in chat buffer

SourceForge.net — 2013-01-23T22:57:30

Bugs item #2833220, was opened at 2009-08-06 08:38
Message generated for change (Comment added) made by legoscia
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=2833220&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: Git
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Evgenii Terechkov (evg_krsk)
Summary: undo erases messages in chat buffer

Initial Comment:
Undo erases not only my input in preview zone under three dashes, but also messages from participants in chat buffer.

----------------------------------------------------------------------

Date: 2013-01-23 14:57

Message:
This was "fixed" by disabling undo in chat buffers on 2010-01-10.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=2833220&group_id=88346

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d

[ emacs-jabber-Bugs-3601013 ] Roster keys in chat buffer

SourceForge.net — 2013-01-15T19:41:40

Bugs item #3601013, was opened at 2013-01-15 11:41
Message generated for change (Tracker Item Submitted) made by
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3601013&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interface
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Roster keys in chat buffer

Initial Comment:
When you type RET in the roster on the contact, chat buffer with this contact is opened. Kill this buffer and type RET in roster again: before first user input roster keybindings are in effect. After user makes any keypress or C-g or even C-h, buffer keybindings become active.
For example, first time you start chat with foo< at >test.com. You press 's' button, self-insert-command is run as expected.
Now you kill buffer and start chat with foo< at >test.com again. You press 's' button, jabber-send-subscription-request is run. If you type C-g followed by 's', self-insert-command is run as expected.
This effect continues untill emacs is restarted.
If you open chat via M-x jabber-chat-with or C-x C-j C-j, it's ok. This bug only encountered when you open chat from roster.
Tested on emacs 24.2.1 with -Q option.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3601013&group_id=88346

------------------------------------------------------------------------------
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512

[ emacs-jabber-Bugs-2950401 ] Invalid TLS certificate checking

SourceForge.net — 2013-01-14T01:21:21

Bugs item #2950401, was opened at 2010-02-12 00:12
Message generated for change (Comment added) made by legoscia
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=2950401&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Connectivity
Group: Git
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Invalid TLS certificate checking

Initial Comment:
Debian bug report (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569338):

when connecting via TLS, jabber.el does not check for the correct CN in
the certificate:

  Jabber-ID: bob< at >example.com/Emacs
  DNS:       _xmpp-client._tcp.example.com IN SRV 50 50 5022 jabber.example.org.

jabber.el now looks up the SRV entry and connects to
jabber.example.org.  It then expects the certificate's CN to match
"jabber.example.org", but it should expect "example.com" as documented
in RFC 3920:

  Certificates MUST be checked against the hostname as provided by the
  initiating entity (e.g., a user), not the hostname as resolved via the
  Domain Name System; e.g., if the user specifies a hostname of
  "example.com" but a DNS SRV lookup returned "im.example.com", the
  certificate MUST be checked as "example.com".
    -- http://xmpp.org/rfcs/rfc3920.html#tls, 8.


----------------------------------------------------------------------

Date: 2013-01-13 17:21

Message:
This is fixed with the new "native" TLS connection feature; see
jabber-starttls-process-input in jabber-conn.el.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=2950401&group_id=88346

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412

[ emacs-jabber-Bugs-3152972 ] URLs stop being highlighting

SourceForge.net — 2013-01-14T01:16:57

Bugs item #3152972, was opened at 2011-01-07 08:26
Message generated for change (Comment added) made by legoscia
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3152972&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interface
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: eurekafag ()
Assigned to: Nobody/Anonymous (nobody)
Summary: URLs stop being highlighting

Initial Comment:
URLs become plain inactive text after buffer length reaches ~30000. I checked this using (point). All URLs can't be opened with C-c RET after that, they aren't highlighted. It's a pain for active conferences. Ugly workaround: C-x C-k RET and then wait for message in that conference, a new buffer will be created with working URLs.

----------------------------------------------------------------------

Date: 2013-01-13 17:16

Message:
Turns out this is a feature:

goto-address-fontify-maximum-size is a variable defined in `goto-addr.el'.
Its value is 30000

Maybe goto-address should have an option to look at the _last_ 30000
characters instead...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3152972&group_id=88346

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412

[ emacs-jabber-Feature Requests-3518686 ] Use emacs 24 builtinsupport for GnuTLS

SourceForge.net — 2012-09-16T23:11:52

Feature Requests item #3518686, was opened at 2012-04-17 00:39
Message generated for change (Settings changed) made by legoscia
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586353&aid=3518686&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Git
Priority: 5
Private: No
Submitted By: Kai Tetzlaff (kate21)
Assigned to: Magnus Henoch (legoscia)
Summary: Use emacs 24 builtin support for GnuTLS

Initial Comment:
SSL/TLS connections are currently established using external programs (gnutls-cli, starrtls) which does not work very well in Windows. Emacs 24 supports direct use of the GnuTLS as a shared library. It would be great if (optional) support for this could be added to jabber.el.

----------------------------------------------------------------------

Comment By: Kai Tetzlaff (kate21)
Date: 2012-06-13 16:11

Message:
:)
Just got around to do some testing with the current git HEAD. I was using
the just released emacs 24.1 on OS X (10.6) and Windows 7. On both systems,
i have been able to connect to different jabber servers using the builtin
GnuTLS support. So far, i've tried to connect to 3 different jabber
servers, including google talk without a problem.

What i have not checked yet, is how the TLS connection survives network
interruptions (e.g. when using a cellular modem to establish the
connection). But that's really not that important for now.

Thanks a lot!

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2012-05-15 14:48

Message:
Just committed a change that tries to do this. Let me know how it works :)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586353&aid=3518686&group_id=88346

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html

[ emacs-jabber-Bugs-3527994 ] Problems with native gnutls

SourceForge.net — 2012-06-20T14:06:59

Bugs item #3527994, was opened at 2012-05-18 11:17
Message generated for change (Comment added) made by legoscia
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Priority: 5
Private: No
Submitted By: Elias Pipping (pipping)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with native gnutls

Initial Comment:
Ever since

commit f54c1b54b308f38caac66ae567e5f64f6adc631c
Author: Magnus Henoch <legoscia< at >users.sourceforge.net>
Date:   Tue May 15 22:39:43 2012 +0100

    Support native GnuTLS for STARTTLS
    [..]

I've found myself unable to connect to lavabit.com using starttls. Here's what I found in my message buffer:

gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated.
gnutls.el: (err=[-110] The TLS connection was non-properly terminated.) boot: (:priority NORMAL :hostname lavabit.com :loglevel 0 :min-prime-bits nil :trustfiles (/etc/ssl/certs/ca-certificates.crt) :crlfiles nil :keylist nil :verify-flags nil :verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [0] (Emacs) fatal error: The specified session has been invalidated for some reason. [100 times]
ME< at >lavabit.com/nil: connection lost: `connection broken by remote peer
'

(where i replaced my username with ME)

Here's the relevant part of my config:

(setq jabber-account-list '(("ME< at >lavabit.com"
     (:password . "PASSWORD")
     (:network-server . "lavabit.com")
     (:connection-type . starttls)
     (:port . 5222)))

----------------------------------------------------------------------

Date: 2012-06-20 07:06

Message:
That's good to hear; I was running out of things to try :) Closing this
ticket.

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-06-04 09:56

Message:
Sorry, my testing must've been flawed somehow.

I updated and tried again, now it works. Bisection led me to
c382ddead8c42452c3838263f41fc5ba0d997d62. Thanks :)

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-31 08:08

Message:
That doesn't seem to change anything.

A message that is written to the line at the bottom of the screen but not
the message buffer is this btw:

  connection lost: `STARTTLS negotation files: GnuTLS error: #<process
jabber>, -110'

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2012-05-31 02:27

Message:
Just stumbled upon another thing: in the function jabber-ssl-send in
jabber-conn.el, there are two calls to process-send-string, the second one
just sending an extra newline. Could you try commenting out the second one?

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-30 15:26

Message:
I'm on emacs 24.0.97.1 and gnutls 3.0.19.

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2012-05-30 13:53

Message:
Sorry about the delay in responding...

I'm seeing this myself on Mac OS X, with Emacs 24.1.50 and GnuTLS 2.12.11
from Macports; it worked on a Linux machine I have no access to at the
moment... Which OS and GnuTLS version are you using? Are you able to try
different ones?

I discovered that setting gnutls-log-level to 5 yields more log messages,
but they don't tell me very much; pasting here in case it makes the problem
obvious to someone:

gnutls.c: [1] (Emacs) allocating credentials
gnutls.c: [2] (Emacs) allocating x509 credentials
gnutls.c: [2] (Emacs) using default verification flags
gnutls.c: [1] (Emacs) gnutls callbacks
gnutls.c: [1] (Emacs) gnutls_init
gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #0

gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
gnutls.c: [1] (Emacs) setting the priority string
gnutls.c: [2] ASSERT: gnutls_constate.c:695

gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: DHE_DSS_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_MD5

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SAFE RENEGOTIATION (1
bytes)

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.2) DSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.1) RSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.1) RSA-SHA1

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.2) DSA-SHA1

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SIGNATURE ALGORITHMS (10
bytes)

gnutls.c: [3] HSK[0x11c53de00]: CLIENT HELLO was sent [112 bytes]

gnutls.c: [6] BUF[HSK]: Inserted 112 bytes of Data

gnutls.c: [7] HWRITE: enqueued 112. Total 112 bytes.

gnutls.c: [7] HWRITE FLUSH: 112 bytes in buffer.

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[0] Handshake(22) with
length: 112

gnutls.c: [7] WRITE: enqueued 117 bytes for 0xb. Total 117 bytes.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[1] Handshake(22) with length:
117

gnutls.c: [7] HWRITE: wrote 112 bytes, 0 bytes left.

gnutls.c: [7] WRITE FLUSH: 117 bytes in buffer.

gnutls.c: [7] WRITE: wrote 117 bytes, 0 bytes left.

gnutls.c: [7] READ: -1 returned from 0xb, errno=35 gerrno=0

gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable,
try again.
gnutls.c: [7] READ: Got 0 bytes from 0xb

gnutls.c: [7] READ: read 0 bytes from 0xb

gnutls.c: [2] ASSERT: gnutls_buffers.c:640

gnutls.c: [2] ASSERT: gnutls_record.c:969

gnutls.c: [2] ASSERT: gnutls_handshake.c:2762

gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [0] (Emacs) fatal error: A TLS packet with unexpected length was
received.
gnutls.c: [4] REC: Sending Alert[2|22] - Record overflow

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[1] Alert(21) with length: 2

gnutls.c: [7] WRITE: enqueued 7 bytes for 0xb. Total 7 bytes.

gnutls.c: [7] WRITE FLUSH: 7 bytes in buffer.

gnutls.c: [7] WRITE: wrote 7 bytes, 0 bytes left.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[2] Alert(21) with length: 7

gnutls.el: (err=[-9] A TLS packet with unexpected length was received.)
boot: (:priority NORMAL :hostname jabber.se :loglevel 10 :min-prime-bits
nil :trustfiles nil :crlfiles nil :keylist nil :verify-flags nil
:verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [2] (Emacs) Deallocating x509 credentials
gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [4] REC[0x11c53de00]: Epoch #0 freed

gnutls.c: [4] REC[0x11c53de00]: Epoch #1 freed


----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-19 07:44

Message:
After

commit 1dca591d17cf084e6d870f55898e9343926f8bb8
Author: Magnus Henoch <magnus.henoch< at >gmail.com>
Date:   Sat May 19 15:01:05 2012 +0100

    Fix reporting of STARTTLS negotiation errors [..]

My message buffer looks like this:

Sat May 19 16:40:07 2012: Starting jabber-connection
Sat May 19 16:40:07 2012: jabber-connection enters :connecting
Sat May 19 16:40:07 2012: Found enter function for :connecting: #[(fsm
state-data) "\306\307\"\310!\306\311\"\306\312\"\306\313\"


$\210-\314D\207" [state-data connection-type connect-function server
network-server port plist-get :connection-type jabber-get-connect-function
:server :network-server :port nil fsm] 5]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :connected to jabber-connection in state
:connecting
Sat May 19 16:40:07 2012: jabber-connection enters :connected
Sat May 19 16:40:07 2012: Found enter function for :connected: #[(fsm
state-data) "\303!\210\304
\305D\207" [fsm *jabber-connected* state-data jabber-send-stream-header t
nil] 2]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:07 2012: Sent :stream-start to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: jabber-connection enters :starttls
Sat May 19 16:40:08 2012: Found enter function for :starttls: #[(fsm
state-data) "\302!\210\303D\207" [fsm state-data jabber-starttls-initiate
nil] 2]
Sat May 19 16:40:08 2012: Using data from enter function
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: jabber-connection enters nil
Sat May 19 16:40:08 2012: Found enter function for nil: #[(fsm state-data)
"\306\307\"\310!\203\"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ emacs-jabber-Feature Requests-3518686 ] Use emacs 24 builtinsupport for GnuTLS

SourceForge.net — 2012-06-13T23:11:31

Feature Requests item #3518686, was opened at 2012-04-17 00:39
Message generated for change (Comment added) made by kate21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586353&aid=3518686&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Git
Status: Open
Priority: 5
Private: No
Submitted By: Kai Tetzlaff (kate21)
Assigned to: Magnus Henoch (legoscia)
Summary: Use emacs 24 builtin support for GnuTLS

Initial Comment:
SSL/TLS connections are currently established using external programs (gnutls-cli, starrtls) which does not work very well in Windows. Emacs 24 supports direct use of the GnuTLS as a shared library. It would be great if (optional) support for this could be added to jabber.el.

----------------------------------------------------------------------

Comment By: Kai Tetzlaff (kate21)
Date: 2012-06-13 16:11

Message:
:)
Just got around to do some testing with the current git HEAD. I was using
the just released emacs 24.1 on OS X (10.6) and Windows 7. On both systems,
i have been able to connect to different jabber servers using the builtin
GnuTLS support. So far, i've tried to connect to 3 different jabber
servers, including google talk without a problem.

What i have not checked yet, is how the TLS connection survives network
interruptions (e.g. when using a cellular modem to establish the
connection). But that's really not that important for now.

Thanks a lot!

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2012-05-15 14:48

Message:
Just committed a change that tries to do this. Let me know how it works :)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586353&aid=3518686&group_id=88346

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ emacs-jabber-Bugs-3527994 ] Problems with native gnutls

SourceForge.net — 2012-06-04T16:56:26

Bugs item #3527994, was opened at 2012-05-18 11:17
Message generated for change (Comment added) made by pipping
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Elias Pipping (pipping)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with native gnutls

Initial Comment:
Ever since

commit f54c1b54b308f38caac66ae567e5f64f6adc631c
Author: Magnus Henoch <legoscia< at >users.sourceforge.net>
Date:   Tue May 15 22:39:43 2012 +0100

    Support native GnuTLS for STARTTLS
    [..]

I've found myself unable to connect to lavabit.com using starttls. Here's what I found in my message buffer:

gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated.
gnutls.el: (err=[-110] The TLS connection was non-properly terminated.) boot: (:priority NORMAL :hostname lavabit.com :loglevel 0 :min-prime-bits nil :trustfiles (/etc/ssl/certs/ca-certificates.crt) :crlfiles nil :keylist nil :verify-flags nil :verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [0] (Emacs) fatal error: The specified session has been invalidated for some reason. [100 times]
ME< at >lavabit.com/nil: connection lost: `connection broken by remote peer
'

(where i replaced my username with ME)

Here's the relevant part of my config:

(setq jabber-account-list '(("ME< at >lavabit.com"
     (:password . "PASSWORD")
     (:network-server . "lavabit.com")
     (:connection-type . starttls)
     (:port . 5222)))

----------------------------------------------------------------------

Date: 2012-06-04 09:56

Message:
Sorry, my testing must've been flawed somehow.

I updated and tried again, now it works. Bisection led me to
c382ddead8c42452c3838263f41fc5ba0d997d62. Thanks :)

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-31 08:08

Message:
That doesn't seem to change anything.

A message that is written to the line at the bottom of the screen but not
the message buffer is this btw:

  connection lost: `STARTTLS negotation files: GnuTLS error: #<process
jabber>, -110'

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2012-05-31 02:27

Message:
Just stumbled upon another thing: in the function jabber-ssl-send in
jabber-conn.el, there are two calls to process-send-string, the second one
just sending an extra newline. Could you try commenting out the second one?

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-30 15:26

Message:
I'm on emacs 24.0.97.1 and gnutls 3.0.19.

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2012-05-30 13:53

Message:
Sorry about the delay in responding...

I'm seeing this myself on Mac OS X, with Emacs 24.1.50 and GnuTLS 2.12.11
from Macports; it worked on a Linux machine I have no access to at the
moment... Which OS and GnuTLS version are you using? Are you able to try
different ones?

I discovered that setting gnutls-log-level to 5 yields more log messages,
but they don't tell me very much; pasting here in case it makes the problem
obvious to someone:

gnutls.c: [1] (Emacs) allocating credentials
gnutls.c: [2] (Emacs) allocating x509 credentials
gnutls.c: [2] (Emacs) using default verification flags
gnutls.c: [1] (Emacs) gnutls callbacks
gnutls.c: [1] (Emacs) gnutls_init
gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #0

gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
gnutls.c: [1] (Emacs) setting the priority string
gnutls.c: [2] ASSERT: gnutls_constate.c:695

gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: DHE_DSS_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_MD5

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SAFE RENEGOTIATION (1
bytes)

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.2) DSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.1) RSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.1) RSA-SHA1

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.2) DSA-SHA1

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SIGNATURE ALGORITHMS (10
bytes)

gnutls.c: [3] HSK[0x11c53de00]: CLIENT HELLO was sent [112 bytes]

gnutls.c: [6] BUF[HSK]: Inserted 112 bytes of Data

gnutls.c: [7] HWRITE: enqueued 112. Total 112 bytes.

gnutls.c: [7] HWRITE FLUSH: 112 bytes in buffer.

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[0] Handshake(22) with
length: 112

gnutls.c: [7] WRITE: enqueued 117 bytes for 0xb. Total 117 bytes.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[1] Handshake(22) with length:
117

gnutls.c: [7] HWRITE: wrote 112 bytes, 0 bytes left.

gnutls.c: [7] WRITE FLUSH: 117 bytes in buffer.

gnutls.c: [7] WRITE: wrote 117 bytes, 0 bytes left.

gnutls.c: [7] READ: -1 returned from 0xb, errno=35 gerrno=0

gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable,
try again.
gnutls.c: [7] READ: Got 0 bytes from 0xb

gnutls.c: [7] READ: read 0 bytes from 0xb

gnutls.c: [2] ASSERT: gnutls_buffers.c:640

gnutls.c: [2] ASSERT: gnutls_record.c:969

gnutls.c: [2] ASSERT: gnutls_handshake.c:2762

gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [0] (Emacs) fatal error: A TLS packet with unexpected length was
received.
gnutls.c: [4] REC: Sending Alert[2|22] - Record overflow

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[1] Alert(21) with length: 2

gnutls.c: [7] WRITE: enqueued 7 bytes for 0xb. Total 7 bytes.

gnutls.c: [7] WRITE FLUSH: 7 bytes in buffer.

gnutls.c: [7] WRITE: wrote 7 bytes, 0 bytes left.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[2] Alert(21) with length: 7

gnutls.el: (err=[-9] A TLS packet with unexpected length was received.)
boot: (:priority NORMAL :hostname jabber.se :loglevel 10 :min-prime-bits
nil :trustfiles nil :crlfiles nil :keylist nil :verify-flags nil
:verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [2] (Emacs) Deallocating x509 credentials
gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [4] REC[0x11c53de00]: Epoch #0 freed

gnutls.c: [4] REC[0x11c53de00]: Epoch #1 freed


----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-19 07:44

Message:
After

commit 1dca591d17cf084e6d870f55898e9343926f8bb8
Author: Magnus Henoch <magnus.henoch< at >gmail.com>
Date:   Sat May 19 15:01:05 2012 +0100

    Fix reporting of STARTTLS negotiation errors [..]

My message buffer looks like this:

Sat May 19 16:40:07 2012: Starting jabber-connection
Sat May 19 16:40:07 2012: jabber-connection enters :connecting
Sat May 19 16:40:07 2012: Found enter function for :connecting: #[(fsm
state-data) "\306\307\"\310!\306\311\"\306\312\"\306\313\"


$\210-\314D\207" [state-data connection-type connect-function server
network-server port plist-get :connection-type jabber-get-connect-function
:server :network-server :port nil fsm] 5]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :connected to jabber-connection in state
:connecting
Sat May 19 16:40:07 2012: jabber-connection enters :connected
Sat May 19 16:40:07 2012: Found enter function for :connected: #[(fsm
state-data) "\303!\210\304
\305D\207" [fsm *jabber-connected* state-data jabber-send-stream-header t
nil] 2]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:07 2012: Sent :stream-start to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: jabber-connection enters :starttls
Sat May 19 16:40:08 2012: Found enter function for :starttls: #[(fsm
state-data) "\302!\210\303D\207" [fsm state-data jabber-starttls-initiate
nil] 2]
Sat May 19 16:40:08 2012: Using data from enter function
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: jabber-connection enters nil
Sat May 19 16:40:08 2012: Found enter function for nil: #[(fsm state-data)
"\306\307\"\310!\203\"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ emacs-jabber-Bugs-3531561 ] assoc.el deprecated in emacs 24.2

SourceForge.net — 2012-06-02T21:11:11

Bugs item #3531561, was opened at 2012-06-02 14:11
Message generated for change (Tracker Item Submitted) made by haawda
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3531561&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Stefan Husmann (haawda)
Assigned to: Nobody/Anonymous (nobody)
Summary: assoc.el deprecated in emacs 24.2

Initial Comment:
According to http://www.emacswiki.org/emacs-en/assoc-deprecated assoc.el will be removed in emacs 24.2. assoc.el is required in jabber-presence.el and jabber-muc-nick-coloring.el. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3531561&group_id=88346

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ emacs-jabber-Bugs-3527994 ] Problems with native gnutls

SourceForge.net — 2012-05-31T15:08:27

Bugs item #3527994, was opened at 2012-05-18 11:17
Message generated for change (Comment added) made by pipping
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Elias Pipping (pipping)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with native gnutls

Initial Comment:
Ever since

commit f54c1b54b308f38caac66ae567e5f64f6adc631c
Author: Magnus Henoch <legoscia< at >users.sourceforge.net>
Date:   Tue May 15 22:39:43 2012 +0100

    Support native GnuTLS for STARTTLS
    [..]

I've found myself unable to connect to lavabit.com using starttls. Here's what I found in my message buffer:

gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated.
gnutls.el: (err=[-110] The TLS connection was non-properly terminated.) boot: (:priority NORMAL :hostname lavabit.com :loglevel 0 :min-prime-bits nil :trustfiles (/etc/ssl/certs/ca-certificates.crt) :crlfiles nil :keylist nil :verify-flags nil :verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [0] (Emacs) fatal error: The specified session has been invalidated for some reason. [100 times]
ME< at >lavabit.com/nil: connection lost: `connection broken by remote peer
'

(where i replaced my username with ME)

Here's the relevant part of my config:

(setq jabber-account-list '(("ME< at >lavabit.com"
     (:password . "PASSWORD")
     (:network-server . "lavabit.com")
     (:connection-type . starttls)
     (:port . 5222)))

----------------------------------------------------------------------

Date: 2012-05-31 08:08

Message:
That doesn't seem to change anything.

A message that is written to the line at the bottom of the screen but not
the message buffer is this btw:

  connection lost: `STARTTLS negotation files: GnuTLS error: #<process
jabber>, -110'

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2012-05-31 02:27

Message:
Just stumbled upon another thing: in the function jabber-ssl-send in
jabber-conn.el, there are two calls to process-send-string, the second one
just sending an extra newline. Could you try commenting out the second one?

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-30 15:26

Message:
I'm on emacs 24.0.97.1 and gnutls 3.0.19.

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2012-05-30 13:53

Message:
Sorry about the delay in responding...

I'm seeing this myself on Mac OS X, with Emacs 24.1.50 and GnuTLS 2.12.11
from Macports; it worked on a Linux machine I have no access to at the
moment... Which OS and GnuTLS version are you using? Are you able to try
different ones?

I discovered that setting gnutls-log-level to 5 yields more log messages,
but they don't tell me very much; pasting here in case it makes the problem
obvious to someone:

gnutls.c: [1] (Emacs) allocating credentials
gnutls.c: [2] (Emacs) allocating x509 credentials
gnutls.c: [2] (Emacs) using default verification flags
gnutls.c: [1] (Emacs) gnutls callbacks
gnutls.c: [1] (Emacs) gnutls_init
gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #0

gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
gnutls.c: [1] (Emacs) setting the priority string
gnutls.c: [2] ASSERT: gnutls_constate.c:695

gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: DHE_DSS_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_MD5

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SAFE RENEGOTIATION (1
bytes)

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.2) DSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.1) RSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.1) RSA-SHA1

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.2) DSA-SHA1

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SIGNATURE ALGORITHMS (10
bytes)

gnutls.c: [3] HSK[0x11c53de00]: CLIENT HELLO was sent [112 bytes]

gnutls.c: [6] BUF[HSK]: Inserted 112 bytes of Data

gnutls.c: [7] HWRITE: enqueued 112. Total 112 bytes.

gnutls.c: [7] HWRITE FLUSH: 112 bytes in buffer.

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[0] Handshake(22) with
length: 112

gnutls.c: [7] WRITE: enqueued 117 bytes for 0xb. Total 117 bytes.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[1] Handshake(22) with length:
117

gnutls.c: [7] HWRITE: wrote 112 bytes, 0 bytes left.

gnutls.c: [7] WRITE FLUSH: 117 bytes in buffer.

gnutls.c: [7] WRITE: wrote 117 bytes, 0 bytes left.

gnutls.c: [7] READ: -1 returned from 0xb, errno=35 gerrno=0

gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable,
try again.
gnutls.c: [7] READ: Got 0 bytes from 0xb

gnutls.c: [7] READ: read 0 bytes from 0xb

gnutls.c: [2] ASSERT: gnutls_buffers.c:640

gnutls.c: [2] ASSERT: gnutls_record.c:969

gnutls.c: [2] ASSERT: gnutls_handshake.c:2762

gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [0] (Emacs) fatal error: A TLS packet with unexpected length was
received.
gnutls.c: [4] REC: Sending Alert[2|22] - Record overflow

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[1] Alert(21) with length: 2

gnutls.c: [7] WRITE: enqueued 7 bytes for 0xb. Total 7 bytes.

gnutls.c: [7] WRITE FLUSH: 7 bytes in buffer.

gnutls.c: [7] WRITE: wrote 7 bytes, 0 bytes left.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[2] Alert(21) with length: 7

gnutls.el: (err=[-9] A TLS packet with unexpected length was received.)
boot: (:priority NORMAL :hostname jabber.se :loglevel 10 :min-prime-bits
nil :trustfiles nil :crlfiles nil :keylist nil :verify-flags nil
:verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [2] (Emacs) Deallocating x509 credentials
gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [4] REC[0x11c53de00]: Epoch #0 freed

gnutls.c: [4] REC[0x11c53de00]: Epoch #1 freed


----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-19 07:44

Message:
After

commit 1dca591d17cf084e6d870f55898e9343926f8bb8
Author: Magnus Henoch <magnus.henoch< at >gmail.com>
Date:   Sat May 19 15:01:05 2012 +0100

    Fix reporting of STARTTLS negotiation errors [..]

My message buffer looks like this:

Sat May 19 16:40:07 2012: Starting jabber-connection
Sat May 19 16:40:07 2012: jabber-connection enters :connecting
Sat May 19 16:40:07 2012: Found enter function for :connecting: #[(fsm
state-data) "\306\307\"\310!\306\311\"\306\312\"\306\313\"


$\210-\314D\207" [state-data connection-type connect-function server
network-server port plist-get :connection-type jabber-get-connect-function
:server :network-server :port nil fsm] 5]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :connected to jabber-connection in state
:connecting
Sat May 19 16:40:07 2012: jabber-connection enters :connected
Sat May 19 16:40:07 2012: Found enter function for :connected: #[(fsm
state-data) "\303!\210\304
\305D\207" [fsm *jabber-connected* state-data jabber-send-stream-header t
nil] 2]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:07 2012: Sent :stream-start to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: jabber-connection enters :starttls
Sat May 19 16:40:08 2012: Found enter function for :starttls: #[(fsm
state-data) "\302!\210\303D\207" [fsm state-data jabber-starttls-initiate
nil] 2]
Sat May 19 16:40:08 2012: Using data from enter function
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: jabber-connection enters nil
Sat May 19 16:40:08 2012: Found enter function for nil: #[(fsm state-data)
"\306\307\"\310!\203\"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ emacs-jabber-Bugs-3527994 ] Problems with native gnutls

SourceForge.net — 2012-05-31T09:27:41

Bugs item #3527994, was opened at 2012-05-18 11:17
Message generated for change (Comment added) made by legoscia
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Elias Pipping (pipping)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with native gnutls

Initial Comment:
Ever since

commit f54c1b54b308f38caac66ae567e5f64f6adc631c
Author: Magnus Henoch <legoscia< at >users.sourceforge.net>
Date:   Tue May 15 22:39:43 2012 +0100

    Support native GnuTLS for STARTTLS
    [..]

I've found myself unable to connect to lavabit.com using starttls. Here's what I found in my message buffer:

gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated.
gnutls.el: (err=[-110] The TLS connection was non-properly terminated.) boot: (:priority NORMAL :hostname lavabit.com :loglevel 0 :min-prime-bits nil :trustfiles (/etc/ssl/certs/ca-certificates.crt) :crlfiles nil :keylist nil :verify-flags nil :verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [0] (Emacs) fatal error: The specified session has been invalidated for some reason. [100 times]
ME< at >lavabit.com/nil: connection lost: `connection broken by remote peer
'

(where i replaced my username with ME)

Here's the relevant part of my config:

(setq jabber-account-list '(("ME< at >lavabit.com"
     (:password . "PASSWORD")
     (:network-server . "lavabit.com")
     (:connection-type . starttls)
     (:port . 5222)))

----------------------------------------------------------------------

Date: 2012-05-31 02:27

Message:
Just stumbled upon another thing: in the function jabber-ssl-send in
jabber-conn.el, there are two calls to process-send-string, the second one
just sending an extra newline. Could you try commenting out the second one?

----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-30 15:26

Message:
I'm on emacs 24.0.97.1 and gnutls 3.0.19.

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2012-05-30 13:53

Message:
Sorry about the delay in responding...

I'm seeing this myself on Mac OS X, with Emacs 24.1.50 and GnuTLS 2.12.11
from Macports; it worked on a Linux machine I have no access to at the
moment... Which OS and GnuTLS version are you using? Are you able to try
different ones?

I discovered that setting gnutls-log-level to 5 yields more log messages,
but they don't tell me very much; pasting here in case it makes the problem
obvious to someone:

gnutls.c: [1] (Emacs) allocating credentials
gnutls.c: [2] (Emacs) allocating x509 credentials
gnutls.c: [2] (Emacs) using default verification flags
gnutls.c: [1] (Emacs) gnutls callbacks
gnutls.c: [1] (Emacs) gnutls_init
gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #0

gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
gnutls.c: [1] (Emacs) setting the priority string
gnutls.c: [2] ASSERT: gnutls_constate.c:695

gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: DHE_DSS_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_MD5

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SAFE RENEGOTIATION (1
bytes)

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.2) DSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.1) RSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.1) RSA-SHA1

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.2) DSA-SHA1

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SIGNATURE ALGORITHMS (10
bytes)

gnutls.c: [3] HSK[0x11c53de00]: CLIENT HELLO was sent [112 bytes]

gnutls.c: [6] BUF[HSK]: Inserted 112 bytes of Data

gnutls.c: [7] HWRITE: enqueued 112. Total 112 bytes.

gnutls.c: [7] HWRITE FLUSH: 112 bytes in buffer.

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[0] Handshake(22) with
length: 112

gnutls.c: [7] WRITE: enqueued 117 bytes for 0xb. Total 117 bytes.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[1] Handshake(22) with length:
117

gnutls.c: [7] HWRITE: wrote 112 bytes, 0 bytes left.

gnutls.c: [7] WRITE FLUSH: 117 bytes in buffer.

gnutls.c: [7] WRITE: wrote 117 bytes, 0 bytes left.

gnutls.c: [7] READ: -1 returned from 0xb, errno=35 gerrno=0

gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable,
try again.
gnutls.c: [7] READ: Got 0 bytes from 0xb

gnutls.c: [7] READ: read 0 bytes from 0xb

gnutls.c: [2] ASSERT: gnutls_buffers.c:640

gnutls.c: [2] ASSERT: gnutls_record.c:969

gnutls.c: [2] ASSERT: gnutls_handshake.c:2762

gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [0] (Emacs) fatal error: A TLS packet with unexpected length was
received.
gnutls.c: [4] REC: Sending Alert[2|22] - Record overflow

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[1] Alert(21) with length: 2

gnutls.c: [7] WRITE: enqueued 7 bytes for 0xb. Total 7 bytes.

gnutls.c: [7] WRITE FLUSH: 7 bytes in buffer.

gnutls.c: [7] WRITE: wrote 7 bytes, 0 bytes left.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[2] Alert(21) with length: 7

gnutls.el: (err=[-9] A TLS packet with unexpected length was received.)
boot: (:priority NORMAL :hostname jabber.se :loglevel 10 :min-prime-bits
nil :trustfiles nil :crlfiles nil :keylist nil :verify-flags nil
:verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [2] (Emacs) Deallocating x509 credentials
gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [4] REC[0x11c53de00]: Epoch #0 freed

gnutls.c: [4] REC[0x11c53de00]: Epoch #1 freed


----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-19 07:44

Message:
After

commit 1dca591d17cf084e6d870f55898e9343926f8bb8
Author: Magnus Henoch <magnus.henoch< at >gmail.com>
Date:   Sat May 19 15:01:05 2012 +0100

    Fix reporting of STARTTLS negotiation errors [..]

My message buffer looks like this:

Sat May 19 16:40:07 2012: Starting jabber-connection
Sat May 19 16:40:07 2012: jabber-connection enters :connecting
Sat May 19 16:40:07 2012: Found enter function for :connecting: #[(fsm
state-data) "\306\307\"\310!\306\311\"\306\312\"\306\313\"


$\210-\314D\207" [state-data connection-type connect-function server
network-server port plist-get :connection-type jabber-get-connect-function
:server :network-server :port nil fsm] 5]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :connected to jabber-connection in state
:connecting
Sat May 19 16:40:07 2012: jabber-connection enters :connected
Sat May 19 16:40:07 2012: Found enter function for :connected: #[(fsm
state-data) "\303!\210\304
\305D\207" [fsm *jabber-connected* state-data jabber-send-stream-header t
nil] 2]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:07 2012: Sent :stream-start to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: jabber-connection enters :starttls
Sat May 19 16:40:08 2012: Found enter function for :starttls: #[(fsm
state-data) "\302!\210\303D\207" [fsm state-data jabber-starttls-initiate
nil] 2]
Sat May 19 16:40:08 2012: Using data from enter function
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: jabber-connection enters nil
Sat May 19 16:40:08 2012: Found enter function for nil: #[(fsm state-data)
"\306\307\"\310!\203\"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ emacs-jabber-Bugs-3527994 ] Problems with native gnutls

SourceForge.net — 2012-05-30T22:26:14

Bugs item #3527994, was opened at 2012-05-18 11:17
Message generated for change (Comment added) made by pipping
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Elias Pipping (pipping)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with native gnutls

Initial Comment:
Ever since

commit f54c1b54b308f38caac66ae567e5f64f6adc631c
Author: Magnus Henoch <legoscia< at >users.sourceforge.net>
Date:   Tue May 15 22:39:43 2012 +0100

    Support native GnuTLS for STARTTLS
    [..]

I've found myself unable to connect to lavabit.com using starttls. Here's what I found in my message buffer:

gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated.
gnutls.el: (err=[-110] The TLS connection was non-properly terminated.) boot: (:priority NORMAL :hostname lavabit.com :loglevel 0 :min-prime-bits nil :trustfiles (/etc/ssl/certs/ca-certificates.crt) :crlfiles nil :keylist nil :verify-flags nil :verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [0] (Emacs) fatal error: The specified session has been invalidated for some reason. [100 times]
ME< at >lavabit.com/nil: connection lost: `connection broken by remote peer
'

(where i replaced my username with ME)

Here's the relevant part of my config:

(setq jabber-account-list '(("ME< at >lavabit.com"
     (:password . "PASSWORD")
     (:network-server . "lavabit.com")
     (:connection-type . starttls)
     (:port . 5222)))

----------------------------------------------------------------------

Date: 2012-05-30 15:26

Message:
I'm on emacs 24.0.97.1 and gnutls 3.0.19.

----------------------------------------------------------------------

Comment By: Magnus Henoch (legoscia)
Date: 2012-05-30 13:53

Message:
Sorry about the delay in responding...

I'm seeing this myself on Mac OS X, with Emacs 24.1.50 and GnuTLS 2.12.11
from Macports; it worked on a Linux machine I have no access to at the
moment... Which OS and GnuTLS version are you using? Are you able to try
different ones?

I discovered that setting gnutls-log-level to 5 yields more log messages,
but they don't tell me very much; pasting here in case it makes the problem
obvious to someone:

gnutls.c: [1] (Emacs) allocating credentials
gnutls.c: [2] (Emacs) allocating x509 credentials
gnutls.c: [2] (Emacs) using default verification flags
gnutls.c: [1] (Emacs) gnutls callbacks
gnutls.c: [1] (Emacs) gnutls_init
gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #0

gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
gnutls.c: [1] (Emacs) setting the priority string
gnutls.c: [2] ASSERT: gnutls_constate.c:695

gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: DHE_DSS_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_MD5

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SAFE RENEGOTIATION (1
bytes)

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.2) DSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.1) RSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.1) RSA-SHA1

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.2) DSA-SHA1

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SIGNATURE ALGORITHMS (10
bytes)

gnutls.c: [3] HSK[0x11c53de00]: CLIENT HELLO was sent [112 bytes]

gnutls.c: [6] BUF[HSK]: Inserted 112 bytes of Data

gnutls.c: [7] HWRITE: enqueued 112. Total 112 bytes.

gnutls.c: [7] HWRITE FLUSH: 112 bytes in buffer.

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[0] Handshake(22) with
length: 112

gnutls.c: [7] WRITE: enqueued 117 bytes for 0xb. Total 117 bytes.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[1] Handshake(22) with length:
117

gnutls.c: [7] HWRITE: wrote 112 bytes, 0 bytes left.

gnutls.c: [7] WRITE FLUSH: 117 bytes in buffer.

gnutls.c: [7] WRITE: wrote 117 bytes, 0 bytes left.

gnutls.c: [7] READ: -1 returned from 0xb, errno=35 gerrno=0

gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable,
try again.
gnutls.c: [7] READ: Got 0 bytes from 0xb

gnutls.c: [7] READ: read 0 bytes from 0xb

gnutls.c: [2] ASSERT: gnutls_buffers.c:640

gnutls.c: [2] ASSERT: gnutls_record.c:969

gnutls.c: [2] ASSERT: gnutls_handshake.c:2762

gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [0] (Emacs) fatal error: A TLS packet with unexpected length was
received.
gnutls.c: [4] REC: Sending Alert[2|22] - Record overflow

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[1] Alert(21) with length: 2

gnutls.c: [7] WRITE: enqueued 7 bytes for 0xb. Total 7 bytes.

gnutls.c: [7] WRITE FLUSH: 7 bytes in buffer.

gnutls.c: [7] WRITE: wrote 7 bytes, 0 bytes left.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[2] Alert(21) with length: 7

gnutls.el: (err=[-9] A TLS packet with unexpected length was received.)
boot: (:priority NORMAL :hostname jabber.se :loglevel 10 :min-prime-bits
nil :trustfiles nil :crlfiles nil :keylist nil :verify-flags nil
:verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [2] (Emacs) Deallocating x509 credentials
gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [4] REC[0x11c53de00]: Epoch #0 freed

gnutls.c: [4] REC[0x11c53de00]: Epoch #1 freed


----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-19 07:44

Message:
After

commit 1dca591d17cf084e6d870f55898e9343926f8bb8
Author: Magnus Henoch <magnus.henoch< at >gmail.com>
Date:   Sat May 19 15:01:05 2012 +0100

    Fix reporting of STARTTLS negotiation errors [..]

My message buffer looks like this:

Sat May 19 16:40:07 2012: Starting jabber-connection
Sat May 19 16:40:07 2012: jabber-connection enters :connecting
Sat May 19 16:40:07 2012: Found enter function for :connecting: #[(fsm
state-data) "\306\307\"\310!\306\311\"\306\312\"\306\313\"


$\210-\314D\207" [state-data connection-type connect-function server
network-server port plist-get :connection-type jabber-get-connect-function
:server :network-server :port nil fsm] 5]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :connected to jabber-connection in state
:connecting
Sat May 19 16:40:07 2012: jabber-connection enters :connected
Sat May 19 16:40:07 2012: Found enter function for :connected: #[(fsm
state-data) "\303!\210\304
\305D\207" [fsm *jabber-connected* state-data jabber-send-stream-header t
nil] 2]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:07 2012: Sent :stream-start to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: jabber-connection enters :starttls
Sat May 19 16:40:08 2012: Found enter function for :starttls: #[(fsm
state-data) "\302!\210\303D\207" [fsm state-data jabber-starttls-initiate
nil] 2]
Sat May 19 16:40:08 2012: Using data from enter function
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: jabber-connection enters nil
Sat May 19 16:40:08 2012: Found enter function for nil: #[(fsm state-data)
"\306\307\"\310!\203\"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ emacs-jabber-Bugs-3527994 ] Problems with native gnutls

SourceForge.net — 2012-05-30T20:53:19

Bugs item #3527994, was opened at 2012-05-18 11:17
Message generated for change (Comment added) made by legoscia
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Elias Pipping (pipping)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with native gnutls

Initial Comment:
Ever since

commit f54c1b54b308f38caac66ae567e5f64f6adc631c
Author: Magnus Henoch <legoscia< at >users.sourceforge.net>
Date:   Tue May 15 22:39:43 2012 +0100

    Support native GnuTLS for STARTTLS
    [..]

I've found myself unable to connect to lavabit.com using starttls. Here's what I found in my message buffer:

gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated.
gnutls.el: (err=[-110] The TLS connection was non-properly terminated.) boot: (:priority NORMAL :hostname lavabit.com :loglevel 0 :min-prime-bits nil :trustfiles (/etc/ssl/certs/ca-certificates.crt) :crlfiles nil :keylist nil :verify-flags nil :verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [0] (Emacs) fatal error: The specified session has been invalidated for some reason. [100 times]
ME< at >lavabit.com/nil: connection lost: `connection broken by remote peer
'

(where i replaced my username with ME)

Here's the relevant part of my config:

(setq jabber-account-list '(("ME< at >lavabit.com"
     (:password . "PASSWORD")
     (:network-server . "lavabit.com")
     (:connection-type . starttls)
     (:port . 5222)))

----------------------------------------------------------------------

Date: 2012-05-30 13:53

Message:
Sorry about the delay in responding...

I'm seeing this myself on Mac OS X, with Emacs 24.1.50 and GnuTLS 2.12.11
from Macports; it worked on a Linux machine I have no access to at the
moment... Which OS and GnuTLS version are you using? Are you able to try
different ones?

I discovered that setting gnutls-log-level to 5 yields more log messages,
but they don't tell me very much; pasting here in case it makes the problem
obvious to someone:

gnutls.c: [1] (Emacs) allocating credentials
gnutls.c: [2] (Emacs) allocating x509 credentials
gnutls.c: [2] (Emacs) using default verification flags
gnutls.c: [1] (Emacs) gnutls callbacks
gnutls.c: [1] (Emacs) gnutls_init
gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #0

gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
gnutls.c: [1] (Emacs) setting the priority string
gnutls.c: [2] ASSERT: gnutls_constate.c:695

gnutls.c: [4] REC[0x11c53de00]: Allocating epoch #1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
DHE_DSS_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: DHE_DSS_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_128_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_128_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_AES_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_AES_256_CBC_SHA256

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite:
RSA_CAMELLIA_256_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_3DES_EDE_CBC_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_SHA1

gnutls.c: [3] HSK[0x11c53de00]: Keeping ciphersuite: RSA_ARCFOUR_MD5

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SAFE RENEGOTIATION (1
bytes)

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.2) DSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (4.1) RSA-SHA256

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.1) RSA-SHA1

gnutls.c: [2] EXT[SIGA]: sent signature algo (2.2) DSA-SHA1

gnutls.c: [2] EXT[0x11c53de00]: Sending extension SIGNATURE ALGORITHMS (10
bytes)

gnutls.c: [3] HSK[0x11c53de00]: CLIENT HELLO was sent [112 bytes]

gnutls.c: [6] BUF[HSK]: Inserted 112 bytes of Data

gnutls.c: [7] HWRITE: enqueued 112. Total 112 bytes.

gnutls.c: [7] HWRITE FLUSH: 112 bytes in buffer.

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[0] Handshake(22) with
length: 112

gnutls.c: [7] WRITE: enqueued 117 bytes for 0xb. Total 117 bytes.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[1] Handshake(22) with length:
117

gnutls.c: [7] HWRITE: wrote 112 bytes, 0 bytes left.

gnutls.c: [7] WRITE FLUSH: 117 bytes in buffer.

gnutls.c: [7] WRITE: wrote 117 bytes, 0 bytes left.

gnutls.c: [7] READ: -1 returned from 0xb, errno=35 gerrno=0

gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable,
try again.
gnutls.c: [7] READ: Got 0 bytes from 0xb

gnutls.c: [7] READ: read 0 bytes from 0xb

gnutls.c: [2] ASSERT: gnutls_buffers.c:640

gnutls.c: [2] ASSERT: gnutls_record.c:969

gnutls.c: [2] ASSERT: gnutls_handshake.c:2762

gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [0] (Emacs) fatal error: A TLS packet with unexpected length was
received.
gnutls.c: [4] REC: Sending Alert[2|22] - Record overflow

gnutls.c: [4] REC[0x11c53de00]: Sending Packet[1] Alert(21) with length: 2

gnutls.c: [7] WRITE: enqueued 7 bytes for 0xb. Total 7 bytes.

gnutls.c: [7] WRITE FLUSH: 7 bytes in buffer.

gnutls.c: [7] WRITE: wrote 7 bytes, 0 bytes left.

gnutls.c: [4] REC[0x11c53de00]: Sent Packet[2] Alert(21) with length: 7

gnutls.el: (err=[-9] A TLS packet with unexpected length was received.)
boot: (:priority NORMAL :hostname jabber.se :loglevel 10 :min-prime-bits
nil :trustfiles nil :crlfiles nil :keylist nil :verify-flags nil
:verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [2] (Emacs) Deallocating x509 credentials
gnutls.c: [6] BUF[HSK]: Cleared Data from buffer

gnutls.c: [4] REC[0x11c53de00]: Epoch #0 freed

gnutls.c: [4] REC[0x11c53de00]: Epoch #1 freed


----------------------------------------------------------------------

Comment By: Elias Pipping (pipping)
Date: 2012-05-19 07:44

Message:
After

commit 1dca591d17cf084e6d870f55898e9343926f8bb8
Author: Magnus Henoch <magnus.henoch< at >gmail.com>
Date:   Sat May 19 15:01:05 2012 +0100

    Fix reporting of STARTTLS negotiation errors [..]

My message buffer looks like this:

Sat May 19 16:40:07 2012: Starting jabber-connection
Sat May 19 16:40:07 2012: jabber-connection enters :connecting
Sat May 19 16:40:07 2012: Found enter function for :connecting: #[(fsm
state-data) "\306\307\"\310!\306\311\"\306\312\"\306\313\"


$\210-\314D\207" [state-data connection-type connect-function server
network-server port plist-get :connection-type jabber-get-connect-function
:server :network-server :port nil fsm] 5]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :connected to jabber-connection in state
:connecting
Sat May 19 16:40:07 2012: jabber-connection enters :connected
Sat May 19 16:40:07 2012: Found enter function for :connected: #[(fsm
state-data) "\303!\210\304
\305D\207" [fsm *jabber-connected* state-data jabber-send-stream-header t
nil] 2]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:07 2012: Sent :stream-start to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: jabber-connection enters :starttls
Sat May 19 16:40:08 2012: Found enter function for :starttls: #[(fsm
state-data) "\302!\210\303D\207" [fsm state-data jabber-starttls-initiate
nil] 2]
Sat May 19 16:40:08 2012: Using data from enter function
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: jabber-connection enters nil
Sat May 19 16:40:08 2012: Found enter function for nil: #[(fsm state-data)
"\306\307\"\310!\203\"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ emacs-jabber-Bugs-3527994 ] Problems with native gnutls

SourceForge.net — 2012-05-19T14:44:41

Bugs item #3527994, was opened at 2012-05-18 11:17
Message generated for change (Comment added) made by pipping
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Elias Pipping (pipping)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with native gnutls

Initial Comment:
Ever since

commit f54c1b54b308f38caac66ae567e5f64f6adc631c
Author: Magnus Henoch <legoscia< at >users.sourceforge.net>
Date:   Tue May 15 22:39:43 2012 +0100

    Support native GnuTLS for STARTTLS
    [..]

I've found myself unable to connect to lavabit.com using starttls. Here's what I found in my message buffer:

gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated.
gnutls.el: (err=[-110] The TLS connection was non-properly terminated.) boot: (:priority NORMAL :hostname lavabit.com :loglevel 0 :min-prime-bits nil :trustfiles (/etc/ssl/certs/ca-certificates.crt) :crlfiles nil :keylist nil :verify-flags nil :verify-error t :verify-hostname-error t :callbacks nil)
gnutls.c: [0] (Emacs) fatal error: The specified session has been invalidated for some reason. [100 times]
ME< at >lavabit.com/nil: connection lost: `connection broken by remote peer
'

(where i replaced my username with ME)

Here's the relevant part of my config:

(setq jabber-account-list '(("ME< at >lavabit.com"
     (:password . "PASSWORD")
     (:network-server . "lavabit.com")
     (:connection-type . starttls)
     (:port . 5222)))

----------------------------------------------------------------------

Date: 2012-05-19 07:44

Message:
After

commit 1dca591d17cf084e6d870f55898e9343926f8bb8
Author: Magnus Henoch <magnus.henoch< at >gmail.com>
Date:   Sat May 19 15:01:05 2012 +0100

    Fix reporting of STARTTLS negotiation errors [..]

My message buffer looks like this:

Sat May 19 16:40:07 2012: Starting jabber-connection
Sat May 19 16:40:07 2012: jabber-connection enters :connecting
Sat May 19 16:40:07 2012: Found enter function for :connecting: #[(fsm
state-data) "\306\307\"\310!\306\311\"\306\312\"\306\313\"


$\210-\314D\207" [state-data connection-type connect-function server
network-server port plist-get :connection-type jabber-get-connect-function
:server :network-server :port nil fsm] 5]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :connected to jabber-connection in state
:connecting
Sat May 19 16:40:07 2012: jabber-connection enters :connected
Sat May 19 16:40:07 2012: Found enter function for :connected: #[(fsm
state-data) "\303!\210\304
\305D\207" [fsm *jabber-connected* state-data jabber-send-stream-header t
nil] 2]
Sat May 19 16:40:07 2012: Using data from enter function
Sat May 19 16:40:07 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:07 2012: Sent :stream-start to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:connected
Sat May 19 16:40:08 2012: jabber-connection enters :starttls
Sat May 19 16:40:08 2012: Found enter function for :starttls: #[(fsm
state-data) "\302!\210\303D\207" [fsm state-data jabber-starttls-initiate
nil] 2]
Sat May 19 16:40:08 2012: Using data from enter function
Sat May 19 16:40:08 2012: Sent :filter to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: Sent :stanza to jabber-connection in state
:starttls
Sat May 19 16:40:08 2012: jabber-connection enters nil
Sat May 19 16:40:08 2012: Found enter function for nil: #[(fsm state-data)
"\306\307\"\310!\203\"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3527994&group_id=88346

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/