Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS Certificate is expired. #828

Closed
stc1988 opened this issue Jan 31, 2022 · 8 comments
Closed

TLS Certificate is expired. #828

stc1988 opened this issue Jan 31, 2022 · 8 comments
Labels
confirmed issue reported has been reproduced fixed - please verify Issue has been fixed. Please verify and close.

Comments

@stc1988
Copy link
Contributor

stc1988 commented Jan 31, 2022

Build environment: macOS, Windows
Target device: desktop simulator

Steps to Reproduce

  1. Build and Run examples/network/http/httpsgetjson using this build command: mcconfig -d -m
  2. TLS Error is thrown at ssl_handshake.js .
    And Console log date validation failed on certificate resource is shown.

TLS Certificates located in the module/ecrypt/data folder seems to expired.

@andycarle
Copy link
Member

Thank you for the report! We've confirmed the issue and are contemplating the best options to maintain those certificates on our end.

@wilberforce
Copy link
Contributor

Is there a reason they are named as numeric names- could they be named more descriptively so the filename reflects the cert?

Perhaps symbolic links to the old names?

@phoddie
Copy link
Collaborator

phoddie commented Feb 11, 2022

The numbers reflect their position in the ca.ski index file. Giving them a friendly name at runtime would require additional data.

@andycarle andycarle added the confirmed issue reported has been reproduced label Feb 15, 2022
@stc1988
Copy link
Contributor Author

stc1988 commented Jun 26, 2022

Now I ran examples/network/http/httpsgetjson and got a erorr Resource: Resource not found: ca222.der!.
So I added ca222.der which is not expired to manifest.json.  Eventually Application ran without any error.

I don't know why this issue solved, but can we close this issue?

@phoddie
Copy link
Collaborator

phoddie commented Jul 1, 2022

Interesting. I just tried the example here. The site is still requesting ca109. Maybe you are somehow reaching a different endpoint?

@phoddie
Copy link
Collaborator

phoddie commented Aug 11, 2022

This note from Let's Encrypt seems relevant as the failure is with ca109.der which is the expired DST Root CA X3.

@phoddie phoddie added the fixed - please verify Issue has been fixed. Please verify and close. label Aug 15, 2022
@phoddie
Copy link
Collaborator

phoddie commented Aug 15, 2022

I rebuilt the certificate bundle with an updated certificate. It is working reliably now. Please update give it a try to confirm. Thank you!

@stc1988
Copy link
Contributor Author

stc1988 commented Aug 17, 2022

Thank you for updating.
This issues seems to have been solved.

@stc1988 stc1988 closed this as completed Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed issue reported has been reproduced fixed - please verify Issue has been fixed. Please verify and close.
Projects
None yet
Development

No branches or pull requests

4 participants