workspaces-core-images VS CyberChef

The copy script resides within the Core images and can be adjusted if necessary. It is visible in the workspaces-core-images Github Repo

Another option could be to let the servers just boot into webbrowser and then do somethign VDI (Vitual Desktop infrastructure), for example KASAM: https://www.kasmweb.com/ This would also address/ solve/ simplify many of the mentioned issues above.

https://www.kasmweb.com/ is a popular new solution in this space. I've played around with https://docs.linuxserver.io/images/docker-webtop which is based on their kasmvnc and even in the non lossless mode if feels quite snappy.

I read about Kasm Workspaces here on selfhosted and really wanted to try it out on my Ubuntu VPS. Problem is, I use Traefik for my reverse proxy and it's not technically supported by Kasm. There are also very few hits on searches for the two platforms together, and the information that's available is not very helpful. Maybe I'm the only person really interested in this 😂 but after a lot of time spent figuring it out I decided to write my own guide in case someone else is too. This assumes you already have Traefik setup and running on port 443. The files are available at my Github project.

Check out KASM - https://www.kasmweb.com/ - you can actually play many of your Steam games from it with GPU acceleration.

You could spin up something like Kasm Workspaces, Neko or Docker Webtop.

- The Workspaces Images and Workpaces Core images, are both open source projects that include the image dockerfiles and associated scripts for building the end-user containers such as Chrome , Brave, Ubuntu desktop, etc. You can view the code and licenses here: https://github.com/kasmtech/workspaces-images/blob/develop/LICENSE.md , https://github.com/kasmtech/workspaces-core-images/blob/develop/LICENSE.md

Check out https://www.kasmweb.com/. You could setup a persistent profile storage on a linux distro of your choosing and have all the bookmarks saved there or even have it open chrome directly with all your shortcuts right from the website using 2fa to protect everything.

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