Re: [Licq-devel] Using privileged TCPPorts{Low,High} in licq.conf

2002-04-07 Thread
Jacob Bunk Nielsen wrote: > "" <[EMAIL PROTECTED]> writes: > > > Port 1024 is not a privileged port as far as I know. > Uhuh, could be, okay, you are right, i thought 1024 was not priviledged, it is. Arjen ___ Licq-devel mailing list [EMAIL PR

Re: [Licq-devel] Using privileged TCPPorts{Low,High} in licq.conf

2002-04-04 Thread Jacob Bunk Nielsen
"" <[EMAIL PROTECTED]> writes: > + // The following is a FILTHY hack around the fact that we are not allowed to > + // open a port below 1024. We get a segfault if we try so... > + > + if (_nPort <= 1024) Strictly speaking it should be if (_nPort < 1024) or if (_nPort <= 1

Re: [Licq-devel] Using privileged TCPPorts{Low,High} in licq.conf

2002-04-01 Thread
I wrote a patch around it, it works, BUT someone NEEDS BADLY to look at a better solution, this just checks if the port we are trying to open as a TCP server, is not below 1024. If so, just tell that we cant open that port ;) File atached, just have a l00k at it :) Arjen Mikael Vidstedt wrot

[Licq-devel] Using privileged TCPPorts{Low,High} in licq.conf

2002-04-01 Thread Mikael Vidstedt
If TCPPortsLow and TCPPortsHigh in licq.conf are set to privileged ports (eg. 110 and 120 respectively) and running as a non-privileged user, there will be a segmentation fault at startup. This is because CICQDaemon::StartTCPServer tries to bind to one port at a time, failing each time (Permissio