-
Updated
Jan 16, 2022
security-hardening
Here are 266 public repositories matching this topic...
-
Updated
Jan 25, 2022 - Shell
-
Updated
Jan 24, 2022 - Go
-
Updated
Jan 24, 2022 - Shell
-
Updated
Jan 25, 2022 - C
-
Updated
Nov 24, 2021 - JavaScript
-
Updated
Jan 18, 2022 - Rust
-
Updated
Mar 28, 2021 - JavaScript
-
Updated
Jan 25, 2022 - C++
-
Updated
Jul 26, 2020 - Ruby
-
Updated
Nov 20, 2020
-
Updated
Jan 22, 2022
https://github.com/0xmachos/mOSL is a good replacement until this is updated.
Basically, we should remove all settings that are no longer relevant, and add ones that are newly added.
-
Updated
Jan 15, 2022 - HTML
-
Updated
Jan 13, 2022 - Shell
-
Updated
Jan 23, 2022 - HCL
-
Updated
Jan 24, 2022 - C++
-
Updated
Jan 25, 2022 - TypeScript
-
Updated
Jan 24, 2022 - HTML
I'm not confident in the security brought by the readonly_exec statement.
In the classical *nix DAC model, it is expected for unprivileged users to be able to change the write permission flag on files they own. Therefore, Snuffleupagus readonly_exec statement only relies on the hope that an attacker won't find a way to rely on this standard mechanism to prevent the execution of arbitrary
-
Updated
Sep 21, 2020 - PHP
A nice feature of http.Mux is that it can be used as a handler, so users can set up separate parts of an application on separate muxes that share a common configuration (e.g. a set of interceptors) and then install them on the root mux.
This is currently not possible with GSW, and we should seriously consider doing it.
-
Updated
Sep 7, 2018
-
Updated
Oct 21, 2018 - Shell
-
Updated
Jan 19, 2022 - Ruby
-
Updated
Dec 20, 2021 - JavaScript
-
Updated
Jan 21, 2022 - YAML
-
Updated
Mar 9, 2020 - Shell
-
Updated
Dec 13, 2021 - Python
Improve this page
Add a description, image, and links to the security-hardening topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the security-hardening topic, visit your repo's landing page and select "manage topics."
Description of problem:
The bash remediation of selinux_state runs:
whereas the Ansible remediation doe