[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tarsnap on remote/web servers
- To: tarsnap-users@tarsnap.com
- Subject: Tarsnap on remote/web servers
- From: John Schofield <jms@schof.org>
- Date: Sun, 6 Jun 2010 13:43:59 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=b1kIxyT/7wLC/c2O+N0NGS721LNurEC/WVUhRXN6i8R2Y05WFnKP0O3dVo9tZwrTID UD4V0Dtj/pfiAWL//Mq4E6JtgAFnuOK2E2QtJKNJEYxMIACTkxMHhk9mQUVFs9QENT1H gEosZQ+bCR+svdsIwVPyo+NUn7455ubUn6psg=
- Mailing-list: contact tarsnap-users-help@tarsnap.com; run by ezmlm
- Sender: jschofield@gmail.com
I've been using Tarsnap to back up my laptop (perfect, except for a little problem where Dropbox appears to be modifying metadata, causing Tarsnap to re-archive files).
I'm now considering using Tarsnap on a remote web/application server of mine.
I've seen horror stories posted to pastebin about hackers who break into a server nuke it, then use login credentials found on the server to reach wherever the server's backups are stored, and nuke those too.
Is there a way to limit Tarsnap so I have a key on the web server that allows tarsnap to create archives but not to delete them?
John