Closed
Bug 591520
Opened 14 years ago
Closed 12 years ago
Firefox Home 1.0.2 does not support custom servers with self-signed certs
Categories
(Cloud Services Graveyard :: Firefox Home, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: dwalkowski, Unassigned)
References
Details
No description provided.
Reporter | ||
Comment 1•14 years ago
|
||
Firefox Home 1.0.2 is too strict, and does not support https:// servers with self-signed certs
Summary: Firefox Homw 1.0.2 → Firefox Home 1.0.2 does not support custom servers with self-signed certs
Updated•14 years ago
|
Target Milestone: --- → Future
Example of website: https://fisheye.last.fm
Comment 4•14 years ago
|
||
(In reply to comment #3) > Example of website: > https://fisheye.last.fm Naoki, that should be a separate bug. This one is about the Custom Sync Server, not about sites shown in the built-in browser. Good catch though :-) I created https://bugzilla.mozilla.org/show_bug.cgi?id=609498
Comment 5•14 years ago
|
||
This should only be allowed during setup, not later, IMO. There's a similar bug for FxSync
Comment 6•14 years ago
|
||
I assume that means: we should ask for confirmation during setup and then silently accept that cert for all future sync sessions until the cert (id, hash, whatever) changes.
Comment 7•14 years ago
|
||
Yes, that's my thinking. Basically, like the SSH model (accept fingerprint, raise hell if that changes).
Comment 8•14 years ago
|
||
This will help web authors run their own servers and not have to purchase SSL licenses
Flags: blocking-fx-home1.1?
It seems I was able to work around this finally with the latest Firefox Home update. In the app's configuration "Settings > Firefox Home" I switched "Use Safari" to on. I had previously added my self signed CA to Mobile Safari. I also had to modify get_user_location() (using MySQL) to return 'https://example.com' so that the server would return a 200 result. After setting up my account, I then was able to switch "Use Safari" back to off.
Updated•14 years ago
|
Flags: blocking-fx-home1.1?
Comment 10•13 years ago
|
||
I'm also not able to get Firefox Home (1.1.1) working with my own weave Server. After set up the Server URL like https://example.de/weave/ I get the error: "Authentication failure (Communication to the Server (1) failed)" I translated the message. In german it is: "Anmeldung fehlgeschlagen (Kommunikation zum Server (1) fehlgeschlagen)" Is there any fix to get run the App with my own Server and set up the Settings like Joshua or something like that?
Comment 11•13 years ago
|
||
(In reply to comment #10) > I'm also not able to get Firefox Home (1.1.1) working with my own weave > Server. > After set up the Server URL like https://example.de/weave/ I get the error: > > "Authentication failure (Communication to the Server (1) failed)" > > I translated the message. In german it is: > > "Anmeldung fehlgeschlagen (Kommunikation zum Server (1) fehlgeschlagen)" > > Is there any fix to get run the App with my own Server and set up the > Settings like Joshua or something like that? Same thing here, bug I can add this : I can't see any connection from FFHome to my private server, it didn't even try to ask for something to my server (no entry in the apache log)
Comment 12•12 years ago
|
||
The Firefox Home project has been retired, and Mozilla will no longer invest in future work on this project [1]. All bugs related to Firefox Home are being mass resolved. For those interested in continuing work on this app, the source code for Firefox Home is available on Github [2]. [1] http://blog.mozilla.org/services/2012/08/31/retiring-firefox-home/ [2] https://github.com/mozilla-services/ios-sync-client
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Updated•5 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•