[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] symmetric vs. key
From: |
Kenneth Loafman |
Subject: |
Re: [Duplicity-talk] symmetric vs. key |
Date: |
Tue, 14 Apr 2009 14:30:03 -0500 |
User-agent: |
Thunderbird 2.0.0.21 (X11/20090318) |
If you want to make an announcement, send an email to
address@hidden The list is moderated and I'll have to
approve it, so wait a bit. Once its approved, it's automatically sent
to this list (duplicity-talk) as well.
...Ken
address@hidden wrote:
> I'd just sum up our conversation on the topic and add some juicy links
> or text from gpg docs.
> Eventually ftplicity users will benefit from the same know how , so why
> not putting it to the root...
>
> I'll do it when I find some time... inbetween the new ftplicity 1.4.2
> supporting symmetric encryption will be released. How did that
> announcement list thing work again?
>
> ...ede
> --
>> That would be very helpful. I'm open to any help that I can get.
>>
>> ...Thanks,
>> ...Ken
>>
>> address@hidden wrote:
>>
>>> Good point ... thanks Georg.
>>>
>>> Maybe we should phrase a Mini-Howto for the Website. Or even better the
>>> online help, similar to the chapter TIME, some chapter KEYS vs.
>>> PASSPHRASE.
>>> @ken: would you like that?
>>>
>>> ..ede
>>>
>>>>> Hi all,
>>>>>
>>>>> I am asking myself the pro's and con's of using symmetric encryption
>>>>> versus the use of keys with duplicity.
>>>>>
>>>>>
>>>> I am using duplicity with keys. In fact this is the main use of my GPG
>>>> keys. ;-)
>>>>
>>>> The nice thing about asymetric encryption is that - as long as you
>>>> don't
>>>> decrypt you don't need to store or pass a passphrase at all. So I
>>>> can use
>>>> the same public key for multiple machines and even on that machines I
>>>> don't really trust.
>>>>
>>>> Of course when you want to restore you need to provide it.
>>>>
>>>> Unfourtunately with current versions up from 0.5.12 duplicity also asks
>>>> during normal incremental backups for the private key, but this can be
>>>> fixed when the archive directory holds the hash of the remote manifest
>>>> (see recent thread on "Unnecessarily asking for passphrase on
>>>> incremental
>>>> backup").
>>>>
>>>>
>>>> Regards
>>>> Georg
>>>>
>>>>
>>>> _______________________________________________
>>>> Duplicity-talk mailing list
>>>> address@hidden
>>>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>>>
>>>
>>> _______________________________________________
>>> Duplicity-talk mailing list
>>> address@hidden
>>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>>
>>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
signature.asc
Description: OpenPGP digital signature