From kde-core-devel  Mon Jan 03 01:58:21 2005
From: Brad Hards <bradh () frogmouth ! net>
Date: Mon, 03 Jan 2005 01:58:21 +0000
To: kde-core-devel
Subject: Re: [RFC] Security and Features in KPDF
Message-Id: <200501031258.26647.bradh () frogmouth ! net>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=110471759006488
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1540309.iMHjKBuVZn"

--nextPart1540309.iMHjKBuVZn
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Mon, 3 Jan 2005 11:08 am, Ingo Kl=C3=B6cker wrote:
> Unfortunately, Stephan's suggestion is also not a very good solution
> because you can be sure that several distributions will make "kpdf
> --script %u" the default for PDF "because it's so convenient".
As the other side of this, how about only allowing a whitelist of "safe"=20
options. We could pre-populate it with things that are unlikely to get us=20
into trouble (eg koffice documents, maybe), and allow the user to add other=
s.=20
Just use the same sort of settings / wording as KMail has - "you may=20
compromise your privacy, etc".

Brad

--nextPart1540309.iMHjKBuVZn
Content-Type: application/pgp-signature

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

iD8DBQBB2KbCGwwszQ/PZzgRAsXPAJ4m4YUPJZ504TGI8AG/KXZZAvP8VgCgmsYY
hyR6lPMPOhEoSQDNx0OADXg=
=7C5l
-----END PGP SIGNATURE-----

--nextPart1540309.iMHjKBuVZn--