[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: The situation of KWallet, and what to do about it?
From: Mark Gaiser <markg85 () gmail ! com>
Date: 2016-07-11 20:29:12
Message-ID: CAPd6JnEVfuEtERa5Z5A4O_dv1DKDArAckHZLqTHdhdeS29KmEA () mail ! gmail ! com
[Download RAW message or body]
On Mon, Jul 11, 2016 at 9:58 PM, Thomas Pfeiffer <thomas.pfeiffer@kde.org>
wrote:
> On 07.07.2016 19:50, Kevin Ottens wrote:
>
>> There's two sides to that problem in fact, use from applications and the
>> service provided by our workspace.
>>
>> I think that for applications the answer is neither KSecretService nor
>> KWallet, etc. For the goal of making it easier for our applications to be
>> shipped on more platforms, what we want in fact is to port them away from
>> anything platform specific to something like QtKeyChain:
>> https://inqlude.org/libraries/qtkeychain.html
>>
>
> This way, the actual storage becomes a workspace decision. That could keep
>> being KWallet if improved, or KSecretService, or a simple D-Bus service
>> wrapping libsecret... For sure it would at least simplify things on the
>> KWallet/KSecretService side, they wouldn't need to be frameworks anymore
>> (QtKeyChain or equivalent would play that role) just to expose a D-Bus API
>> (likely the Secret Service one in the end).
>>
>
> Oh, indeed, that would absolutely make sense! Deploying and using
> applications which use KWallet outside of Plasma must be a pain right now.
>
> So how do we make that happen? Deprecate the KWallet framework and
> recommend to use QtKeyChain instead, and then in parallel decide which
> bakcend to use for QtKeyChain in Plasma?
I don't get that. How is deprecating KWallet paves the way to make
something new with QtKeyChain? As far as i can tell, QtKeyChain isn't a
keychain at all, it's a wrapper around platform specific keychains that
provides a unified interface for keychain functionality. It itself doesn't
implement a keychain (or it does on windows?).
Or do you mean deprecating/removing the *graphical* KWallet part and
re-implementing that in top of QtKeyChain?
Using QtKeyChain would be interesting imho. Specially if that itself is
extended to use other web backends as keychain.
>
>
>
>>> https://www.freedesktop.org/wiki/Specifications/secret-storage-spec/secrets->
>>> api-0.1.html
>>>
>>
>> 0.1 being outdated, you probably want to link that one:
>> https://standards.freedesktop.org/secret-service/
>>
>
> Ah yes, indeed.
>
> Hope that somewhat made sense and helps.
>>
>
> It made sense to me at least :)
>
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
[Attachment #3 (text/html)]
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Jul 11, 2016 \
at 9:58 PM, Thomas Pfeiffer <span dir="ltr"><<a \
href="mailto:thomas.pfeiffer@kde.org" \
target="_blank">thomas.pfeiffer@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On 07.07.2016 19:50, Kevin Ottens wrote:<br> \
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> There's two sides to that problem in fact, use from \
applications and the<br> service provided by our workspace.<br>
<br>
I think that for applications the answer is neither KSecretService nor<br>
KWallet, etc. For the goal of making it easier for our applications to be<br>
shipped on more platforms, what we want in fact is to port them away from<br>
anything platform specific to something like QtKeyChain:<br>
<a href="https://inqlude.org/libraries/qtkeychain.html" rel="noreferrer" \
target="_blank">https://inqlude.org/libraries/qtkeychain.html</a><br> </blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> This way, the actual storage becomes a workspace decision. \
That could keep<br> being KWallet if improved, or KSecretService, or a simple D-Bus \
service<br> wrapping libsecret... For sure it would at least simplify things on \
the<br> KWallet/KSecretService side, they wouldn't need to be frameworks \
anymore<br> (QtKeyChain or equivalent would play that role) just to expose a D-Bus \
API<br> (likely the Secret Service one in the end).<br>
</blockquote>
<br></span>
Oh, indeed, that would absolutely make sense! Deploying and using applications which \
use KWallet outside of Plasma must be a pain right now.<br> <br>
So how do we make that happen? Deprecate the KWallet framework and recommend to use \
QtKeyChain instead, and then in parallel decide which bakcend to use for QtKeyChain \
in Plasma?</blockquote><div><br></div><div>I don't get that. How is deprecating \
KWallet paves the way to make something new with QtKeyChain? As far as i can tell, \
QtKeyChain isn't a keychain at all, it's a wrapper around platform specific \
keychains that provides a unified interface for keychain functionality. It itself \
doesn't implement a keychain (or it does on \
windows?).</div><div><br></div><div>Or do you mean deprecating/removing the \
*graphical* KWallet part and re-implementing that in top of \
QtKeyChain?</div><div><br></div><div>Using QtKeyChain would be interesting imho. \
Specially if that itself is extended to use other web backends as keychain. \
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class=""><br> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <a \
href="https://www.freedesktop.org/wiki/Specifications/secret-storage-spec/secrets-" \
rel="noreferrer" target="_blank">https://www.freedesktop.org/wiki/Specifications/secret-storage-spec/secrets-</a>> \
api-0.1.html<br> </blockquote>
<br>
0.1 being outdated, you probably want to link that one:<br>
<a href="https://standards.freedesktop.org/secret-service/" rel="noreferrer" \
target="_blank">https://standards.freedesktop.org/secret-service/</a><br> \
</blockquote> <br></span>
Ah yes, indeed.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> Hope that somewhat made sense and helps.<br>
</blockquote>
<br></span>
It made sense to me at least :)<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org" target="_blank">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" rel="noreferrer" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
</div></div></blockquote></div><br></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic