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
On Mon, Jan 25, 2016 at 07:32:52AM +, Stuart Henderson wrote:
> On 2016/01/25 04:32, Jérémie Courrèges-Anglas wrote:
> >
> > Hi Matthew,
> >
> > Matthew Martin writes:
> >
> > > On Sun, Jan 24, 2016 at 03:05:28AM -0600, Matthew Martin wrote:
> > >> Add a -R flag to tftpd
Stuart Henderson writes:
> 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,
Add a -R flag to tftpd for a read only mode. This allows for a tighter
pledge than currently possible because by default existing files can be
overwritten (but no new files created). Perhaps read only should be the
default since it is surprising that tftp can overwrite by default.
- Matthew
On 2016/01/25 04:32, Jérémie Courrèges-Anglas wrote:
>
> Hi Matthew,
>
> Matthew Martin writes:
>
> > On Sun, Jan 24, 2016 at 03:05:28AM -0600, Matthew Martin wrote:
> >> Add a -R flag to tftpd for a read only mode. This allows for a tighter
> >> pledge than currently
On Sun, Jan 24, 2016 at 03:05:28AM -0600, Matthew Martin wrote:
> Add a -R flag to tftpd for a read only mode. This allows for a tighter
> pledge than currently possible because by default existing files can be
> overwritten (but no new files created). Perhaps read only should be the
> default