Thank you Matt,
I understand that _u8,_u16. _u24 are the variants that helps us set the size of
length field, that precedes the data.
-Saiteja.
-Original Message-
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Matt Caswell
Sent: Friday, December 22, 2017 4
On 25/12/17 10:44 PM, Swapnil Deshpande wrote:
Hi all,
Noob here. I recently discovered that the "-sha1" and "-sha" flags in
the "openssl dgst" command produce different outputs. I thought those
were the same algorithms but turns out they are not:
$ echo -n "password" | openssl dgst -sha
80
Hi all,
Noob here. I recently discovered that the "-sha1" and "-sha" flags in the
"openssl dgst" command produce different outputs. I thought those were the
same algorithms but turns out they are not:
$ echo -n "password" | openssl dgst -sha
80072568beb3b2102325eb203f6d0ff92f5cef8e
$ echo -n "
I found the real issue... recently I fixed a signed/unsigned comparison
warning by adding a (int) to the unsigned side, which made the result of
send() be compared differently, and was triggering when send() would return
-1 (with EAGAIN/WSAEWOULDBLOCK) would cause me to think it was a short send
(
On 23/12/2017 04:06, J Decker wrote:
How can I know what/why openssl is sending control data?
I have this Node addon that uses TLS 1.2 to communicate. I'm sending
a large file transfer (100M), which is chunked into 8100 byte blocks
and sent on websocket protocol. It's additionally chunked int
