Does anyone know of a Linux backup utility that uses GPG to encypt individual
files?
I've recovered files from CRDOMs with bad bits recently, and didn't know it
until I tried using them. Storing each file with a checksum would be the
answer to that. Also, I'd like to be give backups to almost anyone willing to
store them. Encrypting the backups would be the answer to that: "Please keep
this somewhere cool and dry" is far less of an imposition than "Hide this
forever. It has all my personal email on it".
I think GPG encrypting individual files would provide both encryption and
checksum. Is there anything wrong with that idea? And has anyone seen a tool
to do this? (I could write a script to do it if had to, but I'm reinventing
other wheels.)
--
Glyn Webster ~ Simplicity Himself. ~ http://tiddly-pom.com
Hi Gun,
I've CC'd this back to the WLUG mailing list where everyone else can
help too.
> I am going well with Linux. I have been learning basic commands and these
> past few days how to use the 'info' command.
> I have a network problem with my linux box. It is not on the nw. 'route'
> shows:
> eth0 192.168.2.0
> eth1 192.168.1.0
> subnet 255.255.225.0 for both
> eth0 connects to the adsl router with ip add. 192.168.1.1
> eth1 connects to the switch/hub.
> The 2 other workstations are Windows XP with ip add.
> 192.168.1.4 and 192.168.1.3.
> I think the problem is with eth0 being 192.168.2.0 when it should be
> 192.168.1.2. If this is the case, how do I change the eth0 address.
> Is this clear enough? Any help you can offer would be much appreciated.
Assuming you're running Red Hat or Mandrake, try poking around
/etc/sysconfig/network. There's a ifcfg-eth0 file in there that will
contain all the parameters for your networking, that is loaded at boot
time. If you change it, you can reload networking with something like
'/etc/init.d/networking restart' or 'service network restart' - have a
look in the /etc/init.d dir, poke around, Google, see what you can find.
Otherwise, you can 'manually' reconfigure an interface with ifconfig;
# ifconfig eth0 192.168.1.2 netmask 255.255.255.0
You probably shouldn't, however, have this setup. If your ADSL router
is a router, and connects into your switch, you only need one network
card, which connects into the switch as well. After you get this
configuration going, you can look at doing trickier stuff. You may
want, for ease of configuration, to use two different subnets if you're
going to have a "router->linux box" and a "linux box->windows" LAN.
If you have any more questions, you might like to start with RUTE's
networking section at http://www.icon.co.za/~psheer/book/node28.html.gz.
Craig
