[scponly] mysql

[wby oblyr]

I'm going to have to agree with Sven on this one, Mario.  adding mysql support to scponly is way outside the 
design goals.

i have some serious doubts that any administrator would want to treat file transfer privs and database access as 
the same problem to be solved with the same tool.

I think you would be better off with the access control included in mysql, perhaps augmented by some firewall 
rules to limit accessibility to the server.  If the ultimate destination of your backup files is some remote 
system, write your cron job on the remote system and access the data using tcp sql connection.  Running a local 
msqyl_dump through scponly is officially a Bad Idea.

Sorry I cant help you more,
joe





Mario D??ring wrote this message on Sun, Feb 05, 2006 at 22:49 +0100:
> On Sat, 4 Feb 2006 10:26:51 +0100
> Sven Hoexter <sven at timegate.de> wrote:
> 
> > > can you add mysql support to scponly?
> > No ;) Ok you can if you like but I think it's useless.
> > 
> > 
> > > The idea behind this is following:
> > > You can make a remote backup of your database via SSH and transfer
> > > it via rsync to your home computer.
> > > That way you don't have to transfer the whole database each time :)
> > Create the backup files with a cronjob and then use a dedicated
> > account with a scponly shell to transfer the files with rsync.
> 
> 
> Since the user has no shell to this system, he can not create any
> cronjobs :/
> 
> 
> _______________________________________________
> scponly mailing list
> scponly at lists.ccs.neu.edu
> https://lists.ccs.neu.edu/bin/listinfo/scponly