gta6n0w

dns exploit to play gta 6 (and other preordered games) right now

instructions

prerequisites

  • GTA 6 must be fully preloaded
  • the console must be signed in to the PSN account that owns the preorder
  • note your current DNS settings in case you have any custom config

steps

  1. replace the DNS servers with the gta6n0w servers

    1. go to Settings → Network → Settings → Set Up Internet Connection
    2. highlight your active connection, press Options, and choose Advanced Settings
    3. set DNS Settings to Manual
    4. enter the gta6n0w resolvers:
      Primary DNS
      56.51.100.66
      Secondary DNS
      56.51.100.67 (six seven!!)
    5. press OK
  2. disable automatic time and set the clock one week ahead (~5 minutes)

    1. go to Settings → System → Date and Time → Date and Time Setting
    2. turn off Set Using Internet.
    3. choose Set Manually and set the date to exactly 7 days from now, set the time to within 5 minutes of the real current time

    e.g. if it is , set anywhere from 21:25 to 21:35

  3. reboot the console

    open the Control Center (PS button) → Power → Restart PS5 and restart

  4. wait

    after the home loads, leave the console idle on the home screen for about 40 seconds. don't launch anything, don't open the game library, don't choose your account, etc.

    if you see Cannot connect to the server and a clock warning you're almost done

  5. enjoy gta 6 lol

    open gta 6 and you're good. it'll take some time for the game to decrypt but you'll play

now what

  • once the game is decrypted locally it stays playable so you can revert to old time/dns settings
  • I wouldn't recommend logging into rockstar social club right now
  • if it didn't work tough luck kiddo

technical explanation

how does a preloaded PS5 game work?

preoaded content is stored on the SSD encrypted with every PFS block decrypted by the hardware decryption engine. the data is completely useless until the console has the title key

at release time the console asks the PSN entitlement service for a decryption token which is a short-live signed blob that wraps the content key for the game and console. the token is passed to the APU security processor, unwrapped inside the enclave, and loaded into the key slots the decryption engine uses

interestingly, the console can technically ask for the token at any moment. the release time is just a field in the store metadata and the console waits until it thinks that time has passed

even more interestingly, the entitlement server doesn't compare the request against its own time. release times differ by region and timezone and Sony (or the vendor) likes to stagger launches so the server instead trusts a time attestation value that the console attaches to the request. the attestation contains:

  1. the token request nonce
  2. the console's local RTC time
  3. a remote time value obtained from PlayStation time servers (time.playstation.net/time2.playstation.net)

everything is signed by a console key that lives in the security processor. the server checks the signature, checks that local and remote time agree accounting for skew and checks that the remote time is past the release time. if all three pass it issues the token

how does the exploit work?

that time server looks promising. the primary time fetch goes over TLS with certificate pinning to Sony's own CA so sadly we can't forge the signature and you can't mitm the primary time request.

but shit third world countries save us again! the time service in the system software has a degraded mode for networks where the PlayStation time servers are unreachable for things like captive portals, corporate networks, and authoritarian ISPs that for some reason block the ports. in that case it gets time from a router provided source instead:

  1. it reads the time server list handed out by the router (dhcp option 42) or if there is none uses a hardcoded fallback host name at time3ns.playstation.net
  2. it asks the host for time over ***plain http*** and parses the Date: response header (the same trick htpdate uses fyi)
  3. the result is fed into the attestation as the remote time

and wouldn't you know it, the security processor signs whatever remote time the OS gives it. it has no way to know where the value came from

so what does the gta6n0w DNS servers do to make the exploit work?

they are normal recursive resolvers forwarding your reqs to cloudflare (1.1.1.1) with two exceptions:

time.playstation.net, time2.playstation.net
resolves to a non-routable blackhole address hanging forever
time3ns.playstation.net
resolves to the gta6n0w time responder returning Date: header set to your request time + 7 days

why do I have to set the clock manually if the server lies about the time anyway?

the attestation contains both your local RTC time and the remote time and sony's entitlement server rejects attestations where the two disagree by more than the skew window (around ~9-10 mins). if your clock says today and the remote time says next week the request is rejected as clock tampering

why a full reboot?

the time service only gets attested time at boot and after network outages. otherwise it reuses a cached value adjusted from the last good sync (which rest mode doesn't clear)

why wait 40 seconds?

that's how long the path takes to fail. the time service tries the normal time servers 3 times with exponential backoff so about 35 seconds pass before it declares them unreachable

can this get patched?

yea but I doubt it matters we have less than 3 days before gta 6 releases

is this safe?

idk but don't log into your rockstar social club account maybe