[tech] flame, moray's kernel and transparent proxying
Duncan Sargeant
dunc at rcpt.to
Thu Sep 16 15:28:34 WST 1999
Ian McKellar wrote on Thu September 16, at 15:14 +0800:
> On Thu, Sep 16, 1999 at 03:04:46PM +0800, David Luyer wrote:
> > > It may be a hack, but its a more elegant hack than hacking MudOS to bind to
> > > a particlar ip, and:
> > > * running MudOS as root
> > > or
> > > * hacking the kernel to allow non-root to bind to low ports
> > or
> > * using a launcher app (the standard way, see innd and many others)
> >
> > fd0 = bind(flame_ip:23);
> > fd1 = bind(flame_ip:80);
> > exec(flame, fd0#, fd1#);
>
> Ahh, cool, but is this less of a hack than using the transparent proxy
> code?
Yes.
> Also, with the transparent proxy code we can add new services without
> rebooting, recompiling flame, or even restarting the driver :)
*boggle* How were you planning to enable the transparent proxy code
without recompiling the kernel or rebooting moray?
,dunc
More information about the tech
mailing list