Richard Levitte

I suggest `openssl/corpora`. Agree? Disagree? If all agree, then I can make it happen

I can create a PR against the fuzz-corpora from this.

Done, see openssl/fuzz-corpora#1. I created that PR as follows: - checked out this PR, then created a patch: ``` console $ git format-patch HEAD^ 0001-Update-asn1-corpora.patch ``` - Applied that patch...

Closing this in favor of https://github.com/openssl/fuzz-corpora/pull/1.

> This is an unsupported configuration. Supporting it would be a new feature. Er.... they are making their own config targets with inheritance from VC-WIN64A. *That's a supported feature!* Now,...

Another thing to note is this: ``` openssl/1.1.1m: ['"VC-conan-Release-Windows-x86_64-clang-12"', 'no-shared', '--prefix="D:\\.conan\\storage\\openssl\\1.1.1m\\_\\_\\package\\e5dfaa2a6d0ff8915bb91aa1f1e2569e87e2b3dc"', '--openssldir="D:\\.conan\\storage\\openssl\\1.1.1m\\_\\_\\package\\e5dfaa2a6d0ff8915bb91aa1f1e2569e87e2b3dc\\res"', 'no-unit-test', 'threads', 'PERL=D:\\.conan\\fb39bb\\1\\bin\\perl.exe', 'no-tests', '--release'] WARN: replace_in_file didn't find pattern '/MTd ' in 'Configurations\10-main.conf' file. WARN: replace_in_file didn't...

1. Those build scripts are internal to our infrastructure. They essentially run `make`, but with specific targets that only builds the simple web files, or that only builds the docs....

Ah, you need these too: ``` git clone --depth=1 --branch=openssl-3.2 https://github.com/openssl/openssl.git openssl-3.2 git clone --depth=1 --branch=openssl-3.3 https://github.com/openssl/openssl.git openssl-3.3 ```

I would default it to the team key. I just found out that the key user id (i.e. any email address associated with it) can be used in place of...

I have a few things lying around that align with this. I'll collect them into a PR on Monday.