[RFC] Security and Features in KPDF

[George Staikos]

On Monday 03 January 2005 00:00, Gary L. Greene Jr. wrote:
> >   The biggest difference is that people aren't accustomed to not being
> > able to trust a PDF that their application already warns about this way. 
> > They know if you download an unsigned executable and run it, you risk
> > getting a virus or other such problem.  I know that I wouldn't be
> > concerned about myself running commands in PDFs (I know enough to just
> > say no all the time due to the various risks), but I am concerned for
> > others in general.
>
> Interesting argument there, but does this mean that we should also drop
> support for kparts in koffice and kjsembed from KDE? You could use the same
> core technologies to KDE to cause a security risk using a well crafted
> kword document. I agree with Tobias about this feature. Its a useful
> feature. If folks don't want it in KPDF, make this a compile time option
> and be done with it, especially since KDE distributes sources last I
> checked.

   kpdf is a kpart too.  The point is that the kparts themselves should each 
be "safe".

-- 
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/