This repository has been archived by the owner on Jun 6, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 52
Need an expired self-signed certificate to run tests on CI #1
Comments
nathany
added a commit
that referenced
this issue
Dec 18, 2015
exclude certificate tests until figuring out a good way to do that. ref #1
nathany
added a commit
that referenced
this issue
Dec 18, 2015
exclude certificate tests until figuring out a good way to do that. ref #1
nathany
added a commit
that referenced
this issue
Dec 18, 2015
exclude certificate tests until figuring out a good way to do that. ref #1
nathany
added a commit
that referenced
this issue
Dec 18, 2015
exclude certificate tests until figuring out a good way to do that. ref #1
6 tasks
nathany
added a commit
that referenced
this issue
Feb 2, 2016
[ci skip] #1 no self-signed expired cert yet though
nathany
added a commit
that referenced
this issue
Feb 3, 2016
[ci skip] #1 no self-signed expired cert yet though
I've added a self-signed *.p12 cert for testing in #19. Still need a self-signed expired cert as well. Though I tried creating a cert that expires in one day, that didn't work for some reason. |
nathany
added a commit
that referenced
this issue
Feb 5, 2016
[ci skip] #1 no self-signed expired cert yet though
nathany
changed the title
Figure out how to test certificate loading and validation in CI
Need an expired self-signed certificate to run tests on CI
Feb 7, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have valid and expired certificates, but I don't want to include them in the open source project for obvious reasons.
There may be a way to store them on CI, or perhaps some level of mocking instead of full integration tests.
https://docs.travis-ci.com/user/encrypting-files/
The text was updated successfully, but these errors were encountered: