10710 - Migrate 4.x netscape.cfg files

Status: VERIFIED DUPLICATE of bug 2828

(Core Graveyard :: Profile: BackEnd, defect, P3)

Description

[selmer (gone)]

If the MD5 algorithm used in 5.0 does not work when unhashing 4.x netscape.cfg
files, then they will need to be migrated to be hashed with the 5.0 version of
Md5 to work properly.

Comment 1

[varada]

dependant on bug #6350 -i.e. the MD5 hashing - hence moving target milestone to
M11

Comment 2

[varada]

The 4.x netscape.cfg contains user,default,lock as well as config prefs - the
config prefs dont exist in 5.x because the chrome cant be customised using prefs
so we should find a way to handle that.

Comment 3

[varada]

The .cfg doesnt have to be migrated since the new mozilla code for preferences
seems to handle the extraneous information regarding the config prefs. Leaving
the bug as assigned as it has to be decided whether the code that obscures the
input file and the hashed digest will be made public in mozilla.

Comment 4

[varada]

I suggest closing this bug since there doesnt seem to be the need for a tool to
migrate 4.x netscape.cfg files to the seamonkey browser. The code in mozilla
seems to handle the extraneous information and use the old .cfg files. I am
reassigning this bug to Neeti -
Neeti -if you feel that there is no other changes to be made to the code and
that it can handle the .cfg files - please close this bug

Comment 5

[neeti]

I agree that we do not need a tool to do special processing of the 4.x .cfg
files, but they still need to be migrated over to the new 5.0 profile, when
profile migration takes. I am reassigning this bug to dbragg.

Comment 6

[dbragg]

I need some clarification here.  The Netscape.cfg file was a "global" file to
all prefs was it not?  It sits in the program directory along with
netscape.exe.  If that's the case, it doesn't get migrated with a specific
profile since it doesn't exist in a specific profile.  Any other .cfg files that
may exist in the profile to be migrated will get migrated.

Accepting but I need that clarification.

Comment 7

[selmer (gone)]

Don, you're right about how the cfg file works.  This migration doesn't belong
within the profile migrator.  This really needs to be done by the installer
itself since we should have the netscape.cfg available to us by the time we
start the browser up.

Comment 8

[dbragg]

This is a duplicate of 2828 although the 2828 bug needed to have it's
description changed.  (which I just did)

*** This bug has been marked as a duplicate of 2828 ***

Comment 9

[leger]

Moving all Profile Manager bugs to new Profile Manager Backend component.
Profile Manager component to be deleted.