I am trying to run the code from this repository
https://github.com/kbhokray/aadhaar
But getting error 570 as the included certificate is expired.
I replaced the uidai_auth_stage.cer with the latest file "AuthStaging25082025.cer" from this link
https://uidai.gov.in/en/ecosystem/authentication-devices-documents/developer-section/916-developer-section/data-and-downloads-section.html
Still getting same error.
It seems I need to replace the "Staging_Signature_PrivateKey.p12" too with latest one but the .p12 download link does not work on this website.
Can anyone help to spot where is the latest key to download or if I am making some other mistake in running this?
Related
Need Help!
I have been trying to reissue SSL in namecheap.com. I have already created multiple CSR using MacOS Keychain (Both from the Philippines, and from Japan) and through AWS. However, when I get to the Review & Submit part I keep getting an error (screenshot below). Thank you for any assistance with this, as I have tried numerous methods, and I still could not update the SSL.
I have gotten in touch with namecheap.com, and their response is
"... the certificate has this issue due to a bug from our side that is connected to .ink TLD. ..."
It seems that this is a bug in their system.
If anybody gets this error, you might want to connect with namecheap.com, to see if this bug is still not fixed.
I did my project in MEAN stack. I have installed GeoTrust Wildcard SSL certificate. It worked very well till yesterday. From today morning onward, it returns an error : "Your connection is private".
I don't know why this error occurs suddenly in any browser while run an application. It required to adding manually in exception lists to visit site. Right now I am not able to keep going my site. Certificate having 1 year validity and it was renewed in last month.
Please review attached images.
Give me guideline to solve this issue.
The certificate installed has expired. Looks like you have not installed or assigned the new certificate to your website.
I am using BCPPB6 to maintain some legacy projects. One of these needs to GET data from a https URL. I found that the TNMHTTP comnponent that I have used for standard http GET operations in the past does not support https. However the Indy TIdHTTP component apparantly does.
With some trial and error I have found that it needs an Intercept component (TIdConnectionInterceptOpenSSL) and needs InterceptEnabled set to true. I then found that I need to have an OpenSSL library available. Thus I downloaded the latest version from http://indy.fulgan.com/SSL/, extracted the two dll files and placed these into my application folder. However I continue to get the error "Could not load SSL library.". I have also tried it with archived versions of the OpenSSL from 2001 (around the date of
my CPPB) and experimented with having the dlls in the System32 folder, all with the same error.
Is there anyone that can tell me what I am still doing wrong?
I am not sure... but i was having a similar problem (on :=IdHTTP.Get('https://...');) till i used the DLLs:
http://indy.fulgan.com/SSL/Archive/indy_OpenSSL096m.zip
Hope it helps you.
Following the guide at https://www.openshift.com/developers/download-cartridges i wanted to try installing the CDK to see what it brings to the table. Unfortunately, I was unable to install the cartridge because of the following error:
Unexpected error: CLIENT_ERROR: Download of 'http://cdk-claytondev.rhcloud.com/archive/2ccd7a3a7762e4ebb873c0d64a247b180e0600b8/cdk.zip' exceeded Content-Length of 9728. Download aborted.
Execute rhc create-app cdk http://cdk-claytondev.rhcloud.com/manifest/2ccd7a3a7762e4ebb873c0d64a247b180e0600b8 against a local installation of OpenShift Origin. Or try to create an App throught the web console (again on a local installation, both are untested on rhcloud).
Looks like this was an issue on OpenShift Online also, which got fixed, but is still an issue on OpenShift Origin. Here is the bugzilla ticket for this issue (https://bugzilla.redhat.com/show_bug.cgi?id=1017776), I suggest you add your email address to it to be notified as they make progress against fixing it.
Our code-signing certificate recently expired. It's been renewed, but now whenever I try to package the app with the renewed cert (whether I attempt a migration of the expired cert or not), after installation, I get the following message any time I try to run the app:
"This installation of this application is damaged. Try re-installing or contacting the publisher for assistance."
Opening up the package contents, the publisherid file inside Resources/META-INF/AIR is blank. This is apparently the problem, because if I manually edit it to contain our previous publisherID, the app will run.
But of course, it's not like we can tell all our users "oh install it then manually edit this file inside the package."
Has anyone encountered this or know how to fix it?
Ah, after a bit more banging my head against my desk I got it.
For anyone who comes after me:
I had to change a couple things in my app descriptor file.
First I had to change the namespace to point at AIR 1.5.3 instead of 1.5
<application xmlns="http://ns.adobe.com/air/application/1.5.3">
And then I had to manually specify our old publisherID in the descriptor as well
<id>OurAppID</id>
<publisherID>OurOldPublisherID</publisherID>
Now it works just as it's supposed to, installs as an update to our old version instead of a new app, and actually runs instead of just throwing that error.