aboutsummaryrefslogtreecommitdiff
path: root/proc.c
AgeCommit message (Collapse)Author
2024-08-03remove useless debugging logOmar Polo
2024-06-14styleOmar Polo
2024-06-14propagate prefork valueOmar Polo
otherwise the child processes still believet the prefork value is 3 and can end up reading/writing out of bounds when setting up the sockets. Actually, server processes shouldn't create pipes to other servers, but this is left for a follow-up diff. Issue reported by la ninpre, thank you!
2024-01-21remove proc_forward_imsg since it's unusedOmar Polo
2024-01-21convert most of gmid to the new imsg APIsOmar Polo
Makes parsing and handling of imsgs simpler / clearer. only crypto.c is left as-is.
2024-01-21convert to use imsg_get_fd()Omar Polo
since proc_forward_imsg() never forwards a file descriptor (it's never called actually) just use -1 there.
2023-06-24rework checkOmar Polo
2023-06-13work around missing SOCK_NONBLOCK/CLOEXEC on macosOmar Polo
2023-06-11remove proc_ispeer()Omar Polo
unused, and was dropped by other copies of proc.c; reduces the diff with httpd' proc.c.
2023-06-11move setproctitle/privsep_process earlierOmar Polo
We don't always do privilege dropping (as we may start as unprivileged user), so set these two beforehand so when we skip privdrop we don't miss to set privsep_process and set the process' title.
2023-06-09parse the config file only onceOmar Polo
Don't have all the processes read gmid.conf. The parent needs to do that, and the will send the config to the children (already happening.) The other processes were reading the config anyway to figure out the user and the chroot (if enabled); make the parent pass additional flag to propagate that info. We dissociate a bit from the "usual" proc.c but it's a change worth having.
2023-06-08fix build of proc.c on !OpenBSDOmar Polo
2023-06-08rework the daemon to do fork+execOmar Polo
It uses the 'common' proc.c from various OpenBSD-daemons. gmid grew organically bit by bit and it was also the first place where I tried to implement privsep. It wasn't done very well, in fact the parent process (that retains root privileges) just fork()s a generation of servers, all sharing *exactly* the same address space. No good! Now, we fork() and re-exec() ourselves, so that each process has a fresh address space. Some features (require client ca for example) are temporarly disabled, will be fixed in subsequent commits. The "ge" program is also temporarly disabled as it needs tweaks to do privsep too.