Greg Hazel
Greg Hazel
Pretty sure it’s not a problem in my code — I don’t use DNS over TCP explicitly.
That UI oddity is possibly something more intentional than a bug. It's confusing because of the way the UI appears. NewNode has an internal state of whether it is "enabled"...
I still find this library very useful, since it allows direct access to the keystore without being married to specific crypto primitives, and allows explicitly checking the difference between locked/unlocked/uninitialized.
I believe the correct fix would be to consider `ST_FIN` as connection completion (as well as `ST_DATA`): https://github.com/bittorrent/libutp/blob/master/utp_internal.cpp#L2160 ```c++ if ((pk_flags == ST_DATA || pk_flags == ST_FIN) && conn->state ==...
> I don't know what the state of it is. We've had a handful of PRs in limbo @ https://github.com/bittorrent/libutp/pulls for awhile now. > > Maybe @ghazel would know? I...
> Added fix to SSL framework, check if issue fixed pls Tried it, this did not seem to fix it.
I was able to get things compiling and running with clang (`Apple LLVM version 9.1.0 (clang-902.0.39.2)`) using `libomp` from brew (as described in https://github.com/elibensasson/libSTARK/issues/2#issuecomment-370237565). The patch from @kozyilmaz https://github.com/elibensasson/libSTARK/issues/2#issuecomment-370252608 was...
From the README: ``` The write side of the socket is proactive, and you call UTP_Write to indicate the number of bytes you wish to write. As packets are created,...
It's possible the socket is not writable at this time. What does UTP_Write return? To answer your previous question; you call UTP_IsIncomingUTP to process the received packet with libutp. This...