Steven Collison
Steven Collison
Openssl maintains an error queue per thread. An application using s2n may also want to use libcrypto directly for other reasons. It is best if s2n leaves the Openssl error...
+1 on a more flexible I/O paradigm. This issue is more about adding a mechanism to s2n that gives hints about *when* s2n should start creating tls records from input...
You're right. Solution definitely need a flush()-like api so the application can tell s2n to encode/encrypt/etc the accumulated pending data.