Connecting with git (GnuTLS) causes stack trace about pacemaker

[Lekensteyn]

GnuTLS is not affected by Heartbleed, so this test does not work. On Arch Linux, git is compiled against OpenSSL which could be tested.

If it is about the exceptions, well there are other ways to trigger them like echo | nc 127.1 4433. Perhaps it should be fixed.

[joliss]

Ah, that makes sense. Perhaps it's possible to detect this and clarify the error reporting? (I'll leave it up to you to close this issue.)

[Lekensteyn]

It is possible to add, why not? I'll leave it open until it is fixed. Thanks for the report btw.

[hurzl]

Same exception happens when called from midori

[Lekensteyn]

Should be fixed in latest code, please check.

[hurzl]

no, sorry

Listening on :4433 for tls clients
Connection from: 127.0.0.1:30810
----------------------------------------
Exception happened during processing of request from ('127.0.0.1', 30810)
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/SocketServer.py", line 295, in _handle_request_noblock
    self.process_request(request, client_address)
  File "/usr/local/lib/python2.7/SocketServer.py", line 321, in process_request
    self.finish_request(request, client_address)
  File "/usr/local/lib/python2.7/SocketServer.py", line 334, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/local/lib/python2.7/SocketServer.py", line 649, in __init__
    self.handle()
  File "pacemaker.py", line 99, in handle
    self.do_evil()
  File "pacemaker.py", line 146, in do_evil
    if not self.read_memory(self.request, self.args.timeout):
  File "pacemaker.py", line 161, in read_memory
    data = rl[0].recv(wanted_bytes)
error: [Errno 54] Connection reset by peer
----------------------------------------

[Lekensteyn]

Yay, consistency between Python 2 and 3. In Python 3, it is documented that errors should throw an OSError. I'll fix this for Python 2.

EDIT: just pushed a fix.

[hurzl]

Yes it worked with python3 and now with 2, too ;) thanks!

[Lekensteyn]

I guess that is a fixed report. For other readers, this error was reported by the NSS library because the connection got aborted after receiving a fatal alert (because of protocol violation).