{"id":6809,"date":"2025-07-09T15:22:49","date_gmt":"2025-07-09T15:22:49","guid":{"rendered":"https:\/\/notmart.org\/blog\/?p=6809"},"modified":"2025-07-09T15:22:50","modified_gmt":"2025-07-09T15:22:50","slug":"kwallet-to-secretservice-a-client-application-name-wanted","status":"publish","type":"post","link":"https:\/\/notmart.org\/blog\/2025\/07\/kwallet-to-secretservice-a-client-application-name-wanted\/","title":{"rendered":"KWallet to SecretService, a client application: name wanted"},"content":{"rendered":"\n

As i wrote in the previous post<\/a>, now the KWallet service has been splitted in a compatibility layer that exposes the old KWallet api, but actually consumes the Secret Service API, provided by default by the old KWallet daemon converted in a secretservice-only provider.<\/p>\n\n\n\n

Another pain point is the application used to look inside the wallets, KWalletmanager, which only speaks the KWallet api and looks a bit dated nowdays:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

I am working on a new application which goal is strictly to be a client for Secret Service. It can access passwords of any Secret Service provider (being KWallet, Gnome-keyring, KeepassXC, oo7 or whatever else) and should hopefully look a bit more modern and simple, while still being powerful:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

For items imported from KWallet supports editing the values of type “Map” as well:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

As well as visualizing “binary” entries (here super censored for obvious reasons \ud83d\ude09<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

The application can be tested at https:\/\/invent.kde.org\/mart\/kwallets<\/a><\/p>\n\n\n\n

But has a fundamental problem, for which i need help… Right now is just called “KWallets” which can be kinda confusing with old KWallet and KWalletManager, so it probably needs a new name, any opinion is welcome \ud83d\ude04. <\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

As i wrote in the previous post, now the KWallet service has been splitted in a compatibility layer that exposes the old KWallet api, but actually consumes the Secret Service API, provided by default by the old KWallet daemon converted in a secretservice-only provider. Another pain point is the application used to look inside the […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[2,191,194,193,192],"class_list":["post-6809","post","type-post","status-publish","format-standard","hentry","category-software","tag-kde","tag-kwallet","tag-password","tag-secretservice","tag-security"],"_links":{"self":[{"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/posts\/6809","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/comments?post=6809"}],"version-history":[{"count":2,"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/posts\/6809\/revisions"}],"predecessor-version":[{"id":6818,"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/posts\/6809\/revisions\/6818"}],"wp:attachment":[{"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/media?parent=6809"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/categories?post=6809"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/tags?post=6809"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}