Closed Bug 56316 Opened 25 years ago Closed 24 years ago

Backed up cert is 0 bytes

Categories

(Core :: Security: PSM, defect, P3)

1.0 Branch
x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: junruh, Assigned: ddrinan0264)

References

()

Details

(Whiteboard: [rtm-])

1.) Visit the in-house url above, and apply for a dual cert- forced backup. 2.) When asked to backup the cert, do so. What happens: I am only asked to backup one cert instead of two, and the backed up cert has 0 bytes, thus cannot be restored.
rtm
Assignee: lord → ddrinan
Keywords: rtm
This seems serious, can you work on it? If so, please mark [rtm need info] in the whiteboard.
Whiteboard: [need info]
This seems to be a problem with the components PSM picks up at run time. If I launch PSM from a DOS prompt, then everything works just fine. It seems the PATH variable makes it so that PSM uses the components from Mozilla's install and PSM doesn't function correctly with thos components. This will be a tricky one to fix. junruh: Does "Backup All" work for you?
Whiteboard: [need info] → [rtm need info]
junruh: It works on some machines and not others over here. Are you still seeing this with the latest dailies?
Commercial trunk 102004 build. ON Win98 I am only asked to backup once, and the backup can be restored, and is a dual cert. On WinNT, the backed up cert is 0 bytes, and cannot be restored.
Version: 1.3 → 1.4
First of all , I am not sure if we should test on the trunk. Are we sure that the trunk is the exact duplication of the branch. I don't think that will be the case, otherwise why would we have two trees. Branch is what is going to be RTM, so we should file bugs only if they exist on the branch. So I tested the forced backup on dual certs on winNT with the 20001219-MN6 build. The backup window comes up only once instead of twice as john suggested. That is a bug. The backup is not 0 bytes . I got like 9kb. I can also restore the cert. The normal backup for existing certs and also single certs I get work fine and they are not 0bytes. So it is WorksForMe.
It's OK to test the trunk, as long as it is stated in the bug, and the status of the bug is not changed until branch builds are tested. I'll test on the next branch build later today. Keep in mind that I found this bug on a branch build.
is the bug that backup is 0 bytes or that there is only one backup window. Because I cannot reproduce the 0 byte bug , but the backup window comes up only once. I will say test the trunk , since the branch comes out after the trunk builds come out. And once the branch comes out test that and if the bug is there (which will mostly be the case) file it referencing to the branch. There could be factors in the trunk which may not be reflected in the branch. This will hopefully reduce the confusion for engineers and they will need to pick up only the branch. my $0.02 worth. :-)
We made forced dual cert backup put both certs in one file because of this bug. http://bugzilla.mozilla.org/show_bug.cgi?id=48071
cool, nice . Ok so in win98, the backup window does not paint fully for me. It remains blank and the navigator window also remains blank. However when I click on the navigator window , it paints the success page , but the backup window still remains blank. I can kill the backup window and go to the SA and verify that the certs are imported into the SA.
WinNT commercial branch build. I'm still getting a 0 byte backup file as described in the original steps of the bug.
junruh: please try on a different NT machine to see if it we can figure out why it works on some and not on others.
I tried it with the WinNT machine in the lab, and I got a 0 byte backup file. The Win2000 machine backs up the dual cert properly, and it can be restored.
-> [rtm-]
Whiteboard: [rtm need info] → [rtm-]
One observation. When the backup fails, the 0 byte cert cannot be immediately deleted until Netscape 6 is closed. I get a sharing violation from WinNT.
Mass reassigning nitinp's bugs to me.
QA Contact: nitinp → junruh
nsbeta1
Keywords: nsbeta1
nsbeta1. Reproduced today on a Linux box.
junruh: is this still a problem?
This appears to be fixed with PSM 2.0.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm1.4 → 1.0 Branch
You need to log in before you can comment on or make changes to this bug.