Re: [Duplicity-talk] Ubuntu One backend

[Paul Barker]

Hi again,

I'm very busy at the minute so will only occasionally get time to work
on a new Ubuntu One backend for Duplicity. However I do have some
initial code written which I should have time to test later this
weekend. It currently picks up the oauth keys from environment variables
(U1_CONSUMER_KEY, etc). This requires the login to be handled externally
and the oauth keys stored, but this needs to be reviewed. I'll send the
code once I've tested it and added error handling.

Looking at Ubuntu One itself, the recommended practice seems to be to
log in once and store the oauth keys rather than logging in with
username and password for every access. Repeated logins do create extra
oauth keys which are stored on the Ubuntu One server, which is less than
ideal as it may confuse a user who wants to empty out some old unused
sessions. I'm not sure how to fit this type of behavior into Duplicity
as you'd need to provide a username and password on the initial run and
then cache the oauth keys somewhere for future use. The alternative is
to have a separate login command which then stores the oauth keys. Any
advice on how to make this fit in well with the normal usage pattern of
Duplicity would be greatly appreciated.

Thanks,

Paul Barker
address@hidden

On Sun, 24 Jun 2012 22:31:55 -0400, Michael Terry <address@hidden>
wrote:
> Hello!  I wrote the current U1 backend.  I was mostly interested in
> having a version that ran under X (for Deja Dup's purposes), and using
> GNOME bits was easiest.
> 
> I'd certainly be interested in having a version that doesn't rely on
> X/DBus.  I think email would be fine.  I'd be happy to help review
> such a backend.
> 
> -mt
> 
> On 24 June 2012 16:32, Paul Barker <address@hidden> wrote:
>> Hi all,
>>
>> I'm looking to backup a server to Ubuntu One using Duplicity and so I've
>> taken a look at the backend code for U1. This seems to depend on DBUS, Gnome
>> Keyring and a bunch of other stuff which won't be running on a headless
>> server. Looking at the standard python-ubuntuone code, I'm gathering that
>> the expectation is that this is ran while you're logged into an X session.
>>
>> As a quick weekend project I decided to write a command line Ubuntu One
>> client which didn't depend on any of this - it talks directly to the U1 REST
>> API using built in python libraries and one external library: python-oauth2.
>> That's a requirement to properly authenticate. This now seems to work and I
>> can use this client to get, put and list files. I've put the project up at
>> https://bitbucket.org/elprb2/u1c
>>
>> So my question is, would you be interested in replacing the Ubuntu One
>> backend with something simpler? Looks like I can edit my code a bit and use
>> it to implement a Duplicity backend module without massive difficulties. I
>> tend to license my code under an MIT license but am happy to put this under
>> GPL. I've also never used bazaar version control system so if possible I'd
>> just like to write the backend and email it to you. What's your thoughts on
>> this?
>>
>> Thanks,
>>
>> --
>>
>> Paul Barker
>> address@hidden
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk