| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
in case something wants to create massive amounts of environment, like
a bit more than 1/4 of a 32-bit address space. unrealistic -- but why
audit one code path, and not treat others the same? then you have to
re-engage everytime you see the code. read the news, that isn't what
developers do. At least if the code paths look the same, there is hope,
because they are easier to verify for correctness. developers need
to give other developers a chance to want to care.
|
|
|
|
|
|
| |
an empty name, NULL pointer, or a name containing an '=' character.
OK millert@, guenther@
|
|
|
|
| |
via setenv() or putenv(). OK miod@
|
| |
|
|
|
|
|
| |
Someone may have passed a read-only string to putenv() (I'm looking
at you cron!).
|
|
|
|
|
|
| |
standard explicitly disallows passing setenv a name with a '=' in
it but historic BSD behavior is to allow this but to ignore the '='
and anything after it.
|
|
|
|
|
|
| |
Kill old files that are no longer compiled.
okay theo
|
|
|
|
| |
ok otto deraadt
|
|
|
|
|
|
|
|
| |
setting a flag. That way when we are called again we can be sure
to realloc() the right thing, regardless of the current value of
environ. When the stashed value != environ (or when we are called
for the first time), copy the existing entries from environ and set
environ to the new value. OK deraadt@, beck@, djm@
|
|
|
|
| |
rescinded 22 July 1999. Proofed by myself and Theo.
|
| |
|
| |
|
|
|
|
| |
Dave Bodenstab <imdave@mcs.net>
|
|
|
|
| |
Make sure everything uses {SYS,}LIBC_SCCS properly
|
|
|