Open Bug 482471 Opened 16 years ago Updated 1 year ago

Vfychain doesn't find alternative cert path if one is not accessible.

Categories

(NSS :: Libraries, enhancement, P5)

enhancement

Tracking

(Not tracked)

People

(Reporter: slavomir.katuscak+mozilla, Unassigned)

Details

Attachments

(2 files)

Scenarion: RootCA->CA1->Bridge->EE1 ->CA2-^ Both CA's are signed by Root CA, CA2 has newer issuing time then CA1 and, Bridge signed by both CA's using AIA, for CA1 AIA path is correct, for CA2 is pointing to non-existing file. When trying to check EE1 certificate, vfychain returns unpredictable results, sometimes if passes, sometimes fails.
Attached file Scenario file.
Scenario file to reproduce. For test copy to nss/tests/chains/scenarios and set nss/tests/chains/scenarios/scenarios to test only this file. Results are unpredictable, sometimes passes sometimes fails. Looks like algorithm set randomly which path to choose (which CA use to verify patch) and if one with invalid AIA is chosen, it doesn't try second one.
Slavo, please provide the full vfyserv commands for a sample run that fails and for a sample run that succeeds.
Attached file Logs from testing.
I'm attaching logs from 2 runs of the same tests including all commands + input data, once it passed, once it failed.
This bug report contains neither a vfychain command or the sample certs with which to reproduce it. Consequently, one cannot know if it is a libraries bug, or a tools bug, and if it is high priority or low. So, I am removing the target milestone. If it's still in this state at the end of April, I will resolve it as incomplete.
Target Milestone: 3.12.3 → ---

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: alvolkov.bgs → nobody
Severity: normal → S3
Severity: S3 → N/A
Type: defect → enhancement
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: