Skip to content

Use newest groob/pkcs7#87

Closed
jessepeterson wants to merge 1 commit intomicromdm:masterfrom
jessepeterson:fix-go1.10-patch
Closed

Use newest groob/pkcs7#87
jessepeterson wants to merge 1 commit intomicromdm:masterfrom
jessepeterson:fix-go1.10-patch

Conversation

@jessepeterson
Copy link
Copy Markdown
Member

To address fullsailor/pkcs7#31

@knightsc
Copy link
Copy Markdown
Contributor

knightsc commented Jul 4, 2018

If groob/pkcs7#3 gets merged in we'll want to update this to pull in the latest fixes.

@knightsc
Copy link
Copy Markdown
Contributor

Now that we've had a couple changes we probably want to re-update to the latest pkcs7 version. That should get the standalone version of the scep server caught back up

hslatman added a commit to hslatman/caddy-scep that referenced this pull request Jan 20, 2021
The setup seems to work currently. The MicroMDM client
(github.com/micromdm/scep/cmd/scepclient) does report an error
stating the certificate is not within valid date range, which is
reported here micromdm/scep#76 and
talked about here micromdm/scep#87 too.
Unfortunately, this seems to be a bug in the MicroMDM client.

The certnanny/sscep (https://github.com/certnanny/sscep)
implementation does seem to work (so far):

./sscep getca -u http://127.0.0.1:9080/scep -c cacert.crt -v
./sscep: starting sscep, version 0.9.0
./sscep: new transaction
./sscep: transaction id: SSCEP transactionId
./sscep: hostname: 127.0.0.1
./sscep: directory: scep
./sscep: port: 9080
./sscep: SCEP_OPERATION_GETCAPS
./sscep: server response status code: 200, MIME header: text/plain
./sscep: SCEP_OPERATION_GETCA
./sscep: server response status code: 200, MIME header: application/x-x509-ca-cert
./sscep: valid response from server
./sscep: MD5 fingerprint: 22:BA:74:B3:FB:DE:79:A2:F5:42:1B:ED:22:1E:D6:5D
./sscep: CA certificate written as cacert.crt
@groob groob closed this Feb 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants