Reminder End of Survey: Relevance of Configuration Systems in Free and Open Source Software

2016-07-11 Thread Gabriel Rauter
I would like to gently remind anyone interested that the survey will be closed on 18.07.2016. As stated in the previous mailing we are interested in the experience and opinion of people involved in both FLOSS and configuration systems. This includes developers who use or have used configuration rel

Re: The situation of KWallet, and what to do about it?

2016-07-11 Thread Thomas Pfeiffer
On 07.07.2016 18:43, Elvis Angelaccio wrote: - We make encrypted password storage optional and non-default (easiest solution, but not exactly in line with KDE's vision) I disagree on this point. Even if KWallet were free of usability issues, it would still provide a false sense of security. The

Re: The situation of KWallet, and what to do about it?

2016-07-11 Thread Reindl Harald
Am 11.07.2016 um 21:27 schrieb Thomas Pfeiffer: On 07.07.2016 18:43, Elvis Angelaccio wrote: - We make encrypted password storage optional and non-default (easiest solution, but not exactly in line with KDE's vision) I disagree on this point. Even if KWallet were free of usability issues, it

Re: The situation of KWallet, and what to do about it?

2016-07-11 Thread Thomas Pfeiffer
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 sh

Re: The situation of KWallet, and what to do about it?

2016-07-11 Thread Kevin Ottens
Hello, On Monday, 11 July 2016 21:58:34 CEST Thomas Pfeiffer 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 KSecretSer

Re: The situation of KWallet, and what to do about it?

2016-07-11 Thread Mark Gaiser
On Mon, Jul 11, 2016 at 9:58 PM, Thomas Pfeiffer 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 >> KW

Re: The situation of KWallet, and what to do about it?

2016-07-11 Thread Sune Vuorela
On 2016-07-07, Kevin Ottens wrote: > There's two sides to that problem in fact, use from applications and the=20 > service provided by our workspace. One issue that I'm a bit puzzled about is the following scenario: A user uses KMail for emails. But switches between various desktop environments.

Re: The situation of KWallet, and what to do about it?

2016-07-11 Thread Kevin Ottens
Hello, On Monday, 11 July 2016 20:51:43 CEST Sune Vuorela wrote: > On 2016-07-07, Kevin Ottens wrote: > > There's two sides to that problem in fact, use from applications and > > the=20 > > service provided by our workspace. > > One issue that I'm a bit puzzled about is the following scenario: >

Re: The situation of KWallet, and what to do about it?

2016-07-11 Thread Michael Pyne
On Mon, July 11, 2016 21:27:54 Thomas Pfeiffer wrote: > On 07.07.2016 18:43, Elvis Angelaccio wrote: > >> - We make encrypted password storage optional and non-default (easiest > >> solution, but not exactly in line with KDE's vision) > > > > I disagree on this point. Even if KWallet were free of