how to do that securely.
>
> Thanks
>
> Dan
After backing up the database, but before sending the backup to S3,
encrypt the file yourself, for example with gpg. Then you don't have
to use server side encryption. Of course, you will need to decrypt it
when you restore fro
On Tue, 2013-02-19 at 16:16 -0600, Matt Domsch wrote:
> On Tue, Feb 19, 2013 at 01:33:35PM -0600, Domsch, Matt wrote:
> > On Tue, Feb 19, 2013 at 12:27:22PM -0600, John Sauter wrote:
> > > In July-August of 2012 there was a discussion of the new meaning of the
> > >
be moved to a new qualifier for compatibility.
The URL for archive of the discussion is
<http://sourceforge.net/mailarchive/message.php?msg_id=29617785>.
Has my concern been addressed?
John Sauter (john_sau...@systemeyescomputerstore.com)
signature.asc
Description: This is a dig
On Tue, 2012-07-31 at 13:30 -0500, Matt Domsch wrote:
> On Fri, Jul 20, 2012 at 09:27:04AM -0500, Domsch, Matt wrote:
> > On Fri, Jul 20, 2012 at 07:06:33AM -0500, John Sauter wrote:
> > > Matt,
> > >
> > > When I first attempted to use your m
a worldwide fame
by being the main figure in such a prominent project (ok, overstating a
bit :)
>
>Hope to hear from you soon!
>
>Michal
I am tempted, but I must regretfully decline. In order to do a good job
of leading s3cmd, one must understand the code throughly, and I do not.
your new s3cmd if it had a
different version number than the s3cmd it is derived from.
John Sauter (john_sau...@systemeyescomputerstore.com)
signature.asc
Description: This is a digitally signed message part
--
L
files I wish to back up,
using this script:
#!/bin/bash
# Encrypt all the files in a directory.
# File: encrypt_files.sh Author: John Sauter, date: December 11, 2010
#
# One parameter: the directory containing the
# files to encrypt. Default is the current
# directory.
#
dir_name=${1:-".&q
