On 2016/01/26 02:06, Matthew Martin wrote: > I'd bet the most common use case for tftpd is to serve PXE files or > similar where the files being served should not be modified. I'm failing > to find a use case where files need to be overwritten, but new files > must not be created.
It's used to allow devices to write files (config, core dumps, etc) to a tftp server given a known filename, but not allow just anybody with network access to write random files to the server. > Even if such a case did exist, setting the files to > be overwritten as world-writable and the directory to just > world-readable would accomplish the same result. > > Patch below provides a reasonable default of read only tftpd, with -c > allowing writing and creating. OK I see some use for -R. I'm not sure about making it default, my opinion could be swayed in either way with good arguments but if done that the change needs to be communicated clearly (if I am relying on it for a core dump for some network device, I don't want that to be quietly disabled by an update). I am actively opposed to removing the "allow only specific files to be written" feature.
