From fb4ce2b5d52e989de2ffd4dc3f8c85691b2d4bb9 Mon Sep 17 00:00:00 2001 From: cacu Date: Sat, 12 Apr 2025 12:42:05 -0600 Subject: [PATCH 1/2] Update introduction.es.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit add official documentatión link on WSL (es version) --- content/learning-path/1/introduction.es.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/learning-path/1/introduction.es.md b/content/learning-path/1/introduction.es.md index 8b711a01c..a9606a216 100644 --- a/content/learning-path/1/introduction.es.md +++ b/content/learning-path/1/introduction.es.md @@ -80,7 +80,7 @@ Las habilidades en investigación, abordaje y detección de infraestructuras mal * No necesita ningún hardware potente o especializado para esta ruta de aprendizaje. Cualquier computadora moderna debe funcionar. Aunque las herramientas de esta ruta de aprendizaje solo se han probado en sistemas basados en x86, la mayoría, si no todos, también deben funcionar en sistemas ARM como los ordenadores Raspberry Pi o Apple Silicon. * Muchas de las herramientas de esta ruta de aprendizaje funcionan mejor en sistemas operativos con distribuciones Unix. Esto significa que es más fácil usar dispositivos Linux, macOS o Windows con WSL (Subsistema de Windows para Linux) instalado. -* Si está ejecutando Windows, necesitará instalar WSL (Subsistema de Windows para Linux) para ejecutar algunas de las herramientas que se describen a continuación. +* Si está ejecutando Windows, necesitará instalar WSL (Subsistema de Windows para Linux), puedes mirar esta [documentación](https://learn.microsoft.com/es-es/windows/wsl/) para ejecutar algunas de las herramientas que se describen a continuación. * Si está ejecutando macOS, es una buena idea instalar [Homebrew](https://brew.sh/) o [Macports](https://www.macports.org/); estos son administradores de paquetes que pueden automatizar el proceso de instalación de algunas de las herramientas descritas a lo largo del ruta de aprendizaje. * Tanto WSL como Linux deben tener gestores de paquetes integrados que puede utilizar para instalar las herramientas descritas a continuación. From 78cfa3e6c34b7ab6573228108788bafb9234ed52 Mon Sep 17 00:00:00 2001 From: cacu Date: Sat, 12 Apr 2025 12:45:38 -0600 Subject: [PATCH 2/2] Update introduction.en.md add documentation on WSL (en-us version) --- content/learning-path/1/introduction.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/learning-path/1/introduction.en.md b/content/learning-path/1/introduction.en.md index fbd6bbbf5..91729ae98 100644 --- a/content/learning-path/1/introduction.en.md +++ b/content/learning-path/1/introduction.en.md @@ -77,7 +77,7 @@ Skills in investigating, tacking, and detecting malicious infrastructure can hel - You do not need any specialized or powerful hardware for this learning path. Any modern computer should work. While the tools in this learning path have only been tested on x86-based systems, most if not all should also work on ARM systems like the Raspberry Pi or Apple Silicon computers - Many of the tools in this learning path run best on Unix-like operating systems. This means that it’s easiest to use Linux, macOS devices, or Windows devices with WSL (Windows Subsystem for Linux) installed on them. -- If you are running Windows, you will need to install WSL (Windows Subsystem for Linux) to be able to run some of the tools outlined below +- If you are running Windows, you will need to install WSL (Windows Subsystem for Linux) to be able to run some of the tools outlined below, This [documentation](https://learn.microsoft.com/en-us/windows/wsl/) may be referenced as needed. - If you are running macOS, it’s a good idea to install [Homebrew](https://brew.sh/) or [Macports](https://www.macports.org/); those are package managers which can automate the process of installing some of the tools outlined throughout the learning path. - WSL and Linux should both have built-in package managers which you can use to install the tools outlined below. - It is best to analyze malicious infrastructure on a separate device which you do not use for other sensitive work and where you are not logged into any sensitive or work accounts. If you cannot use a discrete device, you could also run the analysis within a virtual machine. If you’re just starting out with virtual machines, check out [this quick guide](https://ubuntu.com/tutorials/how-to-run-ubuntu-desktop-on-a-virtual-machine-using-virtualbox#1-overview) on how to run the user-friendly Ubuntu Linux within one.