Simon Kelley wrote:
> clemens fischer wrote:
>
>> I see src/rfc1035.c::private_net() now has an additional argument
>> "ban_localhost" used to differentiate its use in bogus-priv and
>> stop-rebind. How about making "ban_localhost" a real option so that
>> users can decide for themselves what the
clemens fischer wrote:
> Simon Kelley wrote:
>
>> clemens fischer wrote:
>>
>>> To me your changes from test25..test27 were quite adequate by using
>>> the bogus-priv checks. Rob said he wants his VPN remotes to resolve.
>>> I can imagine he just enters the remotes as rebind-domain-ok domains
>>>
Steve Elliott wrote:
> But I still think I am missing something about the general case -
> Can dnsmasq-tftp serve an arbitary file?
Plain files for sure, yes.
> How can I setup dnsmasq to serve files owned by different users?
Either put the files into a group shared by both dnsmasq and these us
Niels,
Thanks for your input on this issue...
1) Your test confirms that "nobody" cannot access the file from outside the
CWD...
[Steve@regret tmp]$ sudo -u nobody cp
/home/Steve/Shared/workspace/xxx/xxx/bootrom.pxe.0 .
cp: cannot stat `/home/Steve/Shared/workspace/xxx/xxx/bootrom.pxe.0':
Permiss
