On Fri, Dec 21, 2012 at 10:23 AM, Richard Heck <rgh...@lyx.org> wrote: > My suggestion was that the per-file disabling should be done on the basis of > a per-user UUID we generate at installation, or some such time (and, as > Scott suggests, can re-generate if need be). This is not perfect. If someone > had your UUID, they could put that into the file, etc. But it would be > better than disabling globally. > > If it didn't seem good enough, there are more complicated things we could > do. E.g., calculate a hash of the file contents each time we save it,
I wonder if we could skip some of the hash calculations by only calculating & storing the hash each time we close a file or save a *new* file? > and > then encode that hash using a per-user key. Then if the file were externally > modified, you'd get warned again, and no-one would be able to send you files > marked as safe for you. Why would we have to encode the hash? Is this for the case that it's possible to have two documents produce the same hash or even if that weren't possible this would be desired? And all of this would not create a cost for most users because the hash would only be calculated if the knitr or Sweave module or the gnuplot template is enabled. Is that right? Scott
