568216 - Cannot use a different port for the same keypair.

Status: RESOLVED FIXED

(Firefox :: Sync, defect)

Description

[Peter J. Krum]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: 1.0

in order to get get sync to work when using a non standard ssl port i had to edit cef.php.

i changed:

$this->data['extension']['request'] = 'https://' . $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'];

to 

$this->data['extension']['request'] = 'https://' . $_SERVER['HTTP_HOST'] . 'Port#Here' . $_SERVER['REQUEST_URI'];

it should detect what port your using there.

Keep up the good work--Thanks,
Peter

Reproducible: Always

Comment 1

[Peter J. Krum]

The web server is Ubuntu 10.04 w/ apache if that matters

Comment 2

[Peter J. Krum]

ok there is an issue but my "fix" didn't help.  Thought it was working but i guess not.

Comment 3

[Peter J. Krum]

2010-05-26 12:23:12	Service.Main         DEBUG	Weave Version: 1.3b7 Local Storage: 2 Remote Storage: 2
2010-05-26 12:23:33	PrivKeyManager       DEBUG	Failed to import record: NS_ERROR_NET_TIMEOUT JS Stack trace: Channel_onStopRequest([object XPCWrappedNative_NoHelper],null,2152398862)@resource.js:333 < Res__request(...)@resource.js:208 < Res_get()@resource.js:271 < RecordMgr_import([object XPCWrappedNative_NoHelper])@wbo.js:119 < RecordMgr_get([object XPCWrappedNative_NoHelper])@wbo.js:142 < WeaveSvc__remoteSetup()@service.js:897 < ()@service.js:1216 < WrappedNotify()@util.js:114 < WrappedLock()@util.js:86 < WrappedCatch()@util.js:65 < sync()@service.js:1166 < (6)@sync.js:336
2010-05-26 12:23:33	Service.Main         DEBUG	Could not get private key
2010-05-26 12:23:33	Service.Main         WARN	Couldn't download keys from server, aborting sync
2010-05-26 12:23:33	Service.Main         DEBUG	PubKey HTTP status: 200
2010-05-26 12:23:33	Service.Main         DEBUG	PrivKey HTTP status: undefined
2010-05-26 12:23:33	Service.Main         DEBUG	Exception: aborting sync, remote setup failed No traceback available


also wireshark trace show it trying to connect to 443 even thought i have set it to use another port in about:config.

Comment 4

[Peter J. Krum]

here is the problem: 

GET success 200 https://xxx.com/1.0/xxx/storage/keys/privkey
                               ^ no port #

Comment 5

[Peter J. Krum]

Also: 

GET success 200 https://xxx.com/1.0/XXX/storage/crypto/clients
                               ^ no port #

Comment 6

[Mike Connor [:mconnor]]

did you enter the port when you entered the custom server URL.

Comment 7

[Peter J. Krum]

originally no--i then set extensions.weave.clusterURL and extensions.weave.serverURL are to "https://xxx.com:4443/" through about:config. 

Let me know if i there is any other places i need to have the port.

Comment 8

[Mike Connor [:mconnor]]

if you do that + restart the browser, it should be okay... can you paste a full log (or email if, if you're worried about posting it publicly)?

Comment 9

[Peter J. Krum]

email sent!

I am hosting this over my DSL connection so i can't use 443 b/c verizon blocks it.  Anyway attached is the log that i see when i am not at my house. To test things i VPN-ed to my home network and ran a sync.  That's how i could see that it was connecting to the urls above with out the :4443 suffix.  All the other connections look to have the port number in them.

Thanks for the help!
~Peter

Comment 10

[Mike Connor [:mconnor]]

So we cache the URL of the privkey in the pubkey, so using different ports to access the same keypair doesn't work.  Not sure how much we can do here.

Comment 11

[Mike Connor [:mconnor]]

There was talk of using a relative URL to better enable migration.  Probably would fix this, not sure if there's a bug yet.

Comment 12

[Philipp von Weitershausen [:philikon]]

We now use relative URIs for the crypto records.