clevis-pin-tpm2-0.5.3-9.fc41 dbus-parsec-0.5.0-3.fc41 envision-2.0.0-4.20241209git2.0.0.fc41 fido-device-onboard-0.5.1-2.fc41 gotify-desktop-1.3.7-4.fc41 keylime-agent-rust-0.2.7-4.fc41 keyring-ima-signer-0.1.0-17.fc41 libkrun-1.10.1-2.fc41 python-cryptography-43.0.0-4.fc41 rust-afterburn-5.7.0-3.fc41 rust-cargo-vendor-filterer-0.5.17-2.fc41 rust-coreos-installer-0.23.0-2.fc41 rust-crypto-auditing-agent-0.2.3-2.fc41 rust-eif_build-0.2.1-3.fc41 rust-gst-plugin-reqwest-0.13.3-3.fc41 rust-nu-0.99.1-7.fc41 rust-oo7-cli-0.3.3-4.fc41 rust-openssl-0.10.70-1.fc41 rust-openssl-sys-0.9.105-1.fc41 rust-pore-0.1.17-5.fc41 rust-rpm-sequoia-1.7.0-5.fc41 rust-sequoia-keyring-linter-1.0.1-10.fc41 rust-sequoia-octopus-librnp-1.10.0-6.fc41 rust-sequoia-policy-config-0.7.0-3.fc41 rust-sequoia-sop-0.36.0-3.fc41 rust-sequoia-sq-1.1.0-4.fc41 rust-sequoia-sqv-1.2.1-6.fc41 rust-sevctl-0.6.0-4.fc41 rust-snphost-0.5.0-3.fc41 rust-tealdeer-1.7.1-3.fc41 rustup-1.27.1-6.fc41 s390utils-2.35.0-2.fc41

Read Time:1 Minute, 29 Second

FEDORA-2025-f8be7978e3

Packages in this update:

clevis-pin-tpm2-0.5.3-9.fc41
dbus-parsec-0.5.0-3.fc41
envision-2.0.0-4.20241209git2.0.0.fc41
fido-device-onboard-0.5.1-2.fc41
gotify-desktop-1.3.7-4.fc41
keylime-agent-rust-0.2.7-4.fc41
keyring-ima-signer-0.1.0-17.fc41
libkrun-1.10.1-2.fc41
python-cryptography-43.0.0-4.fc41
rust-afterburn-5.7.0-3.fc41
rust-cargo-vendor-filterer-0.5.17-2.fc41
rust-coreos-installer-0.23.0-2.fc41
rust-crypto-auditing-agent-0.2.3-2.fc41
rust-eif_build-0.2.1-3.fc41
rust-gst-plugin-reqwest-0.13.3-3.fc41
rust-nu-0.99.1-7.fc41
rust-oo7-cli-0.3.3-4.fc41
rust-openssl-0.10.70-1.fc41
rust-openssl-sys-0.9.105-1.fc41
rust-pore-0.1.17-5.fc41
rust-rpm-sequoia-1.7.0-5.fc41
rust-sequoia-keyring-linter-1.0.1-10.fc41
rust-sequoia-octopus-librnp-1.10.0-6.fc41
rust-sequoia-policy-config-0.7.0-3.fc41
rust-sequoia-sop-0.36.0-3.fc41
rust-sequoia-sq-1.1.0-4.fc41
rust-sequoia-sqv-1.2.1-6.fc41
rust-sevctl-0.6.0-4.fc41
rust-snphost-0.5.0-3.fc41
rust-tealdeer-1.7.1-3.fc41
rustup-1.27.1-6.fc41
s390utils-2.35.0-2.fc41

Update description:

Update the openssl crate to version 0.10.70 and the openssl-sys crate to version 0.9.105.

This includes a fix for RUSTSEC-2025-0004 / CVE-2025-0977 and rebuilds of all packages that statically link the openssl crate.

Read More

