elvith

Oh, cool. So now we get full transparency which MEP talks and communicates with whom, which websites they visited while using their private and official devices. That should allow us to build an automatic lobby register. And thanks to chat control, we can even get automated summaries of all those talks and what they did? Right? Right?

I mean...

Evangelicals Are Now Rejecting ‘Liberal’ Teachings of Jesus (already from summer 2023)

Im inclined to answer with "Yesn't"

Yes, the problem is readability. You can get "better" code of you know the exact tooling and settings for compilation, as you can then better guess what optimisations and tricks were used (by the compiler) and you may be able to "undo" them. There are so many places where this will only let you make guesses. You write a loop in your code, the compiler removes the loop and replaced it with another construct that may be a bit faster to execute, but may be way harder to understand - or tedious to change if you need to edit it especially if it's not a simple change (character can now run faster!) but needs new functionality that would completely break this optimisation (but it'd be trivial to add in the original code).

Also all context is removed. You won't work with code like this:

(Both pseudocode, not bothered to make a real example that maybe even compiles)

if keyPressed(MOVE_RIGHT){
  player.speed = min(player.MAX_SPEED, player.speed + player.acceleration*frametime)
}
else{
   player.speed = player.speed * player.MOVEMENT_DAMPENING * frametime
}

You'd get something like this:

int *fi93836290= 0x7363728
int *fi22425 = &fi93836290+0x23
fi22425 = fun7362782(0x63627)? fun42638(...)
//and so on

I don't know.

The gist is... When you write a program/game/... You write source code and then compile it - that means translating the source code into machine readable code. While certain things do usually get lost in this process (e.g. function names, variable names, etc.) you can see the resulting machine code and make a valid assumption about how the original code looked like. This is not a 1:1 reconstruction, but will yield code that should compile to the (basically) same result as the original game.

If you hit a Jackpot, you find a version of the program/game that was used for testing. Those often contain many pieces of information that would otherwise be stripped from the end result (e.g. aforementioned variable names, function names and so on). If not, it's a puzzle solved with guess work and experience.

If you know some specifics about the game (which language was it written in, what compiler was used in which version,...) you can get some better results, as you can take patterns in the machine code and translate them back into what the original code was probably looking like based on the tools used.

In the end it's sadly almost everytime still a manual process in which you look at the resulting source code, make some educated guesses based on patterns that are usually used when programming and specific functions that are probably contained in a game and then check those assumptions by changing the code and see if your changes affect the part of the program you thought you were dealing with.

Say you assume a specific variable/value is the maximum walking speed of the character. Then you change it and try to play the game and see if you can walk faster now. If so, label this value accordingly and go on to the next unknown piece of the puzzle.

If you want to display the output unchanged, use a code block:

```
output / log / whatever here
Line 2
Line 3
_even_ *Markdown* ~formatting~ ^will^ **be** 
> ignored
```

Or just indent everything with a few spaces for the same effect but more work (useful if the output contains back ticks that would close the code block)

Your normal comment text

    Output line 1
    Output line 2
    Output line 3

more comment text

And don't listen to the promises of big companies with billion-funds, they cook with water like the rest of us.

Oh, yeah, I remember when one of our super important core systems was migrated to SaaS. My system was interfacing with it, so I got notified about the migration to make a plan. I basically told them: "We're using $API to connect to your system. Tell me the new hostnames and IP ranges and ports and I will configure the firewall on our end. Also, our connector for your migrated system will be deployed in $IP-range so please allow these inbound connections in your firewall."

Half a year later I got a message: "Yeah, we just found out, that $SaaS-provider never configured the firewall after our tickets and everything is reachable from the public internet. We're forcing them to lock down the system now. Can you please tell us again from where you connect to us?"

If you put any data anywhere, assume it will be contained in a breach in the future. Blue teaming is hard. You have to be perfect every time. Red teaming is easy. You just have to wait till the blue team makes a simple mistake...

Mails sent to a company? Their or your mail account will be breached one day.

Account details on a webpage? Their user database will be leaked.

Your cloud drive, ect.

Even your data on your NAS at home or on your PC could get accessed in one way or another, you're just a zero day and an unfortunate click away from disaster.

On the upside, as long as you do not have a target on your back, patch your stuff in a timely manner and keep some hygiene in configs, secops ... You should be fine, as most automated attacks aren't that high level and target the low hanging fruits. But that doesn't make you completely safe.

Whips! Traps! Big round boulders rolling in your direction trying to crush you! Nazis you can punch!

To be fair, if you would use your PC as rarely as you seem to use your gaming console, it's probably also want to take an hour to update...

IIRC release is in two days, but definitely this week.

Same for me. My neighbors got some. Several other neighbors complained about the noise, but I just smile when I'm sitting here with the windows open and chicken noise in the background.

There are 69 reasons why I don't need a flexible spine.