The README has relative links to other Markdown files that only work in GitHub and not in the Docker Hub.

At https://github.com/letsencrypt/boulder/blob/97390560a3bf1f68404087c7011752cf1e4bc302/va/va.go#L421, we log when an RPC to a remote VA failed (e.g. due to network timeout or connection refused). However, we don't currently have a stat that shows just that number (as opposed to overall validation failures, which includes cases where we got, e.g., and invalid challenge token). We should add a stat

What would you like to be added

I would love to have a MongoDB database connector.

Why this is needed

All our other services use MongoDB and I would love to keep everything unified in one database system.

Failing that, is it possible to provide a pluggable webhook that we can have and then enter into our own database?

How to correctly merge parameters from Get-LabPostInstallationActivity and HostStart.ps1 for Custom Roles

When using custom roles (I'll use the MDT role as an example), parameters not provided in the Get-LabPostInstallationActivity call from the parent script are not merged with the param definition in the HostStart.ps1 file, causing the Sync-Parameter call to end up with an incomplete list

Example

The sed commands throw the error because macOS or BSD systems require a more specific -i flag.

A solution may be found here: https://stackoverflow.com/questions/7573368/in-place-edits-with-sed-on-os-x

Looks like there is no reference of mariadb_server__delegate_to in any task file of the role.

I think the entire PEM-encoded certificate chain should be fed to the script over stdin. Cert Spotter should ignore broken pipes in case the script closes stdin before reading anything. Question: what if the script forks with stdin still open and never reads?

We should support

• a known_hosts of registered hosts (what we have right now)
• a known_hosts with the CAs used for all currently issued certs (today, we only support one, so just that)
• or both.

Sharkey-client should grab both by default.

When I first tried to get Pebble running using the binary I downloaded from the releases, it complained about missing files it was looking for. I got it working by copying the test directory from the source repository into the same folder as the Pebble binary. With that, I was able to run Pebble without needing to specify any arguments.

This would be useful to document for people just startin

The general /cgi-bin/ alias in the apache config colides with the default config
Alternative - use another prefix (e.g. openxpki-cgi)

We keep messing up the Markdown documentation files. To avoid that, we should add markdownlint to the Travis build script.

Can't even get the example command to run, getting an error:

PS C:\some\current\dir\with\the script file> . .\New-SelfSignedCertificateEx.ps1
PS C:\some\current\dir\with\the script file> New-SelfsignedCertificateEx -Subject "CN=www.domain.com" -EKU "Server
 Authentication", "Client authentication" `
>> -KeyUsage "KeyEncipherment, DigitalSignature" -SAN "sub.domain.com","www.domain.com",

There is currently no link/reference to our contributing guidelines on the main README, so folks still actively using our code may not immediately know what to do in case of an issue/question/bug.

Follow up to letsencrypt/ct-woodpecker#5

We should also have the certSubmitter submit multiple copies of the same new cert in parallel. If distinct SCTs are returned then all of them should be stored and checked for inclusion.

Details of the scenario you tried and the problem that is occurring:
In the resource CertificateImport there should be no need to have the non-mandatory parameter Ensure in the Get-TargetResource function.

https://github.com/PowerShell/CertificateDsc/blob/6906fc5b31a783a899260c9c9d4ba84a02dd4c14/Modules/CertificateDsc/DSCResources/MSFT_CertificateImport/MSFT_CertificateImport.psm1#L65-

The client currently only requests the authentication path upon a lookup, it doesn't also verify it against the epoch's STR.