• Joined on 2025-07-20
michael closed issue dutchcoders/transfer.sh#246 2026-01-19 18:29:35 +00:00
Suggestion: Continuous Fuzzing
michael commented on issue dutchcoders/transfer.sh#245 2026-01-19 18:29:35 +00:00
Dependency issue with urfave/cli.v1

@paolafrancesca commented on GitHub:

@tbi88 I already opened a ticket on go repo that seems related to the same type of error: https://github.com/golang/go/issues/33154

I experienced that…

michael commented on issue dutchcoders/transfer.sh#245 2026-01-19 18:29:35 +00:00
Dependency issue with urfave/cli.v1

@paolafrancesca commented on GitHub:

I switched to use directly github.com/urfave/cli instead of the forked github.com/minio/cli and it's solved

michael commented on issue dutchcoders/transfer.sh#245 2026-01-19 18:29:35 +00:00
Dependency issue with urfave/cli.v1

@tbi88 commented on GitHub:

Hi

I would prefer if you could do it. I am pretty new with go yet...

cheers

michael commented on issue dutchcoders/transfer.sh#244 2026-01-19 18:29:35 +00:00
Couldn't upload file to docker

@dopessoa commented on GitHub:

The problem is that /tmp does not exist inside the docker container, the method used to create the directory in storage.go does not create directories recursively,…

michael commented on issue dutchcoders/transfer.sh#244 2026-01-19 18:29:35 +00:00
Couldn't upload file to docker

@ichcc commented on GitHub:

Thanks a lot!

On 22 Aug, 2019, at 22:37, Dwaraka Nath notifications@github.com wrote:

The same has been resolved in a previous issue - #187 <https://github.co…

michael opened issue usnistgov/macos_security#190 2026-01-19 18:29:35 +00:00
Create a script who doesn't need answer to fix non compliant settings
michael commented on issue dutchcoders/transfer.sh#246 2026-01-19 18:29:35 +00:00
Suggestion: Continuous Fuzzing

@yevgenypats commented on GitHub:

@aspacca Thanks for your reply we will put it on the near roadmap.

Also, I need to mention that we have a [reward program](https://fuzzit.dev/2019/08/12/announ…

michael commented on issue dutchcoders/transfer.sh#246 2026-01-19 18:29:35 +00:00
Suggestion: Continuous Fuzzing

@yevgenypats commented on GitHub:

Sure. Will put it in our pipeline and ping you once the draft PR is ready.

michael opened issue usnistgov/macos_security#191 2026-01-19 18:29:35 +00:00
Add Safari rules for Monterey (CIS)
michael commented on issue dutchcoders/transfer.sh#246 2026-01-19 18:29:35 +00:00
Suggestion: Continuous Fuzzing

@paolafrancesca commented on GitHub:

thanks!

michael commented on issue dutchcoders/transfer.sh#246 2026-01-19 18:29:35 +00:00
Suggestion: Continuous Fuzzing

@paolafrancesca commented on GitHub:

@yevgenypats I would prefer you will create the PR with a first support for this test feature, thanks

michael commented on issue dutchcoders/transfer.sh#246 2026-01-19 18:29:35 +00:00
Suggestion: Continuous Fuzzing

@paolafrancesca commented on GitHub:

hello @yevgenypats, thanks for your interest in this project. your PR is welcome

michael opened issue usnistgov/macos_security#192 2026-01-19 18:29:35 +00:00
Set rules with pathBlackList to deprecated
michael closed issue dutchcoders/transfer.sh#249 2026-01-19 18:29:35 +00:00
Reverse proxy: support X-Forwarded-Port, or allow some sort of --proxy-port
michael commented on issue usnistgov/macos_security#192 2026-01-19 18:29:35 +00:00
Set rules with pathBlackList to deprecated

@robertgendler commented on GitHub:

We will be marking these rules with tag none unless the STIG or some other compliance requirement needs them.

michael commented on issue usnistgov/macos_security#191 2026-01-19 18:29:35 +00:00
Add Safari rules for Monterey (CIS)

@golbiga commented on GitHub:

This is complete, #230

michael commented on issue usnistgov/macos_security#190 2026-01-19 18:29:35 +00:00
Create a script who doesn't need answer to fix non compliant settings

@robertgendler commented on GitHub:

sudo ./build/800-53r5_low/800-53r5_low_compliance.sh --fix is what you're looking for.

michael commented on issue usnistgov/macos_security#190 2026-01-19 18:29:35 +00:00
Create a script who doesn't need answer to fix non compliant settings

@louisdchrf commented on GitHub:

Nice argument, I didn't see this on the wiki

michael commented on issue usnistgov/macos_security#190 2026-01-19 18:29:35 +00:00
Create a script who doesn't need answer to fix non compliant settings

@golbiga commented on GitHub:

Actually you might want to use the --cfc flag. This will do a check, fix, check.