Hi, for those playing along at home, time for a status update:
r.terraflow is the only module in GRASS 6.0 CVS which hasn't been fixed
for this bug yet (end user set-able but uses /var/tmp as default).
You can make a GRASS package without the r.terraflow module by doing:
./configure
On Thu, 2005-02-03 at 12:55 +1300, Hamish wrote:
Hi, for those playing along at home, time for a status update:
r.terraflow is the only module in GRASS 6.0 CVS which hasn't been fixed
for this bug yet (end user set-able but uses /var/tmp as default).
You can make a GRASS package without
I'll try to get a CVS package squared away tomorrow.
I have just reverted that init.sh $TMPDIR change now, so it should be
all set for a fresh checkout, AFAICT.
Best to do it as quickly as possible I think.
Yes, I hadn't been keeping up with the Debian Weekly News the sarge
release appears
[cc bug lists to archive the link]
This page describes a way to create a secure tmp directory where you
can create tmp files without worrying about their names:
http://www.linuxsecurity.com/content/view/115462/151/#mozTocId316364
..
Maybe someone can help me with this one:
Hamish wrote:
Just an update re. less-insecure tempfiles ..
In the upstream GRASS 5.7 CVS[*] pretty much everything in the scripts/
directory now uses g.tempfile. C modules are next. I am not sure what to
do with the init scripts libs where the GRASS tempfile fn's may not be
available..
[thanks for the 5.0.3 patch Marga]
Just an update re. less-insecure tempfiles ..
In the upstream GRASS 5.7 CVS[*] pretty much everything in the scripts/
directory now uses g.tempfile. C modules are next. I am not sure what to
do with the init scripts libs where the GRASS tempfile fn's may not
6 matches
Mail list logo
