In the gpg section of the client.ini configuration file it's possible to
specify the path to an alternative archive-master keyring. In my test I expect
to generate keys for archive-master (signed by itself), image-master (signed by
the archive-master') and image-signing (signed by image-master).
As long as the client doesn't try to use the archive-master keyring provided by
system-image-common package, I think it should work fine.
In the gpg section of the client.ini configuration file it's possible to
specify the path to an alternative archive-master keyring. In my test I expect
to generate keys for archive-master (signed by itself), image-master (signed by
the archive-master') and image-signing (signed by image-master).
As long as the client doesn't try to use the archive-master keyring provided by
system-image-common package, I think it should work fine.
Please let me know if I'm missing something.