Paul Eggert eggert at CS.UCLA.EDU writes:
With Bison I wanted fopen_safer but not tmpfile_safer (I think tmpfile
is not that safe due to signals and whatnot), so I split the fopen-safer
module into two, as follows:
/usr/ucb/cc on Solaris 7 didn't like fopen-safer or tmpfile-safer:
cc -Xc
Ben Pfaff [EMAIL PROTECTED] writes:
I was worried that there was something bigger here. Usually a
safety issue is something more important than leaving a
temporary file undeleted or limiting their number, like the
possibility of a security hole, a segfault, etc.
Eric Blake mentioned some of
Eric Blake [EMAIL PROTECTED] writes:
Would you accept a similar patch that splits out pipe-safer into its own
module instead of part of unistd-safer?
I think that'd be OK, yes. It sounds pretty straightforward, anyway.
Eric Blake wrote:
tmpfile is
allowed to leave a permanent file behind if the call to tmpfile() is
interrupted, or if the process _exit()s. Yet there is no way to know what
that file is.
Yup. When you look at clean-temp.c you see the various steps that are
needed to avoid leaving a file
Eric Blake [EMAIL PROTECTED] writes:
According to Ben Pfaff on 7/25/2006 11:21 AM:
Can you expand on why tmpfile is not so safe?
I'd still like to fear Paul's reasons.
I hope you mean hear them :-)
But one of mine is that tmpfile is allowed to leave a permanent
file behind if the call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ben Pfaff on 7/26/2006 11:54 AM:
Eric Blake [EMAIL PROTECTED] writes:
According to Ben Pfaff on 7/25/2006 11:21 AM:
Can you expand on why tmpfile is not so safe?
I'd still like to fear Paul's reasons.
I hope you mean hear them
With Bison I wanted fopen_safer but not tmpfile_safer (I think tmpfile
is not that safe due to signals and whatnot), so I split the fopen-safer
module into two, as follows:
2006-07-24 Paul Eggert [EMAIL PROTECTED]
* MODULES.html.sh (File stream based Input/Output):
Add
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 7/25/2006 12:24 AM:
With Bison I wanted fopen_safer but not tmpfile_safer (I think tmpfile
is not that safe due to signals and whatnot), so I split the fopen-safer
module into two, as follows:
Reasonable. In fact, it
Paul Eggert [EMAIL PROTECTED] writes:
With Bison I wanted fopen_safer but not tmpfile_safer (I think tmpfile
is not that safe due to signals and whatnot), so I split the fopen-safer
module into two, as follows:
Can you expand on why tmpfile is not so safe?
--
Ben Pfaff
email: [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ben Pfaff on 7/25/2006 11:21 AM:
Paul Eggert [EMAIL PROTECTED] writes:
With Bison I wanted fopen_safer but not tmpfile_safer (I think tmpfile
is not that safe due to signals and whatnot), so I split the fopen-safer
module into two,
10 matches
Mail list logo
