| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: setuid(geteuid());? |
| Date: | 2001-04-21 17:47:23 |
| Message-ID: | 1831.987875243@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I said:
> On machines that have setreuid(), or even better setresuid(), we could
> force the ruid (and suid for good measure) to match euid. Otherwise we
> probably should refuse to start unless getuid matches geteuid.
But on third thought, it's not worth the trouble of adding two more
configure tests to support a configuration that I doubt anyone uses
anyway (ie, setuid postgres executable). Let's just remove the setuid()
and add a check for getuid() == geteuid() in main.c.
Peter, unless you've already started in on this, I can take care of it
--- I see a couple of other nits I want to fix in those two files, too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-04-21 18:13:57 | Re: setuid(geteuid());? |
| Previous Message | Tom Lane | 2001-04-21 17:29:13 | Re: setuid(geteuid());? |