oelnaggar

This issue was closed but was it every resolved? I find that some priorities need modification but I'd rather just add a line or two instead of having to copy...

Started using Restic recently and was surprised that despite it being so feature-rich, it didn't have this basic feature. Would greatly appreciate adding it. Thanks

I ran into an issue using Proxy Mode. I would run it as follows: ``` ./iamlive --set-ini --mode proxy ``` and in my boto3 script, I had two boto3 calls....

@iann0036 A quick test shows that it now works 👍 I'll try to do some more testing for other use cases. Thanks. PS. The problem wasn't in the HEAD request...

Not sure why, but this command: ``` $ aws elb describe-load-balancers ``` works but shows no output when running iamlive in proxy mode but works + shows the following when...

To build an executable, just run: ``` go install github.com/cybozu-go/transocks/cmd/...@latest ```

Ran into this as well. Just install **cfssl** and **cfssljson** on your machine locally and then git clone the repo and call the `add-user.sh` script. That worked for me

I ran into this issue as well and I confirmed that it is related to `cgroupsv2`. There are some workarounds mentioned [here](https://serverfault.com/questions/1053187/systemd-fails-to-run-in-a-docker-container-when-using-cgroupv2-cgroupns-priva) that work and can be used as temporary...

Thanks @arthaud. Given that this might have resulted in CI/CD pipelines and normal users running **pysa** missing findings, would it be possible to have these types of errors (signature mismatches)...

As a temporary workaround (if you are using X11), you can get it to work by: ``` WINIT_UNIX_BACKEND=x11 ./linux_BoilR ```