Ben G

There you go: ``` Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007ffb845a1b54 in SSL_write () from /lib/x86_64-linux-gnu/libssl.so.1.0.0 [Current thread is 1 (Thread 0x7ffb84dfe740 (LWP 18450))] (gdb) bt full #0...

Seems to be working quite well, except this. I'm using a snapshot from last week. Am 20.02.2018 08:10 schrieb dlmeetei : Looks like, SSL_write is failing due to corrupted structures...

It's not closed.. Problem still exists. Am 20.02.2018 11:56 schrieb dlmeetei : Thanks for confirming. Closing this then — You are receiving this because you authored the thread. Reply to...

Yes, will create another core dump later. Btw. here are the steps to reproduce: Open a connection to a TLS server, keep the connection open. Then shutdown the server and...

Sorry for late response.. ``` Program terminated with signal SIGSEGV, Segmentation fault. #0 SSL_write (s=0x0, buf=0x253bd52, num=236) at ssl_lib.c:1038 1038 ssl_lib.c: No such file or directory. [Current thread is 1...

Digged some more into it. It seems that `read_cb` cb is not triggered with -1 when the TLS connection is dropped. Stock `uv_read_start` does exactly this. Howto detect that the...

Is there any interest in relaunching this service? I could host it on one of my relays.

Monero would be a good choice Am 03.02.2018 15:40 schrieb theblazehen : @5moufl I've been considering launching an instance, but with a cryptocurrency with lower fees. — You are receiving...

Didn't thought about that, you're right it makes sense to not use an untraceable coin for this scenario. LTC isn't a bad choice. Am 05.02.2018 07:58 schrieb theblazehen : @Bendr0id...

Same on boost 1_57_0. Any fixes for this?