As ssltap is running, when it sees certificates going by, it copies them to files in the CWD with names cert.001, cert.002, ... Every time the program is started, it starts over at cert.001. When it opens the file for writing, it does not truncate the file, so if the file previously existed and was longer than the new data to be written, the result is a file that contains the new cert followed by the leftovers of the old cert. NSS programs that read certs from files all reject such a file. The solution is to truncate the file. Patch forthcoming.
Created attachment 180309 [details] [diff] [review] patch v1 The obvious fix
Attachment #180309 - Flags: review?(julien.pierre.bugs)
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → 3.10
Attachment #180309 - Flags: review?(julien.pierre.bugs) → review+
Checking in ssltap.c; new revision: 1.6; previous revision: 1.5 Thanks for the review.
Status: ASSIGNED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.