public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Wil Reichert" <wil.reichert@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Local network backup
Date: Fri, 14 Sep 2007 12:01:58 -0400	[thread overview]
Message-ID: <7a329d910709140901xaaf206fid399a47e617f5e66@mail.gmail.com> (raw)
In-Reply-To: <200709141303.46235.prh@gotadsl.co.uk>

On 9/14/07, Peter Humphrey <prh@gotadsl.co.uk> wrote:
> On Friday 14 Sep 2007, Wil Reichert wrote:
> > I'm assuming since you're asking this question your firewall is locked down
> > pretty tight.
>
> Not particularly, but it seems silly to take needless risks. It has shorewall
> to manage iptables, but I still let it run squid, ntpd, dnsmasq and a few
> other little goodies. I suppose I rely on shorewall to keep me safe.
>
> > That said, backing up your personal data to it seems like a not very good
> > idea. Were you planning on encrypting it or something?
>
> I see what you mean, but really the main use of the backup would be to recover
> a working system to a damaged box (I can be just as clumsy in admin as anyone
> else), rather than spending a week or more rebuilding it from source. User
> data could perhaps be backed up elsewhere - I have a handy little USB disk
> that would do nicely.
>
> > Who uses your internal network seems to be the variable here. Is this at
> > work or home?
>
> The clue was in "my tiny LAN" which means my own  :-)
>
> > Is there a wireless router thrown in there somewhere?
>
> The one wireless link is between the laptop and an access point; the WAP is
> connected to an Ethernet switch which lives between the workstation and the
> gateway. Why do you ask?

Shorewall is good =)

If its your own private LAN with no (few?) external users, why bother
with ssh & encrypting traffic?

Wil
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2007-09-14 16:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14  9:22 [gentoo-amd64] Local network backup Peter Humphrey
2007-09-14 11:26 ` Hamish
2007-09-14 11:42   ` Peter Humphrey
2007-09-14 13:17     ` Peter Humphrey
2007-09-14 13:34     ` Jordi Molina
2007-09-14 14:24       ` Etaoin Shrdlu
2007-09-14 14:31         ` Jordi Molina
2007-09-15  7:52         ` Peter Humphrey
2007-09-15  9:19           ` Etaoin Shrdlu
2007-09-15 10:21             ` Peter Humphrey
2007-09-15 10:43               ` Etaoin Shrdlu
2007-09-16 12:08                 ` Peter Humphrey
2007-09-16 14:10                   ` Etaoin Shrdlu
2007-09-14 16:10       ` Jack Lloyd
2007-09-14 16:32         ` Mike Williams
2007-09-14 16:41           ` Jack Lloyd
2007-09-14 16:38       ` Steve Herber
2007-09-17  9:34     ` Hamish
2007-09-14 11:29 ` Wil Reichert
2007-09-14 12:03   ` Peter Humphrey
2007-09-14 16:01     ` Wil Reichert [this message]
2007-09-14 18:51     ` [gentoo-amd64] " Duncan
2007-09-15 12:39 ` [gentoo-amd64] " Volker Armin Hemmann

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=7a329d910709140901xaaf206fid399a47e617f5e66@mail.gmail.com \
    --to=wil.reichert@gmail.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    /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