Re: debconf's web frontend
Seth Cohn wrote:
> However, I just read the documentation, and noticed one catch: the client
> must be on the same machine (for security purposes). While this will
> still solve the disconnect problem (if your ssh/telnet dies, you
> can reconnect and still run lynx/whatever) it's not the solution I was
> suggesting (ie, if your box stops answering ssh/telnet ports, you can't
> continue configuring it, and it's a trip to the console)
>
> > (Shittiest web server on earth too, btw.)
>
> I thought M$ IIS was :) At least it's a bit heavier a pile of ....
> how big a pile can 256 lines be?
Pretty big. Look at it this way: It can only support one client at a
time. In fact, multiple clients will completly confuse it. It is, of
course, utterly insecure if it is reconfigured (trivial) to listen to
connects from the big bad network, because anyone can jump in and add
input, or just sniff what the admin is doing.
It's really a proof of concept only. A real implementation would
require, at a minimum, ssl and password support.
--
see shy jo
Reply to: