Split-gpg2: NotImplementedError

User Support
,
1

I’m setting up split-gpg2 and seemingly have it working in that a client VM can run gpg --list-secret-keys and it will return my key.

Great! However, in my server VM I see this pop out of journalctl -f each time I run gpg --list-secret-keys in a client:

servervm qubes.Gpg2+-clientvm[1120]: Traceback (most recent call last):
servervm qubes.Gpg2+-clientvm[1120]:   File "<frozen runpy>", line 198, in _run_module_as_main
servervm qubes.Gpg2+-clientvm[1120]:   File "<frozen runpy>", line 88, in _run_code
servervm qubes.Gpg2+-clientvm[1120]:   File "/usr/lib/python3/dist-packages/splitgpg2/__main__.py", line 3, in <module>
servervm qubes.Gpg2+-clientvm[1120]:     main()
servervm qubes.Gpg2+-clientvm[1120]:   File "/usr/lib/python3/dist-packages/splitgpg2/__init__.py", line 1457, in main
servervm qubes.Gpg2+-clientvm[1120]:     loop.run_until_complete(server.run())
servervm qubes.Gpg2+-clientvm[1120]:   File "/usr/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
servervm qubes.Gpg2+-clientvm[1120]:     return future.result()
servervm qubes.Gpg2+-clientvm[1120]:            ^^^^^^^^^^^^^^^
servervm qubes.Gpg2+-clientvm[1120]:   File "/usr/lib/python3/dist-packages/splitgpg2/__init__.py", line 426, in run
servervm qubes.Gpg2+-clientvm[1120]:     await self.client_writer.wait_closed()
servervm qubes.Gpg2+-clientvm[1120]:   File "/usr/lib/python3.11/asyncio/streams.py", line 350, in wait_closed
servervm qubes.Gpg2+-clientvm[1120]:     await self._protocol._get_close_waiter(self)
servervm qubes.Gpg2+-clientvm[1120]:           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
servervm qubes.Gpg2+-clientvm[1120]:   File "/usr/lib/python3.11/asyncio/streams.py", line 178, in _get_close_waiter
servervm qubes.Gpg2+-clientvm[1120]:     raise NotImplementedError
servervm qubes.Gpg2+-clientvm[1120]: NotImplementedError

If you are using split-gpg2, do you see this in your server VM journal also?

2

For posterity: I opened an issue for this:

2 Likes
3

I tested it with qubes-gpg-client --list-secret-keys and it works fine for me. Also no scary log message… strange…

1 Like
4

Thanks, that is interesting. If you don’t mind sharing, what base template do you use for the vault?

5

nothing either, I’m using a fedora-39 for both the gpg client and the gpg vault

1 Like
6

Thanks. It’ll be a little while before I can look into this again but next I’ll try to reproduce the logging w/ a Fedora template.

7

my template is debian 12, also for both

1 Like