I sense that this would make tftp non-trivial (in the eyes of many people), and increases the possibility for SystemImager introduced security holes. I prefer to not do that if at all possible.
The current daemon in CVS seems to work fine for now (for me at least), and doesn't open up any holes to the network -- it only operates locally. I'm willing to consider other possibilities, but I prefer to avoid touching code that listens directly to the network unless there are no reasonable alternatives. On Sat, 2002-09-14 at 17:23, dann frazier wrote: > you know, i just had another thought. > why not just have a wrapper or patch against a tftp server, that checks a > config file before returning a config file for the client? > > would this remove any need for an additional daemon? > > -- --------------------------------------------------- Brian Elliott Finley http://baldguysoftware.com/ phone: 214.280.8188 http://systemimager.org/ --------------------------------------------------- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Sisuite-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
