Replies: 1 comment 8 replies
-
|
The reason is likely that the default for generating a self signed certificate is 30 days. You could probably update the command such that the certs work for longer by following the details here: https://serverfault.com/questions/916740/local-ssl-ca-always-expires-30-days-after-creation |
Beta Was this translation helpful? Give feedback.
-
|
The reason is not the certs expiration. The reason is composer has a hard coded check to see when the cert was generated. If it's more than 40 days it doesn't trust it. It's why you have to recreate it. |
Beta Was this translation helpful? Give feedback.
-
|
This spawns a couple questions. If the cert expires in 30 days (default for creation command as above) does it still work or you have to regen because it expired? If I try in 35 days will it fail because it expired but it would fail in 40 days anyway since c4 is going to not like it? I seem to think there is a way to import a CA into your keystore (maybe on the director side) such that if you generated against it (as is happening here) then it is as good as if you had paid a CA to issue you a key/cert that is trusted from a root CA issuer. |
Beta Was this translation helpful? Give feedback.
-
|
The cert does not expire in 30 days. I believe the one Garry creates expires in 365 days. The expiration date doesn't matter. Composer is hard coded to look at the creation date and compare that to the current date. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like it expires in 10 years.
|
Beta Was this translation helpful? Give feedback.
-
|
I wonder if you imported the cert into your windows keystore if it would then be ok. |
Beta Was this translation helpful? Give feedback.
-
Why does this Jailbreak require to generate and replace the Composer Pro certificates every 30days?
I'm looking for a way to bypass it. Is it some "trial" feature in Composer Pro?
Beta Was this translation helpful? Give feedback.
All reactions