Since the list responsiveness seems to be at a high, le me take the opportunity to repost a message that got no answers in March: I've searched the list, and I can't find reference to this being implemented: reverse veto files - a list of files *allowed* rather than the current list of files *denied*. Possibly implemented by just allowing a ! in the veto files directive. eg: veto files = /!*.png/!*.gif/ = only allow pngs and gifs to be read or written through that share. (though that's probably not the best syntax) I still think it's a good idea that I would find really valuable. Was this discussed further? Has it been implemented under another directive that I've missed? Has my google-foo let me down? -- Illtud Daniel illtud.daniel at llgc.org.uk Prif Swyddog Technoleg Chief Technical Officer Llyfrgell Genedlaethol Cymru National Library of Wales
On Tue, Jul 28, 2009 at 09:43:37PM +0100, Illtud Daniel wrote:> Since the list responsiveness seems to be at a high, le me > take the opportunity to repost a message that got no > answers in March: > > > I've searched the list, and I can't find reference to this being > implemented: > > reverse veto files - a list of files *allowed* rather than > the current list of files *denied*. Possibly implemented by > just allowing a ! in the veto files directive. > > eg: > > veto files = /!*.png/!*.gif/ > > = only allow pngs and gifs to be read or written through that > share. > > (though that's probably not the best syntax) > > I still think it's a good idea that I would find really > valuable.It's doable, but I wouldn't use that syntax. I'd use an "allowed files = /XXX/" style.> Was this discussed further? Has it been implemented under > another directive that I've missed? Has my google-foo let > me down?Not been implemented yet.... Patch welcome :-). Jeremy.
Ryan Parker-Hill wrote:> If you wanted to veto everything except jpeg files I imagine you > would not use the veto files directive at all and simply specify: > > Allowed Files = /*.jpg/Yup, that would work fine for me - ie that any 'Allowed Files' directive implies that all non-matching files are vetoed. Anybody else got an opinion before I dig out my K&R? -- Illtud Daniel illtud.daniel at llgc.org.uk Prif Swyddog Technegol Chief Technical Officer Llyfrgell Genedlaethol Cymru National Library of Wales
On Mon, Aug 03, 2009 at 09:24:04AM +1000, Ryan Parker-Hill wrote:> If you wanted to veto everything except jpeg files I imagine you would not use the veto files directive at all and simply specify: > > Allowed Files = /*.jpg/ > > If you wanted to allow only jpeg files but not foo.jpg you would use Allowed Files and Veto Files: > > Veto Files = /foo.jpg/ > Allowed Files = /*.jpg/Yes, this is pretty much how I envisaged this working... Jeremy