News for hackers. Stuff that matters.
Re:Securing a GitHub repo is a ton of work by yosito on Friday October 21, 2022 @01:40AM (#33284876)
TL;DR turn on signed commits and 2FA, don't commit secrets, and be careful with dependency vulnerabilities.

Doesn't really seem like "a ton of work".

Re:Securing a GitHub repo is a ton of work by stoplying1 on Friday October 21, 2022 @01:50AM (#33284927)
So much advice these days is "do what you're supposed to do instead of being lazy and it works out!".
Re:Securing a GitHub repo is a ton of work by bombolo on Friday October 21, 2022 @01:53AM (#33284943)
> be careful with dependency vulnerabilities

I'm sure all the go/rust binaries/docker containers out there have sensible paths to keep them up to date, right?

Re:Securing a GitHub repo is a ton of work by z33k on Friday October 21, 2022 @02:49AM (#33285248)
> Docker Containers

You could set up trivy.dev scanning as part of your CI pipeline. Patch until your builds are green again :)

Re:Securing a GitHub repo is a ton of work by bombolo on Friday October 21, 2022 @03:27AM (#33285457)
What if I'm a user of a container?
Re:Securing a GitHub repo is a ton of work by bombolo on Friday October 21, 2022 @05:59AM (#33286357)
I tried it on some random containers. It gave me "returned an error". That's it. No details, no nothing.

Doesn't seem something worthy of investing my time into.

Re:Securing a GitHub repo is a ton of work by stoplying1 on Friday October 21, 2022 @08:03PM (#33294245)
It's called CI. Gasp.

You know, the thing you need if you're stuck in 2000's eea deployments. Or the thing you need if you're deploying VMs. Or the thing you need if you're deploying containers. "You know*, the thing you need if you give a shit about your product.

Oh wait, what, you're running a live service, connected to public internet? And you somehow think "lol gotcha rust updates are a thing" is an own? Once again, y'all keep tattling on yourselves!! While acting so smug, I (really don't) need some of that ignorant confidence! *Please!!!!* Feel free to link us to your running live services that you apparently can't run CI/CD for. Its totes fine, right?

Re:Securing a GitHub repo is a ton of work by bombolo on Saturday October 22, 2022 @05:55AM (#33296867)
It is a well known fact. Please don't get angry at me.

> It's called CI

So do you have a CI about every single binary (maybe closed source) that you run?

I don't have a CI for bash, cat, ls, stat, ln, bc, grep… I know they are well maintained and get updates.

If I need a CI as a end user… that thing is already obviously garbage.

> Oh wait, what, you're running a live service, connected to public internet? And you somehow think "lol gotcha rust updates are a thing" is an own? Once again, y'all keep tattling on yourselves!! While acting so smug, I (really don't) need some of that ignorant confidence! Please!!!! Feel free to link us to your running live services that you apparently can't run CI/CD for. Its totes fine, right?

Ping me when you are done making random rageful assumptions thanks.