I am having problem getting Sigul 1.1.1 working with Koji.

Koji: (version 1.21.1-1 on EL7).
Sigul bridge (version 1.1.1 on Fedora 33) with Koji 1.24.0 client.
Sigul server: (version 1.1.1 on Fedora 33) .

sigul sign-rpm --koji-only --store-in-koji --v3-signature my-signing-key binutils-2.30-79.el8.armv5tel.rpm Key passphrase: ERROR: I/O error: EOFError()

sigul bridge log shows:
2021-03-09 21:08:39,729 INFO: Client with CN 'siguladmin' connected 2021-03-09 21:08:39,730 INFO: Request: 'import-signature' = b'\x01', 'key' = b'my-signing-key', 'op' = b'sign-rpm', 'return-data' = b'\x00', 'rpm-arch' = b'armv5tel', 'rpm-epoch' = b'', 'rpm-name' = b'binutils', 'rpm-release' = b'79.el8', 'rpm-sigmd5' = b'\xb3+\x16H\xf2T|\x04\x8b\x04q\x9d\xb0Q\x83\xda', 'rpm-version' = b'2.30', 'user' = b'siguladmin', 'v3-signature' = b'\x01' 2021-03-09 21:08:42,193 WARNING: Error working with request data: Missing signature

sigul server log shows:
2021-03-09 21:08:40,940 INFO: Connection from CN=siguladmin 2021-03-09 21:08:41,248 ERROR: Starting signing operation 2021-03-09 21:08:41,494 INFO: Signed RPM ('binutils', None, '2.30', '79.el8', 'armv5tel', b'b720ff956b3bb4a894751ff55a8ffa17fd4ef13ece5d8659b8267d51fd048953033ceb70baeb78a733c9c5b5122203b9a0189984c1259c5be0193746af3b3ad4') with key my-signing-key

And rpm never get signed.

If I install a good old EL6.10 and use the sigul 0.100.0 rpm from
http://people.redhat.com/mitr/rpmsigner/rhel6/sigul-0.100-0.1.el6.noarch.rpm and last koji version (1.21.0-2) it works like a charm.

bridge log from working set up (note im signing another rpm but should not matter):
2021-03-09 19:05:11,757 INFO: Client with CN 'siguladmin' connected 2021-03-09 19:05:11,757 INFO: Request: 'import-signature' = '\x00\x00\x00\x01', 'key' = 'my-signing-key', 'op' = 'sign-rpms', 'return-data' = '\x00\x00\x00\x00', 'user' = 'siguladmin', 'v3-signature' = '\x00\x00\x00\x01' 2021-03-09 19:05:11,941 INFO: Subrequest: 'id' = '\x00\x00\x00\x00', 'rpm-arch' = 'src', 'rpm-epoch' = '', 'rpm-name' = 'redsleeve-release', 'rpm-release' = '1.el8', 'rpm-sigmd5' = 'H\xcbha\tv\xd1/Ta\xf0\x93\x97\xc0\x8e\xfe', 'rpm-version' = '8.3'

server log from working setup:
2021-03-09 19:05:11,795 INFO: Request: 'import-signature' = '\x00\x00\x00\x01', 'key' = 'redsleeve-el83-signing-key', 'op' = 'sign-rpms', 'return-data' = '\x00\x00\x00\x00', 'user' = 'siguladmin', 'v3-signature' = '\x00\x00\x00\x01' 2021-03-09 19:05:11,803 INFO: Connection from CN=siguladmin 2021-03-09 19:05:12,021 INFO: Subrequest: 'id' = '\x00\x00\x00\x00', 'rpm-arch' = 'src', 'rpm-epoch' = '', 'rpm-name' = 'redsleeve-release', 'rpm-release' = '1.el8', 'rpm-sigmd5' = 'H\xcbha\tv\xd1/Ta\xf0\x93\x97\xc0\x8e\xfe', 'rpm-version' = '8.3' 2021-03-09 19:05:13,113 INFO: Signed RPM ('redsleeve-release', None, '8.3', '1.el8', 'armv5tel', 'a964dcf34f12377f58b948ea709b9dd9b067db7b739a71b5e0bc35cf2c9fe7c479d06dfebb82e30344f1c5d8787d9a76fc1cbcce03d486faee0f13f576366af1') with key my-signing-key

Sigul bridge.conf/client.conf/server.conf are identical on the Fedora 33 and EL6 systems, but I rather prefer NOT to have an old unsecure EL6 system running.

Am I missing something or is something broken ?

I noticed if I just run
sigul sign-rpm --v3-signature my-signing-key binutils-2.30-79.el8.armv5tel.rpm -o signed.rpm on the F33 system, the signed.rpm does not get signed. So I suspect something might be wrong between the bridge and the server (2 seperate F33 servers).

BR,
Bjarne