On 1/11/19 12:42 PM, Sam Roberts wrote:
On Wed, Jan 9, 2019 at 6:54 PM Corey Minyard wrote:
My first inclination for a secure connection was to use ssh. However,
ssh is not as well suited for this as I would have liked, and all the
ssh libraries are tied to a file descriptor in ways that are no
On 1/11/19 12:14 PM, Jordan Brown wrote:
On 1/10/2019 10:55 AM, Corey Minyard wrote:
It is unusual, perhaps, but I'm trying to implement something like
ssh does. I can't expect users of ser2net to obtain certificates
from a real certificate authority, that's too high a barrier for
entry. I w
>SSL_shutdown(connection) || SSL_shutdown(connection);
I like it! (Not!)
I don't pretend to be a bits and bytes expert on TCP protocol. You can't be
an expert on everything.
So I will listen to expert advice. I know 99% of you all are 'nix guys and
this is a Windows problem. I am seeing
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Karl Denninger
> Sent: Friday, January 11, 2019 13:04
>if (!SSL_shutdown(connection)) {
>SSL_shutdown(connection)
>}
Or if you really want to baffle future maintainers:
SSL_shutdown(connectio
@Karl, thanks, I'm not sure of anything. This was my first OpenSSL project
and I just hacked on it until it "worked." It's been working for years but
now we are seeing a re-connection error.
So, it sounds like
. Do the SSL_shutdown() a second time if it returns 0.
. Lose th
On Wed, Jan 9, 2019 at 6:54 PM Corey Minyard wrote:
> My first inclination for a secure connection was to use ssh. However,
> ssh is not as well suited for this as I would have liked, and all the
> ssh libraries are tied to a file descriptor in ways that are not easily
> fixable, and thus can't be
On 1/10/2019 10:55 AM, Corey Minyard wrote:
> It is unusual, perhaps, but I'm trying to implement something like ssh
> does. I can't expect users of ser2net to obtain certificates from a
> real certificate authority, that's too high a barrier for entry. I
> want them to be able to generate a key
On 1/10/2019 17:07, Charles Mills wrote:
>
> On Windows, for a new session, I am issuing a Windows accept()
> followed by SSL_new(), SSL_set_fd() and so forth.
>
>
>
> When the session sees some sort of an abnormal receive condition, I am
> doing
>
>
>
> int *retCode* = SSL_get_shutdown
On 10/01/2019 18:09, Ananthu Unnikrishnan wrote:
> Hi Matt,
>
> Thanks a lot for the reply.
>
> After calling ASYNC_pause_job() from the engine, control will transfer
> to
> the place where we start the ASYNC_start_job right? So how can we write the
> code
> to put a trigger on