Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Apr 1995 15:06:42 -0600
From:      Nate Williams <nate@trout.sri.MT.net>
To:        jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi), edward@edcom.com
Cc:        freebsd-bugs@freefall.cdrom.com
Subject:   Re: ports/352: tex package generally messed up
Message-ID:  <199504192106.PAA05283@trout.sri.MT.net>
In-Reply-To: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) "Re: ports/352: tex package generally messed up" (Apr 19, 10:46pm)

next in thread | raw e-mail | index | archive | help
>  > 	* MakeTeXPK should put generated pk files in a more permanant place
>  > 	  (or is that in the dvips package?)
> 
> The default is to generate them in /tmp. You can choose an alternate
> location when configuring dvips/xdvi. Otherwise, you have to let
> /usr/local/lib/texmf/fonts/pk writable by everyone.

At my site we made /usr/local/lib/texmf/fonts/pk writeable by everyone
(mode 1777) which is no bigger security hole than what you propose
below and it doesn't require any additional setup by the user which
adding lines to /etc/daily requires.

>The best is to 
> add the following code in your /etc/daily:
> 	if [ -d /tmp/pk ]; then
> 	    echo -n "Moving pkfonts"
> 	    for f in /tmp/pk/*pk; do
> 	      if [ -f $f ]; then
> 	        mv $f /usr/local/lib/texmf/fonts/pk/
> 	      fi
> 	    done
> 	fi

The response given for using the above instead of making the lib
directory writable is that is stops people from purposefully putting
bogus fonts into the world directory.  However, you can still put bogus
fonts in /tmp now which will end up in the global directory, and it
requires more setup at install time.

If there another valid reason for not doing this I'd like to hear it.



Nate






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504192106.PAA05283>