Re: [Duplicity-talk] Duplicity + asymmetric encryption

[edgar . soldin]

On August 9, 2015 12:39:44 AM GMT+02:00, "Marko Božiković" <address@hidden> 
wrote:
>On 08.08.2015. 21:22, address@hidden wrote:
>> 
>> 
>> On August 8, 2015 9:41:21 PM GMT+02:00, "Marko Božiković"
><address@hidden> wrote:
>>> On 03.08.2015. 3:31, address@hidden wrote:
>>>>
>>>>
>>>> probably 
>>>>  https://sourceforge.net/p/ftplicity/feature-requests/36/
>>>>
>>>> try setting --use-agent manually in conf.
>>>>
>>>> ..ede/duply.net
>>>
>>> Hi,
>>>
>>> Does this mean that it's a duply issue? Will duplicity still create
>a
>>> session
>>> key when asymmetric gpg encryption is used?
>>>
>> 
>> more a duplicity/gpg2.1 issue because the new gpg _always_ uses the
>agent.
>> 
>> what do you mean w/ session key creation?
>
>Session key is a key used to actually encrypt the message in GnuPG
>using a
>symmetric crypto algorithm (e.g. AES256) and then the key itself is
>encrypted
>using the public key of the recepient. A new session key is generated
>for each
>message/file.

well, yeah thats how symmetric pgp works

>I got confused about the error output from duply/duplicity and some of
>the
>comments in duply's config files 

which in particular? there might be room for improvement..

>and thought that the passphrase being
>asked
>is actually used as the session key, but as far as I can tell, there's
>no way
>to specify a session key when encrypting with GnuPG - it is always
>generated.

right because we use gpg for crypto

>
>Don't mind me :)

done ;).. ede/duply.net