Frontpage VS CyberChef

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

Terms of service are generally pretty shitty, yes. But this is egregiously shitty.

https://tosdr.org/ is a good site to compare. Any service over Grade E (Spotify, Facebook, the usual suspects) is (very likely to be) less bad. DeviantArt for example is a D, and doesn't include waiving your moral rights among some of the other overreach.

Some service terms are actually quite good (DuckDuckGo, Mullvad, off the top of my head). Though these aren't content sharing platforms so it's not really as fair of a comparison.

This is super useful https://tosdr.org/

> Meaningful consent is becoming increasingly difficult for consumers; for instance ...

https://tosdr.org is good for that, why don't Mozilla just contribute to an existing project

I can't give you a complete guide here, but I recommend you go to privacy subreddits or watch relevant Youtube videos for more info. I also recommend sites like privacytools.io and privacyguides.org They contain lists of alternatives and tools. Also check out tosdr.org which contains summaries of the TOS of a ton of sites. Also try email aliases like simplelogin or anonaddy. Use burner emails for throwaways if possible emailnator.com or tempail.com . Try to use as many open-source applications as possible. You can even self-host certain things.

I think what you're looking for is TOSDR (Terms of Service, Didn't Read): https://tosdr.org

It's been going for several years and has very thorough analysis of various ToS, done by volunteers who are often legal professionals.

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...