Closed Bug 80789 Opened 23 years ago Closed 23 years ago

change hashing algorithm for cfg file

Categories

(SeaMonkey :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: chipc, Assigned: chipc)

Details

(Whiteboard: PDT+)

Attachments

(1 file)

Change the hashing algorithm for the cfg file from the current +/- 7 to 
intentially break from 4.x cfg hashed files.
Status: UNCONFIRMED → NEW
Ever confirmed: true
eClient issue, assigning QA to trix and adding dean pinckert to Cc.
QA Contact: doronr → trix
Would not this best be accomplished via a versioning scheme?
That way you can selectively handle compatability issues
between versions and not just fail.  I the need arose, you
could even give a conversion hint.  Just one man's opinion. 
Status: NEW → ASSIGNED
Whiteboard: requesting r= sr=
I have to agree with the versioning thing. There are a finite number of prime
numbers between 0 and 255...
but sr=alecf anyway.
Comment on attachment 49811 [details] [diff] [review]
changes algorith from 7 to 13 to intentionally break existing cfg files

:) Let's just hope we don't have to change it everytime we ship a new release. r=bnesse.
Attachment #49811 - Flags: review+
Whiteboard: requesting r= sr=
Mitesh checked the patch into the tree for chipc
Whiteboard: PDT
Chip, apparently this wasn't checked in by Mitesh.  This needs to get checked in
to test the new hash tool. Grega, can we get PDT approval for this, this is
vital for testing out the factory product.
Approved.  PDT+ added
Whiteboard: PDT → PDT+
Checked into branch.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Keywords: vbranch
Resolution: --- → FIXED
this has been verified on the branch and trunk on all supported platforms, new
hash tool hashes CFG with new algorithm, browser now reads new algorithm.
Status: RESOLVED → VERIFIED
QA Contact: trix → rvelasco
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: