John,
That's OK. I've just joined this list, but have used STN for some time now.
Keep it simple. Concentrate on user accessibility, which got much better in
version 2.1. Here's a few suggestions based on my 9-months experience with
STN:
1) Make it easier yet to set up. There are quite a few configuration
settings that are made only after generating the floppy, when STN
is booted and running. Make these back before the floppy is written
(on the Windows machine) so that a 100% complete record exists and
the floppy can be regenerated, or modified slightly and regenerated,
with ease.
2) Work on the firewall a bit. The addition of the several options to
forward selected ports is great. Are there more common ones? Like
I am just now trying to get retrieval of mail through the firewall
using POP3 going. I hope it's just a matter of adding port 110.
3) Logging: Is it possible to send a log (whose verbosity is user selected)
of accesses (in, out, in/out, ...) to another computer for monitoring
the state of the STN system? Any sort of information that an "attack"
on the system was made would be great.
4) Speaking of attacks: Have you unleashed SATAN on STN? Patching any
security holes would be important. This may be more of a core Linux
problem, however.
Thanks for the great effort.
Dave
John Lombardo wrote:
>
> Hi everyone,
>
> After looking at code and experimenting with the current lpd server, I just
> don't see how ShareTheNet can act as a print server with any reliability.
>
> Regards,
> John
>
> _______________________________________________
> ShareTheNet maillist - [EMAIL PROTECTED]
> http://www.webserv.com/mailman/listinfo/sharethenet
_______________________________________________
ShareTheNet maillist - [EMAIL PROTECTED]
http://www.webserv.com/mailman/listinfo/sharethenet
