Skip to content

Comments

pcsclient: improvements to keyring handling#494

Open
berrange wants to merge 2 commits intointel:mainfrom
berrange:pcsclient-keyring
Open

pcsclient: improvements to keyring handling#494
berrange wants to merge 2 commits intointel:mainfrom
berrange:pcsclient-keyring

Conversation

@berrange
Copy link
Contributor

@berrange berrange commented Feb 5, 2026

Not all distros (in my case RHEL-9/10) have the python3-keyring module available.

Use of the keyring is not a critical feature of pccsadmin, just a "nice to have". The user already has the option to decline to store a password in the keyring, so it is conceptually reasonable to support running without the keyring module present at all.

Furthermore, when seeing an authentication failure, a failure to clear the keyring should be treated as non-fatal since the user may have declined to store in the keyring to begin with.

The equivalent patches were previously submitted as #480 and as #476 for pccsadmin. This new PR for pcsclient combines the two, since they were complementary parts of the same problem.

The changes are still applicable to the new separated pccsadmin tool, so have also been submitted to intel/confidential-computing.tee.dcap.pccs#39

This is not available in some distros, and since it is merely a
convenience to avoid repeated password entry, it can be made
optional.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
On authentication errors with PCS, an attempt is made to clear the
keyring. This may fail if the user's login environment has no keyring
configured. The user would have declined to store the key when first
prompted, so there would be nothing to clear either in this case.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant