gamesensepub

This is not gamesense.pub crack; this was gamesensepub orgs repo gamesense, it’s a private repo, you can verify my fork of it on my page: https://github.com/h4xrOx/gamesense.bar AND by visiting the following url: https://api.github.com/orgs/gamesensepub/repos

// The repo:

[email protected] Moderating this section: wish, esoterik and 1al9o (second coder of the loader)

Discovering hacking and leaking/cracking attempts from our server: 12/1/20

(Private Repo for later use)

// The DLL testing.dll gamesense team members buildt from reversing gamesense.bar’s claim to a "cracked gamesense ", and the only origional gamesense file they found as mentioned in their commit history was rainbow bar.

//---------------------------------------------------------------------------------------------------------------------------------------// The only gamesense.pub info I got from reversing testing.dll and debugging reflectiveloader.exe came from their reflective // loader esotk buildt from gamesense.pub loader source. Apparently to test, the testing.dll they buildt from reversing gamesense.bar’s " crack " . The only useful gamesense.pub information retrieved from this was the endpoints I got from debugging the the reflective loader. That gave me endpoint to their project for the gamesense client for visual studio teams //---------------------------------------------------------------------------------------------------------------------------------------//

The master key is a solution to protect those POST requests that don’t require user to be authenticated. This should not be exposed to the client. however the endpoints were a big find because I got the Public Key Infrastructure (PKI) this is a system of processes, technologies, and policies that allows you to encrypt and sign data. Their mistake of exposing the endpoints allow everyone to get an access_token, which means everyone can make POST requests issuing digital certificates that authenticate the identity of users, devices, or services.These certificates used for Active Directory Certificates Services (AD CS) for their Visual Studio Teams AD connected services

---

//ADCS

is Microsoft’s on-premise PKI solution and while it has been around for some time, there can still be a lot of confusion around the set-up process.

//When I see a custom PKI , when I see self signed certificates while pentesting cheat sites, or skid services: I know I will be able //to exploit some mistake or misconfiguration by spoofing , forging and if I am really lucky - a master key to generate CA’s //that validate my device to use one of the domains trusted users.

//Interestingly enough I did get the MASTER-KEY:

SSL_SESSION_get_master_key() , this function exposes internal values from the TLS handshake. The security of TLS session depends on keeping the master key secret. ( their mistake ) open terminal:

// Run: openssl s_client --connect gamesense.pub:443 --showcerts --crl_download --debug

// MASTER KEY

Master-Key: 6805BB1AF6A0ACFC91EA9FBCD4107405D50F53D24248BC82B03D2168317FDB9EAA988767F7F79EDF53E83DD53A0F511F

---

Moderating this section: wish, esoterik and 1al9o (second coder of the loader)

Discovering hacking and leaking/cracking attempts from our server: 12/1/20

(Private Repo for later use)

https://gamesense.pub