Red Hat Bugzilla – Bug 192910
cannot use conserver by TCP
Last modified: 2007-11-30 17:11:33 EST
Description of problem:
Using --with-uds in %configure makes a build that does not support having the
conserver daemon on one machine and the console client on another machine.
That is a big part of what makes conserver useful. Before it went into extras,
I was using an unofficial conserver rpm of my own and the extras version updated
over it leaving me unable to use conserver.
The upstream code should really support making this a runtime configuration
choice rather than compile-time. But I am not energetic enough to fix it that
way this week. The conserver network support can work with SSL and tcp-wrappers
and I think that can provide sufficient security for people who want to restrict
it to local use. The configuration using --with-uds renders it useless to me.
Please consider removing --with-uds from the %configure line in conserver.spec.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Ditto, half the fun of conserver is the network support :)
Suggest running configure with "--with-openssl --with-libwrap --with-pam"
instead (plus CFLAGS fun) so it'll "just work" for the most part (users will
still need to edit conserver.passwd).
Nate Straz bugged me about this a month ago (with patches); I should have
committed the fix then. My apologies.
Should be fixed in 8.1.14-3, coming soon to a mirror near you.