Closed Bug 18107 Opened 26 years ago Closed 26 years ago

[DOGFOOD] PSM files are installed in wrong place - psm doesn't start, can't visit https sites

Categories

(Core :: Security, defect, P3)

x86
Windows 98
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: junruh, Assigned: ssu0262)

References

Details

(Whiteboard: [PDT+])

Overview Description: The PSM folder is installed in wrong place Steps to Reproduce: 1) Install Mozilla with all options. 2) View the directory structure on the hard drive. Actual Results: The PSM folder is installed to Program Files\netscape\psm Expected Results: The PSM files should be installed to Program Files\Common Files\Netscape Shared\Security. Build Date & Platform Bug Found: 11/5 - Win98 Additional Builds and Platforms Tested On: Additional Information:
Summary: PSM files are installed in wrong place → [DOGFOOD] PSM files are installed in wrong place - psm doesn't start, can't visit https sites
this causes psm to to not be found when you hit a https site and you really don't know what to do to find it, or to get the https site to load. If by chance you know where to find psm.exe and you type that into the dialog psm.exe crashes on startup, (atleast it did for me.)
Assignee: dougt → ssu
I will look into the crash, but installation is ssu's bug. assign to him.
Blocks: 13785
Status: NEW → ASSIGNED
Since this has been reassigned to me, is the installation path problem really dogfood? It should be able to run from anywhere, correct? chofmann, can you file a bug against the crash problem and leave this bug as the installation bug?
Whiteboard: [PDT+]
Putting on PDT+ radar.
Target Milestone: M12
setting target milestone to M12.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
okay, the fix is finally checked in. It should appear in the next commercial build. Here's what it does (in the order listed) to determine the destination installation path: 1) look in the Netscape Registry for: /Netscape/Personal Security Manager/Program/psm.exe If it contains a path, use it as the default destination path 2) look in the Windows Registry for: key: HKEY_LOCAL_MACHINE\Software\Netscape\Personal Security Manager\Main name: Install Directory if it exists, use it as the default destination path. 3) look in the Windows Registry for: key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion name: CommonFilesDir (it should exist) and append "\\Netscape Shared\\Security" to it and use this as the default destination path. To clean up the Netscape Registry, do the following (or simply delete [windows dir]\nsreg.dat if you don't care about it): 1) run communicator 4.x and go to: http://slip/softupdate/BiggerRegToy.html 2) enter the following in the Subkey edit box field: version registry/netscape/personal security manager/program/psm.exe 3) click on the "Delete Node" button, and it's cleared for testing. I assume it's known how to clean the Windows Registry given the information here, so I won't go into it. Right now, the user logged in must have administrator privileges under NT (as discovered by Mark Welch under 4.x). I will investigate this to see if this can *not* be a requirement in 5.0.
*** Bug 17492 has been marked as a duplicate of this bug. ***
Status: RESOLVED → REOPENED
Reopening. As of 11/16, the psm folder is still created at the same level as Seamonkey. 1.) Delete any psm or security folders on the PC. 2.) Delete nsreg.dat, and mozregistry.dat. 3.) Delete the Seamonkey folder. 4.) Delete the Personal Security Manager key found at: HKEY_LOCAL_MACHINE\Software\Netscape\Personal Security Manager\Main 5.) Verify that HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\CommonFilesDir shows c:\Program Files\Common Files 6.) Install M11 (11/16) seamonkey32.exe Actual Results: The PSM folder is installed to Program Files\netscape\psm Expected Results: The PSM files should be installed to Program Files\Common Files\Netscape Shared\Security.
Resolution: FIXED → ---
Clearing FIXED resolution due to reopen.
Status: REOPENED → RESOLVED
Closed: 26 years ago26 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Fixed in the 11/16 M12 build.
Verified fixed.
No longer blocks: 13785
Bulk moving all Browser Security bugs to new Security: General component. The previous Security component for Browser will be deleted.
Component: Security → Security: General
You need to log in before you can comment on or make changes to this bug.