Closed
Bug 289817
Opened 20 years ago
Closed 20 years ago
ssltap creates cert files containing garbage
Categories
(NSS :: Tools, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
3.10
People
(Reporter: nelson, Assigned: nelson)
Details
Attachments
(1 file)
1.16 KB,
patch
|
julien.pierre
:
review+
wtc
:
superreview+
|
Details | Diff | Splinter Review |
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.
Assignee | ||
Comment 1•20 years ago
|
||
The obvious fix
Attachment #180309 -
Flags: review?(julien.pierre.bugs)
Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → 3.10
Updated•20 years ago
|
Attachment #180309 -
Flags: review?(julien.pierre.bugs) → review+
Assignee | ||
Comment 2•20 years ago
|
||
Checking in ssltap.c; new revision: 1.6; previous revision: 1.5
Thanks for the review.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Attachment #180309 -
Flags: superreview+
You need to log in
before you can comment on or make changes to this bug.
Description
•