openbsd/src/lib/libc/stdlib/getenv.3, branch OPENBSD_7_9

For putenv(3), return an error if string starts with a '=' character.

2022-08-08T22:40:03+00:00

Both FreeBSD and NetBSD have this behavior. OK deraadt@

If a command or interface first appeared in PWB/UNIX, UNIX System III or

2022-07-25T02:25:55+00:00

UNIX System V mention it. Only do so in manual pages with a pre-existing HISTORY section. Prompted by the comparison of System V and BSD commands and interfaces in Sun's "System V Enhancements Overview" document. checked against manuals on bitsavers, TUHS archive and CSRG archive CDs ok jmc@ schwarze@

better document perils of setuid getenv and xr with issetugid

2014-07-11T09:24:03+00:00

ok deraadt

Correctly document the return value of getenv(3)

2014-04-21T08:46:59+00:00

From Ben Cornett (ben (at) lantern.is)

Use the fancy .In macro for includes. From Jan Klemkow. ok jmc schwarze

2013-06-05T03:39:23+00:00

Make setenv(3) consistent with unsetenv(3), giving EINVAL if passed

2012-09-23T16:08:04+00:00

an empty name, NULL pointer, or a name containing an '=' character. OK millert@, guenther@

Update STANDARDS section for a few functions

2012-06-02T00:14:16+00:00

Update SYNOPSIS for setkey() to show it's in ok jmc@, millert@

Tweak the description of the optional parts around =. Found this in my

2011-04-27T13:40:15+00:00

tree, no idea where it came from; ok millert@ jmc@

Document new unsetenv() error returns.

2010-07-06T20:52:00+00:00

From Nicolas Legrand ; ok jmc@

It's unsetenv() that doesn't like `=' in the argument, not putenv().

2010-03-10T20:46:16+00:00

ok millert@