SaltStack Management

The REMnux distro uses SaltStack to automate the installation and configuration of the tools that comprise the distro. This is accomplished using Salt state files, each one describing the steps necessary to set up the software component. These files are stored in the REMnux/salt-states repository on Github, and are available for your review. Read on to learn how REMnux uses these State Files to manage the configuration of a REMnux system.
REMnux uses SaltStack for locally managing the configuration of the system where the distro is installed. It doesn't use other SaltStack capabilities, such as remote command execution.
A state file can direct SaltStack to install a tool by supporting a variety of formats in which such tools migh be packages, including Ubuntu packages, pip modules, Git repositories, Ruby gems, etc. Each state file represents one aspect of the state in which the system should be after SaltStack runs. The files follow the YAML markup language.
Salt State File to Install an Ubuntu Package
For example, here's the Salt state file edb-debgger.sls for installing edb, a powerful debugger for examining ELF binaries:
1
include:
2
  - remnux.repos.remnux
3
  - remnux.packages.xterm
4
  
5
edb-debugger:
6
  pkg.installed:
7
    - pkgrepo: remnux
8
    - require:
9
      - sls: remnux.packages.xterm
Copied!
The line edb-debugger: specifies the name of the Ubuntu package that SaltStack should install. The pkgrepo: remnux line specifies that SaltStack will find this package in the Ubuntu package repository named "remnux." The require statement explains that this package depends on "xterm." The distro also includes state files that explain SaltStack should install the remnux repository and the xterm package.
Salt State File to Install a pip Package
Here's an example of a Salt state file pyzipper.sls to install pyzipper, a Python library for interacting with Zip file archives. SaltStack will use the Python 3 version of pip (pip3), which is installed using remnux.packages.python3-pip, to install pyzipper from the standard PyPI repository of Python software:
1
include:
2
  - remnux.packages.python3-pip
3
  - remnux.python3-packages.pycryptodomex
4
​
5
remnux-python-packages-pyzipper:
6
  pip.installed:
7
    - name: pyzipper
8
    - bin_env: /usr/bin/python3
9
    - require:
10
      - sls: remnux.packages.python3-pip
11
      - sls: remnux.python3-packages.pycryptodomex
Copied!
Since pyzipper depends on the "pycryptodomex" package, which might not be automatically installed by pip, the state file above explicitly specifies the state file of pycryptodomex as a dependency.
Salt State File to Configure a Tool
REMnux also uses Salt state files configure the environment and the tools installed as part of the distro. For example, here's a short excerpt from the Salt state file that configures Ghidra, which is a reverse-engineering tool that includes a disassembler and debugger. (The installation of Ghira is handled using a separate ghidra.sls file.)
1
remnux-config-ghidra-file-preferences:
2
  file.managed:
3
    - name: {{ home }}/.ghidra/.ghidra_9.1.2_PUBLIC/preferences 
4
    - source: salt://remnux/config/ghidra/preferences
5
    - replace: False
6
    - user: {{ user }}
7
    - group: {{ user }}
8
    - makedirs: True
9
    - require:
10
      - user: remnux-user-{{ user }}
11
    - watch:
12
      - file: remnux-config-ghidra-gdt-owner
Copied!
In the example above:
​file.managed specifies the desired state of the Ghidra "preferences" file, located in the user's home directory. 
source of the file is the version of "preferences" in the GitHub repository where this state file resides; this directs SaltStack to copy this file to the location specified by name. 
replace  directs SaltStack not to replace the file if it already exists.
user and group specify that the file should be owned by the user and the user's group.
makedirs direct SaltStack to create the directory structure so the file can be placed in the location specified by name.
The state file instructions above rely on the values home and user, which are set earlier in the file:
1
{%- set user = salt['pillar.get']('remnux_user', 'remnux') -%}
2
{%- if user == "root" -%}
3
  {%- set home = "/root" -%}
4
{%- else %}
5
  {%- set home = "/home/" + user -%}
6
{%- endif -%}
Copied!
This excerpt from the Ghidra configuration state file uses the "pillars" feature of SaltStack, which gives SaltStack access to named values defined before the state file has a chance to run. In this case, the state file sets the user value by retrieving the pillar variable named remnux_user, which is normally set by the REMnux installer; if it's not available, SaltStack is directed to use the default value "remnux." Further, depending on the user value, the state file sets the home value to point to the user's home directory.

Behind the Scenes - Previous

Technologies

REMnux Installer

Last modified 1yr ago

Copy link

Contents

Salt State File to Install an Ubuntu Package

Salt State File to Install a pip Package

Salt State File to Configure a Tool