9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Alexander Schreiber <als@thangorodrim.ch>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: Venti backups from unix
Date: Tue, 17 Dec 2024 20:57:27 +0100	[thread overview]
Message-ID: <Z2HXpytcCAhWsQcP@mordor.angband.thangorodrim.de> (raw)
In-Reply-To: <17344543920.A102dDcb.377@composer.9fans.topicbox.com>

On Tue, Dec 17, 2024 at 11:53:12AM -0500, wb.kloke@gmail.com wrote:
> 
> On a desktop system using a browser like chromium or firefox, we got a lot of
> files we simply don't want to backup. The browsers, and a lot of other
> desktop applications, scatter those files over several dot-named directories
> like .config, .local or .cache.  Excluding dot-named files and directories
> from backup is a good idea, especially for .ssh, which contains secrets,
> which are not secret anymore, if backupped.

Except if those ssh keys are used to authenticate to other systems,
are not backed up and then subsequently lost to storage failure, one
might have a somewhat not fun time.

So I recommend splitting your backups into unprotected sets (no damage,
at most mildly irritated if it becomes public) and protected sets
(e.g. ssh keys, financial/medical data, etc), the latter of which
should be encrypted.

Kind regards,
           Alex.
-- 
"Opportunity is missed by most people because it is dressed in overalls and
 looks like work."                                      -- Thomas A. Edison

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T5f59d7df5796d0cc-Me5b0d5c6d64128366682091c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

      reply	other threads:[~2024-12-17 20:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-14 19:37 [9fans] " Anthony Sorace
2024-12-17 16:53 ` [9fans] " wb.kloke
2024-12-17 19:57   ` Alexander Schreiber [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z2HXpytcCAhWsQcP@mordor.angband.thangorodrim.de \
    --to=als@thangorodrim.ch \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).