[Bug 870456] New: problem with emacs and gnutls
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c0 Summary: problem with emacs and gnutls Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: pmlists@free.fr QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 Hi, This command fails in emacs: (url-retrieve-synchronously "https://btc-e.com/api/2/btc_eur/ticker") Error message: Contacting host: btc-e.com:443 gnutls.c: [0] (Emacs) fatal error: An unexpected TLS handshake packet was received. gnutls.el: (err=[-19] An unexpected TLS handshake packet was received.) boot: (:priority NORMAL :hostname btc-e.com :loglevel 0 :min-prime-bits 256 :trustfiles (/etc/ssl/ca-bundle.pem) :crlfiles nil :keylist nil :verify-flags nil :verify-error nil :callbacks nil) Entering debugger... Workaround: Install gnutls-3.0.28-1.1.1.x86_64.rpm and libgnutls28-3.0.28-1.1.1.x86_64.rpm from openSUSE-12.3. Peter Reproducible: Always Steps to Reproduce: 1. emacs -Q 2. M-: (url-retrieve-synchronously "https://btc-e.com/api/2/btc_eur/ticker") 3. Error... Actual Results: The command fails. Expected Results: The command should return a buffer with the content of the web-page. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c1 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |meissner@suse.com InfoProvider| |pmlists@free.fr --- Comment #1 from Marcus Meissner <meissner@suse.com> 2014-03-26 20:06:01 UTC --- did you install all online updates for 13.1 before trying? i tried the above code and it seems to work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c2 Peter Münster <pmlists@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|pmlists@free.fr | --- Comment #2 from Peter Münster <pmlists@free.fr> 2014-03-26 21:31:03 UTC --- Hi, Yes: "zypper -n up -l" Sometimes it works. Please try again later. Perhaps it's a timing issue, that depends on network traffic? My connection is ADSL with 2Mbits/s. I've 4 systems with openSUSE-13.1 (upgraded from 12.3) and they have all the same problem. Fast test: emacs --batch -Q --eval '(url-retrieve-synchronously "https://btc-e.com/api/2/btc_eur/ticker")' I hope, that somebody can reproduce it. Peter -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c3 --- Comment #3 from Marcus Meissner <meissner@suse.com> 2014-03-26 21:39:46 UTC --- $ emacs --batch -Q --eval '(url-retrieve-synchronously "https://btc-e.com/api/2/btc_eur/ticker")' Contacting host: btc-e.com:443 gnutls.c: [1] Note that the security level of the Diffie-Hellman key exchange has been lowered to 256 bits and this may allow decryption of the session data $ its not getting things back. Does this also happen with plain $ gnutls-cli btc-e.com .. for me long good output, but no abort ... gnutls-3.2.4-2.14.1.x86_64 libgnutls28-3.0.28-1.4.1.x86_64 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c4 --- Comment #4 from Marcus Meissner <meissner@suse.com> 2014-03-26 21:40:52 UTC --- note that the emacs -Q does not return the content for me... but I am no emacs user/expert ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c5 --- Comment #5 from Peter Münster <pmlists@free.fr> 2014-03-26 22:07:43 UTC --- (In reply to comment #3)
its not getting things back.
When there is the gnutls-error, emacs returns with exit-code other than 0. And the output is: Contacting host: btc-e.com:443 gnutls.c: [0] (Emacs) fatal error: An unexpected TLS handshake packet was received. gnutls.el: (err=[-19] An unexpected TLS handshake packet was received.) boot: (:priority NORMAL :hostname btc-e.com :loglevel 0 :min-prime-bits 256 :trustfiles (/etc/ssl/ca-bundle.pem) :crlfiles nil :keylist nil :verify-flags nil :verify-error nil :callbacks nil) GnuTLS error: #<process btc-e.com>, -19
Does this also happen with plain
$ gnutls-cli btc-e.com ... for me long good output, but no abort ...
Output of gnutls-cli seems good.
gnutls-3.2.4-2.14.1.x86_64 libgnutls28-3.0.28-1.4.1.x86_64
You have libgnutls28-3.0.28-1.4.1.x86_64 installed??? This is not a 13.1-package. And then it's normal, that you don't have any problem (see above my workaround). Please try with libgnutls28-3.2.4-2.14.1.x86_64.rpm Peter -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c Xiyuan Liu <xyliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@suse.com AssignedTo|bnc-team-screening@forge.pr |shchang@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c7 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |pmlists@free.fr --- Comment #7 from Marcus Meissner <meissner@suse.com> 2014-06-14 12:58:12 UTC --- needinfo is on reporter. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c8 --- Comment #8 from Peter Münster <pmlists@free.fr> 2014-06-14 14:06:27 UTC --- (In reply to comment #7)
needinfo is on reporter.
Hi, What info do you need? Here a summary of the problem: Test command: emacs --batch -Q --eval '(url-retrieve-synchronously "https://btc-e.com/api/2/btc_eur/ticker")' Output with installed libgnutls28-3.0.28-1.1.1.x86_64: Contacting host: btc-e.com:443 gnutls.c: [1] Note that the security level of the Diffie-Hellman key exchange has been lowered to 256 bits and this may allow decryption of the session data Output with installed libgnutls28-3.2.4-2.24.1.x86_64: Contacting host: btc-e.com:443 gnutls.c: [1] Note that the security level of the Diffie-Hellman key exchange has been lowered to 256 bits and this may allow decryption of the session data gnutls.c: [0] (Emacs) fatal error: An unexpected TLS handshake packet was received. gnutls.el: (err=[-19] An unexpected TLS handshake packet was received.) boot: (:priority NORMAL :hostname btc-e.com :loglevel 0 :min-prime-bits 256 :trustfiles (/etc/ssl/ca-bundle.pem) :crlfiles nil :keylist nil :verify-flags nil :verify-error nil :verify-hostname-error nil :callbacks nil) GnuTLS error: #<process btc-e.com>, -19 Peter -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c9 --- Comment #9 from Marcus Meissner <meissner@suse.com> 2014-06-16 12:16:03 UTC --- 3.0.28-1.4.1 is current openSUSE 12.3 gnutls (with updates) 3.2.4-2.24.1 is current openSUSE 13.1 gnutls (with updates) I tested it on both with your testcase, it prints: $ emacs --batch -Q --eval '(url-retrieve-synchronously "https://btc-e.com/api/2/btc_eur/ticker")' Contacting host: btc-e.com:443 gnutls.c: [1] Note that the security level of the Diffie-Hellman key exchange has been lowered to 256 bits and this may allow decryption of the session data $ So I am not seeing the unexpected handshake problem. Is there a transparent proxy perhaps? Can you try: $ gnutls-cli btc-e.com and if it reproduces the alert problem can you try: $ gnutls-cli -d 255 btc-e.com and attach the debug outpzut? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c10 --- Comment #10 from Marcus Meissner <meissner@suse.com> 2014-06-16 12:20:57 UTC --- its really weird that this is timing related. I called it repeatedly, but it does not seem to trigger above for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c11 Peter Münster <pmlists@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|pmlists@free.fr | --- Comment #11 from Peter Münster <pmlists@free.fr> 2014-06-16 14:00:14 UTC --- (In reply to comment #9)
Can you try:
$ gnutls-cli btc-e.com
Hi, There is no problem: Processed 153 CA certificate(s). Resolving 'btc-e.com'... Connecting to '141.101.121.194:443'... - Certificate type: X.509 - Got a certificate list of 2 certificates. - Certificate[0] info: - subject `OU=Domain Control Validated,CN=*.btc-e.com', issuer `C=US,ST=Arizona,L=Scottsdale,O=GoDaddy.com\, Inc.,OU=http://certs.godaddy.com/repository/,CN=Go Daddy Secure Certificate Authority - G2', RSA key 2048 bits, signed using RSA-SHA256, activated `2014-03-19 13:36:01 UTC', expires `2016-03-19 13:36:01 UTC', SHA-1 fingerprint `823c6c432ce1db127f43cf2891620570bfd2985e' Public Key Id: e66d3115b21aa22025b78955f82efb29533e515e Public key's random art: +--[ RSA 2048]----+ |. +o. . . | | *.o o . | |o +. . . . . | | . .....Eo . | | ..o .S o | | . + .o . o | | = . . o | | + o. . | | +o. | +-----------------+ - Certificate[1] info: - subject `C=US,ST=Arizona,L=Scottsdale,O=GoDaddy.com\, Inc.,OU=http://certs.godaddy.com/repository/,CN=Go Daddy Secure Certificate Authority - G2', issuer `C=US,ST=Arizona,L=Scottsdale,O=GoDaddy.com\, Inc.,CN=Go Daddy Root Certificate Authority - G2', RSA key 2048 bits, signed using RSA-SHA256, activated `2011-05-03 07:00:00 UTC', expires `2031-05-03 07:00:00 UTC', SHA-1 fingerprint `27ac9369faf25207bb2627cefaccbe4ef9c319b8' - Status: The certificate is trusted. - Description: (TLS1.2-PKIX)-(ECDHE-RSA-SECP256R1)-(AES-128-GCM)-(AEAD) - Session ID: 56:2A:58:51:F6:F0:6B:4B:7D:F9:D5:7F:23:C9:94:8E:8F:BA:2E:D3:7E:EA:58:F4:54:86:D6:E1:EB:9E:A8:1C - Ephemeral EC Diffie-Hellman parameters - Using curve: SECP256R1 - Curve size: 256 bits - Version: TLS1.2 - Key Exchange: ECDHE-RSA - Server Signature: RSA-SHA512 - Cipher: AES-128-GCM - MAC: AEAD - Compression: NULL - Handshake was completed - Simple Client Mode: - Peer has closed the GnuTLS connection It's perhaps a bit emacs-related...? Peter -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c12 --- Comment #12 from Marcus Meissner <meissner@suse.com> 2014-06-17 14:46:32 UTC --- I also saw it now via emacs. It happens however seldom, similar to your experience. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c13 --- Comment #13 from Peter Münster <pmlists@free.fr> 2014-06-17 15:04:36 UTC --- (In reply to comment #12)
I also saw it now via emacs. It happens however seldom, similar to your experience.
On my system it works seldom, I get the error almost always (about 99%). Peter -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c14 --- Comment #14 from Marcus Meissner <meissner@suse.com> 2014-06-30 14:07:19 UTC --- i looked a bit at the emacs code, nothing bad stands out. :/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=870456 https://bugzilla.novell.com/show_bug.cgi?id=870456#c15 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|lnussel@suse.com |meissner@suse.com --- Comment #15 from Ludwig Nussel <lnussel@suse.com> 2014-07-07 14:24:35 CEST --- I don't know why this is assigned to me -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com