Open Euwiiwueir opened 2 months ago
Recent posts in the forum thread have me wondering if this is something specific to my configuration rather than a more general issue. I will take another look when I can and follow up here.
This is not specific to your configuration. It is a consequence of split-gpg2 erroneously instantiating asyncio.StreamWriter
by calling its constructor, which isn’t allowed, and using asyncio.FlowControlMixin
, which isn’t part of the public Python API.
There are two correct ways to fix this:
StreamReader
and StreamWriter
, possibly by including a copy of the classes in split-gpg2.open_unix_connection
or create_unix_server
.@marmarek which do you prefer?
How to file a helpful issue
Qubes OS release
4.2 Debian 12 templates
Brief summary
In attempting to set up
split-gpg2
I noticed this pattern logged injournalctl
:(The logging above comes from the server VM journal but it's also logged in the client VM under the
split-gpg2-client.service
unit.)Having stepped through the code, I think it's probably innocuous, as it occurs during cleanup. But it is alarming logging coming from security-related software so it should probably be fixed.
The cause seems to be:
asyncio.streams.FlowControlMixin
protocol instantiated here_get_close_waiter()
function which is "implemented" onasyncio.streams.FlowControlMixin
like so:At least, this is my best understanding. I posted about this on the forum but got no other reports, therefore I'm not super confident it shows up for other users.
Steps to reproduce
Install and set up
split-gpg2
on a server and client, attempt to sign something on the client, then check the logs.Expected behavior
No logging
Actual behavior
Scary logging