Show newer

Our Server for Continuous Integration has been super helpful, pushing out alerts of Failed Builds ... Here's how we installed Mastodon Server with Compose

Article: lupyuen.org/articles/mastodon.

Compromised `reviewdog` "injected Malicious Code into any CI Workflows using it, dumping the CI Runner memory containing the Workflow Secrets"

wiz.io/blog/new-github-action-

Apache RTOS on QEMU was failing our Continuous Integration Test ... Here's how we fixed it

lupyuen.org/articles/ci7.html

Show thread

ReCamMaster: "re-capture in-the-wild Videos with novel Camera Trajectories"

jianhongbai.github.io/ReCamMas

@lupyuen

also, many actions have side-effects and/or do not document that they only work on Ubuntu-based (public) runners.

When you have self-hosted runners, disk layout, and the OS, might differ. I use CentOS/Fedora.

I also prevent the use of something like apt or dnf installs, as the OS itself is immutable.

@lupyuen what concerns me is how this got propagated to others.

GitHub Actions has no security model or vetting process. Best to pin on a sha, as versions can easily be 'recreated' to contain malicious code. I always fork and/or create my own actions.

GitHub Action `tj-actions/changed-files` "used in over 23,000 repositories, has been compromised ... The compromised Action prints CI/CD Secrets in build logs"

stepsecurity.io/blog/harden-ru

Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.