clevis-pin-tpm2-0.5.3-9.fc42 dbus-parsec-0.5.0-3.fc42 envision-2.0.0-4.20241209git2.0.0.fc42 fido-device-onboard-0.5.1-3.fc42 gotify-desktop-1.3.7-4.fc42 keylime-agent-rust-0.2.7-4.fc42 keyring-ima-signer-0.1.0-17.fc42 libkrun-1.10.1-2.fc42 python-cryptography-44.0.0-3.fc42 rust-afterburn-5.7.0-3.fc42 rust-cargo-vendor-filterer-0.5.17-2.fc42 rust-crypto-auditing-agent-0.2.3-3.fc42 rust-eif_build-0.2.1-3.fc42 rust-gst-plugin-reqwest-0.13.3-3.fc42 rust-nu-0.99.1-7.fc42 rust-oo7-cli-0.3.3-4.fc42 rust-openssl-0.10.70-1.fc42 rust-openssl-sys-0.9.105-1.fc42 rust-pore-0.1.17-5.fc42 rust-rpm-sequoia-1.7.0-5.fc42 rust-sequoia-keyring-linter-1.0.1-10.fc42 rust-sequoia-octopus-librnp-1.10.0-6.fc42 rust-sequoia-policy-config-0.7.0-3.fc42 rust-sequoia-sop-0.36.0-3.fc42 rust-sequoia-sq-1.1.0-4.fc42 rust-sequoia-sqv-1.2.1-6.fc42 rust-sevctl-0.6.0-4.fc42 rust-snphost-0.5.0-3.fc42 rust-tealdeer-1.7.1-3.fc42 rustup-1.27.1-6.fc42 s390utils-2.35.0-5.fc42 trustee-guest-components-0.10.0^124.git0061d03-2.fc42

Read Time:1 Minute, 30 Second

FEDORA-2025-12e84667f4

Packages in this update:

clevis-pin-tpm2-0.5.3-9.fc42
dbus-parsec-0.5.0-3.fc42
envision-2.0.0-4.20241209git2.0.0.fc42
fido-device-onboard-0.5.1-3.fc42
gotify-desktop-1.3.7-4.fc42
keylime-agent-rust-0.2.7-4.fc42
keyring-ima-signer-0.1.0-17.fc42
libkrun-1.10.1-2.fc42
python-cryptography-44.0.0-3.fc42
rust-afterburn-5.7.0-3.fc42
rust-cargo-vendor-filterer-0.5.17-2.fc42
rust-crypto-auditing-agent-0.2.3-3.fc42
rust-eif_build-0.2.1-3.fc42
rust-gst-plugin-reqwest-0.13.3-3.fc42
rust-nu-0.99.1-7.fc42
rust-oo7-cli-0.3.3-4.fc42
rust-openssl-0.10.70-1.fc42
rust-openssl-sys-0.9.105-1.fc42
rust-pore-0.1.17-5.fc42
rust-rpm-sequoia-1.7.0-5.fc42
rust-sequoia-keyring-linter-1.0.1-10.fc42
rust-sequoia-octopus-librnp-1.10.0-6.fc42
rust-sequoia-policy-config-0.7.0-3.fc42
rust-sequoia-sop-0.36.0-3.fc42
rust-sequoia-sq-1.1.0-4.fc42
rust-sequoia-sqv-1.2.1-6.fc42
rust-sevctl-0.6.0-4.fc42
rust-snphost-0.5.0-3.fc42
rust-tealdeer-1.7.1-3.fc42
rustup-1.27.1-6.fc42
s390utils-2.35.0-5.fc42
trustee-guest-components-0.10.0^124.git0061d03-2.fc42

Update description:

Update the openssl crate to version 0.10.70 and the openssl-sys crate to version 0.9.105.

This includes a fix for RUSTSEC-2025-0004 / CVE-2025-0977 and rebuilds of all packages that statically link the openssl crate.

Read More

