description (1722B)
1For a good Guacamole you need avocado, salt, pepper and some 🌶️. We will provide the base Guacamole, but you need to season it just right. And if you do so, the Guacamole will reveal its secrets to you. 2 3You'll get access to a (beautiful) Guacamole frontend. The frontend connects to the Guacamole backend via WebSocket. Eventually, the backend talks to the guacd component which establishes a connection to our Windows Server 2019. 4 5Some more notes on our setup: 6 7The VM runs without hardware acceleration 🤕 Wait for around 10 minutes after your session start. By then the VM is fully booted and actually quite responsive 8Guacamole does not like the Windows OpenSSH Server algorithms, no SSH via Guacamole 9You have internet access in the container(s) 10You can use the docker-compose file to spin up your own instance of our setup. But remember: Some secrets are redacted in those files ;) 11We also provide a local setup (docker-compose.yaml) for your testing. Some notes on this: 12 13The Windows image is huge. But you don't have to build it yourself! It is hosted on our public Docker registry 14No hardware acceleration in this VM as well (we use the same container) 15You get SSH access to the Windows VM via port 50022, which might help to overcome the missing clipboard :) 16 17Part 1: 18 19You goal for the first part is to obtain the flag on the guacd container component. It is located in `/flag.txt. 20 21Part 2: 22 23You goal for the final part is to obtain the second flag on the guacd container component. You can print it by calling the (setuid) binary /opt/flagtool readflag. 24 25https://guacamole.apache.org/ 26https://github.com/vadimpronin/guacamole-lite 27https://guacamole.apache.org/doc/gug/guacamole-architecture.html#guacd