Jonathan Weaver

Hi again, that makes perfect sense. I’ll check it out and report back! I’m also a bit of a neovim noob, but I can certainly provide an MR and others...

Same issue here. I have been communicating with the JetPack.io Head of Product about my same issue. Thanks for identifying the root problem - it was lost on me until...

Hi @rgmz , thanks for the quick response and suggestion. We are not manually tracking false positives via `.gitleaksignore`. Rather, we are using the built-in Gitlab security vulnerability to classify...

> Hmm, none of [the changes in v8.21.0](https://github.com/gitleaks/gitleaks/releases/tag/v8.21.0) jump out as an obvious cause to seeing additional false positives. > > > I have found that after the 8.21.0 updates,...

> @createchange another thing that would be useful is letting us know the command you were using. `git` vs `dir` (detect --no-git). Thanks for offering up your contact info -...

> @createchange Ahh! I think I know what's goofed here. GitLab is using < `v8.21.0` which does not support `[[rules.allowlists]]` syntax. The `master` branch uses `[[rules.allowlists]]` in the default config....

This would benefit my organization, as well.

Hi - it looks like this issue may have fizzled out, but I am coming by way of Trusted Advisor checks and, subsequently, this article: https://aws.amazon.com/blogs/containers/preventing-log-loss-with-non-blocking-mode-in-the-awslogs-container-log-driver/ I work in Security...

Hi there! I can share a sample as needed. Would a dump from a VM with

Good find on that repository! I cloned and built the tool, but unfortunately volatility3 failed to execute on the decompressed output. ```shell # WSL └─$ file output.dmp output.dmp: MS Windows...