ubuntuone-users team mailing list archive
-
ubuntuone-users team
-
Mailing list archive
-
Message #00052
Re: Identifying Computers
-
To:
Steve Alexander <steve@xxxxxxxxxxxxx>
-
From:
Torsten Bronger <bronger@xxxxxxxxxxxxxxxxxxxxx>
-
Date:
Tue, 30 Jun 2009 15:59:14 +0200
-
Cc:
ubuntuone-users@xxxxxxxxxxxxxxxxxxx
-
Face:
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEWVTEMoFxP8/Pnw4Nn8 tqbbi3ju7eqxc2XlqJjz8u/LYySDAAACVElEQVR4nF2UMW/bMBCFqUEluokIUGf21i1xArTd ilZBM6pICGpMa0C2NiYuQXdrDBNlt0IGDOvf9h1JKUJv0MBPd+/ueEfW9mSPYrTZYk7GwvlK TOw8gradOjD67CLA+SmdkmVCnI2hLoUoGOOWDD6zAJoQqWA4k2QKLovkcUQUbo2svfdS6ihC HpBgOJeeTCohnpLHShQccfy+LL13iPU6gb8ACFTCbgM4S+ABkaTcl5FMwFrwAK6JEHiVwEkw Q+DqKoFB45BA+fk6gqeU7jH7T2M3Vl5wWSeArIpuaOIzgE8ABc6GJr4PoBxANna3yhizdcwK zcqKTQQHzTJ0fUv/o+3mkeUD0Bl6DXKT4bK41rwL4gCMfPKywg0ao60l0LQHC8AKm5fKMMtl xe33AJZGc5Ybacq6/u2MrIyKHq3VdNk197WTpnaVMqHyplUahXvHHe5wj9JtAs0XTfUpHvvl FB/AOyTvXRXBrbRym8AJoJY6d/KeSrdqkzTeKmp7ZaARJOynBLoTg3q1dTK03d7NU6i2R3yv f9yQhgvJRo++/wVQ5dJSUnYzHz2OAFJxW1Mo+3MCPoZJN94jKb17Af1FGPbaY6zVBDTHFdpr 7/e3tAZT0KwZtd7SzCu2eAHtEqFoo1CjnYKm0Rwu+N8pzf50E3DBQyzsE8veYHBGsEZTJDws bv+877shq+ah4FuPrYESRrfr5l30aJ8x8J6KKCztOYJFsBQFbZvUGa+w8+28Sxp4SzBYXEOJ Xo/iwyD+jd4LehyMDI8HSASXBKhA+TW9Tf4fSktOMtuPmUoAAAAASUVORK5CYII=
-
In-reply-to:
<4A4A1206.7040708@canonical.com>
-
Jabber-id:
torsten.bronger@xxxxxxxxxxxxxxxxxxxxx
-
Organization:
Phoenix Foundation
-
User-agent:
Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.94 (gnu/linux)
Hallöchen!
Steve Alexander writes:
> [...]
>
> I can look at this using the "Passwords and Encryption Keys"
> program, which is in this menu:
>
> Applications -> Accessories -> Passwords and Encryption Keys
>
> If I look under the "Passwords" tab and expand the "Passwords:
> login" part of the table, I can see a row that says
>
> UbuntuOne token for https://ubuntuone.com
>
> Right-clicking on that, and choosing "propertise", I can see the
> key. It's even possible to see the actual password. Mine is:
>
> oauth_token_secret=pHxxxxxxx...&oauth_token=XhXxxxxx...
>
> This token is what registers my account on this computer with
> Ubuntu One.
I have a remote machine registered with Ubuntu One. But if I call
"u1sync --action=sync", I get a traceback with some sort of key
error. I suspect that seahorse likes to get my permission that
u1sync gets the token. But this doesn't work through "ssh -X". Is
there a remedy?
Tschö,
Torsten.
--
Torsten Bronger, aquisgrana, europa vetus
Jabber ID: torsten.bronger@xxxxxxxxxxxxxxxxxxxxx
or http://bronger-jmp.appspot.com
Follow ups
References