blob: f59baf27057f99af07cf22bc712110c0d58b76e3 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
|
#+TITLE: Installing Hak5's Cloud C2 on Alpine Linux
#+DATE: 2020-09-06T19:08:56-04:00
#+DRAFT: true
#+DESCRIPTION:
#+TAGS[]: alpine linux hak5
#+KEYWORDS[]: alpine linux hak5
#+SLUG:
#+SUMMARY:
I recently purchased some products from [[https://hak5.org][Hak5]], some of which integrate
with their self-hosted service for monitoring your equipment called
the [[https://shop.hak5.org/products/c2][Cloud C2]]. The binaries for it are distributed as (mostly)
statically linked go binaries for several platforms all bundled
together in a zip folder. I decided to run it on one of my servers
which runs one of my favourite Linux distributions, Alpine Linux.
Their website provides a small tutorial for installing C2 on a
systemd-based system, unfortunately it doesn't help me since Alpine
uses the OpenRC init system.
You have the option to purchase the community edition for free from
their shop, after which you'll receive a product registration code via
email. This email will also contain a link to the aforementioned zip
file containing the binaries.
One of the interesting thing I found was that despite my server being
64-bit x86, =c2_community-linux-64= wouldn't work on Alpine
Linux. It's dynamically linked to =/lib64/ld-linux-x86-64.so.2=, which
doesn't exist on musl libc machines. The =c2_community-linux-32=
binary is completely statically linked however.
|
