Markus Fröhlich wrote at about 18:43:01 +0200 on Thursday, September 22, 2011: > backupPC processes run as user "wwwrun" - this is the apache user - > because of the permissions making the configuration over the webinterface. > the archive request get startet over a cronjob and a small skript once a > week: > "sudo -u wwwrun /usr/local/BackupPC/bin/BackupPC_archiveStart > archive-tape xadmin $XALL_HOSTS" > where the variable XALL_HOSTS contain all hosts of the backupPC server. >
As has been pointed out several times before on the list, making backuppc run as the apache user is potentially a HUGE security hole since it may end up allowing anybody to have permission to read any of the backups... Backuppc should be run as a *separate*, secure user. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
