-- Spectre and Meltdown vulnerabilities
-- Change in MX sources
-- MX Linux on social media: here
-- Mepis support still here
-- MX-17.1 Final release info here
-- antiX-17 release info here
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules
Search found 2463 matches
BTW we have copy_initrd_modules and copy-initrd-programs in cli-shell-utils (usr/local/lib/cli-shell-utils/bin) which is a depencency of live-usb-maker so we don't need copy_initrd_modules and copy-initrd-programs in snapshot. But, that probably means some editing of the snapshot app since that app ...
ok, got some successs. we need to add "xts" to the copy_initrd_modules in build-iso, and I assume snapshot as well. I just booted up a default mx18b1 32bit iso this way. CRYPT_LIST=" aes blowfish dm-crypt dm-mod serpent sha256 xts " I thought the same. You beat me to it. I'll need to add it to cli-...
Don't "=y" and "=m" both enable the feature? One just makes it part of the monolithic kernel and the other makes it a loadable module. honestly not sure, but the 64 bit has an "m" as well. I've only tried 2, but I can't make a 32 bit encrypted usb with a 4.19 kernel, yet. building a 64 bit encrypte...
Used live-usb-maker to make an encrypted live stick (32 bit version), but on first boot on this T60, I get this error. Failed to set up dm-crypt key mapping for device /dev/sdb2 Check that kernel supports aes-xts-plin64 cipher Using live-ub-maker without encryption and the stick boots fine and beta1...
- Sat Dec 08, 2018 4:48 pm
- Forum: General
- Topic: MX-17 to MX-18 update testing
- Replies: 59
- Views: 1865
Can anyone running the 4.19 32-bit kernel install spectre-meltdown-checker and see if it now supports the PTI Meltdown hardening, as was advertised? Steve (too dang lazy to upgrade in a virtual machine and check for himself) In VBox spectre-meltdown-checker Spectre and Meltdown mitigation detection...