tmp_server prints now and then “read() error. Error is 0 Success”.
• If this is success, then the word “error” shall not be emited (twice)
• If this is an error, then the word “success” shall not be emitted.
Attach is the captured traffic with the tpm_server, created with “tcpdump -i lo -v -s 0 "(port 2321) or (port 2322)" -w ttt”. To unfold, use “tcpdump -Xr ttt”.
Thank you for the report. I believe that I found the error and fixed it. A few questions:
The fix is that, in ReadBytes(), the first test should be (res < 0), not (res <= 0). Both cases are errors, but res == 0 does not set errno.
I use Linux.
Attach is the captured traffic with the tpm_server, created with “tcpdump -i lo -v -s 0 "(port 2321) or (port 2322)" -w ttt”. To unfold, use “tcpdump -Xr ttt”.
Ciao. We have reported exactly the same issue on Windows. Still not fixed! Cheers.
That was also reported and is fixed for the next release. The Windows socket API does not use strerror and errno.