weave 1.0 - PrivKeyManager fails for another user's private key...?

0 views
Skip to first unread message

Leho Kraav

unread,
Dec 4, 2009, 3:02:45 AM12/4/09
to Mozilla Labs Weave Server Users
server is hg tip from Nov 30, client is 1.0b2 addon.

User anna-maria tries to do first sync. For some totally unknown
reason PrivKeyManager starts looking at another user's (leho) private
key, instead of anna-maria's and obviously fails. User leho is in the
middle of a long sync session on another computer, but I don't see how
this should affect anna-maria in any way. Log below. What's going on?

2009-12-04 09:43:56 Service.Main DEBUG Next sync in
6370 sec.
2009-12-04 09:43:56 Service.Main DEBUG Event:
weave:service:login:finish
2009-12-04 09:52:04 Service.Main DEBUG Event:
weave:service:sync:start
2009-12-04 09:52:04 Service.Main DEBUG Event:
weave:service:wipe-remote:start
2009-12-04 09:52:04 Service.Main INFO Sending
clients: wipeAll(); Delete all client data for all engines
2009-12-04 09:52:04 Service.Main DEBUG Event:
weave:service:wipe-remote:finish
2009-12-04 09:52:04 RecordMgr TRACE Importing
record: https://myserver/1.0/anna-maria/storage/meta/global
2009-12-04 09:52:04 Net.Resource DEBUG GET request
for https://myserver/1.0/anna-maria/storage/meta/global
2009-12-04 09:52:04 Net.Resource DEBUG GET success:
200
2009-12-04 09:52:04 Service.Main DEBUG Weave Version:
1.0b2 Compatible: 1.0b2pre1 Remote: 1.0b2
2009-12-04 09:52:04 PrivKeyManager TRACE Importing
record: https://myserver/1.0/leho/storage/keys/privkey
2009-12-04 09:52:04 Net.Resource DEBUG GET request
for https://myserver/1.0/leho/storage/keys/privkey
2009-12-04 09:52:04 Net.Resource DEBUG GET fail: 401
2009-12-04 09:52:04 Service.Main DEBUG Could not get
private key
2009-12-04 09:52:04 Service.Main WARN Couldn't
download keys from server, aborting sync
2009-12-04 09:52:04 Service.Main DEBUG PubKey HTTP
status: 200
2009-12-04 09:52:04 Service.Main DEBUG PrivKey HTTP
status: 401
2009-12-04 09:52:04 Service.Main DEBUG Event:
weave:service:sync:error
2009-12-04 09:52:04 Service.Main DEBUG Next sync in
8177 sec.
2009-12-04 09:52:04 Service.Main CONFIG Starting
backoff, next sync at:Fri Dec 04 2009 12:08:21 GMT+0200 (EET)
2009-12-04 09:52:04 Service.Main DEBUG Exception:
aborting sync, remote setup failed No traceback available

Leho Kraav

unread,
Dec 4, 2009, 3:15:45 AM12/4/09
to Mozilla Labs Weave Server Users
ok inspecting the /global GET request reveals that it has exactly the
same syncID for both users. how does that happen?

On 4 dets, 10:02, Leho Kraav <l...@kraav.com> wrote:
> server is hg tip from Nov 30, client is 1.0b2 addon.
>
> User anna-maria tries to do first sync. For some totally unknown
> reason PrivKeyManager starts looking at another user's (leho) private
> key, instead of anna-maria's and obviously fails. User leho is in the
> middle of a long sync session on another computer, but I don't see how
> this should affect anna-maria in any way. Log below. What's going on?
>
> 2009-12-04 09:52:04     RecordMgr            TRACE      Importing
> record:https://myserver/1.0/anna-maria/storage/meta/global
> 2009-12-04 09:52:04     Net.Resource         DEBUG      GET request
> forhttps://myserver/1.0/anna-maria/storage/meta/global

Leho Kraav

unread,
Dec 4, 2009, 3:20:25 AM12/4/09
to Mozilla Labs Weave Server Users
default_constants.php:

define('WEAVE_AUTH_ENGINE', 'none');
define('WEAVE_STORAGE_ENGINE', 'mysql');
define('WEAVE_MYSQL_STORE_READ_HOST', 'localhost');
define('WEAVE_MYSQL_STORE_READ_DB', 'weaveserver');

Leho Kraav

unread,
Dec 14, 2009, 3:54:12 AM12/14/09
to Mozilla Labs Weave Server Users
the fact that this gets no replies means that everyone else running
weave server for many users are not seeing this private key mixup
problem?

Leho Kraav

unread,
Dec 14, 2009, 4:12:25 AM12/14/09
to Mozilla Labs Weave Server Users
perhaps i'm misunderstanding something - is the weave addon 'secret
passphrase' the same for all users? currently it has been logical to
me that every user has their on 'secret passphrase'.

Toby Elliott

unread,
Dec 14, 2009, 12:27:59 PM12/14/09
to mozilla-labs-we...@googlegroups.com
Secret passphrases are per-user and distinct, yes.

This sounds like a client bug, and you might want to post on that list to see if anyone has experienced this issue.

Regards,
Toby
Reply all
Reply to author
Forward
0 new messages