Agreguesi i feed

The majority of Linux breaches don't begin at root.

Usually I blog about new additions to the GNOME wallpapers after a release, to give some behind the scenes look on how they were produced. This time I'm asking for some feedback beforehand.

Pixels has shipped as a wallpaper before. The wallpaper landed back in 2021 and keeps getting refreshed as new Circle apps join the lineup, and 47 added LCD and LCD-rainbow, revealing the curator's pixelart kink.

The raw material is a side project years in the making — app icons redrawn as chunky pixels (Pixels, Mo' Pixels, Revert That Vector Nonsense!).

The idea and layout remains the same as the old wallpaper. This time that's more than two variants though. The old Adwaita default used to cycle morning, day and night variants through a slideshow. While we switched to the dark/light variants, the format is still understood today. Thus pixelart comes in not 2, not 3, but 9 color variants. And here's where I'd like your feedback. Do you like the focus on contrast and having the whole set with dark background colors? Should there be more bright colors in the mix? Do you think the grain goes against the spirit of the pixel art? Is the small grid too toned down with the depth fog?

As always, the Blender project files are available in wallpaper-assets if you want to poke at the node setup yourself:

As with any wallpaper, don't judge it based on a preview, regardless of how large you view it. Apply it, use it. The most straightforward way to test GNOME development is with GNOME OS. It ships pixels and all the other wallpapers.

The fact this movie tanked at the box office just makes the ride all the more enjoyable. I had a bad headache and had to call off the screening with a friend yesterday. Thursday is when the movies rotate in our part of the world where we use the un-American units, so I thought I'd missed yet another great cinematic experience. Luckily they still showed it in a small neighboring town, to the two of us and two other people, with an introduction by a charming young person.

I don't remember anything these days, but I clearly remember when I saw Dr. Strangelove in Amherst, NH, in 1993. I was completely taken by the humor, despite thinking I'd never enjoy an ancient movie like that. It's probably way longer between my viewing and today than it was between then and the actual production of it. I don't wanna check.

Anyhow, this is masterfully done cinema, and all four of us laughed out loud at the horrors we saw. Absolute must-see.

★★★★★

Say a developer queues a build on a shared Linux host.

Let's Encrypt switched its staging service to 64-day certificates on October 14, 2026.

A developer clones a repository, changes into it, and opens Zellij.

On September 22 we released systemd v262 into the wild.

In the weeks leading up to that release (and since then) I have posted a series of serieses of posts to Mastodon about key new features in this release, under the #systemd262 hash tag. In case you aren't using Mastodon, but would like to read up, here's a list of all 35 posts:

• Post #1: Word List Based Hostname Patterns
• Post #2: Extended Attributes on Socket Inodes
• Post #3: Varlink Socket Tagging & varlinkctl list-sockets
• Post #4: Machine Tags from udev/hwdb
• Post #5: systemd-sysupdate's installdb
• Post #6: Signed systemd-report Reports
• Post #7: CLI Introspection via --introspect-cli
• Post #8: fscrypt v2 Support in systemd-homed
• Post #9: Read-Only ESP Support in systemd-boot/systemd-stub
• Post #10: Recovery Key Enrollment on First Boot & Varlink IPC for systemd-cryptenroll
• Post #11: Rogue TPM Protection for LUKS Enrollments
• Post #12: Encrypted + Verity Protected DDIs
• Post #13: FONT_SCALE= in /etc/vconsole.conf
• Post #14: Static, Single-Binary Service Manager Builds
• Post #15: Intel TDX CoCo Support in systemd-vmspawn
• Post #16: Varlink IPC for systemd-sysinstall
• Post #17: systemd-report as Varlink Service & New Metrics
• Post #18: Sessions as Inhibitors via pam_systemd's inhibit=
• Post #19: NvPCR Rework
• Post #20: bootctl link-auto
• Post #21: systemd-sysupdate Completion Hooks
• Post #22: /etc/clonetab
• Post #23: Atomically Enqueuing Multiple Jobs
• Post #24: Following the Journal via Varlink
• Post #25: Coredumps via the Kernel's New Socket Protocol
• Post #26: Hardware-Suggested systemd-sysupdate Features/Components
• Post #27: ActivatingConcurrencyMax=
• Post #28: Restarting/Reloading Units on confext/sysext Application
• Post #29: System Credentials for CoCo VMs in systemd-vmspawn
• Post #30: Persisting the TPM EK
• Post #31: systemd.firstboot=headless
• Post #32: RestartRandomizedDelaySec=
• Post #33: systemd.credentials_boot_policy=
• Post #34: systemctl kexec --kernel-cmdline-reuse
• Post #35: PCR Signature Policyrefs

I intend to do a similar series of serieses of posts for the next systemd release (v263), hence if you haven't left tech Twitter for Mastodon yet, now is the opportunity. My series for v263 will begin in a few weeks most likely, under the #systemd263 hash tag.

In case you are interested, here is the corresponding blog story for systemd v261, here for v260, here for v259, here for v258, here for v257, and here for v256.

Hello, I am pleased to announce a new Cambalache release.

Cambalache is a WYSIWYG (What You See Is What You Get) tool that allows you to create and edit user interfaces for Gtk 4 and 3 applications.

This new version depends on GNOME SDK 51 and includes all new properties and types from Gtk and Adwaita! It also removes the file hash from the project file which should prevent unnecessary git conflicts.

In case you missed it, you can read more about Cambalache in version 1.0 release blog.

Cambalache’s First Major Milestone!

Help us continue developing

If you find this application useful you can support it’s development by contributing on Liberapay or Patreon

Where to get it?

From Flathub

flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo flatpak install flathub ar.xjuan.Cambalache

or directly from gitlab

git clone https://gitlab.gnome.org/jpu/cambalache.git Matrix channel

Have any question? come chat with us at #cambalache:gnome.org

Mastodon

Follow me in Mastodon @xjuan to get news related to Cambalache development.

As usual happy coding!

Imagine releasing a software solution into the market only to realize the user cannot use the app properly. They have been reporting numerous bugs, which has lowered your reputation and reliability.

Business email compromise has long involved targeted impersonation and fraudulent payment requests. Generative AI can make those established tactics faster to prepare and more convincingGenerative AI has turned BEC into a tailored, low-noise operation that mimics writing style, voice, and even video presence. This piece looks at what's actually changed under the hood, what defenders are testing in response, and why so many organizations are still structurally unprepared for it.

If you run Postfix, Exim, or OpenSMTPD on Linux, DKIM is already your problem. The private key lives on your box. If that key leaks or signing stops, your domain reputation moves without you.

You've probably trained your team to look for red flags. Odd sender names, urgent language, mismatched links. But a well-crafted spoofed email won't trip any of those wires. It looks legitimate, sounds legitimate, and often comes from a domain that passes every automated check you throw at it.

Template email is more than a design tool in the campaign of consistent communication; it also has a hidden danger.

Email threats have long outgrown spamming and obvious phishing. Attackers now exploit trust itself. They impersonate internal users, hijack legitimate threads, and abuse misconfigured configurations. Defenses like perimeter filtering or static rules are not adequate any longer. A Zero Trust model redefines the issue by eliminating implicit trust at all phases of email processing. This shift is especially important in modern Linux mail environments where services are often modular, network-exp...

QR codes were originally designed for industrial logistics. They were optimized for efficiency, not security. In recent years, they have become embedded across enterprise workflows, authentication flows, ticketing systems, packaging, and internal documentation systems. That expansion has created a new attack surface.

Suspicious emails rarely confess in the body. The clues live in headers, MIME parts, and tiny inconsistencies between what a message claims and what it actually delivers. If your team can read those signals quickly—and connect them to the attachment—you’ll cut off credential theft, loaders, and ransomware without slowing operations.

A threat report names an address in your server logs. Should you block it?

Users who can read logs or create Kubernetes resources could obtain Google Cloud credentials they are not allowed to read directly, according to two new reports.

Vim has patched two flaws that could let a malicious file run commands as a user reads or edits it.

An attacker-written template can run commands on a web server under the conditions in an expanded Handlebars advisory.