23
top 5 comments
sorted by: hot top controversial new old
[-] halfdane@lemmy.world 11 points 2 days ago

Read the article so you don't have to:

Unlike the title suggests, the docker images they found won't leak your credentials when you use them, but already contain the credentials of whoever created the image (p.e. through .env files that were accidentally added to the image).

While it contains the valuable reminder to avoid long lived credentials (like API - keys) or use secrets-stores, this "leak" is on the same level as accidentally pushing confidential information to github IMHO.

Fix: have both .gitignore and .dockerignore files and make sure they both contain .env. You use .env and don't hardcode your secrets, right?

[-] bjoern_tantau@swg-empire.de 4 points 2 days ago

My .dockerignore is a link to .gitignore.

[-] halfdane@lemmy.world 2 points 1 day ago

That's ... actually really clever! I'll steal that idea ๐Ÿ˜„

[-] scytale@piefed.zip 2 points 2 days ago

Also, don't rawdog publicly available docker images and make sure image scanning and vulnerability scans are part of your SDLC.

[-] folekaule@lemmy.world 2 points 2 days ago

This 100%. For a little extra help, there are tools such as gitleaks to help. I suggest setting one up in a pre commit hook.

this post was submitted on 11 Dec 2025
23 points (100.0% liked)

Cybersecurity

8776 readers
7 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Community Rules

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 2 years ago
MODERATORS