andrew.rioux/sparse-v2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: clarify wording and context, link to image

Browse Source 
specify in the example docker compose to use a container registry link
as a shortcut around building
This commit is contained in:
Andrew Rioux 2025-10-21 14:08:39 -04:00
parent 65bed79678
commit e6530bcf20
Signed by: andrew.rioux
GPG Key ID: 9B8BAC47C17ABB94
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.org
View File

@ -31,12 +31,12 @@ These are the abstractions used to represent beacons and the management of beaco
- Commands are issued to beacon instances or categories - Commands are issued to beacon instances or categories
* Running * Running
Running sparse will require knowing what ports to use for HTTPS access for the beacons. For the most common use case of port 443, the following Docker compose file should work: Running sparse will require knowing what ports to the beacons will connect to via HTTPS. For the most common use case of port 443, the following Docker compose file should work:
#+BEGIN_SRC yaml #+BEGIN_SRC yaml
services: services:
server: server:
image: sparse-server:latest image: gitea.riouxs.co/andrew.rioux/sparse-server:latest
volumes: volumes:
- ./files:/sparse-server - ./files:/sparse-server
ports: ports:
@ -45,7 +45,7 @@ services:
restart: always restart: always
#+END_SRC #+END_SRC
Once deployed, add the first user with the following command: Once deployed, add the first sparse management interface user with the following command:
#+BEGIN_SRC sh #+BEGIN_SRC sh
docker compose exec server /bin/sparse-server user create -n USERNAME docker compose exec server /bin/sparse-server user create -n USERNAME
@ -54,6 +54,7 @@ docker compose exec server /bin/sparse-server user create -n USERNAME
Once deployed, the management interface is available at port 3000 over HTTP. Once deployed, the management interface is available at port 3000 over HTTP.
** Deploying a beacon ** Deploying a beacon
- Sign into the management interface of the sparse C2 server
- Add a listener with a port that matches the port specified in the docker compose and allowed through NAT, and use an IP address that can be routed to this C2 server - Add a listener with a port that matches the port specified in the docker compose and allowed through NAT, and use an IP address that can be routed to this C2 server
- Add a configuration to perform a periodic callback - Add a configuration to perform a periodic callback
- Add a template, selecting the prior listener and configuration. It will need an IP address that corresponds to the LAN that the beacon will be running on - Add a template, selecting the prior listener and configuration. It will need an IP address that corresponds to the LAN that the beacon will be running on