moxie0 / Convergence

An agile, distributed, and secure alternative to the Certificate Authority system.
http://convergence.io
621 stars 108 forks source link

firefox sync convergenze #30

Closed almark closed 12 years ago

almark commented 13 years ago

when convergence is enabled firefox 6.0.1 sync gives this message, sync encountered an error while syncing: Unknown error. Sync will automatically retry this action

Macil commented 13 years ago

I've been getting this error occasionally. Seems like it doesn't happen when I disable the Convergence plugin.

Lcstyle commented 13 years ago

@moxie0 issue is reproduced on firefox 7.

ewanm89 commented 13 years ago

Was convergence enabled when setting up sync in the first place? As I seem to have it working with convergence now, but it's not clear how or why. The issue is in agreeing the symmetric keys to actually use for the sync. This might be related to the NSS key generation issue.

almark commented 13 years ago

No convergence wasn't enabled when setting sync up, I'm using sync and earlier incarnations way before convergence appeared...

almark commented 13 years ago

Oops closed the issue accidentally...

almark commented 13 years ago

OK, de / re installed firefox 6 installed convergence and THEN enabled sync again, waiting for sync errors, I'll let you know what happens.

Lcstyle commented 13 years ago

For me it (convergence) was (enabled during setup of sync). Mind you I had already established sync on other browsers and my method for setting up sync is to copy my sync key by bypassing the initial screen and entering my sync acct username and pw. Out of curiosity, @moxie0 does convergence set itself up as a proxy in the proxy settings? If so, how would one capture a header trace using fiddler? I am assuming that there would be no way to chain another mitm proxy like fiddler to convergence. This maybe something we should consider adding in order that we might be able to study what convergence is doing.

almark commented 13 years ago

No luck, again sync errors

moxie0 commented 13 years ago

I don't use sync, but perhaps it's using a pinned certificate, like FF update was? Does it fail every time there's something new to sync, or just occasionally?

ewanm89 commented 13 years ago

No, it has problems with own sync servers (weave) too and no information on a pinned certificate anywhere.

mutantmonkey commented 12 years ago

Here's a copy of the Firefox Sync log after a failure with Convergence on; it appears the POST request to sync bookmarks is failing, but for some reason the GET requests are working fine. It doesn't look like there's a pinned certificate at all.

