alpine-cloudc2: write more of article

1 files changed, 23 insertions, 1 deletions

diff --git a/content/posts/alpine-hak5-cloudc2/index.org b/content/posts/alpine-hak5-cloudc2/index.org
index f30db76..f59baf2 100644
--- a/content/posts/alpine-hak5-cloudc2/index.org
+++ b/content/posts/alpine-hak5-cloudc2/index.org
@@ -3,6 +3,28 @@
 #+DRAFT: true
 #+DESCRIPTION:
 #+TAGS[]: alpine linux hak5
-#+KEYWORDS[]:
+#+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.