Closed Bug 37890 Opened 24 years ago Closed 24 years ago

program crashes after loading psm.exe

Categories

(Core Graveyard :: Security: UI, defect, P3)

1.0 Branch
x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: jimh, Assigned: norrisboyd)

References

()

Details

(Keywords: crash)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m16) Gecko/20000501
BuildID:    2000050111

When I try to use a secure website that requires that I enter a password, I'm
prompted by Mozilla to locate the file psm.exe. After I find it and it begins to
load, the browser freezes up and I have to use ctrl+alt+del to get out of it.

Reproducible: Always
Steps to Reproduce:
1.Go to website
2.Find password manager	
3.

Actual Results:  Mozilla freezes up.	

Expected Results:  Transfer to secure site which requires password
This appears to be working for me on the same build under Windows 2000. If the 
PSM is properly installed, you shouldn't be asked to locate psm.exe. Did you 
reinstall the PSM after installing this build? If not, reinstall it from 
http://docs.iplanet.com/docs/manuals/psm/psm-mozilla/index.html and try again.
unable to verify right now, but fixing up report as a crash

->Security:General for now, is this crypto?
Severity: major → critical
Component: Browser-General → Security: General
Keywords: crash
reassigning
Assignee: asadotzler → norris
QA Contact: jelwell → junruh
Win98SE
Build 50111

Did not crash for me and so far no crash in today's build. Will leave it up to 
someone else to mark "worksforme" tho
Worksforme. I cannot duplicate the problem.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Component: Security: General → Security: Crypto
Resolution: --- → WORKSFORME
Verified.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.