sserver VS CyberChef

did not abandoned it since i am using for myself but didn't put any effort into marketing either other than mentioning it on hn few times https://github.com/newbeelearn/sserver . It's hHeadless server for hosting courses and associated blog/static content from private github repository.

I am working on creating a hosting server that can cater to landing page+blog+selling digital content with minimal maintenance overhead.

Beta version is ready here https://github.com/newbeelearn/sserver

I am looking for following

working on adding e-commerce functionality to my simple hosting server https://newbeelearn.github.io/sserver/

if you want to self host, give my product a try https://github.com/newbeelearn/sserver. It will auto-sync your static site from git repo.

I built something that will take care of the publish part but not the static site generation part here https://github.com/newbeelearn/sserver. Right now it only has one user i.e. me :-)

./sserver -token "$GITHUB_AUTH" -repo "https://github.com/newbeelearn/sserver.git?ref=gh-pages"

My plan is to add e-commerce functionality to it so that users can sell digital content i.e. books/videos/courses etc. through single config file in their github repository where the content is stored without needing to change their workflow.

If you would like any specific feature please let me know in the comments or create issue in the repository. Looking forward for your feedback.

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