queue

Here's the basics of my set up for what I can bring around:

• A Crucial 1TB M.2 Drive
• A M.2 Drive Enclosure that has USB 3.1 Gen 2 output So with these together are desktop performance in a small thing. It is not a flash drive that just gets ruined in like 3 months of constant use.

And with these, I use a Ventoy set up called Medicat. I love it, and there's no issue with it for me, besides that Medicat/Microsoft requires NTFS for Windows stuff. Aside from standard NTFS bullshit, it's wonderful.

Since I have so much space, I had the idea of storing a Linux set up for on the go use on any laptop/computer without needing to sign into 10 websites for one time use. Here's my two methods of how to do it:

• Make a persistent data block for Fedora/Ubuntu/etc. and make a Live ISO point to it, then boot from Ventoy into the ISO, which then handles mounting the "drive".
• Clear a space on the drive, install a distro like Fedora/Debian and encrypt it, allowing me to just run apt upgrade and move on like a normal PC.

Here's the upsides and downsides to both that I can see, just thinking about it.

Persistence:

• ✅ Don't need to fuck with partitions of NTFS, last time I tried to shrink the drive NTFS had a breakdown and I couldn't fix it.
• ✅ Can expand the persistence as time goes on
• ❌ NTFS constantly has issues with me, where I can cleanly eject the drive but I need to run ntfsfix to make it work again, and I don't know when that will happen in the future.
• ❓ Not sure how it will go with Arch Linux, but that might be a bad choice for a drive I boot into for fun/infrequently.

Partition and full install:

• ✅ Easier to just get going, point an ISO to install there and good to go.
• ✅ Easier to upgrade to new packages/editions, instead of downloading new ISOs and pointing it each time. I'm unsure if it would let me use a .dat file from Fedora 36 for Fedora 40, for example.
• ✅ I can encrypt it so I don't need to worry about people nabbing it and messing with personal files.
• ✅ I can use something like ext4 or btrfs, so I don't need to rely on NTFS.
• ❌ Trying to resize NTFS was really fucky, and felt like I was breaking something. I did break it, and had to reinstall Medicat/Ventoy.
• ❓ I'm unsure of how to boot from it and keep Medicat/Ventoy as the main option. Maybe create a file on Ventoy to boot the distro? Maybe it varies from BIOS to BIOS?

Wanting to hear the thoughts from people smarter than me, maybe have done this before. I just want to make it clear It's not a USB flash drive, this won't break randomly from one too many R/Ws.

Hello! The TL;DR is:

I have an m.2 drive that is in a sturdy enclosure that has 1 TB. I have Ventoy with Medicat on there, with some backups of important data.

I still have a lot of room left on there, so I was thinking what else I could do, and the idea of basically installing a Linux Distro to a chunk of free space on there. Maybe Debian/Fedora or Arch.

Is there anything I should be aware of to help not break that system or rapidly kill the drive? It's not a USB flash drive, it's a M.2 drive that's put on a small board that then allows it to talk via USB C/Thunderbolt.

EDIT: Just to be sure, if I use Ventoy's EFI, do I need to be worried about a conflict with the bootloader of the Linux install?

Firmware security company Binarly on Wednesday disclosed the details of an attack method that can be used to compromise many consumer and enterprise devices by leveraging malicious UEFI logo images.

The attack method, dubbed LogoFAIL, exploits vulnerabilities in the image parsers used by the UEFI firmware to display logos during the boot process or in the BIOS setup. Getting the affected parsers to process a specially crafted image can enable the attacker to hijack the execution flow and run arbitrary code.

Hackers can use the LogoFAIL attack to compromise the entire system and bypass security measures such as Secure Boot.

“These vulnerabilities can compromise the entire system’s security, rendering ‘below-the-OS’ security measures like any shade of Secure Boot ineffective, including Intel Boot Guard. This level of compromise means attackers can gain deep control over the affected systems,” Binarly explained.

Binarly’s analysis showed that UEFI vendors use various types of parsers for BMP, PNG, JPEG, GIF and other types of images. The security firm’s research targeted firmware from Insyde, AMI and Phoenix and led to the discovery of two dozen vulnerabilities, more than half of which have been assigned a ‘high severity’ rating.

The impacted firmware is shipped with hundreds of consumer and enterprise computer models — including x86 and ARM-based devices — made by companies such as Acer, Dell, Framework, Fujitsu, Gigabyte, HP, Intel, Lenovo, MSI, Samsung, and Supermicro. This means millions of devices worldwide could be exposed to attacks.

A LogoFAIL attack can be launched by abusing the firmware update procedure to replace the legitimate logo with a malicious version. Attacks through physical access may also be possible, using an SPI flash programmer, assuming that the logo is not protected by hardware verified boot technologies.

Some vendors — this includes Intel, Acer and Lenovo — offer features that enable users to customize the logos displayed during boot, which can make it possible to launch LogoFAIL attacks from the OS, without the need for physical access to the device.

It’s important to note that while image parser vulnerabilities have been found in devices from all of the aforementioned vendors, they cannot always be exploited. In Dell’s case, for instance, the logo is protected by Intel Boot Guard, which prevents its replacement even if the attacker has physical access to the targeted system. In addition, Dell does not offer any logo customization features.

Details of the attack were presented by Binarly at the Black Hat Europe conference on Wednesday, and the company has published a technical blog post describing its findings.

The security firm has published a video showing a proof-of-concept (PoC) LogoFAIL exploit in action, demonstrating how an attacker who has admin permissions on the operating system can escalate privileges to the firmware level.

The vulnerabilities were reported to impacted vendors through CERT/CC several months ago, but it can take a lot of time for patches for these types of security holes to reach end devices, even if vendors create the fixes.

Title. Mainly asking for the library side, but PC cafe is also interesting to ask about.

Mainly since Windows 11 is 64-bit only, and it seems Windows 12 is going to subscription based on top of that, neither of which public libraries can afford tossing out computers and paying more in subscription fees than they make with overdue books.

My local library is only open for 2 days a week, due to a lack of funds for hiring more staff in the area. They use older Dell all in ones, and that just makes me think if they don't have the money for being open 5 days a week, they don't have the money to buy 4 new computers for the space.

Not even getting into the bigger libraries part of that system or the ones nearby. Some have 8 computers in groups, with 4 stations of groups.

So I was just wondering, if anyone has started or is aware of a Library/Public Computer focused linux-based OS? Perhaps one that allows immutable systems, and the library card system backed most use to enable end user access. Perhaps that's a config file tucked away somewhere.

And I guess the PC cafe OS is interesting, simply due to the fact that Linux gaming has been making huge strides, and PC cafes are still popular in Japan, Korea, and China.

EDIT: I am not in control or assistance to the library, just looking if there's a potential solution to libraries like mine. If I could give links to a library computer manager, or if I could give upstream bug reports to people making such software.