From: "James Stevenson" <mistral@stev.org>
To: GOMEZ NOGUERA DAVIDEDUARDO <davidgn@servidor.unam.mx>,
Glynn Clements <glynn.clements@virgin.net>
Cc: xmp <xmp@multipasto.net.co>, linux-c-programming@vger.kernel.org
Subject: Re: Misc C question
Date: Thu, 20 Jun 2002 22:53:32 +0100 [thread overview]
Message-ID: <002d01c218a4$ecb20cb0$0501a8c0@Stev.org> (raw)
In-Reply-To: Pine.GSO.4.33.0206201540260.13436-100000@servidor.unam.mx
Hi
thats because you can check for it.
it disappears and sombody creates a symlink to somewhere like /etc/passwd :)
you need to check it open it and check it again on the open fd
----- Original Message -----
From: "GOMEZ NOGUERA DAVIDEDUARDO" <davidgn@servidor.unam.mx>
To: "Glynn Clements" <glynn.clements@virgin.net>
Cc: "xmp" <xmp@multipasto.net.co>; <linux-c-programming@vger.kernel.org>
Sent: Thursday, June 20, 2002 9:42 PM
Subject: Re: Misc C question
> hello.
> sorry if the message gets duplicated.
>
> I read a while ago of some security issues on doing checks on files before
> opening, wich is harmfull if the program is suid.
>
> But i dont remember what to do about it.
> can someone refresh it to me?
> is there anyway you can lock a file access and tell the kernel? and what
> would happen if the program crashes without unlocking the file?
>
> bye bye
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2002-06-20 21:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 2:46 Misc C question xmp
2002-06-20 3:10 ` mike
2002-06-20 4:44 ` xmp
2002-06-20 5:08 ` mike
2002-06-20 12:46 ` William N. Zanatta
2002-06-20 6:28 ` Oleg O. Ossovitskii
2002-06-20 8:05 ` Mohammed Khalid Ansari
2002-06-20 8:51 ` Re[2]: " Oleg O. Ossovitskii
2002-06-20 13:23 ` Glynn Clements
2002-06-20 20:42 ` GOMEZ NOGUERA DAVIDEDUARDO
2002-06-20 21:53 ` James Stevenson [this message]
2002-06-20 23:24 ` Glynn Clements
2002-06-20 23:24 ` Glynn Clements
2002-06-21 0:07 ` Christopher Quinn
2002-06-20 18:09 ` James Stevenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002d01c218a4$ecb20cb0$0501a8c0@Stev.org' \
--to=mistral@stev.org \
--cc=davidgn@servidor.unam.mx \
--cc=glynn.clements@virgin.net \
--cc=linux-c-programming@vger.kernel.org \
--cc=xmp@multipasto.net.co \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).