diff --git a/.gitbook/assets/image (1) (1) (4).png b/.gitbook/assets/image (1) (1) (4).png new file mode 100644 index 000000000..6cdd2befe Binary files /dev/null and b/.gitbook/assets/image (1) (1) (4).png differ diff --git a/.gitbook/assets/image (1) (1).png b/.gitbook/assets/image (1) (1).png index 6cdd2befe..a3049cbbd 100644 Binary files a/.gitbook/assets/image (1) (1).png and b/.gitbook/assets/image (1) (1).png differ diff --git a/.gitbook/assets/image (1).png b/.gitbook/assets/image (1).png index a3049cbbd..bda84db54 100644 Binary files a/.gitbook/assets/image (1).png and b/.gitbook/assets/image (1).png differ diff --git a/.gitbook/assets/image (3) (5) (1).png b/.gitbook/assets/image (3) (5) (1).png new file mode 100644 index 000000000..9c0135519 Binary files /dev/null and b/.gitbook/assets/image (3) (5) (1).png differ diff --git a/.gitbook/assets/image (3) (5).png b/.gitbook/assets/image (3) (5).png index 9c0135519..9659bd69f 100644 Binary files a/.gitbook/assets/image (3) (5).png and b/.gitbook/assets/image (3) (5).png differ diff --git a/.gitbook/assets/image (3).png b/.gitbook/assets/image (3).png index 9659bd69f..c65f8a06e 100644 Binary files a/.gitbook/assets/image (3).png and b/.gitbook/assets/image (3).png differ diff --git a/.gitbook/assets/image.png b/.gitbook/assets/image.png index c65f8a06e..884a59fd2 100644 Binary files a/.gitbook/assets/image.png and b/.gitbook/assets/image.png differ diff --git a/linux-hardening/privilege-escalation/docker-breakout/cgroups.md b/linux-hardening/privilege-escalation/docker-breakout/cgroups.md index 3a56c7c94..f1d375aea 100644 --- a/linux-hardening/privilege-escalation/docker-breakout/cgroups.md +++ b/linux-hardening/privilege-escalation/docker-breakout/cgroups.md @@ -57,11 +57,11 @@ To explore the cgroup setup of a shell, you can look in the `/proc/self/cgroup` Among the many files that can be here, **the primary cgroup interface files begin with `cgroup`**. Start by looking at `cgroup.procs` (using cat is fine), which lists the processes in the cgroup. A similar file, `cgroup.threads`, also includes threads. -
+
Most cgroups used for shells have these two controllers, which can control the **amount of memory** used and the **total number of processes in the cgroup**. To interact with a controller, look for the **files that match the controller prefix**. For example, if you want to see the number of threads running in the cgroup, consult pids.current: -
+
A value of **max means that this cgroup has no specific limit**, but because cgroups are hierarchical, a cgroup back down the subdirectory chain might limit it. diff --git a/pentesting-web/file-inclusion/lfi2rce-via-eternal-waiting.md b/pentesting-web/file-inclusion/lfi2rce-via-eternal-waiting.md index 54542e4b7..c80b998a0 100644 --- a/pentesting-web/file-inclusion/lfi2rce-via-eternal-waiting.md +++ b/pentesting-web/file-inclusion/lfi2rce-via-eternal-waiting.md @@ -100,7 +100,7 @@ Then, the attacker could use those **100 connections** to perform a **search bru Yes, it's possible to generate 100000 temporary files in an EC2 medium size instance: -
+
## Nginx diff --git a/todo/radio-hacking/flipper-zero/fz-sub-ghz.md b/todo/radio-hacking/flipper-zero/fz-sub-ghz.md index ac619d340..fe3e75618 100644 --- a/todo/radio-hacking/flipper-zero/fz-sub-ghz.md +++ b/todo/radio-hacking/flipper-zero/fz-sub-ghz.md @@ -12,7 +12,17 @@ -## +## Intro + +Flipper Zero can **receive and transmit radio frequencies in the range of 300-928 MHz** with its built-in module, which can read, save, and emulate remote controls. These controls are used for interaction with gates, barriers, radio locks, remote control switches, wireless doorbells, smart lights, and more. Flipper Zero can help you to learn if your security is compromised. + +
+ +## Sub-GHz hardware + +Flipper Zero has a built-in sub-1 GHz module based on a [](https://www.st.com/en/nfc/st25r3916.html#overview)[CC1101 chip](https://www.ti.com/lit/ds/symlink/cc1101.pdf) and a radio antenna (the maximum range is 50 meters). Both the CC1101 chip and the antenna are designed to operate at frequencies in the 300-348 MHz, 387-464 MHz, and 779-928 MHz bands. + +
## Actions @@ -99,9 +109,10 @@ Check the list in [https://docs.flipperzero.one/sub-ghz/frequencies](https://doc Get dBms of the saved frequencies {% endhint %} -## 125 kHz RFID - +## Reference +* [https://docs.flipperzero.one/sub-ghz](https://docs.flipperzero.one/sub-ghz) +*
diff --git a/windows-hardening/active-directory-methodology/kerberos-double-hop-problem.md b/windows-hardening/active-directory-methodology/kerberos-double-hop-problem.md index 3b1d25c66..a2321fcfa 100644 --- a/windows-hardening/active-directory-methodology/kerberos-double-hop-problem.md +++ b/windows-hardening/active-directory-methodology/kerberos-double-hop-problem.md @@ -104,7 +104,7 @@ netsh advfirewall firewall add rule name=fwd dir=in action=allow protocol=TCP lo Now establish the session, which will forward us to **the first server**. -
+
#### winrs.exe