Skip to main content

Automattic Inc. Claims It Owns the Word 'Automatic'

3 months ago
An anonymous reader shares a report: Automattic, the company that owns WordPress.com, is asking Automatic.CSS -- a company that provides a CSS framework for WordPress page builders -- to change its name amid public spats between Automattic founder Matt Mullenweg and Automatic.CSS creator Kevin Geary. Automattic has two T's as a nod to Matt. "As you know, our client owns and operates a wide range of software brands and services, including the very popular web building and hosting platform WordPress.com," Jim Davis, an intellectual property attorney representing Automattic, wrote in a letter dated Oct. 30. "Automattic is also well-known for its longtime and extensive contributions to the WordPress system. Our client owns many trademark registrations for its Automattic mark covering those types of services and software," Davis continued. "As we hope you can appreciate, our client is concerned about your use of a nearly identical name and trademark to provide closely related WordPress services. Automattic and Automatic differ by only one letter, are phonetically identical, and are marketed to many of the same people. This all enhances the potential for consumer confusion and dilution of our client's Automattic mark."

Read more of this story at Slashdot.

msmash

AMD Confirms Zen 5 RNG Flaw: When ‘Random’ Isn’t Random Enough

3 months ago
by George Whittaker

AMD has officially confirmed a high-severity security vulnerability in its new Zen 5–based CPUs, and it’s a nasty one because it hits cryptography right at the source: the hardware random number generator.

Here’s a clear breakdown of what’s going on, how bad it really is, and what you should do if you’re running Zen 5.

What AMD Just Confirmed

AMD’s security bulletin AMD-SB-7055, now tracked as CVE-2025-62626, describes a bug in the RDSEED instruction on Zen 5 processors. Under certain conditions, the CPU can:

  • Return the value 0 from RDSEED far more often than true randomness would allow

  • Still signal “success” (carry flag CF=1), so software thinks it got a good random value

The issue affects the 16-bit and 32-bit forms of RDSEED on Zen 5; the 64-bit form is not affected.

Because RDSEED is used to feed cryptographically secure random number generators (CSPRNGs), a broken RDSEED can poison keys, tokens, and other security-critical values.

AMD classifies the impact as:

Loss of confidentiality and integrity (High severity).

How the Vulnerability Works (In Plain English) What RDSEED Is Supposed to Do

Modern CPUs expose hardware instructions like RDRAND and RDSEED:

  • RDRAND: Gives you pseudo-random values from a DRBG that’s already been seeded.

  • RDSEED: Gives you raw entropy samples suitable for seeding cryptographic PRNGs (it should be very close to truly random).

Software like TLS libraries, key generators, HSM emulators, and OS RNGs may rely directly or indirectly on RDSEED to bootstrap secure randomness.

What’s Going Wrong on Zen 5

On affected Zen 5 CPUs:

  • The 16-bit and 32-bit RDSEED variants sometimes return 0 much more often than a true random source should.

  • Even worse, they simultaneously report success (CF=1), so software assumes the value is fine rather than retrying.

In cryptographic terms, this means:

  • Entropy can be dramatically reduced (many key bits become predictable or even fixed).

  • Keys or nonces derived from those values can become partially or fully guessable.

Go to Full Article
George Whittaker