Adversarial C2 Protocol Implemented in Zig

Automatically publish binaries to nextcloud

Updated the releases directory to use a specific account for releases

+27 -1
+26
.tangled/workflows/build.yml
··· 1 + when: 2 + - event: ["push", "pull_request", "manual"] 3 + branch: ["dev", "master", "test*"] 4 + tag: ["v*"] 5 + 6 + engine: "nixery" 7 + 8 + dependencies: 9 + nixpkgs: 10 + - rclone 11 + git+https://github.com/mitchellh/zig-overlay: 12 + - master 13 + 14 + steps: 15 + - name: "Build" 16 + command: "zig build --release=fast -Dcpu=baseline" 17 + - name: "Publish" 18 + command: | 19 + rclone sync ./zig-out \ 20 + --webdav-url "$RELEASE_NEXTCLOUD_HOST/remote.php/dav/files/$RELEASE_NEXTCLOUD_USER/" \ 21 + --webdav-user "$RELEASE_NEXTCLOUD_USER" \ 22 + --webdav-pass "$RELEASE_NEXTCLOUD_PASS" \ 23 + --webdav-vendor nextcloud \ 24 + :webdav:"zaprus/zaprus-$TANGLED_REF_NAME" \ 25 + -q 26 +
+1 -1
README.md
··· 3 3 This is an implementation of the [Saprus protocol](https://gitlab.com/c2-games/red-team/saprus) in Zig. 4 4 It is useful for developing clients either in Zig, or in any other language using the C bindings. 5 5 6 - Binary releases can be downloaded [here](https://cloud.zambito.xyz/s/cNaLeDz38W5ZcZs). 6 + Binary releases can be downloaded [here](https://cloud.zambito.xyz/s/7jJPTm68Zp3mN8F).