187 karma · joined April 1, 2022
I fundamentally see the same structure: A client-server relationship, some game developers DO trust Anti-Cheats to a huge extent and the AC tools even have ring0 power on your device. And every game ever is full of cheaters and most of them with 0 IT knowledge.
As long as you have access to the network connection or own the end device, I dont see how this can end well for advertisers. Maybe for a few days / weeks / months here and there, but at what price.
But lets really be honest: These kind of companies dont give two sh*ts about security leaks and GDPR infringements, as is demonstrated almost every other week by news. Privacy or legal compliance is most certainly not the reason they are doing this.
I would distinguish between an Anti-Cheat actively doing shady stuff (like it seems to be the case here) and companies simply shipping crappy software - because that's too often the case in many areas.
1.) Windows is a closed-source and really huge system. There are many places you will leave traces, and they change all the time. Getting it right is hard.
2.) At least for malware, windows offers official ways to get to go first with e.g. https://learn.microsoft.com/en-us/windows-hardware/drivers/i... - I do not know if this is used by any Anti Cheat though.
The super exotic theory would be a rootkit, in those cases not even windows can help you. But as with security, as long as there is easy money to be made (because most anti-cheat systems are simply bad), those very expensive solutions will be limited to selected few professionals.
- Reading from and writing to memory (either by direct means provided by windows, by custom drivers, or by exploiting installed vulnerable drivers to bypass secure boot and such)
- Reading network traffic (particularly nasty because it can be done on a device where the game and Anti-Cheat is NOT running provided you get access to SSL decryption keys)
- Having an external device react to your video feed only (either "dumb" aka on colors, pixels shapes etc. or fancy with AI and stuff) and then react by a "faked" input device (mouse, controller, etc).
- Modifying game files (e.g. replace texture walls with transparent textures)
- The very easy way: Simply exploiting game bugs. E.g. you can cheat in Fifa on console (!) since years by doing stuff in the system menu. Fifa will just disconnect the game without giving you a loss for the match.
Please just don't. If your CI / CD pipelines do not offer the option to retrigger builds in some way other than modifying the repository, rather spend some time improving them.
I am aware of the "Squash commits" and similar features most CI systems have, but those boxes are easily forgotten. Plus you end up squashing everything and there are valid reasons for having more than one commit in the same PR and keeping them separate
My 2 cents only, and if you can make it work that's great. But I will never go ahead and recommend this to juniors or even younger seniors.
With "cloud computing" (to me even before there was the word cloud around, but thats nitpicking) suddenly your only real investment needed was your own time, which to you is "free" if you can somehow make a living on the side (some people simply accept to live poor for some time, some had their family, etc.). The few Euros for a vserver (or "webspace" at the time) were doable for most if not all. Not to mention student programs, free credits to lock you down to hyperscaler X, etc. we all have nowadays.
Or comparing it to myself: I learnt programming at the age of 12 because we got a free environment alongside our ISP contract for executing PHP with a mysql database behind it. I would never have spent any money. Now I have been a professional software developer for almost 16 years which I say is thanks to that way lower barrier of entry that was created along the lines of ~ 1995 - 2005.
Some secrets don’t belong in your password manager. Things like backup private keys, 2FS recovery keys, wallet keys, safe combinations, treasure maps, etc.
I am a 1password user and am aware that I am trusting a 3rd party with most of my life basically (minus the 2FA, my phone), but that's the way I decided for convenience. But why would I keep passwords in there but not PKs, wallet keys etc.? To me they all have the same value. What am I missing? and use it in another without those servers needing to consult a central service.
part. Unless you take care of key distribution yourself (like another poster wrote), this consultation of a central service has to take place to exchange key information (but not for additional authentication or authorization information). it has all the information the server needs except the signing keys, so the server doesn't need to store this information server-side. This means that users can get a token from your authorization server and use it in another without those servers needing to consult a central service.
In order to not have to care about rotating keys, a typical Resource Server would fetch the public key from the SSO server. Not necessarily in real-time, but at least on a frequent periodic basis. It even says "except the signing key", which is half true, since the public key needs to be well.. public and available.Now this may be nitpicking but it comes with an important implication: Your jwt validating party needs to have network access to the SSO service (unless you want to provide keys for token verification yourself, which I do not recommend), which is not always a given, especially in hybrid setups (On-Prem + Cloud).
On a side note: Newer cars also really do a lot to avoid dangers to the outside world (e.g. emergency braking for bikes and pedestrians), so I would rather throw a lot at improving here than discussing the safety of heavier-build cars.
There used to be (and still are) things like https://mreidsma.github.io/bookmarklets/jquerify.html which allow to inject JavaScript on click (and thus would make it possible to transform that site), but I gave it a shot and HN is set up to disallow this:
Refused to load the script 'https://code.jquery.com/jquery.min.js' because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/ https://cdnjs.cloudflare.com/". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.Let me spoil it to you: The cloud is also not an actual cloud, it's just someone else's server.
It is a hot topic, here are a few: IONOS - https://cloud.ionos.com/ Onep Telekom Cloud - https://open-telekom-cloud.com/en
But if you want to do scale in Europe you have to go for OVH: https://www.ovhcloud.com/en/
Good read, but I am not really a fan of that stance. The "separate schema per ms" pattern is an overhead which has to be justified and even paid for by customers (small 50k projects and enterprise grade projects of million $). First and foremost the db is a shared data structure which CAN be used for communication and in a one actor writes and 1..n actors read scenario (especially when all connecting services are controlled by the same team) is typically the simpler and better approach as a start. Schema evolution will also hit you with messaging and APIs which can be done properly in smaller databases as well.