Let's stop migrating the Windows/IE SSL configuration (whether SSL 3.0 is enabled and whether TLS 1.0 is enabled). We have good defaults in Firefox and we have compatibility logic that allows us to handle pretty much every server without requiring any configuration. (Every browser does.) There will be cases where we support newer versions of TLS than what the operating system supports (e.g. we will support TLS 1.1 when Windows XP doesn't), and it doesn't make sense to disable our TLS 1.1 support on Windows XP. It also doesn't make sense to maintain this code when our defaults work fine.
Created attachment 603546 [details] [diff] [review] Stop migrating SSL version options from Windows/IE Felipe, I think we had already talked about this before. It would be useful to do this sooner than later, because it will simply adding TLS 1.1 support to Firefox.
Comment on attachment 603546 [details] [diff] [review] Stop migrating SSL version options from Windows/IE This is fine. I've already removed this from the new migrator, but that most likely won't land for Fx 13, so if you want to get it sooner than we should take the patch. Do you also need to remove these 2 settings: http://mxr.mozilla.org/mozilla-central/source/browser/components/migration/src/nsIEProfileMigrator.cpp#379 ? While we are at it, if you want to remove the CopyProxyPreferences too, go ahead. I've also removed it from the new migrator
Attachment #603546 - Flags: feedback?(felipc) → feedback+
Comment on attachment 603546 [details] [diff] [review] Stop migrating SSL version options from Windows/IE Na-na, na-na-na-na, hey-hey, goodbye. I wouldn't worry too much about cleaning up the current migrator, hopefully we can get the new one landed for the next release. Much working going on in migratorland.
Attachment #603546 - Flags: review?(dolske) → review+
Target Milestone: --- → Firefox 14
Component: Bookmarks & History → Migration
QA Contact: bookmarks → migration
we don't import these settings anymore.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.