Daniel McCarney
Daniel McCarney
Hi there, neat client! Whenever I find a new ACME client I check the source to see if they're setting a user agent. This is really useful from a server...
Hi there, Your project has a hardcoded URL reference to the [current](https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf) Let's Encrypt subscriber agreement: https://github.com/kristapsdz/acme-client-portable/blob/e82c130dd942a74c50c1631042c1bc60fafe8bad/main.c#L35:L36 This URL is [**going to change November 15th**](https://community.letsencrypt.org/t/subscriber-agreement-update-november-15-2017/45607). If your project does not...
## Background Historically the [CABF baseline requirements](https://cabforum.org/wp-content/uploads/CA-Browser-Forum-BR-1.6.7.pdf) have considered FQDNs with `.onion` as the rightmost label "internal names" because the TLD is not registered in IANA's root zone database: >...
In https://github.com/jlund/streisand/pull/660 a SSH config is generated as part of the end-to-end client testing of the SSH forward user. This should be done by the base SSH role as part...
### Expected behavior: It's reasonable to expect that the `shadowsocks-libev` service that Streisand runs will be compatible with a `shadowsocks-libev` client. The `test-client` infrastructure should test the server using a...
The work to support a modular Streisand deploy (e.g. one without all services enabled by default) has completed. We should update the README to make this more prominent.
Related to https://github.com/StreisandEffect/discussions/issues/98 we should describe how we prefer the process of new feature implementation / larger PR submission be done. We should touch on: * reaching out initially on...
Discussion on https://github.com/letsencrypt/pebble/pull/39 indicated that there are users who would find it valuable to be able to inject test data into Pebble to help support integration testing with an ACME...
Boulder allows configuration of [issued end entity certificate lifetime](https://github.com/letsencrypt/boulder/blob/2131065b2d0393fdbd21a5060c021873f2cb5121/test/config/ca-a.json#L38). Pebble presently hard-codes it: https://github.com/letsencrypt/pebble/blob/0abe0523af6f711c2f4c4a29a3a9a5f91aa9282e/ca/ca.go#L197 [RFC 8555 7.5](https://tools.ietf.org/html/rfc8555#section-7.4) specifies that a new order request may have optional `notBefore` and `notAfter` fields...
Pebble originated as a piece of test code and one of the unfortunate side effects of that is that it doesn't have significant integration test coverage (and no unit tests...