diff options
| author | George Lebl <jirka@5z.com> | 2003-09-12 21:50:46 +0000 |
|---|---|---|
| committer | George Lebl <jirka@src.gnome.org> | 2003-09-12 21:50:46 +0000 |
| commit | dde96cfce197fe25b39412a0c9892b70d15470a0 (patch) | |
| tree | 01bd52a9a59b19268a2d5c524ce0e4052b36344c /TODO | |
| parent | 1eedcd47213dd470fc7e9a5aa3849a88cd20a8d2 (diff) | |
| download | gdm-dde96cfce197fe25b39412a0c9892b70d15470a0.tar.gz | |
raise version
Fri Sep 12 14:49:30 2003 George Lebl <jirka@5z.com>
* configure.in: raise version
* daemon/gdm-net.c: some cleanup and be utterly anal when creating /tmp/.gdm_socket
(note: we were anal before, but now we're really REALLY anal)
* daemon/gdm.c: disable substituting 'nobody' for 'gdm', what was I
smoking when I wrote that?
* daemon/misc.c: some cleanup and make sure gdm_fdprintf writes all
the characters it really needs to write. Also the ensure extension
doesn't append extensions to empty strings.
* daemon/slave.c: use only one pipe for all the waitpids, since we
really don't need more then one and this make code simpler.
* docs/C/gdm.xml: update
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -10,7 +10,9 @@ run from within the mainloop. The one thing that will always cause trouble here is the XDMCP server pinging, I think in this case it would be sane to do the setjmp thing and just ignore the ping if a signal comes, not sure how this will play with the X stuff and if this would completely whack us out. The other option is to have -a separate "pinger process" but that seems to heavyweight. +a separate "pinger process" but that seems to heavyweight. Another option here +is to give up on complete mainloopishness and during pinging set up an alarm or +some other polling thing that checks all the mainloops stuff. All the GUIs running as the gdm user should have some resource limits set to make it hard to do DoS attacks by somehow exploiting a leak or some such. |