Not directly. UEFI itself only supports mounting a minimal set of filesystems. That’s why your EFI system partitiion needs to be FAT32, for example, and why the kernel and initial ramdisk are also located there. UEFI mounts the ESP and executes the bootloader, which then loads the kernel (located at ESP/vmlinuz-linux on Arch) and initial ramdisk (ESP/initramfs-linux.img) into memory. The initial ramdisk is a compressed image of an early root filesystem that contains the tools and drivers necessary to boot the full system, including the filesystem drivers for ext4/btrfs/whatever.

You could build an EFI program that natively supports different filesystems, though.

Yes, it was a stroke of genius to label their mediocre confectionery as “coffee”, although it can lead to near fatalities when someone who’s only ever had Starbucks encounters real coffee for the first time.

Still, my point stands. That website is like 20% useful content, 40% flair, and 40% wasted space.

That website is atrocious. It’s the web design equivalent of shoving five kilograms of sugar and whipped cream in a cup of coffee.

The highest address of a subnet is the broadcast address. You can’t assign it to a host.

I might be able to snag that same model with an i5-6500 for around 60€. Could you tell me more about your experience with it? In particular, how are the thermals and the power consumption, can it handle 1Gb/s on both ethernet ports, and have you encountered any compatibility issues with OPNsense?

The borrow checker is a feature in the compiler. It only ensures that the source code doesn’t violate its rules at compile time, and if it does, stops the compilation and shows an error message. If the borrow checker is disabled, the code will be compiled even if borrowing rules are violated (as long as the source code is otherwise valid).

In short: removing the borrow checker turns Rust into C.

It’s that damn borrow checker again! Try the rust-- compiler, it disables that antifeature.

Since your last post here, a new rule has been introduced. You must disclose AI usage in both the title and in the post body.

The collarbones, and the way the skin gets sucked in between.

Four… Fucking… Pixels?

The working hypothesis is that this was some sort of debug or test key that was never meant to be used in production, being used in production.

The encryption that SSL/TLS provides (that puts the “secure” in HTTPS) uses a public–private key pair and a specific mathematical function. Generating the key pair requires a cryptographically secure random number that is impossible or very difficult to guess, which must be kept secret at all times. If this random number is leaked or guessed by a malicious actor, the private key can be reconstructed and used to impersonate a website or break the encryption.

The security of the encryption comes from the fact that the function is easy to calculate one way, but difficult to calculate its inverse. To demonstrate: multiplying the prime numbers 88117 and 44543 is easy, but the inverse, factorizing the semiprime 3924995531, is extremely lengthy in comparison.

One of the factors that determine the security of the key is the size of the number, i.e. the number of digits. In this case, a proper key should’ve had a length of 384 bits (or 116 decimal digits). In reality, the keys that eMudhra used had eight bits, which can only represent 256 possible values, and can be easily guessed even by brute force. The specific private keys were the numbers 4, 56, 66, 115, 155, 156, 230, and 237.

Currently having a very fun day at work.

Fortunately our own certificates are unaffected, but it’s the autumn break and most of the staff are absent and incommunicado.

I have no experience with MAUI, I only heard that it was cross-platform.

Then what other toolkit has stable .NET bindings on both Linux and Windows? This might become relevant to me professionally in the near future.

Adding dependencies, adding complexity, adding points of failure… not to mention that the first sentence in the readme literally says it’s an experimental project. Not something that a production software should ever be built upon.

Except Mono implements the Windows-only .NET Framework, but PDN targets .NET 9. I have no idea how those two could be used at the same time for different parts of the app, what kinds of issues may arise from it, or if it can be done at all. Again, it sounds simple, but it never is.

compiling it for .NET on Linux

It always sounds so simple for the layperson. Just looking through the list of DLLs in the portable ZIP, PDN uses Windows Forms (System.Windows.Forms namespace), which, as far as I understand, isn’t included in the cross-platform releases of .NET. They’d have to rebuild the entire UI with .NET MAUI or some other cross-platform toolkit. Then there are lots of other bundled libraries that may or may not work in a .NET-on-Linux environment.

Releasing and then supporting a second platform is never as easy as just compiling the executable. Figuring out the quirks and differences of various systems, especially one as heterogenous as the Linux ecosystem, is a drain on resources that small development studios often can’t afford. Raiguard (hallowed be his name), one of the developers of Factorio, and the person who is single-handedly maintaining the Linux-native build, wrote a blog post about its challenges.

No, we were taught about HTTP, the fundamentals of hypertext and how it gets rendered, how embedded code (Flash at the time; yes, I’m old) runs in the browser, and the concept of the digital footprint. The cybersecurity implications were obvious.

Actually, I have to correct myself. Some of this was taught in the 7th or 8th year of primary school, around ages 12-14. I was fortunate to be born in a country, at the right time, where the public education system was still worth something. My heart bleeds when I hear of what goes on across the ocean.

Not me. Call me old-fashioned, but I prefer organic.