Project

General

Profile

Actions
Copy link

Bug #3090

closed

CRL manager - revocation reason dropdown is no-op

Added by Doktor Notor almost 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
07/11/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.1
Affected Plus Version:
Affected Architecture:

Description

As per subject.

Actions
Copy link
 #1

Updated by Jim Pingle almost 11 years ago

  • Status changed from New to Rejected

Is there a forum thread for this?

It works fine for me. Once a cert is added to the CRL, the reason column is filled in. The Reason is a property of the certificate being revoked, not of the CRL itself.

Actions
Copy link
 #2

Updated by Jim Pingle almost 11 years ago

Tried it on a VM full install and ALIX both on a current snapshot, reason drop-down is always filled in for me.

Actions
Copy link
 #3

Updated by Doktor Notor almost 11 years ago

Once a cert is added to the CRL, the reason column is filled in.

Negative, Captain :-)

Anyway: http://forum.pfsense.org/index.php/topic,64369.0.html

Actions
Copy link
 #4

Updated by Doktor Notor almost 11 years ago

Fixed by

--- /etc/inc/certs.inc  2013-07-10 05:35:46.000000000 +0200
+++ etc/inc/certs.inc   2013-07-11 20:10:53.000000000 +0200
@@ -576,6 +576,7 @@
 OCSP_REVOKED_STATUS_REMOVEFROMCRL
 */

+global $openssl_crl_status;
 $openssl_crl_status = array(
        OCSP_REVOKED_STATUS_NOSTATUS              => "No Status (default)",
        OCSP_REVOKED_STATUS_UNSPECIFIED           => "Unspecified",

Thanks, Jim!

Actions
Copy link
 #5

Updated by Jim Pingle almost 11 years ago

  • Status changed from Rejected to Resolved

For the record, it seems to be that when an ALIX is starved for RAM, somehow globals start disappearing unless they're explicitly declared global. Might need to go through other .inc files and be on the lookout for other similar issues.

Actions
Copy link
 #6

Updated by Doktor Notor almost 11 years ago

Weird... when the poor little thing really gets abused too heavily and runs out of RAM, I get php killed in system log. No such thing at the moment.

Actions
Copy link

Also available in: Atom PDF