Thank you and I’m going through and creating patches now.



However, this leaves open a few questions:

1.    Why was this (TEMP$status) introduced and does removing/changing back eliminate or break functionality?

2.    Is there a reason this issue, which obviously causes severe problems in production, was released and what type of q/a release management is occurring here?

3.    Is this product being maintained?  I’ve noticed extremely limited interaction on both the sourceforge and mailing lists.





Jack D. Pond

Description: PSITEX Logo


"To get something done, a committee should consist of no more than three men, two of whom are absent." -- Robert Copeland

From: Ali Reza Karbasian [mailto:ilia_4002@yaho...]
Sent: Saturday, July 14, 2012 2:15 AM
To: Users' Help and Suggestions
Subject: Re: [Openca-Users] Can't get public request to show up in RA Interface



hi Jack



the problem is TEMPNEW!

in 1.3 version there is such problem

you can fix this by serching for "TEMP$status" in installdir/lib/cmds folder and remove TEMP word! you will find it in 4 files (i think) and by removing that everything works again for new requests!

if you want to fix the already issued certificates and requests you have to fix the status field in ca_certificates, certificates and CSR tables in your database manually!



  _____  

From: Jack D. Pond <jack.pond@psit...>
To: 'Users' Help and Suggestions' <openca-users@list...>
Sent: Saturday, July 14, 2012 7:10 AM
Subject: [Openca-Users] Can't get public request to show up in RA Interface



Weirdness.



I create a browser request CSR via the public interface, but when I go into the RA interface, it doesn’t show up.



It does, however, show up when I go into the CA interface and look at the:



PKI Init & Config->Initialization->RA Certificate->Issue the certificate



Where it shows up as having a status of:



Request Status Information



Current Status          TEMPNEW

Signed By                 Not Signed



What am I doing wrong that it does not show up in the “RA Operations->Certification Requests” (checked under “New”, “Pending”, “Signing Require”, “Approved”).



I’m logging into RA operations as the administrator set up in the installation process.






Server Information for OpenCA Server Version 1.3.0


Saturday 14 July 02:28:37 UTC



Module

Version


OpenSSL

2.0.32


Tools

0.4.3


DB

2.1.50


Configuration

1.5.3


TRIStateCGI

1.5.5


REQ

0.9.9


X509

0.9.11


CRL

0.9.7


PKCS7

0.9.1.1.1


HTML

0.9.40







Jack D. Pond

Description: PSITEX Logo


"We herd sheep, we drive cattle, we lead people. Lead me, follow me, or get out of my way." -- General George S. Patton(1885-1945)


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Openca-Users mailing list
Openca-Users@list...
https://lists.sourceforge.net/lists/listinfo/openca-users