Stewart X Addison

Defined and implemented. We should add the unlock policy when agreed to the RELEASING.md guide, therefore bumping to next iteration for agreement with @andrew-m-leonard

ping @andrew-m-leonard :-)

Note: Jenkins won't accept an `ssh-rsa` or `ssh-dss` key and will therefore requre the contents of `ssh_host_ecdsa_key.pub` or `ssh_host_ed25519_key.pub` to be used in the agent configuration

Running through https://ci.adoptium.net/label/(dockerhost||build)&&!windows/ to cover all build systems connected over ssh (Excluding RISC-V which will ned a separate tidy up). All are configured with the ecdsa key (`/etc/ssh/ssh_host_ecdsa_key.pub`) unless mentioned...

@Haroon-Khel is going to look at implementing the changes for the other jenkins nodes which we connect to over ssh (The `test-` ones) and look at ensuring that any nodes...

Sounds good thanks - we have no such document currently. This is very much a "let's define and document the process" issue :-)

I've added a few comments. On making them, I'm thinking that it might make sense to have separate recommendations for infrastructure team access (where root access is typically granted to...

@steelhead31 Has that document been put anywhere or is it still just in google doc? It looks like it's restricted access at the moment.

> Just as a question, do we distribute binaries built w/ gcc? Yes :-)

Note - this is only a problem if credentials are required. https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-linux-x64-temurin/639 went through OK after the images were made public, but we do still require the ability to pull...