From kde-pim  Thu Oct 20 20:50:13 2011
From: Milian Wolff <mail () milianw ! de>
Date: Thu, 20 Oct 2011 20:50:13 +0000
To: kde-pim
Subject: Re: [Kde-pim] Need help with the undefined reference hack
Message-Id: <2548015.DEkc8O5cbf () minime>
X-MARC-Message: https://marc.info/?l=kde-pim&m=131916868504331
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============6475477107374649083=="


--===============6475477107374649083==
Content-Type: multipart/signed; boundary="nextPart1516087.3ixaiaam7s"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: quoted-printable


--nextPart1516087.3ixaiaam7s
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

On Wednesday 19 October 2011 21:48:17 Ingo Kl=F6cker wrote:
> On Wednesday 19 October 2011, Milian Wolff wrote:
> > Christian Mollekopf, 19.10.2011:
> > > On Wednesday, October 19, 2011 1:13 PM, "Andras Mantia"
> > >=20
> > > <amantia@kde.org> wrote:
> > > > Christian Mollekopf wrote:
> > > > > In the long run only if there is a way to get hold of the
> > > > > encrypted/unencrypted content without the MessageViewer.
> > > > > (Frankly I'm not a big fan of using the MessageViewer for the=

> > > > > feeder, but it seems to be the only way).
> > > >=20
> > > > Yes, using the messageviewer for this is not a good solution.
> > > > Sincerely I'd just ignore indexing of encrypted mails for now a=
nd
> > > > move the
> > > > feeder to kdepim-runtime.
> > >=20
> > > I'd prefer that solution too. Objections anyone?
> > >=20
> > > > There is anyway a need for explicitly enable that indexing (as
> > > > normally the
> > > > user doesn't want to have (part of) its encrypted content
> > > > unencrypted in a
> > > > database), and most users probably don't have that many encrypt=
ed
> > > > mails anyway.
> > > >=20
> > > > Then we can find a solution later for encryption.
> >=20
> > what what? if encrypted stuff gets indexed in plain text somewhere
> > I'd see that as a severe security breach. So yes, please do disable=

> > this - I wasn't even aware that this is done so far!
>=20
> It has already been said that it's off by default and I agree that it=

> must not be enabled without explicit consent of the user. Nevertheles=
s I
> want to point out that it depends on your threat model whether indexi=
ng
> encrypted messages is a problem.
>=20
> If you use mail encryption for protecting the content of messages dur=
ing
> transit and when stored on an IMAP server then indexing of encrypted
> messages (where the index is stored on your local harddisk) is no
> problem at all.
>=20
> If your threat model includes physical or remote access to your local=

> filesystem/harddisk then not using indexing will not protect you beca=
use
> the attacker will simply own your box, steal your OpenPGP key and
> install a keylogger or a special version of gpg in order to steal you=
r
> passphrase.
>=20
> So, before you talk about a severe security breach please explain you=
r
> threat model.

I agree that I didn't think too much about it.

But personally, I still have to insert a password to read encrypted mai=
ls -=20
even though I use gpg agent... So just having the private key does not =
seem to=20
be enough?!

Also: isn't the nepomuk database back'ed-up by default and hence such b=
ackups=20
would contain the plaintext passwords?  Which a user would then probabl=
y move=20
to some other backup place, like an unprotected usb/harddisk or so..

Furthermore, wouldn't the same reasoning of yours ("plaintext is OK as =
it's in=20
local files only") also apply to all kind of configuration files? KWall=
et e.g.=20
also uses a password by default. So imo it's good practice to never lea=
ve stuff=20
in plaintext around, "just because it's local".

And ps: of course this discussion is more or less moot if this feature =
is=20
already a) disabled and b) only enabled by explicit user choice in the =
future.

bye
--=20
Milian Wolff
mail@milianw.de
http://milianw.de
--nextPart1516087.3ixaiaam7s
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAk6giYUACgkQDA6yEs0dE5OnMgCgwZAHSK2tQPf5L0GJqhtFmDC7
v9sAniCTm1upMsPVjBSEQLpuGd5MG7Tf
=oqp1
-----END PGP SIGNATURE-----

--nextPart1516087.3ixaiaam7s--


--===============6475477107374649083==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
--===============6475477107374649083==--