- 0 Posts
- 40 Comments
You didn’t store the key anywhere but on that disk.
Windows does not let you store the recovery key on an encrypted drive.
The rest only means, we need to deal better with our data. All the above basically also applies when you HDD or SSD dies, which can happen any time.
Backups is what you need, not an unencrypted drive.
All the input verification and processing of player locations is done on the server (at least in any respectable game), I can smell the fact that you haven’t touched a single line of multiplayer code in your life from here
Those checks can be buggy ofc or do not cover all possible exploitable behaviors. But when there are implemented correctly you can not circumvent them. Similar to a Login form, bugs excist.
A youtuber named CodeOverflow made two great series about game exploitation.
EDIT: things like physical hardware hacks are also near impossible to detect reliably except for stuff like blatant recoil hacks
Not talking about that. And Client side anti cheat does also not help here.
Every. Single. Serverside anticheat ever implemented has been defeated with absolute ease.
Even if true (it is not) this does not proof anything other the that to less resources are invested in it. Client side Anti Cheat is cheaper because you just simply buy that product and yiu have not fix your broken game code which bately runs smooth anyway.
Client side Anti Cheat goes against basic IT-Security principles. Every single packet that is sent from the Client to the Server is User Input. It is not to be trusted. You have to validate it.
When you login to your Online account the check if your password is correct does not happen on your Computer. It gets sent to the server and the server validates it.
You could use things like ray tracing to determine if one player can be seen by another on the serverside and only send packages when they can see.
But to resource heavy to do that.
Edit: Thinking about it, you simply have to render the whole map with all players server side and based on that determine which players can see each other and based on that send the information to the clients.
That is just wrong. For example, increased movement speed. Just check every couple of seconds if the movement that the player actually did is possible with the allowed parameters. Yes there can be bugs in that too, but not trivial to bypass when you validate every packages.
It is resource intensive. But much more effective for things like movement then client side.
The user does not need to understand it. A user does not understand https or hashing and salting. Still, every one of these is important these days for online security.
I am not a huge fan of passkeys themself, especially when the secrets are held by big tech, but they promise better security and protection against command n attacks like phishing.
The difference is, that even if you enter the “password” on a phishing site, it is useless. Or when the server is compromised.
The only way the passkey can get compromised, is when the device that holds it gets compromised.
The same reason why hardware tokens for things like FIDO or U2F are recommended.
Passkeys are not passwords. When you authenticate using passkeys you will proof that you have the secret (passkey), but you will never reveal that secret to the service you are authentication against.
So even if someone is able to steal that package containing the answer, that answer will not be valid a second time.
Let’s not forget this here.
https://www.youtube.com/watch?v=bRdL0StldJM
Wired headphones do not have the need for replaceable batteries.
The problem is that you cannot be sure if it follows spec. You as a normal user can only verify that it works on the current gear you have. What if the output signal strength is on the higher side of the spec on the current gear and you buy a new (for example) graphics card which has a lower output strength (but still in spec). And the cable no longer works?
HDMI and DP are especially frustrating. Had enough problems with cables that ‘worked at home’ but no longer on a different setup in the past.
Nope thanks, after this “fix” for wayland support on linux i do not touch this software https://github.com/rustdesk/rustdesk/blob/1.1.9/src/platform/linux.rs#L411-L422 Basically editing the config to disable wayland without user interaction.
Not sponsored, I just genuinely like the product. Adguard doesn’t require manifests because it works outside the browser.
But trivial to circumvent. Just change the origin url from (for example) ‘ads.google.com’ to ‘google.com’ and you no longer can block ads based on DNS blocking.
While it is now not a hugh thread it will eventually happen when they manage to eradicate adblockers in the browser.
I would call this actually ignorance. There are other languages then english. Other languages have (even with the roman alphabet) have special characters that are not supported without punycode. For example âäàáßœöō. Workaround exists for a lot of those but without punycode you would be leftout when younhave on of those character ind you name,cityname,companyname.
Punycode has is problems in the URL and if jt is just the point that not every piece of software understands it but it allows for more domain names to choose from when youn have a special character in you family name.
Like it happend with the last tariff’s? Not.