1319402164780   Sync.SyncScheduler  DEBUG   Global Score threshold hit, triggering sync.
1319402164780   Sync.Service    INFO    Starting sync at 2011-10-23 16:36:04
1319402164781   Sync.SyncScheduler  DEBUG   Clearing sync triggers.
1319402164781   Sync.Service    INFO    In sync().
1319402165365   Sync.Resource   DEBUG   mesg: GET success 200 https://scl2-sync405.services.mozilla.com/1.1/mutantmonkey/info/collections
1319402165365   Sync.Resource   DEBUG   GET success 200 https://scl2-sync405.services.mozilla.com/1.1/mutantmonkey/info/collections
1319402165365   Sync.Service    DEBUG   Fetching global metadata record
1319402165365   Sync.Service    DEBUG   Weave Version: 1.10.0 Local Storage: 5 Remote Storage: 5
1319402165365   Sync.Service    INFO    Sync key is up-to-date: no need to upgrade.
1319402165366   Sync.Service    DEBUG   Fetching and verifying -- or generating -- symmetric keys.
1319402165366   Sync.Service    INFO    Testing info/collections: {"bookmarks":1319380900.57,"meta":1317863967.73,"crypto":1318255449.67,"clients":1319177550.29}
1319402165366   Sync.CollectionKeys INFO    Testing for updateNeeded. Last modified: 1318255449.67
1319402165366   Sync.Service    DEBUG   Refreshing client list.
1319402165366   Sync.Engine.Clients INFO    0 outgoing items pre-reconciliation
1319402165366   Sync.Engine.Clients INFO    Records: 0 applied, 0 failed to apply, 0 newly failed to apply, 0 reconciled.
1319402165367   Sync.Service    INFO    Updating enabled engines: 2 clients.
1319402165367   Sync.Engine.Bookmarks   INFO    2 outgoing items pre-reconciliation
1319402165368   Sync.Engine.Bookmarks   INFO    Records: 0 applied, 0 failed to apply, 0 newly failed to apply, 0 reconciled.
1319402172401   Sync.Engine.Bookmarks   INFO    Uploading all of 2 records
1319402172402   Sync.Collection DEBUG   POST Length: 30513
1319402177773   Sync.SyncScheduler  DEBUG   Global Score threshold hit, triggering sync.
1319402177775   Sync.Service    INFO    Starting sync at 2011-10-23 16:36:17
1319402177775   Sync.Service    DEBUG   Exception: Could not acquire lock. Label: "service.js: sync". No traceback available
1319402177775   Sync.Service    INFO    Cannot start sync: already syncing?
1319402199305   Sync.SyncScheduler  DEBUG   Global Score threshold hit, triggering sync.
1319402199603   Sync.Service    INFO    Starting sync at 2011-10-23 16:36:39
1319402199603   Sync.Service    DEBUG   Exception: Could not acquire lock. Label: "service.js: sync". No traceback available
1319402199603   Sync.Service    INFO    Cannot start sync: already syncing?
1319402199791   Sync.SyncScheduler  DEBUG   Global Score threshold hit, triggering sync.
1319402199805   Sync.Service    INFO    Starting sync at 2011-10-23 16:36:39
1319402199805   Sync.Service    DEBUG   Exception: Could not acquire lock. Label: "service.js: sync". No traceback available
1319402199805   Sync.Service    INFO    Cannot start sync: already syncing?
1319402253317   Sync.SyncScheduler  DEBUG   Global Score threshold hit, triggering sync.
1319402253322   Sync.Service    INFO    Starting sync at 2011-10-23 16:37:33
1319402253322   Sync.Service    DEBUG   Exception: Could not acquire lock. Label: "service.js: sync". No traceback available
1319402253322   Sync.Service    INFO    Cannot start sync: already syncing?
1319402253630   Sync.SyncScheduler  DEBUG   Global Score threshold hit, triggering sync.
1319402253630   Sync.Service    INFO    Starting sync at 2011-10-23 16:37:33
1319402253631   Sync.Service    DEBUG   Exception: Could not acquire lock. Label: "service.js: sync". No traceback available
1319402253631   Sync.Service    INFO    Cannot start sync: already syncing?
1319402255188   Sync.Collection DEBUG   mesg: POST success 200 https://scl2-sync405.services.mozilla.com/1.1/mutantmonkey/storage/bookmarks
1319402255188   Sync.Collection DEBUG   POST success 200 https://scl2-sync405.services.mozilla.com/1.1/mutantmonkey/storage/bookmarks
1319402255188   Sync.Service    DEBUG   bookmarks failed: resp.obj is null JS Stack trace: ("all")@engines.js:1005 < innerBind("all")@util.js:1159 < SyncEngine__uploadOutgoing()@engines.js:1041 < SyncEngine__sync()@engines.js:1092 < wrappedSync(null)@bookmarks.js:257 < _sync()@bookmarks.js:263 < WrappedNotify()@util.js:164 < Engine_sync()@engines.js:399 < WeaveSvc__syncEngine([object Object])@service.js:1617 < ()@service.js:1509 < WrappedNotify()@util.js:164 < WrappedLock()@util.js:132 < _lockedSync()@service.js:1415 < ()@service.js:1406 < WrappedCatch()@util.js:106 < sync()@service.js:1394
moxie0 commented 12 years ago

It's possible that this issue is fixed as of 0bb44f591c577913fc28d8f8b113d88329293bb9 if anyone could confirm.

almark commented 12 years ago

I think it's fixed now.