Johannes Schnatterer
banner
schnatterer.info
Johannes Schnatterer
@schnatterer.info
25 followers 14 following 54 posts
Software engineer, author, speaker. Field CTO of Cloudogu. My particular interests are #k8s, #GitOps, #PlatformEngineering, #o11y, #IaC, #DevOps technical leadership and of course #FLOSS/ #FOSS/ #OSS. I like owning my data and devices.
Posts Media Videos Starter Packs
I think we all recognize that AI changes the way we produce code.
To me it seems it wides the gap what a single dev can reach in terms of output.
The HN discussions shows mixed feelings about this:
news.ycombinator.com/item?id=4550...

What are your thoughts?
Vibe engineering | Hacker News
news.ycombinator.com
Using Coding Agents in combination with software engineering best practices: Unit testing, concept-first, version control, code review, manual testing, etc. for higher output.
TIL the term #VibeEngineering" as opposite of #VibeCoding, proposed by @simonwillison.net

While the term does not feel intuitive to me, the idea does:
Vibe engineering | Hacker News
news.ycombinator.com
⚠️ Recommendations:
At least run: npm/yarn/pnpm audit

npm config set ignore-scripts true --global

What else?

Does anyone know of any specific tooling to check if impacted?
🗓️ 17 Sep: attack #Shai-Hulud / #CrowdStrike / #tinycolor
Self-replicating worm 😱 started by briefly infecting tinycolor and packages by vendor CrowdStrike. Exposes code and secrets via GitHub and tries to propagate to other packages via npm tokens. Now impacts nearly 500 packages.
TLDR recent #npm supply chain attacks

🗓️ 26 Aug: #nx packages compromised stealing SSH keys, npm tokens, and .gitconfig files and weaponized AI CLI tools 😱 upload to repo named #S1ngularity

HackerNews: news.ycombinator.com/item?id=4503...
GHSA: github.com/nrwl/nx/secu...
Reposted by Johannes Schnatterer
Yep, I've been pwned. 2FA reset email, looked very legitimate.

Only NPM affected. I've sent an email off to @npmjs.bsky.social to see if I can get access again.

Sorry everyone, I should have paid more attention. Not like me; have had a stressful week. Will work to get this cleaned up.
@bad-at-computer.bsky.social Hey. Your npm account seems to have been compromised. 1 hour ago it started posting packages with backdoors to all your popular packages.
Shouldn't this be opt in? 🧐😱

Now is the time to opt out.

#linkedin #ai #gdpr
The switch was really easy.

The only customization I did was to enable the constant reminder of my cloud account and node.js version.

Having the time displayed as part of the prompt also turns out useful when scrolling back up later.

github.com/schnatterer/...
github.com
Anyone still using #powerlevel10k #zsh theme?
It has been on "life support" > 1 year.

I had been using it for almost 5 years because of instant prompt.
Now switched to #starship, which I already had an eye on back then.

Is there a reason not to use starship?
What common (zsh) themes are there?
#docker or #podman?

A polarised discussion 👇
news.ycombinator.com/item?id=4513...

Does not motivate me to give podman another go.
I like being efficient and not struggle with things I wouldn't have to with docker 😐

Can anyone share podman success stories?
Anyway, here is my workaround (to be executed on the host) 😱

sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.slapd

Anyone ever had similar problems and have a better solution?
Presumably, this is a limitation of k3d running in a container itself, leading to kubelet lacking privilege to modify AppArmor profiles on host.
Eventually found out that my host system has an AppArmor profile for slapd.
However, I was unable to ignore it via k8s' annotation or securityContext setting for unconfined AppArmor profile.
My LDAP pod failed to start with permission denied errors when the startup script used slapadd. These would not go away, even as root.
As a longtime fan of local #k8s clusters for fast feedback (especially #k3d ),I've just faced my first real challenge: deploying #LDAP 😅
(caused by apparmor and nested containerization)
Anyway, here is my workaround (to be executed on the host) 😱

sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.slapd

Anyone ever had similar problems and have a better solution?
Presumably, this is a limitation of k3d running containerized itself, leading to kubelet lacking privilege to modify AppArmor profiles on host.
My LDAP pod failed to start with permission denied errors when the startup script used slapadd.

Eventually found out that my host system has an AppArmor profile for slapd.
However, I was unable to ignore it via k8s' annotation or securityContext setting for unconfined AppArmor profile.
TIL: #helm image plugin shows all images for a chart, even respecting dependencies 🧐

github.com/nikhilsbhat/...