letsencrypt / boulder / 649 / 1
66%
master: 66%

DEFAULT BRANCH: master
Ran
Files 14
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 40.338% (-3.3%) from 43.647%
649.1

Pull #266

travis-ci

jsha 
<a href="https://github.com/letsencrypt/boulder/commit/<a class=hub.com/letsencrypt/boulder/commit/4db9e8c954ddb6eb01cf82bb56f20ae05066d9f4">4db9e8c95<a href="https://github.com/letsencrypt/boulder/commit/4db9e8c954ddb6eb01cf82bb56f20ae05066d9f4">&quot;&gt;Move boulder to using local signer.

This allows us to use the same PKCS#11 key for both cert signing and OCSP
signing, and simplifies config and startup.

This also starts building with -tags pkcs11 in all scripts, which is required
now that the CA can choose between pkcs11 and non-pkcs11.

In order to successfully issue using a pkcs11 key, you&amp;#39;ll need to run a version
of Go built off the master branch. The released versions are missing this
commit:
https://github.com/golang/go/commit/</a><a class="double-link" href="https://github.com/letsencrypt/boulder/commit/<a class="double-link" href="https://github.com/letsencrypt/boulder/commit/fe40cdd756763982db6815ee87318f418218fcf5">fe40cdd75</a>">fe40cdd75</a><a href="https://github.com/letsencrypt/boulder/commit/4db9e8c954ddb6eb01cf82bb56f20ae05066d9f4">,
which is necessary for PKCS#11 signing.
Pull Request #266: Use local signer rather than remote one.

1169 of 2898 relevant lines covered (40.34%)

4490.35 hits per line

Source Files on job 649.1