clevis-pin-tpm2-0.5.3-9.fc43 dbus-parsec-0.5.0-3.fc43 envision-2.0.0-4.20241209git2.0.0.fc43 fido-device-onboard-0.5.1-3.fc43 gotify-desktop-1.3.7-4.fc43 keylime-agent-rust-0.2.7-4.fc43 keyring-ima-signer-0.1.0-17.fc43 libkrun-1.10.1-2.fc43 python-cryptography-44.0.0-3.fc43 rust-afterburn-5.7.0-3.fc43 rust-cargo-vendor-filterer-0.5.17-2.fc43 rust-crypto-auditing-agent-0.2.3-3.fc43 rust-eif_build-0.2.1-3.fc43 rust-gst-plugin-reqwest-0.13.3-3.fc43 rust-nu-0.99.1-7.fc43 rust-oo7-cli-0.3.3-4.fc43 rust-openssl-0.10.70-1.fc43 rust-openssl-sys-0.9.105-1.fc43 rust-pore-0.1.17-5.fc43 rust-rpm-sequoia-1.7.0-5.fc43 rust-sequoia-keyring-linter-1.0.1-10.fc43 rust-sequoia-octopus-librnp-1.10.0-6.fc43 rust-sequoia-policy-config-0.7.0-3.fc43 rust-sequoia-sop-0.36.0-3.fc43 rust-sequoia-sq-1.1.0-4.fc43 rust-sequoia-sqv-1.2.1-6.fc43 rust-sevctl-0.6.0-4.fc43 rust-snphost-0.5.0-3.fc43 rust-tealdeer-1.7.1-3.fc43 rustup-1.27.1-6.fc43 s390utils-2.35.0-5.fc43 trustee-guest-components-0.10.0^124.git0061d03-2.fc43

Read Time:1 Minute, 30 Second

FEDORA-2025-6dd003943f

Packages in this update:

clevis-pin-tpm2-0.5.3-9.fc43
dbus-parsec-0.5.0-3.fc43
envision-2.0.0-4.20241209git2.0.0.fc43
fido-device-onboard-0.5.1-3.fc43
gotify-desktop-1.3.7-4.fc43
keylime-agent-rust-0.2.7-4.fc43
keyring-ima-signer-0.1.0-17.fc43
libkrun-1.10.1-2.fc43
python-cryptography-44.0.0-3.fc43
rust-afterburn-5.7.0-3.fc43
rust-cargo-vendor-filterer-0.5.17-2.fc43
rust-crypto-auditing-agent-0.2.3-3.fc43
rust-eif_build-0.2.1-3.fc43
rust-gst-plugin-reqwest-0.13.3-3.fc43
rust-nu-0.99.1-7.fc43
rust-oo7-cli-0.3.3-4.fc43
rust-openssl-0.10.70-1.fc43
rust-openssl-sys-0.9.105-1.fc43
rust-pore-0.1.17-5.fc43
rust-rpm-sequoia-1.7.0-5.fc43
rust-sequoia-keyring-linter-1.0.1-10.fc43
rust-sequoia-octopus-librnp-1.10.0-6.fc43
rust-sequoia-policy-config-0.7.0-3.fc43
rust-sequoia-sop-0.36.0-3.fc43
rust-sequoia-sq-1.1.0-4.fc43
rust-sequoia-sqv-1.2.1-6.fc43
rust-sevctl-0.6.0-4.fc43
rust-snphost-0.5.0-3.fc43
rust-tealdeer-1.7.1-3.fc43
rustup-1.27.1-6.fc43
s390utils-2.35.0-5.fc43
trustee-guest-components-0.10.0^124.git0061d03-2.fc43

Update description:

Update the openssl crate to version 0.10.70 and the openssl-sys crate to version 0.9.105.

This includes a fix for RUSTSEC-2025-0004 / CVE-2025-0977 and rebuilds of all packages that statically link the openssl crate.

Read More

mpdecimal-4.0.0-2.fc43 python3.10-3.10.16-4.fc43 python3.11-3.11.11-4.fc43 python3.12-3.12.9-2.fc43 python3.13-3.13.2-2.fc43 python3.14-3.14.0~a4-3.fc43

Read Time:21 Second

FEDORA-2025-26a9109b0e

Packages in this update:

mpdecimal-4.0.0-2.fc43
python3.10-3.10.16-4.fc43
python3.11-3.11.11-4.fc43
python3.12-3.12.9-2.fc43
python3.13-3.13.2-2.fc43
python3.14-3.14.0~a4-3.fc43

Update description:

Update mpdecimal to 4.0.0. Rebuild Pythons.

Automatic update for python3.13-3.13.2-1.fc43.

Read More

Thailand cuts power and internet to areas of Myanmar to disrupt scam gangs

Read Time:20 Second

Well, this is a different approach to the scam problem…

