Re: [IPCop-devel] TO-DO on Backup]

[Tim B. <tim...@mi...>]

Since I worked on the web backup GUI, perhaps I should add my voice to 
this conversation.  Here are a few things I would be concerned about:

1) risk - Are there files on the IPCop system that should NOT be 
accessible through the web interface?  Given the conversation so far 
and possible new features, any file that can be browsed to can be added 
to include.user and downloaded via the .tar.gz archive.  This allows 
ANY file to be easily viewed by anyone with access to the web 
interface.  Is this a risk worth taking?

2) necessity - Is this a feature that is needed by many users or just 
something that might be used by 10 percent or fewer of the users?  The 
web backup is useful to many, if not most users.  I'm not sure if this 
feature would be in the same category.

3) how useful - Granted that including a file browser in the web 
interface would allow easily finding files, if #1 above excludes that 
functionality, you would still need to find the specific path to add to 
include.user or exclude.user.  Without #1, that would likely be done by 
exploring the file system via an SSH login.  If that is true, a simple 
'echo /var/log/rrd >> include.user' might suffice with much less 
development effort or without the user having to go to the web  GUI to 
do what can easily be done at the prompt currently logged in to.

--
Tim Butterfield
http://www.timbutterfield.com/