News for hackers. Stuff that matters.

strenholme

My car came with a cheap low-quality aftermarket combination car stereo and GPS. It would only play music from discs (no USB support), didn’t even support variable bitrate MP3s, and the GPS didn’t know the car’s location half the time.

I finally replaced the head unit with a plastic bracket and a standard old school in-dash stereo system. Much nicer setup.

It’s the cars which can’t have their head unit replaced with a simple stereo which worry me.

Re:WTF Ubuntu? on Monday November 02, 2026 @10:25PM (#50347663)
Rocky was created by one of CentOS’s founders, so is closer to CentOS’s original vision. It’s also closer to upstream RHEL. Alma is more a minor fork from RHEL than a RHEL clone.
Re:WTF Ubuntu? on Monday November 02, 2026 @05:35PM (#50344990)
`unattended-upgrades` was frequently giving me Python warnings in Ubuntu 24.04 about how `fork()` should not be called. `apt-get` has given me issues, years ago, where it would pull up a crappy full screen text UI asking me (usually irrelevant) questions about some update it was doing, and the entire update process was halted by those questions.
Re:WTF Ubuntu? on Monday November 02, 2026 @03:18PM (#50343071)
Well, I did it. This was the straw that broke the camel’s back: I have moved over to Rocky Linux. Took me maybe four hours to do the full transition.

I am more a RedHat user, and Ubuntu never felt really comfortable for me. I don’t like having to do incremental upgrades every two years or so; I would rather do a single big upgrade about once every 7-8 years and have a rock solid development environment. Also, `dnf` is simpler and more stable than the mess of `apt-get` and `unattended-upgrades`.

Re:WTF Ubuntu? on Monday November 02, 2026 @12:42PM (#50340528)
It isn’t quite in RockyLinux yet, but Rocky has a special security repo for getting updates quicker than the RHEL → Rocky security update path:

  sudo dnf --enablerepo=security update
(This command is run every time one needs an urgent security fix right now when using Rocky Linux)

Reboot to have the new kernel

This is how to get the patched kernel right now if running Rocky Linux.

Here is the patched kernel (`rpm -qa | grep kernel-6`)

  kernel-6.12.0-211.69.1.el10_2.x86_64
More information:

https://rockylinux.org/news/2026-05-14-introducing-security-...

https://forums.rockylinux.org/t/cve-2026-98432-any-roadmap/2...

Re:WTF Ubuntu? on Monday November 02, 2026 @10:33AM (#50338237)
Agreed. Two weeks is pathetic. But, yes, I went over to Ubuntu because they were supposed to provide five years of security updated.

When I interviewed with them a couple of years ago, I got the sense there was a lot broken with their culture. It was the best choice back when RedHat/CentOS stopped providing long term security updates, but now that Rocky Linux is around, it’s getting to be time to jump ship again.

Re:WTF Ubuntu? on Monday November 02, 2026 @10:23AM (#50338063)
Ubuntu has a timeline for how long they will provide updates for a given long term distribution release. I moved over to Ubuntu back when CentOS was converted in to a Fedora type release without a long term commitment to providing security fixes.

I might be moving over to Rocky Linux 10.

Re:WTF Ubuntu? on Monday November 02, 2026 @10:19AM (#50337998)
Here is Ubuntu’s webpage on this vulnerability:

https://ubuntu.com/security/CVE-2026-98432

It’s still, over a week after disclosure and patches, unpatched in Ubuntu.

As for me, a part of me wants to move over to Rocky Linux 10.

While Righthaven LLC v. Hoehn did rule that copying and pasting an entire newspaper article is fair use, this ruling was vacated on appeal and instead the lawsuit was nullified because they ruled Righthaven never had the right to bring the lawsuit in the first place. So, yes, one can be sued for copying and pasting a newspaper article verbatim.
Re:Python's experimental JIT to be removed on Wednesday October 28, 2026 @06:44PM (#50281999)
I agree Numba is great. The reason I stay clear of Python is because the Python2 → Python3 transition burned me; the bureaucrats at Debian decided that, since my open source project had one Python2 script in it I wrote many years ago, I had to update my code to make that script a Python3 script. A very toxic and arrogant attitude; old versions of languages should not be killed like that when there is so much code written in the language, and when it can be very difficult [1] to convert a script from Python2 to Python3.

Lua5.1 is much more stable by the virtue that the only updates it code gets are very minor changes to fix any lingering security issues it has (the last Lua5.1 CVE is from 2014).

[1] I guess these days a LLM can do the grunt work of converting a Python2 script to Python3.

[2] There is a project which converts Lua in to native code: https://github.com/samyeyo/clx

Re:Python's experimental JIT to be removed on Wednesday October 28, 2026 @06:39PM (#50281950)
LuaJIT handles double, strings, and dictionaries at near C level performance. Also, arrays, but Lua’s data model has dictionaries and arrays be the same data structure. Lua 5.1 (i.e. LuaJIT) only supports double numeric types,[1] and its strings are immutable.

Lua 5.1’s edge over Javascript and Python is that it’s a lot smaller and simpler.

[1] It’s possible to recompile Lua 5.1 to have the numeric data type be an int, but the standard compiles of Lua5.1 only have double precision floats for numbers. Bitwise operators are technically not part of Lua 5.1, but a library to add support is easy and is usually done: Most Lua5.1 forks including LuaJIT and MediaWiki’s version of Lua5.1 have such a library available. Later versions of Lua have both int and float support.

One legal way to share news stories which generate controversy is to have an AI make a summary of the article, rewording it to remove any copyright from the article (this legal trick only works when the news site in question is reporting on factual events, since facts can’t be copied as per Feist vs. Rural 1991, and I make sure that the summary has “a different sequence, pace, and setting than the original article” as per legal judgments on whether an AI summary of factual events as reported by a news source is subject to copyright).
And, indeed, you can use archive.today to get past the login wall:

https://archive.ph/HcOq2 (This is a link to the post for this article)

(If one’s ISP can’t access archive.today, I find that Firefox’s built in free VPN can usually access them)

Or, you can use on of the various Reddit scrapers, e.g:

https://redlib.catsarch.com/r/Seattle/comments/1xhf6qp/archi...

Here’s a list of Reddit scrapers:

https://github.com/redlib-org/redlib-instances/blob/main/ins...

Personally, as scummy as archive.today is at times, I can generally trust them to have an honest archive about, say, someone’s drunk post before said drunk deletes the post.

Re:Python's experimental JIT to be removed on Wednesday October 28, 2026 @09:31AM (#50273260)
I have moved my more complex scripting from Perl/PHP/Python to Lua for a lot of reasons. One being that Lua (even PUC Lua) is a good deal faster than Python (or /bin/sh); another is that, if I want even more speed, I can use LuaJIT (which keeps me stuck at Lua 5.1, but Lua 5.1 is perfect for my needs).

I wish Lua 5.1 could become part of POSIX; there are a lot of implementations of it out there.

Re:Websites Should Be Printable on Tuesday October 27, 2026 @05:37AM (#50256585)
I fixed it with print-color-adjust:

  background: #eee;
  print-color-adjust: exact;
  -webkit-print-color-adjust: exact;
Re:Websites Should Be Printable on Monday October 26, 2026 @12:35PM (#50246662)
The advantage of a COLR font over SVGs is that they are functionally identical for this use case (indeed, the font in question was converted from SVG vector files) and a good deal more compact to boot.
Re:Websites Should Be Printable on Monday October 26, 2026 @08:41AM (#50242638)
Having horizontal scroll is annoying, yes, but I don’t think it makes a website unusable on a mobile device.

The way to handle elements wide enough to induce horizontal scrolling is to put them in a <div> (or make CSS for the tag in question) and make CSS with overflow-x: scroll; for just that element. An example from one of my webpages:

  pre {max-width: 90vw; overflow-x: scroll;}
Re:Websites Should Be Printable on Monday October 26, 2026 @08:25AM (#50242488)
One issue with making websites printable is that printing, by default, removes background colors and images. So, for the chess diagrams I have on my webpage, I use background colors to have the chessboard be a checkerboard instead of a white background (the chess pieces are a color webfont)—but since web printing removes backgrounds, the chessboards have white backgrounds unless the person printing the webpage chooses “print backgrounds”.

The only way to work around this is to have two sets of chess pieces in the font, one with a white background for pieces on light squares, and one with a colored background for pieces on dark squares.

Printing web pages is rare enough I just assume someone doing that will also click on “print backgrounds”.

(The reason to not use images for the chessboard diagrams is because they use more bandwidth and can’t have usable “dark mode” colors)

Re:Websites Should Be Printable on Monday October 26, 2026 @08:20AM (#50242418)
I did. It’s perfectly readable. What was the issue you experienced on your phone?
Re:Show HN: Steal My Bitcoin on Sunday October 25, 2026 @07:39PM (#50237158)
Well done. It’s important to know the difference between a real world exploitable bug and hot air; as an open source maintainer, over half of the bug reports I get are “hot air” bugs.
I’m surprised this level of surveillance from a smart TV (if this is real; right now the only sources are social media) doesn’t open up Samsung to a lawsuit.

To wit: There was a lawsuit where Susan Clements-Jeffrey sued Absolute Software (Lojack) for a stolen laptop she acquired; Lojack used surveillance to track down the stolen laptop and Susan successfully sued for invasion of privacy (Lojack settled instead of trying to fight it).

Re:CVE Tracker on Friday October 23, 2026 @10:50PM (#50217973)
“Forced” is a little strong. RedHat/Fedora filed a bug report, and I felt it was prudent to have a patch for them to use, even though I explained why they didn’t need to use the patch.
Re:CVE Tracker on Friday October 23, 2026 @07:43PM (#50216897)
It has hit the point where I’ve told people reporting bugs with my software that I won’t acknowledge the bug unless they provide a patch to mitigate the issue.

A lot of these bug reports are incorrectly filed. Let’s look at one issue, which I am sure was found with AI assistance:

CVE-2026-40719

Here’s the issue: An IP authorized to perform recursive queries can cause the DNS server to be non-responsive if it sends hundreds of specially crafted packets a minute (this can be changed to millions of packets a minute if one sets a parameter in the configuration file). Normal service is restored within a minute of the attack being stopped. The workaround would require me to essentially rewrite the recursive part of the DNS server.

Since the DNS server, like any server in a LAN, is already vulnerable to a flooding attack, this is just a flooding attack with extra steps.

I told the guy that was interesting, I’m not being paid enough to rewrite the DNS server to be immune to the attack, and people shouldn’t be using its recursion (it has very limited IPv6 support, for starters), and if they do use its recursion, only authorized IPs (e.g. 127.0.0.1 or 192.168.1.0/24) should be allowed to perform recursion.

It wasn’t a serious enough attack to merit a patch, and anyway the guy reporting the bug didn’t even have the decent courtesy to give me a patch.

The guy responded by filing for a CVE report, incorrectly calling it a “high impact” bug, and I had to make a “patch” which simply disables recursion: https://samboy.github.io/MaraDNS/patches/MaraDNS-CVE-2026-40...

Point being, a lot of these CVE reports out there which supposedly are high impact bugs are trivial things like “someone can overload a server for about one minute if they send hundreds to thousands of specially crafted DOS packets”.

(Today, I got an issue which, as far as I can tell, looks to be a Linux kernel issue and not an issue with my code. I told him to show me how he would patch my code to “fix” the issue, but so far have gotten nothing but crickets)

Re:Quad9 (DNS Resolver) to Exit France on Thursday October 22, 2026 @03:45PM (#50200095)
I’ll bite. I have written a recursive DNS resolver. It’s buggy, mind you, it doesn’t handle improperly configured domains bug-for-bug the way BIND9 does, it doesn’t support IPv6 for resolving records (it can still resolve AAAA records, mind you), but it’s about 80 kilobytes in size, runs nicely on 32-bit systems, and does full DNS resolution starting from the root servers.

Does the fact I have written this resolver make me liable should it not block the domains they listed which may contain copyright infringing content? Am I now required to add these domains, and make them part of a mandatory block list? Will I still be held liable if people can still access these allegedly copyright infringing domains by modifying the source to my program?

Keep in mind that when Quad9 had a similar lawsuit in Germany, they blocked queries from German IPs, but the idiots said Quad9 was still liable because people could use VPNs in Germany to bypass their geoIP blocking.

Quad9 being forced to block these domains will achieve nothing. Will these copyright enforcers now go after Google for 8.8.8.8? Cloudflare for 1.1.1.1? Level3 for 4.2.2.1? Will they go after ISC for BIND? NLnet Labs for Unbound? CZ.NIC for KnotDNS? Me for MaraDNS? Even if they enjoin me from making a recursive resolver which can resolve these domains, that won’t stop anyone and everyone from forking my code (see also: Twitter trying to take down Nitter).

Re:Using AI to reverse engineer hardware on Sunday October 18, 2026 @03:37PM (#50144562)
For people looking for the Lexicon 224 which supposedly is on GitHub, here are two possible links:

https://github.com/joelanders/reflecticon-224

This one needs actual 224 ROMs to run, but we also have...

https://github.com/filipeborato/borato-224

The second one is an 8-line FDN. While the actual 224 used “circle 8” algorithms instead of FDNs (it was Eventide who started using FDNs for reverberation) one can get amazing reverbs from a FDN, e.g. Valhalla Supermassive is a 16-line FDN where the 16 delay line amounts are the only thing that changes between algorithms. I myself have made a good sounding 4-line FDN reverb, and 8 lines was used in one of FreeVerb’s algorithms.

There are some notable improvements, most visibly the slash in 0.

From https://github.com/tonsky/FiraCode

“Fira Code is not only about ligatures. Some fine-tuning is done for punctuation and frequent letter pairs.” Note that without ligature support, a lot of that fine tuning is lost.

Considering the way `/bin/sh` had a bunch of different implementations before POSIX standardization minimized that in the mid-1990s, I wouldn’t be surprised if one of those distinguished spaces from tabs.

That said, the original UNIX V7 implementation of /bin/sh didn’t distinguish different kinds of whitespace:

https://www.in-ulm.de/~mascheck/bourne/v7/

In a lot of places, no.

For example, ligatures in Fira Code cannot be disabled when using the Cygwin terminal in Windows (mintty). In that application, for example, “===” looks like three continuous long lines atop each other in Fira Code, with no way to make it look like three equal signs again.

Older »