Looks like I forgot that SoftEther's certificate management facilities also have a Certificate Revocation List functionality that could possibly be of use
I think this is similar to #1634
Because users must use auth, remove their access via your auth mechanism.
This could be done by deleting their User via Admin controls, or via your RADIUS mechanism, etc. If you used certificates and their certificates is used elsewhere then you will need to remove them there, or investigate Certificate Revocation Lists or other mechanisms that you might have in play that work in that space, otherwise you will need to sign new certs and distribute them to be sure.
Scanning code reading the log files would probably be the easiest route
Could https://github.com/containers/gvisor-tap-vsock be of help here?
Just wanted to report we ran into this in a pipeline that hadn't been run in a while.
We tried both
alpine3.13 as well as with Docker v20.10.8, and still ran into this error.
After noticing our pipeline was downloading the latest helm-s3 v0.13.0 I noticed these commits semi-recently made to the install.sh script:
I tried pinning helm-s3 to an older version and found it fixed it, both the
alpine3.13 and the newer Docker engine solutions worked. (Without them they still break, of course)
helm plugin install https://github.com/hypnoglow/helm-s3.git --version v0.12.0
I do not know a solution to work in 0.13.0 yet, so I wanted to let y'all know this might have regressed in some way
Sure thing, I will get to this as soon as I can :) Thanks for following back up!