Actions
action #37330
closedCheck that certificates are successfully created
Start date:
2018-06-13
Due date:
% Done:
100%
Estimated time:
Description
The CA password is needed several times during the sine-setup, but there is no check for correct input and successful certificate creation. Thus the setup can end up in a unusable system without any error message from sine.
sine should check the exit code from inviscerts/openssl and offer to try the certificate creation again.
Updated by flacco almost 6 years ago
- Status changed from New to Feedback
This could be difficult, because in case of given a wrong password for the ca-privkey, we have to clean up before we could start a second try.
Updated by flacco almost 6 years ago
- Status changed from Feedback to In Progress
- % Done changed from 0 to 60
Script inviscerts is hardened against wrong given ca-key passwords.
No we have to look at sine2.
Updated by flacco almost 6 years ago
- Status changed from In Progress to Resolved
- Target version changed from Future to 14.0
- % Done changed from 60 to 90
Job done. sine2 now also reacts to errors during the creation of the local CA. Now we have to test it.
Updated by flacco almost 6 years ago
- Status changed from Resolved to Closed
- % Done changed from 90 to 100
Test was positive.
Actions