princessnorah

why not just run the IP check script on the box jitsi is on? a quick google gave me this: dig +short myip.opendns.com @resolver1.opendns.com and this: wget -q -O - checkip.dyndns.org | sed -e 's/.\*Current IP Address: //' -e 's/<.\*$//'

Good news! Google paid up and still has access I'm pretty sure.

There's actually a European open source initiative that funds them. However, the program is being sunsetted :(

I think you're misunderstanding the purpose of Secure Boot. It's not designed, nor very good at, preventing physical access. It's designed to verify the authenticity of the code you are booting each time, most generally to prevent remote attacks. Think of it more like how HTTPS works. The reason you commonly have to install new keys when installing Linux is because there are separate ones for the bootloader, the OS, and kernel modules. GRUBs is generally already in the database. The OS can be hit and miss, Canonical generally has theirs included for example. Then there's the kernel modules. If they were built and included in binary form, they're usually signed with the same key as the OS. But if they're built locally, say when you install NVIDIA driver's, then they're signed with a local key, which has to be enrolled. So it's similar to a self-signed HTTPS certificate. A lot of routers use those, and browser's will throw a big warning you have to click through. It's the same with Secure Boot. For example, if a virus tries to build a malicious kernel module, it will throw the same enrollment screen, which would let you know something's up if you didn't initiate it. There also has to be a password, that you set in userspace, and then re-enter on the enrollment screen, confirming that it's a requested action.

Disabling other keys won't prevent someone from simply entering the bios and disabling Secure Boot first if they have physical access, which would let them boot anything. If you want to prevent that, then the methods you would generally use is setting a system password in the BIOS it asks for each boot, or disabling other boot options (or the boot menu depending on the computer) and setting a BIOS password. However, if you're trying to prevent people from booting other OSes as a way to protect your files from being accessed, well someone could just take the drive out with physical access. The best practice there is to encrypt the drive with something like BitLocker, FileVault or LUKS/dm-crypt (basis of many distros full-disk encrypt features).

Edit: You could also have Secure Boot enabled, delete every other key and set a BIOS password if you wanted too I guess. I haven't tried, nor read of anyone trying too.

Ya know, if not for the other person's comment, I might have been gullible enough to try this...

Look, I'm not going to try and argue the point. However, I'm (sometimes) Butch, and I enjoy being chivalrous at times. I think it hits different when it's a girl doing it, especially when you always get consent first 👉😎👉

Bluefin would be a great choice of distro honestly. Immutable so can't be messed with, automatic upgraded out of the box, GNOME on Fedora.

Based. I made a comment here a while ago with a* bunch of links to DIY resources. Was worried it would get removed. Glad to see this stance from the mod team :)

This is basically verbatim what I came to the comments to write out. I'm not sure how long you've been on hormones but I'm seven years in and still feel caught between woman and nonbinary. But I'm certain that feminising HRT was the right call, I'm so much comfier in my skin than I was.

Chivalry isn't dead, it's a lesbian.

Ya know, I somehow managed to forget it was in the meme when I saw that person repeat it. Thanks for pointing it out.

You still didn't comment on including VOY & ENT as "NuTrek" era shows. Would love to hear the justification on that one.