Just bumping this patch. If someone is able to provide feedback, that
would be much appreciated. Thanks!
On 11/23/20 2:23 PM, Thomas Neuman wrote:
From 417ed338179d9856334e9b738abd71952581785a Mon Sep 17 00:00:00 2001
From: Thomas Neuman
Date: Mon, 23 Nov 2020 21:02:08 +
Subject: [PATCH
From 417ed338179d9856334e9b738abd71952581785a Mon Sep 17 00:00:00 2001
From: Thomas Neuman
Date: Mon, 23 Nov 2020 21:02:08 +
Subject: [PATCH branch-2.11] stream-ssl: Make 'stream_ssl_set_key_and_cert'
atomic
When attempting to set the SSL key and cert via this function,
firs
From ba3b444d8c182ab7ff2e007c8960e30706089faa Mon Sep 17 00:00:00 2001
From: Thomas Neuman
Date: Tue, 27 Oct 2020 17:39:27 +
Subject: [PATCH branch-2.11] python: Add 'six' to list of install requirements
Fixes: 73eb682edb
Signed-off-by: Thomas Neuman
---
python/setup.py | 2
Yup, fair enough. LGTM
Acked-by: Thomas Neuman
I get why it seems a little weird, but the reason I chose @staticmethod is
because @classmethod would imply that we are going to actually reference
the class that is passed in the first argument, and we won't. The only
thing this method de
From 1bcd0b930a04df78fe5ca81ef6a17e11a1b867a1 Mon Sep 17 00:00:00 2001
From: Thomas Neuman
Date: Tue, 13 Oct 2020 16:09:54 -0700
Subject: [PATCH] python: Use Unbound to resolve DNS names of OVSDB remotes
If the Unbound library is present, allows for resolving remote OVSDB
instances in the
>From 66126413b47872b06a2acfc5d00219db2704c7c4 Mon Sep 17 00:00:00 2001
From: thomas-neuman
Date: Tue, 13 Oct 2020 16:09:54 -0700
Subject: [PATCH] [python] Use Unbound to resolve DNS names of OVSDB remotes
If the Unbound library is present, allows for resolving remote OVSDB
instances in
With other socket types, trying to connect and failing will return
an error code, but if an SSL Stream is used, then when
check_connection_completion(sock) is called, SSL will raise an
exception that doesn't derive from socket.error which is handled.
This adds handling for SSL.SysCallError which
go uncaught when they arise; instead of returning an errno
to the caller, the exception bubbles back up. Therefore this patch amends
this issue by checking for an OpenSSL.SSL.Error in addition to the
standard socket.error, when running with OpenSSL support.
Signed-off-by: thomas-neuman
---
python
go uncaught when they arise; instead of returning an errno
to the caller, the exception bubbles back up. Therefore this patch amends
this issue by checking for an OpenSSL.SSL.Error in addition to the
standard socket.error, when running with OpenSSL support.
Signed-off-by: Thomas Neuman
---
python
