Open
Bug 412318
Opened 18 years ago
Updated 3 years ago
Verify that all pkix functions that return SECStatus set NSPR error code
Categories
(NSS :: Libraries, defect, P2)
Tracking
(Not tracked)
NEW
3.12.5
People
(Reporter: alvolkov.bgs, Unassigned)
Details
(Whiteboard: PKIX SUN_MUST_HAVE)
In review comments to bug 408434:
3. There are many pkix_pl_ functions (like the following one) that return a
SECStatus, but do not set any error code (e.g. don't call PORT_SetError).
How is the caller supposed to know what went wrong if they fail?
> SECStatus
> pkix_pl_HttpDefaultClient_CreateSessionFcn(
> const char *host,
> PRUint16 portnum,
> SEC_HTTP_SERVER_SESSION *pSession)
> {
> PKIX_Error *err = pkix_pl_HttpDefaultClient_CreateSession
> (host, portnum, pSession, plContext);
>
>- if (err == NULL) {
>- return SECSuccess;
>- } else {
>+ if (err) {
> PKIX_PL_Object_DecRef((PKIX_PL_Object *)err, plContext);
> return SECFailure;
> }
>+ return SECSuccess;
> }
Reporter | ||
Updated•18 years ago
|
Whiteboard: PKIX
Reporter | ||
Updated•17 years ago
|
Priority: -- → P2
Updated•17 years ago
|
Summary: Verify that all pkix functions that return SECStatus have a way to pass error code to theirs callers → Verify that all pkix functions that return SECStatus set NSPR error code
Target Milestone: 3.12 → 3.12.1
Reporter | ||
Updated•17 years ago
|
Target Milestone: 3.12.1 → 3.12.2
Reporter | ||
Updated•17 years ago
|
Whiteboard: PKIX → PKIX SUN_MUST_HAVE
Updated•17 years ago
|
Target Milestone: 3.12.2 → 3.12.3
Updated•16 years ago
|
Target Milestone: 3.12.3 → 3.12.5
Comment 1•3 years ago
|
||
The bug assignee is inactive on Bugzilla, and this bug has priority 'P2'.
:beurdouche, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: alvolkov.bgs → nobody
Flags: needinfo?(bbeurdouche)
Updated•3 years ago
|
Severity: normal → S3
Comment 2•3 years ago
|
||
We have modified the bot to only consider P1 as high priority, so I'm cancelling the needinfo here.
Flags: needinfo?(bbeurdouche)
You need to log in
before you can comment on or make changes to this bug.
Description
•