Is possible that linux can be infected with ransomware without me running the program as a root user?

https://bugs.telegram.org/c/18946

please upvote

Done

Didn’t know about that site, now I may fill a few suggestions

Any solution for one clip CSV, VCard converting of a list of numbers?

grep ^TEL file.vcf | cut -f 2 -d :

Is possible that linux can be infected with ransomware without me running the program as a root user?

If you run untrusted code as your regular user it can do what it wants with your user files

But not the hole system

No (depending on your sudo config), but it’s probably your user files you value

But i have to run this malicious program to work, right?

what did you do with the program/script, if not run it?

I mean it has to be a reason to get infected with Ransome not randomly

And the reason is the user

Hi there. Some updates that may help me to get some help. So I’ve formated sda1 from btrfs to ext4. Thought I was getting the error cause of it. But I’m getting same error. Any tips?

Thread 🧵 head

Just tried with –disk-module=bios-disk also with native. Same results. 😢

awk is great at stuff like that

i suggest putting grub on fat32, not btrfs

bioses usually only support fat32, which is where they’ll find the efi for the kernel/the initram

It’s a pretty old machine. A Thinkpad x200. In grub manual says it supports most file systems. If it was cause of filesystem, moving into ext4 should solve it.

grub needs to be loaded by the bios, regardless

grub supports many filesystems

but your bios doesn’t

grub is loaded through an efi file, located on a partition

usually it finds this partition by looking for the ESP flag, by looking at the first partition of the first drive, and usually only supports fat32

some bioses work with more filesystems, but that’s quite rare

the specification says any fat system should do, but in my experience it’s mostly only fat32

maybe I’ve misread: do you manage to load grub?

Don’t have EFI. This is a legacy bios machine. I think that Bios read the MBR that loads core.img from /boot partition.

ah, I’m not too familiar with mbr booting

how does mbr know what /boot is supposed to be?

Looks like bios always search the first bytes “hard disk” and load into as instructions. Then this instructions load grub. That’s why most modern partition manager create first partition leaving 1k free at the beginning.

MBR reads first 441 bytes of the disk

and runs that

so grub must be <441b to work on legacy?