Perfect example of a (part of a) security vulnerability being fixed in a commit that doesn’t immediately seem security related and would never be back ported to a stablestale distro

The code which parses the binary MaxMind database after decompression is well guarded as of 2024 but used to look different, potentially providing more attack surface. There is also an interesting commit where a contributor makes adjustments to the gzip::decompress() function which hints at a stack overflow, as the destination buffer was changed from static allocation on the stack to dynamic allocation on the heap, though it was not exploitable due to checks before it is written to

The article on theregister stated

Also inside the uploaded source code was some GPL 2 source code, which renders the not-very-open WCL moot.

Winamp published their code as “open source”. Problem is…

1. It wasn’t open source, it was proprietary but you can see the source code.
2. Their custom license didn’t even allow forks, which is against GitHub TOS
3. The codebase apparently contains proprietary code from third parties that they don’t have the right to relicense.
4. The codebase apparently contains GPL code from third parties that they probably didn’t have the right to make proprietary in the first place

This is a standard feature on any IPv6 enabled network if you enable IPv6 Privacy Extensions

Huh, I misremembered then. I stand corrected.

Notable though that there are specific countries (such as India) where adoption is far higher at 72%

Huh weird that it would be removed, that’s a fair comment.

For Web scraping and other activities by so-called “legitimate” companies to varying degrees, this may be the case. But for general bots, they are generally attempting to scan and probe the entire IPv4 range, since it can be exhaustively checked in a reasonable amount of time and the majority of IPs have hosts on them. Enumerating the entire IPv6 space is quite literally impossible without some external list of hosts known to exist, due to the number of hosts. This happens, but it’s a much higher hanging fruit for an attacker so far fewer will bother. So you generally see few to no continuous probes on things like sshd over IPv6 unless you have a domain name. I’m guessing a lot of bots (in botnets) are dumb old technology that doesn’t even have IPv6.

NAT was always a hacky workaround. And although it effectively ends up functioning as a firewall under normal usage when combined with a typical “drop invalid incoming packets” rule, it was not designed to be a firewall and shouldn’t be assumed to always function as one. A simple accept established, default drop firewall rule should do the trick and should be used on both v4 and v6 regardless of NAT (and probably is on your router already).

If your goal is privacy in the sense of blending in, you can still use NATv6 and this is a good use case for it. This is what VPNs like Mullvad use. If your goal is privacy in the sense of being more difficult to track across sessions, you can enable IPv6 privacy extensions which essentially generates a new IPv6 address for every connection your device makes. So in this sense it’s more private than IPv4

Or you could just… learn to use the modern internet that 60% of internet traffic uses? Not everyone has a dedicated IPv4 anymore, we are in the days of mobile networks and CGNAT. IPv4 exhaustion is here today.

Best to set a firewall rule with nftables to block non-vpn traffic from leaving (you should also do the save for IPv4 traffic to prevent leaks in case the tunnel disconnects)

Wait till you hear about the idiots who unironically make that argument for banning Bitcoin too

Accessing printers? Resolving hostnames of internal hosts? I can’t imagine having a lan without mDNS

https://www.phoronix.com/news/Ben-Skeggs-Joins-NVIDIA

I think this will change. Nvidia hired devs on Nouveau, NVK is coming along, etc

Some of it probably comes from other companies that are unable or unwilling to relicense it even if Nvidia wanted to

Looks like the birdie has escaped phoronix…

In the small chance that this comment is serious, Nvidia is found this because the corporate server-based customers need the ability to troubleshoot and debug the driver.

The actual trade secrets are being moved into the proprietary firmware blob and out of the driver.

They’re already trying. Payment processors and big banks are increasingly refusing to do business with porn companies, and even sites that host nsfw artwork with no actual participants.

I’m pretty sure there’s nearly zero overlap between Monero users/people who actually use cryptocurrency as payment and “crypto bros” (those who use Bitcoin and shitcoins as investments)

PNG is a rather slow algorithm based on the DEFLATE compression from zip/gzip. You could extract to bmp or some other uncompressed format. First, to ensure it is lossless, make sure it supports the video’s pix_fmt without needing conversion.

This would not be the default behavior of yt-dlp. Run yt-dlp -vF <video> to view the sort order used. Acodec should come before abr.

It used to be the behavior of the original youtube-dl, however.

Resampling does not lead to any perceptible quality loss, but encoding to aac with libavcodec’s encoder (as YouTube does) definitely will. At the very least, it cuts all frequencies above 15 kHz which are potentially audible. Opus does not, and 128k opus is usually considered transparent.

I can’t find it but somewhere there’s a very detailed explanation from Monty himself about it

Are you using the very latest version? YouTube changed their site again a few days ago and it broke yt-dlps ability to find all thr formats. Update yt-dlp and it should be back to normal. yt-dlp will prefer the opus when it is available by default.

Opus is much better than (YouTube’s) m4a. m4a is better than mp3 (which is an obsolete 30 year old format). YouTube doesn’t serve mp3 (so creating one means re-encoding), and re-encoding lossy formats always loses quality.