From: presotto@plan9.bell-labs.com
To: quinn@envy.ugcs.caltech.edu, 9fans@cse.psu.edu
Subject: [9fans] getenv/putenv
Date: Mon, 19 Mar 2001 09:40:37 -0500 [thread overview]
Message-ID: <20010319144040.8224B199D5@mail.cse.psu.edu> (raw)
My inclination would be to have the libc getenv() and putenv() check
their args. It costs almost nothing, and the less potentially dangerous
things the client has to think about checking the better.
I think you're right. We not as env crazy as Unix is so the risk is
lower but not nonexistant of somehow fooling a program to write
something, so why have it at all. Anyone else want to comment?
If not, I'll just check for '/' in getenv/putenv names and punt
if I find one.
next reply other threads:[~2001-03-19 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 14:40 presotto [this message]
2001-03-19 15:21 ` Lucio De Re
2001-03-19 15:58 presotto
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=20010319144040.8224B199D5@mail.cse.psu.edu \
--to=presotto@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
--cc=quinn@envy.ugcs.caltech.edu \
/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).