From 84910f8cec53daeac1fdd20cc700d33624f087ab Mon Sep 17 00:00:00 2001 From: ManuelPOISSON Date: Sun, 24 Oct 2021 22:36:53 +0200 Subject: [PATCH 1/3] fix README-Creating-scenario.md fix path removing "simple_examples" which doesn't exists --- README-Creating-Scenarios.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README-Creating-Scenarios.md b/README-Creating-Scenarios.md index d2c7f0e8f..6824e84cc 100644 --- a/README-Creating-Scenarios.md +++ b/README-Creating-Scenarios.md @@ -14,7 +14,7 @@ SecGen's scenario specification is a powerful interface for specifying the const The selection logic for choosing the modules to fulfill the specified constraints can filter on any of the attributes in each module's secgen_metadata.xml file (for example, difficulty level and/or CVE), and any ambiguity results in a random selection from the remaining matching options (for example, any vulnerability matching a specified difficulty level). -For example, scenarios/simple_examples/simple_any_random_vulnerability.xml specifies one system with a Debian Linux base, and a vulnerability. In this case the base module is specified by module name, so this selection is predefined (there is only one possible module that matches), and the vulnerability is randomly selected from the entire set of vulnerabilities because no attribute filters are specified, which could have limited down the potential matches. +For example, scenarios/simple_any_random_vulnerability.xml specifies one system with a Debian Linux base, and a vulnerability. In this case the base module is specified by module name, so this selection is predefined (there is only one possible module that matches), and the vulnerability is randomly selected from the entire set of vulnerabilities because no attribute filters are specified, which could have limited down the potential matches. ```xml From a295e6ad6854ef8f7e6ff850a9b3025adcff88bf Mon Sep 17 00:00:00 2001 From: ManuelPOISSON Date: Sun, 24 Oct 2021 22:44:33 +0200 Subject: [PATCH 2/3] fix README-Creating-scenario.md add "examples" to path --- README-Creating-Scenarios.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README-Creating-Scenarios.md b/README-Creating-Scenarios.md index 6824e84cc..451a697bd 100644 --- a/README-Creating-Scenarios.md +++ b/README-Creating-Scenarios.md @@ -14,7 +14,7 @@ SecGen's scenario specification is a powerful interface for specifying the const The selection logic for choosing the modules to fulfill the specified constraints can filter on any of the attributes in each module's secgen_metadata.xml file (for example, difficulty level and/or CVE), and any ambiguity results in a random selection from the remaining matching options (for example, any vulnerability matching a specified difficulty level). -For example, scenarios/simple_any_random_vulnerability.xml specifies one system with a Debian Linux base, and a vulnerability. In this case the base module is specified by module name, so this selection is predefined (there is only one possible module that matches), and the vulnerability is randomly selected from the entire set of vulnerabilities because no attribute filters are specified, which could have limited down the potential matches. +For example, scenarios/examples/simple_any_random_vulnerability.xml specifies one system with a Debian Linux base, and a vulnerability. In this case the base module is specified by module name, so this selection is predefined (there is only one possible module that matches), and the vulnerability is randomly selected from the entire set of vulnerabilities because no attribute filters are specified, which could have limited down the potential matches. ```xml From 48cfc1dfca1f3a99a6710ed7d121e28910085c2e Mon Sep 17 00:00:00 2001 From: ManuelPOISSON Date: Tue, 26 Oct 2021 08:34:49 +0200 Subject: [PATCH 3/3] fix path in README-Modules-Puppet.md --- README-Modules-Puppet.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README-Modules-Puppet.md b/README-Modules-Puppet.md index b6f903cd7..9c75e3eee 100644 --- a/README-Modules-Puppet.md +++ b/README-Modules-Puppet.md @@ -7,7 +7,7 @@ The module directory contains The following example should help illustrate. -Distcc has a documented security weakness that enables remote code execution. The below example comes from modules/vulnerabilities/misc/distcc_exec. +Distcc has a documented security weakness that enables remote code execution. The below example comes from modules/vulnerabilities/unix/misc/distcc_exec. A manifest/ directory contains the Puppet files for a distcc_exec Puppet class.