Re: [Duplicity-talk] Scp calls

[Kenneth Loafman]

It's as secure as any ssh target, nothing is sent in the clear.  I don't
think openvpn would be any more secure.

...Ken

AJ Weber wrote:
> Hmm.  That seems like a lot of overhead, and I wonder if it increases
> the ability of hacking the target server (because the username and
> password are sent repeatedly)?
> 
> I wonder if I should setup an openvpn pipe and use straight FTP inside
> that instead?
> 
> -AJ
> 
> On Jan 2, 2010, at 8:10 PM, Kenneth Loafman <address@hidden> wrote:
> 
>> Unless you run the --asyncronous-upload option, it's just one connection
>> at a time, very serial.  With --async, it's 2 at a time.
>>
>> ...Ken
>>
>> AJ Weber wrote:
>>> I guess I could try to trace this, but figure someone might already
>>> know...
>>>
>>> When using scp URL for target, how many ssh or scp sessions are run?  Is
>>> it one per duplicity invocation, or closer to one per 25M archive file
>>> transferred (plus sig and other files)?
>>>
>>> I ask, because I might try to get fancy with firewall rules to protect
>>> the target server, and if it's one session, it'll be more
>>> straightforward to implement.
>>>
>>> Thanks!
>>> -AJ
>>>
>>>
>>> _______________________________________________
>>> 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