

One way of helping would be to tell people how to mitigate it. Telling them it’s impossible does the exact opposite.
Main: @gnufuu@lemmy.ca, Backup: @gnufuu@infosec.pub


One way of helping would be to tell people how to mitigate it. Telling them it’s impossible does the exact opposite.


Gotta love a call for contribution that makes you want to paint your face blue and attack Adobe with a sword lmao


Booting a live USB and reinstalling GRUB as follows has saved my butt in the past. Obviously replace the /dev/sdXY paths with your own. Further adjustments might be needed depending on your system.
# mount root partition:
sudo mount /dev/sdXY2 /mnt
# mount boot partition (if there is any)
sudo mount /dev/sdXY3 /mnt/boot
# mount efi partition (if there is any)
sudo mount /dev/sdXY1 /mnt/boot/efi
# mount other partitions:
for dir in /dev /dev/pts /proc /sys /sys/firmware/efi/efivars /run; do sudo mount --bind $dir /mnt$dir; done
# chroot into mounted system:
sudo chroot /mnt /bin/bash -i
# reinstall grub:
grub-install
# rebuild grub.cfg:
update-grub
# rebuild initramfs (not sure if necessary):
update-initramfs -u
# sync, exit chroot, reboot:
sync
exit
sudo reboot


Welcome to Lemmy :), you’ll fit right in lmao


Nice specs, nice setup. You might want to add another rainbow sticker or two, just in case :p


Using an officially supported secondary app store and calling it a Play Integrity bypass seems like a bit of a stretch.


Never heard of iodéOS. At first glance it looks like they take LineageOS for microG, bloat it with some random apps, and expect us to pay them for adblocking. Am I missing something?


Windows 7 hasn’t received security updates for ages. Your machine is probably part of seven bot nets.
Only a matter of time until it demands for Windows to be installed
mdadm --stop /dev/mdX should at least tell you whether or not mdadm is causing the spinning.


Is there anything similiar for non-mobile?
The EFF provides pretty sound advice, see the 2nd link in my initial comment.