Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support KWallet #204

Open
oldkentuckymark opened this issue Oct 5, 2024 · 5 comments
Open

Support KWallet #204

oldkentuckymark opened this issue Oct 5, 2024 · 5 comments

Comments

@oldkentuckymark
Copy link

ksshaskpass is not included with the environment, making git non functional.

qtc

@marbub marbub changed the title missing ksshaskpass Support KWallet Oct 6, 2024
@marbub
Copy link
Collaborator

marbub commented Oct 6, 2024

AFAIK Qt Creator has already kwallet support with a DBUS interface. I am not using a password manager for ssh but the public key system. So I never run into that problem.

Can you add the DBUS interface "org.kde.KWallet" with FlatSeal? If that works I will add that to the flatpak build file.

@marbub
Copy link
Collaborator

marbub commented Oct 6, 2024

If you want ksshaskpass added to the kde runtime you have to file a bug report there. Everything under /usr is from the runtime.

@marbub
Copy link
Collaborator

marbub commented Oct 6, 2024

To my understanding, KWallet supports org. freedesktop.portal.Secret. And Qt Creator is compiled with libsecrets(I never tested that).

@oldkentuckymark
Copy link
Author

AFAIK Qt Creator has already kwallet support with a DBUS interface. I am not using a password manager for ssh but the public key system. So I never run into that problem.

Can you add the DBUS interface "org.kde.KWallet" with FlatSeal? If that works I will add that to the flatpak build file.

I gave "org.kde.KWallet" talk permissions on both the session bus and system bus policy sections, no change.

@oldkentuckymark
Copy link
Author

If you want ksshaskpass added to the kde runtime you have to file a bug report there. Everything under /usr is from the runtime.

I'm an end user, I don't (and should not have to) know or care what a runtime is, or what comes in it, I know this application is supposed to be able to use git and it can not. If the password asking doohickey doesn't come with a runtime, then the app should ship it (doesn't matter to me weather it's in /usr or /app). Otherwise this flatpak is broken.

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

No branches or pull requests

2 participants