Groups | Search | Server Info | Login | Register

Groups > alt.os.linux.mint > #47113

Re: Secure boot

Show all headers | View raw

Paul wrote:
> On Mon, 3/23/2026 3:10 PM, Axel wrote:
>
>> thanks for that. I'll just leave it off. computing was much simpler before all this crap.
> You never know what the future holds.
>
> 1) A person standing in your room, can bypass lots of the "trivial security".
> 2) Having a BIOS level password, will slow them down. Consumer machines, 20 seconds to bypass.
>     Business machines, maybe 5-10 minutes to fit a programming clip to the 2KB password chip
>     and flash the null image into it. For the "merely curious", a BIOS password will keep
>     them out for a good while, before they get to boot their LiveDVD with sudo.
>
> 3) Given your security posture in the room is typically poor (I know mine is),
>     you want a disaster recovery plan. That's what backups are for. The disk
>     storing the backups, should be offline when the machine is being operated
>     normally.

i have the timeshift disk and the files disk permanently in the machine 
for convenience. guess I should remove them and connect them only via 
usb as necessary

> It is up to you to decide how quickly you need to tip the machine
>     upright again (assuming there isn't a persistent pest onboard). It can be
>     almost impossible to tip a room upright, with the right pest onboard.
>     That's why, in an "emergency situation", don't be surprised that
>     the modern machines aren't coming back up.
>
> I've probably told the story about the guy who got wiped out by ransomware.
> He posted a question "my Excel files have .osirus extensions added to them".
> That was Osirus Ransomware, which encrypted data files such as .xlsx and .docx
> and so on. It goes for the high value files, first.

was he using Linux? and he wouldn't he have had to click on some file he 
shouldn't have to install the ransomware?

>
> The OP in that case, didn't have backups. He had OS CD/DVD install media in the room, but
> he didn't know which license key went with which machine.
>
> It took around three months, before he dropped in one day, and said the room
> was more or less upright again. Sans whatever data loss from the lost files.
> He had a small business, and I think he closed up shop. He no longer
> drops into USENET, as he is "functionally retired".
>
> Even your backups can be ruined. Some ransomware hides for a month, to give
> time to discover and monitor your backup pattern. Maybe it takes a chance
> and ruins every backup image you made. Then when the "red dialog" appears
> on your screen, your Disaster Recovery Plan is already ruined.

in that case wouldn't even backups to a USB hard drive be corrupted?

>
> For people without a profile, they have little to worry about in terms
> of "focused campaigns". But if someone "wants to drop the big one",
> that will be a test of everyones Disaster Recovery Plan.
>
> Remember, that most malwares today, are reversible or "clean-able".
> They don't have to be. Wipers like Sality still exist, and BleepingComputer
> would "tell you to reinstall" if such is detected. It seems a lot of
> these pests have worm capability, or at least, they are armed with
> exploits which a lot of people have not patched up for. Like, say you
> had SMB1 enabled on a machine, how "worm-able" are you ? I don't know.
> Couldn't give an estimate.
>
> Rather than being worried about your Secure Boot setting, I would
> advise some more general principles about running a computer room.
> "Bring your umbrella, because it looks like rain." Consider what
> you'd do in an emergency.

I have Timeshift, Backup Tool saves, and regular Foxclone image and the 
files disk copies

>
>     Paul


-- 
Linux Mint 22.3

Back to alt.os.linux.mint | Previous | Next — Previous in thread | Find similar

Thread

Secure boot Axel <none@not.here> - 2026-03-22 06:02 +1100
  Re: Secure boot "Alan K." <alan@invalid.com> - 2026-03-21 15:35 -0400
    Re: Secure boot Axel <none@not.here> - 2026-03-22 17:23 +1100
    Re: Secure boot Axel <none@not.here> - 2026-03-24 06:48 +1100
      Re: Secure boot rbowman <bowman@montana.com> - 2026-03-24 01:14 +0000
  Re: Secure boot rbowman <bowman@montana.com> - 2026-03-22 04:05 +0000
    Re: Secure boot Axel <none@not.here> - 2026-03-22 17:23 +1100
  Re: Secure boot Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-22 05:18 +0000
    Re: Secure boot Axel <none@not.here> - 2026-03-22 17:25 +1100
  Re: Secure boot Paul <nospam@needed.invalid> - 2026-03-22 02:03 -0400
    Re: Secure boot Axel <none@not.here> - 2026-03-24 06:10 +1100
      Re: Secure boot Paul <nospam@needed.invalid> - 2026-03-23 17:02 -0400
        Re: Secure boot Axel <none@not.here> - 2026-03-25 10:37 +1100

csiph-web