On Friday, April 04, 2014 10:08:36 PM Thomas Lübking wrote:
> On Freitag, 4. April 2014 02:42:32 CEST, Michael Pyne wrote:
> > Of course if an attacker is running code they'd probably just
> > find it easier
> > to open the .kwl directly and read the folder and key names,
> > since apparently
> > t
On Thursday, April 03, 2014 08:42:32 PM Michael Pyne wrote:
> On Fri, April 4, 2014 02:20:28 Valentin Rusu wrote:
> > On Sunday, March 30, 2014 05:25:58 PM Michael Pyne wrote:
> > > In fact the list of folders and keys present in KWallet (though
> > > not their values) can be queried without unlock
On Freitag, 4. April 2014 02:42:32 CEST, Michael Pyne wrote:
Of course if an attacker is running code they'd probably just
find it easier
to open the .kwl directly and read the folder and key names,
since apparently
those are stored unencrypted, if the API docs are to be believed.
Apparentl
On Friday 04 April 2014 09:42:34 Ivan Čukić wrote:
> Hi all,
>
> Since we have changed the location of our config files not to use .kde
> anymore, we will need some way of moving the old configuration files to
> their new locations.
>
> Should we use kconf_update for this, or is something else in
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116953/
---
(Updated April 4, 2014, 1:26 p.m.)
Status
--
This change has been di
On Fri, Apr 4, 2014, at 1:11, Aurélien Gâteau wrote:
> On Sun, Mar 30, 2014, at 16:42, Albert Astals Cid wrote:
> > Hello people, at the moment we have various 4.13 projects failing.
> >
> > Since we promised a while ago to not release without failing tests we
> > have
> > 10 days until tagging to
On Sun, Mar 30, 2014, at 16:42, Albert Astals Cid wrote:
> Hello people, at the moment we have various 4.13 projects failing.
>
> Since we promised a while ago to not release without failing tests we
> have
> 10 days until tagging to fix the tests or we'll have to delay the
> release.
>
> If you
Hi all,
Since we have changed the location of our config files not to use .kde
anymore, we will need some way of moving the old configuration files to their
new locations.
Should we use kconf_update for this, or is something else in the works?
Cheerio,
Ivan
--
Make your code readable. Prete
