@paolafrancesca commented on GitHub:
is this a feature request?
there's a stale branch about gpg crypting: https://github.com/dutchcoders/transfer.sh/pull/162
you still have to trust the…
@computeralex92 commented on GitHub:
The issue is related to the switch from Version 2 of the signature to Version 4 happen step by step from AWS. Every newer region (e.g. eu-central-1 or…
@paolafrancesca commented on GitHub:
@computeralex92 can you point to some documentation about the topic? the S3 storage backend was done by @nl5887 and I never worked on it (neither I have the…
@paolafrancesca commented on GitHub:
I see @computeralex92. as I said I don't use S3 and I didn't developed that part. I think the whole code has to be moved to use official AWS SDK, unlikely I…
@paolafrancesca commented on GitHub:
please @computeralex92 can you test #243 ?
@computeralex92 commented on GitHub:
please @computeralex92 can you test #243 ?
I will try it and give you a result as soon as possible.
@paolafrancesca commented on GitHub:
@zmwangx, putting the proxy port in the Host header is enough:
proxy_set_header Host $host:8443;
@robertgendler commented on GitHub:
sudo ./build/800-53r5_low/800-53r5_low_compliance.sh --fix is what you're looking for.
@golbiga commented on GitHub:
Actually you might want to use the --cfc flag. This will do a check, fix, check.
@louisdchrf commented on GitHub:
Nice argument, I didn't see this on the wiki
@robertgendler commented on GitHub:
We will be marking these rules with tag none unless the STIG or some other compliance requirement needs them.