notabot

Can you still SSH to the machine when it’s in that state? If you can it’s likely to be a problem in the graphics stack, if you can I’d probably start by running memtest86+ for a full cycle to rule out memory issues. After that, checking things like CPU temps would be good.

Assuming that’s all good, check for anyone else reporting issues with the same motherboard, CPU, GPU, or other components

Good luck, this sort of thing can be quite frustrating to get to the bottom of.

That would be similar to the “web of trust” approach where users vouch for each other, and you can determine how much you trust someone, or at least their account, based on how many others vouch for them, and much you trust those users.

So, they’re speaking from experience?

Most of them are multi billionaires, their children will inherit their estates when they pass, and most have more than one child. Which means that, when they do pass, we’ll actually have more billionaires than we do now.

I’m sorry for you Ioss. Was it caused by poor font design?

I know it’s an old photo, and they probably had to stay very still, but she look so totally done with his nonsense.

Is that the Domway building, or the Subino’s place?

It’s not well known, but the Allies had a top secret plan to end the war by parachuting Major into Germany, near Berlin, and showing him a picture of an ss officer kicking a puppy. The predicted extreme colateral damage was considered acceptable as it was expected that this action would end hostilities within 24 hours. The only reason the plan was not carried out was no one knew how to stop him afterwards.

I like the idea of those pieces, it would have made teaching the kids a little easier, although they picked up standard western chess moves fairly easily anyway. I think you could make pieces like this fairly easily, though the Knight in particular, would need a bit of thinking about to find a clear symbol for its moves.

Due to the way federation works those stats are public information, and @jet@hackertalks.com appears to be an admin of their instance, so the data is even more easily to hand.

Whilst I agree with your overall point, this isn’t about them touching his pay, but his military pension.

An option I found quite relaxing was, rather than taking a week off, take Wednesdays off for 5 weeks. Now you only have 2 day work weeks, and a day off when everything else is open and relatively quiet.

…Wait, if we can’t take anything you say seriously because you say you’re lieing, then you’re lieing about lieing, which means you actually telling the truth about lieing, which means…

SEGFAULT

It’s ao obvious now! We just haven’t been using enough bombs! Kill everyone and there’ll be no more wars, ergo permenent peace achieved.

Ah, you see, all those authors, translators, editors, and indeed committee members were influenced and guided by god to ensure the true word of god was passed down. The fact that different versions don’t agree with each other is neither here nor there.

In the end we ended up with a weirdly written, contradictory work open to interpretation that is supposed to be treated as fact.

Ah, um, it’s… yes, it’s all part of god’s plan. God works in mysterious ways, you know. Yes, that’s bound to be it…part of the plan, mysterious ways, etc.

How many of them survived the next day without going insane and babbling about the hobbit wizzard who ate their souls?

I came here to mention these too. One addition that can be helpful in large trees is to add a depth attribute to each node so that you can easily limit the depth of subtree you retrieve.

I was a picky ass eater.

That’s something we should all be picky about.

The general process would look something like:

1. Find all of the SSH keys you want to replace.
2. For each of thise keys, identify everywhere you use it to authenticate, and write this down! This list will form the basis of the rest of the plan. Make sure you list all of the accounts/servers you log in to, and don’t forget things like github or other external systems if you use them.

You’ll need to perform the following steps for each SSH key you are replacing:

1. Rename the public and private keys to something like old_id_rsa and old_id_rsa.pub (obviously use the same type name as your key, just prefix old_)
2. In your ~/.ssh/config, add a line telling SSH to use the old key as well as the new ones: IdentityFile ~/.ssh/old_id_rsa (change the key filename as aporopriate)
3. Check you can still log in to the servers you could log in to before. It should still be using the old key, just with a different filename, so it should still work.
4. Generate your new SSH keys ssh-keygen -t ed25519
5. Log in to each server and ADD the new ~/.ssh/id_ed25519.pub key to the authorized_keys file or equivalent mechanism. Do not remove the old public key yet.
6. Remove the IdentityFile line from your ~/.ssh/config
7. Check you can log in to all your systems. This will validate that your new key is working.
8. Remove your old public key from the authorized_keys file on each server you log in to.

Depending on your threat model you’re going to want to do this more or less often, and so you may want to consider automating it with sonething like ansible if it’ll be a regular job.

That’s certainly an option, but depending on how paranoid you are that still typically means that a compromised server can overwrite all of its backup images on the NAS, which could leave you in trouble. If you can configure your NAS to only allow creation of new backups but not allow changing old ones, you might be ok.