The government of Thailand has cut the power supply to areas near its border with Myanmar that are known to host brutal scam compounds. These heavily-guarded fraud factories house armies of people, coerced into defrauding innocent people through bogus investment and romance-baiting scams.

Read more in my article on the Hot for Security blog.

Read More

AIs and Robots Should Sound Robotic

Read Time:4 Minute, 19 Second

Most people know that robots no longer sound like tinny trash cans. They sound like Siri, Alexa, and Gemini. They sound like the voices in labyrinthine customer support phone trees. And even those robot voices are being made obsolete by new AI-generated voices that can mimic every vocal nuance and tic of human speech, down to specific regional accents. And with just a few seconds of audio, AI can now clone someone’s specific voice.

This technology will replace humans in many areas. Automated customer support will save money by cutting staffing at call centers. AI agents will make calls on our behalf, conversing with others in natural language. All of that is happening, and will be commonplace soon.

But there is something fundamentally different about talking with a bot as opposed to a person. A person can be a friend. An AI cannot be a friend, despite how people might treat it or react to it. AI is at best a tool, and at worst a means of manipulation. Humans need to know whether we’re talking with a living, breathing person or a robot with an agenda set by the person who controls it. That’s why robots should sound like robots.

You can’t just label AI-generated speech. It will come in many different forms. So we need a way to recognize AI that works no matter the modality. It needs to work for long or short snippets of audio, even just a second long. It needs to work for any language, and in any cultural context. At the same time, we shouldn’t constrain the underlying system’s sophistication or language complexity.

We have a simple proposal: all talking AIs and robots should use a ring modulator. In the mid-twentieth century, before it was easy to create actual robotic-sounding speech synthetically, ring modulators were used to make actors’ voices sound robotic. Over the last few decades, we have become accustomed to robotic voices, simply because text-to-speech systems were good enough to produce intelligible speech that was not human-like in its sound. Now we can use that same technology to make robotic speech that is indistinguishable from human sound robotic again.

A ring modulator has several advantages: It is computationally simple, can be applied in real-time, does not affect the intelligibility of the voice, and—most importantly—is universally “robotic sounding” because of its historical usage for depicting robots.

Responsible AI companies that provide voice synthesis or AI voice assistants in any form should add a ring modulator of some standard frequency (say, between 30-80 Hz) and of a minimum amplitude (say, 20 percent). That’s it. People will catch on quickly.

Here are a couple of examples you can listen to for examples of what we’re suggesting. The first clip is an AI-generated “podcast” of this article made by Google’s NotebookLM featuring two AI “hosts.” Google’s NotebookLM created the podcast script and audio given only the text of this article. The next two clips feature that same podcast with the AIs’ voices modulated more and less subtly by a ring modulator:

Raw audio sample generated by Google’s NotebookLM

Your browser does not support the audio element.

Audio sample with added ring modulator (30 Hz-25%)

Your browser does not support the audio element.

Audio sample with added ring modulator (30 Hz-40%)

Your browser does not support the audio element.

We were able to generate the audio effect with a 50-line Python script generated by Anthropic’s Claude. One of the most well-known robot voices were those of the Daleks from Doctor Who in the 1960s. Back then robot voices were difficult to synthesize, so the audio was actually an actor’s voice run through a ring modulator. It was set to around 30 Hz, as we did in our example, with different modulation depth (amplitude) depending on how strong the robotic effect is meant to be. Our expectation is that the AI industry will test and converge on a good balance of such parameters and settings, and will use better tools than a 50-line Python script, but this highlights how simple it is to achieve.

Of course there will also be nefarious uses of AI voices. Scams that use voice cloning have been getting easier every year, but they’ve been possible for many years with the right know-how. Just like we’re learning that we can no longer trust images and videos we see because they could easily have been AI-generated, we will all soon learn that someone who sounds like a family member urgently requesting money may just be a scammer using a voice-cloning tool.

We don’t expect scammers to follow our proposal: They’ll find a way no matter what. But that’s always true of security standards, and a rising tide lifts all boats. We think the bulk of the uses will be with popular voice APIs from major companies—and everyone should know that they’re talking with a robot.

This essay was written with Barath Raghavan, and originally appeared in IEEE Spectrum.

Read More