On Thursday 03 April 2008 20:30:45 Bo Peng wrote:
> You have gone from not fixing the problem to denying the problem.  At
> least lyx user's guide refers to ../images/blah.png on every machine
> it is installed.

  It does make sense to use the "user guide" as an example because we do not 
distribute only the user guide but all the directories, including those where 
the images are. There are no external links in the lyx documentation or else 
our users would not be able to use it.

  If you have now an external file referred without it being present the 
document will not work (compile), even if that is graphic and we know its 
dimensions where we could draw a blank we don't do it. With your model it 
will work. So we are comparing different things.

  I agree that discussing without an implementation can be difficult so here 
follows the reason why I am against this feature:

  Every bit of personal information that we release unnecessarily is a 
potential security threat. The original file location of an embedded file is 
one of those cases.

  Since to me it does not make sense to compromise on the security issue the 
original file location is a bad idea.

  The same would be true, if for absurd, our pdf documents had the reference 
to which directory the were created, even if it was /tmp/%$#""#%/&(1/lyx-1122

  Our binaries should not have any reference to the directory where they were 
created.

  In terms of security it better to be safe than sorry.

> Bo

-- 
José Abílio

Reply via email to