Windows will break your bootloader in a few updates time. It will literally check all drives in your PC and put a windows bootloader on it, overwriting any others that are already there.

With a tiny bit of offsec you can make pretty bulletproof setup.

Work only exists inside of a Win11 VM. It never touches the underlying system! All files associated with that VM (most importantly the virtual disk) live on a separate partition, or better separate drive. That partition is not mounted in fstab. So under normal circumstances it should never be mounted. So any fuck up they do to their Linux system will leave that partition untouched. If worst comes to worst that can boot a live iso from USB and run their work VM from there.

I would trust that setup infinitely more than having windows as a base system.

Yeah standard bash Ctrl+r is just so painful. I much rather use “history | grep searchtearm” than that awfull search. fzf is a whole other level. But nowadays I just use fish shell which IMO has even better search than fzf

Sounds perfectly reasonable to me. If OP is unable or unwilling to fix a problem that is important to her, why isn’t she allowed to pay someone to fix it?

You wouldn’t say its toxic if she threatens to call a plumber after OP promised multiple times to fix the leaking toilet.

Dont even need to make it open source for that. Just use either visual studio/vsc or have the code on github (private repo so not OSS)

Terminology: revoked means the issuer of the certificate has decided that the certificate should not be trusted anymore even though it is still valid.

If a attacker gets access to a certificates key, they can impersonate the server until the validity period of the cert runs out or it is revoked by the CA. However … revocation doesn’t work. The revocation lists arent checked by most clients so a stolen cert will be accepted potentially for a very long time.

The second argument for shorter certs is adoption of new technology so certs with bad cryptographic algorithms are circled out quicker.

And third argument is: if the validity is so short you don’t want to change the certs manually and automate the process, you can never forget and let your certs expire.

We will probably get to a point of single day certs or even one cert per connection eventually and every step will be saver than before (until we get to single use certs which will probably fuck over privacy)

One reason for the short certs is to push faster adoption of new technology. Yes that’s about new cryptography in the certs but if you still change all your certs by hand maybe you need to be forced …

You don’t need something ever. Sometimes you just want something because the alternative is realy bad. I don’t need to eat. I want to eat because I don’t want to starve.

I want to watch a movie with my partner at the agrees time because otherwise they will be mad. I want to access my digitalized documents to send a letter in time because otherwise I will have to pay late fees. I want to access my gameserver because that’s the one time a week I get to have fun with my friends from my college time.

There are many situations where I’d rather do the thing I want instead of doing maintenance.

There is still a good reason to know about problems early. Without any monitoring you will find out about problems exactly in that moment when you what to use the service that doesn’t work. Sometimes you need something quick and you don’t have time to debug and fix in that moment. If you get an alert early you can decide to fix it right away or in a few hours or tomorrow.

A memory pointer? So it must have been a program sending a pointer using an API to itself so it ends up in the same process again?

I wouldnt blame that on stupidity as much as on ignorance and naivety. Many people simply don’t think about anybody deliberately misusing their design. The idea that somebody could even want to access somebody elses receipts didn’t occur to them. And if they were still doing their studies they might not have known that you can “combine” SQL queries and ask for two things at once.

I don’t blame the girl, but whoever chose her to design a system with sensitive information.

If it shows up in gparted correctly it sounds like you did it correctly but just to make sure, don’t dd the iso to the mounted partition, you don’t want to have a filesystem with a .iso file on it. dd directly to the device (like /Dev/sda1 or whatever). BTW you don’t need dd just use cp.

Not like the whole video goes from 1080p to 720p or something but single bits of the drive will fails over time. If that bit is part of your video file, one pixel of one frame will be the wrong color/black. If multiple bits close to each other fail you might get a video stutter. If even more fail your video player will not play the video at all (or just stop playing at the place of the errors).

That is the smallest scale of self hosting. The server and the client are the same device. It is also the most insecure way as you probably don’t have any backups and very limited storage space.

Actually self hosting is the next step when you decide you want 5+ TB of data and have it automatically create backups. Digital storage media degrade pretty quickly and if you just have your movies on a hard drive in your computer, after 5-10 years you might start to lose quality or some files completely.

Sometimes I wonder how people can be so naive. Even if they don’t know just how much money is thrown at AI, just the fact that it is now in literally anything and on the news every day should be a clue that it is a huge industry. You wouldn’t expect the guy that changes your cars tires to be able to single handedly build a car that is better, faster, cheaper and more efficient than all car companies together.

And all websites use wake-on-lan over the internet so the first person every day just starts the server and the last one turns off the lights!

My 10yo gaming PC is probably “faster” to boot because it is set up to auto logon without password promt so it boots straight to desktop without any interruptions while my Linux laptop has pre-boot-authentication and then normal login. But between these two password promts is basically no time at all

If you run it like that every day you will always be one day behind in packages. Not realy that big of a problem (unless on an internet facing server)

(I’m just being silly, I recognize that an old package list would probably cause issues with installing or upgrading packages.)

No problems anywhere you can always install older versions from a repo.

Upgrade -> update two days ago and then again today will leave me with exactly the same packages as it would if I ran it correctly the first time and then not at all today. Just the state of two days ago.

No it will update and once that is done it will shut down. But the update includes a restart so it will restart and then require you to type your password so it can finish the update, after which it will shut down.