From:	Alain Magloire <alainm AT rcsm DOT ece DOT mcgill DOT ca>
Message-Id:	<199902171924.OAA14128@mccoy2.ECE.McGill.CA>
Subject:	inetutils ?
To:	eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date:	Wed, 17 Feb 1999 14:24:00 -0500 (EST)
Cc:	djgpp-workers AT delorie DOT com
In-Reply-To:	<Pine.SUN.3.91.990216094827.14991M-100000@is> from "Eli Zaretskii" at Feb 16, 99 09:48:52 am
X-Mailer:	ELM [version 2.4 PL25]
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com

Bonjour

[I got inetutils on DJGPP on my todo list.
Please CC, cause I'm not on the list]

- Socket API, for DJGPP. Such a beast exists ?
I heard about wattcp, but they have some strange API
and don't know if it's worth the try to slap Socket API
on top. And the license policy is not clear.
wsock ? can't find it, sock seems to say socket ?

- Security ? How to get security from a DOS box ?
The concept of seteuid/setuid/setgpid/getpw* etc ...
seems somewhat nebulous.

- how about chroot () ? supported ?
chroot adds a level of security when you're dealing with
guests accounts.

- the infamous fork (). For example inetd on a busy
day, with a good wind can for requests in 2 digits
per second. Can djgpp fork()'s handle it.

- OOB, Out-of-band request ?

- select (), O_NONBLOCKING, exec (), signal ().

My real concern really is the security aspects of things
basically .. How do you loggin, in the POSIX/Un*x sense ?
Can you logging ? This implies some sort of
Multi{user/task/share} support.

-- 
au revoir, alain
----
Aussi haut que l'on soit assis, on n'est toujours assis que sur son cul !!!

- Raw text -