- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just received the access confirmation for test-as.sgx.trutedservices.intel.com but when I try to test it by:
"curl -v --tlsv1.2 --key ./testCertKey.pem --cert ./testCert.pem https://test-as.sgx.trustedservices.intel.com:443/attestation/sgx/v2/sigrl/0000ae0 "
The IAS will terminal the TCP connection upon the client has sent "Certificate, Client Key Exchange, Certificate Verify, Change Cipher Spec, Encrypted Handshake Message" handshake messages. Curl doesn't even get a chance to send in the "Get" request to IAS for processing. I have check that both the private key and the cert are correct and the cert is the same one I included in the access request for the test environment. It seems like my cert is not trusted by test-as.sgx.trustedservices.intel.com.
My question is, do I have to wait a few days before the registration kick into effect? If not then where do I go for support?
Thanks,
Eddie.
Link Copied
- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Goh, Nicholas wrote:
Hello John,
Unfortunately I am also facing this similar problem, are you able to help me too?
I will have the team look into your issue as well. Thank you for letting me know!
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
John M. (Intel) wrote:
Quote:
Goh, Nicholas wrote:
Hello John,
Unfortunately I am also facing this similar problem, are you able to help me too?
I will have the team look into your issue as well. Thank you for letting me know!
John
I am doing this for a project submission so any updates would be helpful
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
John M. (Intel) (Intel) wrote:We believe we have identified the root causes for each of the issues reported in this thread. As they don't all have the same cause, we'll be reaching out to you all individually.
In addition to fixing the issues, there are some changes we can make in our own processes to help identify potential problems sooner rather than later.
Hi Jogn,
I'm facing this issue as well. Is it due to the [common name] in cert mismatch the real host?
It will be helpful if any one can contact to me via mail.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello John and all,
Now I'm having the same problem with a self-signed certificate that I registered last year and was previously working. Has something changed? I have sent mail to intelapiservicesupport. Unfortunately, I don't know precisely when my certificate stopped working.
I did notice that my certificate fails openssl verify, because I didn't set the CA:true basic constraint in the config. However, the self-signing instructions for SGX don't mention this, and as I said, my certificate was working until some time in the past. Today I get the same error previous posters got because their certificate was not deployed to the test environment: curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to test-as.sgx.trustedservices.intel.com:443
Would appreciate any help anyone can offer!
Thanks,
Matt
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »