Re: [Texmacs-dev] Re: [Bug #1789] temporary files are created in an insecure way

[Joris van der Hoeven]

> > > The only good reason I see not to put temporary files in "~/.TeXmacs",
> > > is that on big systems, the admin will typically tune differently the
> > > filesystems of /home and of /tmp. Also, using /tmp ensures that
> > > garbage is periodically cleant by the system.
> > 
> > Well, TeXmacs may clear the garbage itself, as it does already
> > (hmm, maybe I forgot about some stuff in ~/.TeXmacs/system)...
> 
> That misses the point of putting temp files in a different filesystem.

Yes, but since they are destroyed immediately after use,
this does not seem to be a big problem...

> > No, the caching may improve performance over *several* runs.
> 
> I agree. I just think cached stuff should not be in /home.

Yes, but not in /tmp or /var either, because these might be cleant.
I don't know of a /cache file system...

> A few additional points:
> 
>   -- files and directories should be created with the right permission
>      (I think the UMASK env variable is of use there).
> 
>   -- if the user sets unsafe permissions, texmacs should refuse to
>      run.
> 
>   -- texmacs should *not* quietly change the permissions of existing
>      files or directories.
> 
>   -- safe permissions should not restrict reading, only writing.
>
> PS: while we are at it, it would make sense to automatically create
> token my-init-texmacs.scm and my-init-buffer.scm which just exec the
> corresponding file in TEXMACS_PATH.

Yes, this might be done if find time for it.