JSON-to-Go VS CyberChef

That site likely uses Matt's lib for that functionality: https://github.com/mholt/json-to-go

https://mholt.github.io/json-to-go/ is a nice tool for generating a struct definition to fit some sample JSON.

json-to-go is your friend.

JSON to struct. I use this about 100 times a day, no joke.

https://mholt.github.io/json-to-go/

Do your best to get static types on everything. Play a game with yourself where interface{} is banned and try to do your work. One of the most common sources of such loosely-typed values in JSON, so I'll point out this automatic struct generator for instance. If you have questions about a specific place you don't see how to avoid interface, feel free to ask. Every once in a while I do have to reach for something like this, but it should be rare.

But given we know ChatGPT can't accurately generate structs from even moderately complex json objects why bother doing all of that legwork of verifying and chiding chatgpt, when you can just drop it into a tool like https://mholt.github.io/json-to-go/ and get a correct struct in a fraction of the time?

I use https://marketplace.visualstudio.com/items?itemName=maracko.json-to-go, which is an extension version of https://mholt.github.io/json-to-go/

I think using struct in such cases is almost always the right approach. There are tools which generates go structs from json this.

Then we take the encrypted text and use CyberChef to decrypt it.

Let's go to CyberChef and insert our pieces of evidence.

A parameter was changed from '2AMBCgIQBg' to 'CgIIAdgDAQ%3D%3D' which is just the correct base64 encoding they should have been using the entire time.

I don't think this was a hostile action by Google, I think someone just added better input validation for security reasons and it accidently broke the bad requests they were sending.

https://gchq.github.io/CyberChef/#recipe=URL_Decode()From_Ba...

❗This is indeed the flag, but the text is encrypted with Base64. Usually, the presence of padding character "=" indicates that's Base64 type of encoding (but that's only one of the hints). To decrypt it, we can use CyberChef. Copy-paste the text and we either:

It uses a combination of magic bytes (like the `file` command), entropy analysis and character frequency detection to determine whether an output is likely to be of interest to the user.

The file type mechanism is written here[0]. There's a list of all signatures we detect here[1].

[0] https://github.com/gchq/CyberChef/blob/master/src/core/lib/F...

I think this can be deciphered using CyberChef...