You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On GrapheneOS (and possibly iPad) the mTLS cert generated by step-ca does not import. This was tested by @mcmikemn to be due to the fact that the CA cert is not included. Even though its the server's job to validate the client cert, graphene seems to need it anyway.
@CN=$$(${BIN}/ask_echo "Enter the subject (CN) to be certified, a domain name, or a client name"); ${STEP} ca certificate "$${CN}""certs/$${CN}.crt""certs/$${CN}.key" --not-after "$$(${BIN}/dotenv -f ${ENV_FILE} get STEP_CA_AUTHORITY_CLAIMS_DEFAULT_TLS_CERT_DURATION)" && ${STEP} certificate p12 "certs/$${CN}.p12""certs/$${CN}.crt""certs/$${CN}.key" && ${STEP} certificate inspect "certs/$${CN}.crt"
On GrapheneOS (and possibly iPad) the mTLS cert generated by step-ca does not import. This was tested by @mcmikemn to be due to the fact that the CA cert is not included. Even though its the server's job to validate the client cert, graphene seems to need it anyway.
d.rymcg.tech/step-ca/Makefile
Lines 53 to 55 in 7352447
mike says
The text was updated successfully, but these errors were encountered: