Zardus — 08/05/2021 :OOO: ATTENTION TEAMS! :OOO: We hope that you are excited about DEF CON CTF (reminder: setup is on Friday at 9:00am Vegas time)! To keep you amped until then, we have compiled info for you that might cause (or simplify) some prep work on your part! :OOO: Game network access: How will you access your network? We're glad you asked. We will provide you each with a VM that is VPNed into the game. You can use this VM as a jump box, or you can extract the wireguard configuration to set it up on your own (though we will offer absolutely no tech support for such a configuration). We'll grant access to these VMs by literally emailing ssh keys to your team POC emails like massive noobs, so make sure those mailboxes are secure! We won't send out the wireguard configs: you can scp them off of the VMs. The VMs will have several spare configurations so that you can distribute them to any players that need them, without compromising the configuration of the jump box. :OOO: Jump box??? There will be no services running on the jumpbox. The machine will have something like 2 cores and 8gb RAM, running Ubuntu 20.04. The jump box is there just for your convenience. You can nuke your jumpbox if you really want to, but honestly, you're just hurting yourself at that point. Use the jump box. :OOO: Services??? As in previous years, challenges will be running at 10.13.37.TEAM_ID. If you choose to export the wireguard config, your (hopefully) non-vulnerable personal machines will use 10.1.100+TEAM_ID.0/24, though we have reserved the lower 128 IPs of that network for our own use, so back off. Your gateway should be 10.1.100+TEAM_ID.1. We will tell you your team ID when we mail you your ssh key. :OOO: If you want to colocate your infra with our infra, Amazon's us-west will be pretty close. :OOO: PCAP access! This year, we once again put the decision of releasing PCAPs in YOUR hands. Each service will have a STEALTH port alongside its normal port. The stealth port will be 10000+SERVICE_PORT, so If a challenge listens on port 1337, the stealth port will be 11337. The stealth port hits the exact same challenge endpoint as the normal port, but traffic through that port will not be released to the victim team. But beware: maintaining backdoor access to other teams ain't cheap! If your team sends any traffic through a service's stealth port to a given team, you will only receive half points for stealing that team's flag that round. :OOO: What are OOO's DEF CON CTFs like? Prepare for trouble, and make it double! If you're new to the game, you might want to get a feel for our style by reading prior writeups by player(s): - DEF CON 28: https://dttw.tech/posts/Skww4fzGP - DEF CON 27: https://dttw.tech/posts/SJ40_7MNS - DEF CON 26: https://dttw.tech/posts/Hka91N-IQ Or viewing our prior challenges: http://archive.ooo/ Or reading our own writeup of last year: https://oooverflow.io/dc-ctf-2020-finals/ Or reviewing archives of tons of data from prior years: https://oooverflow.io/ In the archives, please take a special look at the game state JSON. We will communicate this to you with a brief time delay, and it gives you a near-complete view of the state and history of the game up to that point. Please make absolutely sure to familiarize yourself with last year's JSON (https://oooverflow.io/dc-ctf-2020-finals/final_tick.json). We're not guaranteeing that this year's will be identical, but last year's will be a great start. Down to the Wire Down to the Wire is a collaborative project hosted by a group of students across the country. Topics range from hardware to software to security. Down to the Wire Down to the Wire is a collaborative project hosted by a group of students across the country. Topics range from hardware to software to security. Down to the Wire Down to the Wire is a collaborative project hosted by a group of students across the country. Topics range from hardware to software to security. OOO — DEF CON CTF OOO — DEF CON CTF :OOO: In-person Logistics! If you are joining us in person, awesome! Some info: each team will have 4 tables and 8 chairs. You'll be provided with one power cord (ONE outlet) and one ethernet cable. The ethernet cable will have internet, and the power cord will probably kill you if you lick it (the Order highly discourages such actions). You should bring your own power strips, switches, etc. DEF CON wifi has actually been pretty reliable in recent years, FWIW, so you can also give that a try: https://wifireg.defcon.org/. Setup is 9am every day: you'll need your captain card to get in. The CTF network goes live at 10am! CTF ends at 8pm on Friday and Saturday and 2pm on Sunday. All times are Las Vegas local time. Zardus — 08/06/2021 :OOO: TEST EMAILS SENT! Test emails just went out to the captain and point-of-contact emails. If you did not get a test email, something is wrong, you will not get your jumpbox keys at 9am, and you need to get in touch with us ASAP. :OOO: PRE-GAME CAPTAINS MEETING! There'll be a captain's meeting sometime between 9am and 10am, as chaos allows. We'll hold the meeting in ctf-captains-voice and in meatspace at the same time. Zardus — 08/06/2021 :OOO: We've updated https://oooverflow.io/dc-ctf-2021-finals/ with some general rules and other info. OOO — DEF CON CTF OOO — DEF CON CTF Zardus — 08/06/2021 :OOO: SSH KEYS ARE SENT! Zardus — 08/06/2021 :OOO: The keys might need to be run through dos2unix. sshing into your jumpbox is not intended to be a challenge :slight_smile: :OOO: ATTENTION TEAMS! Captains meeting in 10 minutes, both in person and on ctf-captains-voice! Zardus — 08/06/2021 :OOO: Start delayed to 10:30am! Tracking down some networking issues. :OOO: While we wait! First challenge: inspired by @babaisyou_, a hacking gaming to practice your shellcoding skillz. Become Zero and hack through fun challenges of hacking madness! https://dc2021f-challs.s3.amazonaws.com/0aa863b61fb77ebc8479cb1ced1aaa4a87362e1d38e02f00b7d0395f5f7a84ac.tar.gz :OOO: This is a King of the Hill challenge, with score determined by how many levels you solve. First level incoming here shortly! Attachment file type: unknown lvl01.dat 225 bytes First level! ^ hacopo — 08/06/2021 We're having huge network issues -- the game is paused. Really sorry about this. Zardus — 08/06/2021 :OOO: Start delayed to 11am! Sorry about this. Zardus — 08/06/2021 :OOO: ATTENTION TEAMS! As expected, this year is a bit chaotic. In the network issues chaos, a screwed up game state JSON was accidentally released to the teams. Unfortunately, this contained many of this year's challenges. For fairness, we are uploading the JSON here. We cannot guarantee that these challenges will launch, or that they will launch in the exact state that they are in the JSON, so invest resources into these at your peril. You have the information, what you do with it is up to you. { "current_tick": 496, "current_tick_created_on": "Fri, 06 Aug 2021 16:50:21 GMT", "current_tick_duration": 60, "est_time_remaining": 58.737792, "exploitation_events": [... (2 MB left) Expand game_state-2.json 2 MB To be extra clear: there are URLs in there to download challenges that have not been released (and might not be / might not be in their current form). :OOO: ATTENTION TEAMS! Captains meeting at 11:00am for anyone that has questions about the above. Zardus — 08/06/2021 :OOO: Captain’s meeting no in voice and meatspace! Zardus — 08/06/2021 :OOO: Captain's meeting summary: - Some challenges leaked in the game state json. - Not all of them will be launched in their current form, so analyze at your own risk. - Flag limits for challenge retirement will likely not apply. We'll use the GREEN / YELLOW / ORANGE / RED system for challenge state. - Google is throttling DNS, so if you're on-site, try changing DNS. :OOO: DEF CON replaced our uplink, so the non-DNS issues should be mitigated. hacopo — 08/06/2021 game should be back up Zardus — 08/06/2021 :OOO: Imagine a world of bare metal ruby? Is it a dream? A nightmare? Find out, with OOO's new smarthome system, barb-metal, available at a team interface (and game state JSON!) near you! Zardus — 08/06/2021 :OOO: ATTENTION HACKERS! OOO's game dev division is still starting out, and we don't have the bandwidth for multi-platform development. Zero Is You ONLY supports computers running Ubuntu 20.04 on x86_64. Everything else is at your own risk. Zardus — 08/06/2021 :OOO: ATTENTION HACKERS! We'll be wiping all Zero Is You scoring that happened before 11am (i.e., while the network was down). :OOO: ATTENTION TEAMS! Update on the challenge disclosure: of the disclosed chals, the Order can 100% assure you that hyper-o will not be released in anywhere near its disclosed state. Take that as you will. :OOO: I was wrong before: ticks were set to 10 mins. Time is speeding up, and ticks are 5 mins now that things are flying!! hacopo — 08/06/2021 clarification on current_tick in the game state json: the file is generated right after the new tick kicks in, so at current_tick=N you're seeing events of <= N-1 Zardus — 08/06/2021 :OOO: OOO is happy to announce the next extension of "machine learning": an automated "Reviewer #2"! If you like getting rejections, submit to ooopf! mike_pizza — 08/06/2021 FYI: All flags follow the format of 000 followed by 45 printable bytes. All flags are 48 bytes total unless otherwise stated Zardus — 08/06/2021 :OOO: Sample flag: 000AAA6BBFD62CCCCA282457409C173D0CD20EEDE01337A (obf, that one is fake) Zardus — 08/06/2021 :OOO: FIRST BLOOD! HITCON :crossed_swords: Balsn solves the first level of Zero Is You that we consider not easy! ^ That level is Level 6 :slight_smile: Zardus — 08/06/2021 :OOO: ATTENTION TEAMS! Are you worried that JeffBezos will leave the planet and abandon AWS? SWITCH TO OOOWS, the new cloud computing infrastructure from OOO, coming to a DEFCON CTF challenge near you! Cloud, reimagined. Zardus — 08/06/2021 :OOO: FIRST BLOOD! StarBugs pwns ooopf to score the first A/D flag in DEFCON 29 CTF! Zardus — 08/06/2021 :OOO: FIRST BLOOD! Shellphish virtualizes their hopes and dreams and pwns ooows-flag-baby! The cloud, your way. Zardus — 08/06/2021 :OOO: FIRST BLOOD! Tea Deliverers take over Katzebin's smart home on barb-metal! Zardus — 08/06/2021 :OOO: PCAPs on ooows-flag-baby should start propagating soon. Sorry about that! adamd — 08/06/2021 ooows-flag-baby was done for a bit, but it should be back up now Zardus — 08/07/2021 :OOO: If you have questions about patching (inc: are we allowed to do X?), please feel free to ask! Patching is part of the hacking process, too! Zardus — 08/07/2021 :OOO: Flag Baby is going nighty night! The challenge has been retired. But maybe there's something else coming? adamd — 08/07/2021 :OOO: If a patch fails nothing happens: whatever was running before (either default or last patch) continues to run Zardus — 08/07/2021 :OOO: ATTENTION TEAMS! New challenge released: ooows-p92021 is ready to address your file storage needs! Zardus — 08/07/2021 :OOO: The flag for barb-metal is stored in memory on the virtual device. It's the first thing read over the serial in qemu. Zardus — 08/07/2021 :OOO: Attention DEFCON! Want to try Zero Is You, the shellcoding game inspired by Baba Is You that's currently stumping the best hackers in the world at DEFCON 29 CTF? Now you can! Come to the CTF room and give it a try on our kiosk! (some shellcoding experience recommended) Zardus — 08/07/2021 :OOO: Say goodbye to barb-metal! Maybe we should stick with BPF for the smarthome? adamd — 08/07/2021 :OOO: REMOTE HACKERS: MISSING THAT BEAUTIFUL IN-PERSON DISTRACTIONS? WE GOT YOU: https://www.twitch.tv/oooverflow (NOT INCLUDED (YET): EAR SPLITTING "ATTENTION TEAMS" FROM @Zardus ) Twitch OOOverflow - Twitch Zardus — 08/07/2021 :OOO: ATTENTION TEAMS! ooopf is gooone! Zardus — 08/07/2021 :OOO: ATTENTION TEAMS! Captain's meeting in 30 minutes! :OOO: Attention teams, the game is pausing for the night in 30 minutes! Zardus — 08/07/2021 :OOO: ATTENTION TEAMS! Captain's meeting in 15 minutes (9:45)! Zardus — 08/07/2021 :OOO: ATTENTION TEAMS! CTF is live! Zardus — 08/07/2021 :OOO: FIRST BLOOD! StarBugs coerces ooows-p92021 into a flag disclosure! hacopo — 08/07/2021 As part of PPP's score adjustment we added some exploits events. We accidentally included team 17 (our fake test team) as exploiter. We removed those team-17 attack events. Zardus — 08/07/2021 :OOO: ATTENTION TEAMS! OOO is proud to bring secure computation to OOOWS. Be what's next, with OGX. adamd — 08/07/2021 :OOO: Minor update to ooows-* challenges: the Order is releasing a new Dockerfile to improve stability (hard for the cpus to find time to pwn with so many vms), last line should be the only thing that changed from ubuntu:focal-20210723 # example: run apt-get -qq update && apt-get -qq upgrade && apt-get install -qq --no-install-recommends python3 python3-dev python3-venv python3-pip python-is-python3 supervisor curl sqlite3 libsqlite3-dev netbase sudo && \ pip3 install --upgrade pip setuptools && \ rm -r /root/.cache RUN useradd -s /bin/bash -m app RUN useradd -s /bin/bash -m device RUN mkdir /app && chown app:app /app USER app RUN python3 -m venv /app/venv RUN . /app/venv/bin/activate && pip3 install -U pip setuptools wheel RUN mkdir /app/web COPY /web/requirements.txt /app/web/requirements.txt RUN . /app/venv/bin/activate && pip3 install -r /app/web/requirements.txt RUN mkdir /app/bios copy supervisord.conf /etc/supervisord.conf COPY ./bios/bios /app/bios/bios COPY ./vmm /app COPY ./devices.config /app COPY ./devices-bin /app/devices-bin COPY ./web /app/web RUN . /app/venv/bin/activate && cd /app/web && ./init-db.py USER root RUN chown root:device /app/devices-bin/p9fs && chmod g+s /app/devices-bin/p9fs run touch /flag && chown root:device /flag && chmod 640 /flag && echo "000AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA" > /flag expose 9999 # We can't start without /dev/kvm anyways, so it's good if this fails CMD chmod 666 /dev/kvm && while true; do timeout 120 /usr/bin/supervisord; pkill -9 vmm; rm -rf /tmp/disks /tmp/vms && sudo -u app /bin/sh -c ". /app/venv/bin/activate && cd /app/web && rm ooows-web.db && ./init-db.py"; done MAJOR UPDATE ^ This reverted all your patches, please submit again Zardus — 08/07/2021 :OOO: ATTENTION TEAMS! You asked for the World Wide Web? We're giving you the Wild Wild West! A new CTF-in-CTF challenge is LIVE! mike_pizza — 08/07/2021 :OOO: Teams, we relaxed some of the patch testing constraints for ooows-p92021. If your patches were receiving an "expected version 'P92021'" error we encourage you to reupload your patch Zardus — 08/07/2021 :OOO: ATTENTION TEAMS! Please make sure to launch your WWW attacks through your WWW routers, NOT ON THE OPEN INTERNET TO ACTUAL INTERNET COMPUTERS OMG Zardus — 08/07/2021 :OOO: TEAMS! Make sure you're using the real OGX, not the leaked OGX. Zardus — 08/07/2021 :OOO: ATTENTION TEAMS! Scores are LIVE on WWW! (or will be, when they propagate to the public scoreboard in 5 - 10 mins) Zardus — 08/07/2021 :OOO: RARE HINT for WWW: please consider the security of your team routers. If your WWW team box gets grilled, check out http://10.13.37.x:5050/restart_my_device Zardus — 08/07/2021 :OOO: ATTENTION TEAMS! In a never-ending quest to provide the cutting edge in cloud technology, OOOWS now supports NETWORKING. Go, network, and PWN! Zardus — 08/07/2021 :OOO: The original 600-flag limit for ooows-p92021 will hold. The service will be retired after the top team scores 600 flags! :OOO: WWW is the Wild Wild West. It's up to you to figure out the individual services running in that insanity! Please stop asking us to hold your hands :slight_smile: Zardus — 08/07/2021 :OOO: UNCOMMON HINT FOR WWW: the team boxes aren't the only targets in the Wild Wild West. Find some more! adamd — 08/07/2021 :OOO: WWW Clarification: Self-run device resets should take roughly 2 minutes or so. If it takes significantly longer than that, create a ticket please and tell us how long it's been. Zardus — 08/07/2021 :OOO: ATTENTION TEAMS! StarBugs clunks ooows-p9 by capturing 600 flags. Great job! Zardus — 08/08/2021 :OOO: FIRST BLOOD! StarBugs breaks the enclave in OGX! adamd — 08/08/2021 :OOO: ATTENTION TEAMS: There are some problems with stealth events getting registered to the database (they are being missed), so teams are attacking over stealth but seem to be not stealth (yet there is nothing in the pcaps). We have all the original pcaps, we'll fix the issue, and recreate the stealth events. You're not missing attacks in pcaps :slight_smile: adamd — 08/08/2021 :OOO: ATTENTION TEAMS: As you know, the ooows-* family of services are hosted on different infra than the normal services. As an artifact of that, restarting pods are different: there might be some downtime when it's not available, there will likely be a small time delta when the default flag is on the service (we are running the same docker containers that we give you), etc. This should not affect your ability to get flags (I believe eventually consistent is the phrase), and if you see issues please file a ticket or ping me. trick-e — 08/08/2021 :OOO: ATTENTION TEAMS: Find out your WWW-CTF score by going to http://10.13.37.x:5050/current_scores Remember only the top 5 scores above 0 score in KoH. adamd — 08/08/2021 :OOO: ATTENTION TEAMS: ooows-ogx has all the flags pwned out of it. Congrats to StarBugs for pushing it over the limit (quite the close race). adamd — 08/08/2021 :OOO: (Zardus voice) ATTENTION TEAMS: The game will go down at 8pm today, and we will have a captain's meeting directly after. See you on the floor and on discord. Zardus — 08/08/2021 :OOO: Two more challenges will drop here on discord shortly after the team meeting! Sorry, we were geared up to launch them at 7:55, but things went haywire :slight_smile: adamd — 08/08/2021 :OOO: and the Wild Wild Frontier of the WWW is no more: the service is retired adamd — 08/08/2021 :OOO: ATTENTION TEAMS: Get ready to show us your shell! This King of the Hill challenge will launch tomorrow! Can you out-shellcraft your opponents? Only the worthy will hold the hill! https://dc2021f-challs-b.s3.amazonaws.com/91afc5fdbf42663ca001a84b6f3433a8d7ac2824046d36a6ac72e62db12181c7.tar.gz glhf Zardus — 08/08/2021 :OOO: Quick answer to something that scrolled through discord: broadcooom is very much alive and well tomorrow as well! adamd — 08/08/2021 :OOO: ATTENTION TEAMS: OOOWS is beta testing an update to OOOWS called ooows-hyper-o! Too long have the Users struggled with KVM, requiring ROI-dampening access to source code. To maximize organizational impact and promote our Junior Engineers to Senior Engineers and beyond, we have circled back to the hypervisor. Let's take things back to basics with a detail-oriented, technical deep dive into operational disruptors. Hyper-o is our most advanced hypervisor ever. We've obsessed over every painstaking detail, and we think our customers will love it. Only OOO is able to provide this industry-redefining product. Join us, to Be What's Next. This phase will remain active until the end of the CTF! https://dc2021f-challs-b.s3.amazonaws.com/388cdb406c90453e15e593e7ece1e86ebab4fcc25dd7ca2cc5c35392e6da101c.tar.gz File to patch: hyper-o.ko Max Patchable Bytes: 628768 Zardus — 08/08/2021 :OOO: There's a slight difference in our xinetd config for shooow-your-shell: socket_type = stream protocol = tcp wait = no - user = nobody + user = root bind = 0.0.0.0 server = /wrapper type = UNLISTED @@ -24,7 +24,7 @@ service service # max number of "CPU seconds" (less than the wallclock timeout) rlimit_cpu = 60 # internal memory limit -- also see the k8s limit in info.yml - rlimit_as = 64M + rlimit_as = 1024M # Leave this one in. Mostly innocuous, but could help if we need # to debug the container / in case of OOM / etc. Sorry about the inconvenience! Zardus — 08/08/2021 :OOO: ATTENTION TEAMS! Please download this encrypted blob: https://mega.nz/file/h5VQhJCI#9_uqmdNME7SMmVUeL2dBl9GaU_V7uCSq9eg_8tQ9QAs . We'll give more details at the captain's meeting at 9:45am! 707.44 MB file on MEGA Zardus — 08/08/2021 :OOO: ATTENTION TEAMS! Captains meeting in 5 minutes! adamd — 08/08/2021 :OOO: ATTENTION TEAMS: ooows-broadcooom was redeployed to handle the new tick times and now bounces every 60 seconds (change to Dockerfile). If you have/had patches that you were relying on, they were wiped away and you'll need to resubmit your patch when the game starts. Here's the relevant line: CMD chmod 666 /dev/kvm && while true; do timeout 60 /usr/bin/supervisord; pkill -9 vmm; rm -rf /tmp/disks /tmp/vms && sudo -u app /bin/sh -c ". /app/venv/bin/activate && cd /app/web && rm oo ows-web.db && ./init-db.py"; done Zardus — 08/08/2021 :OOO: Captain’s meeting now in captains-voice and meatspace! Zardus — 08/08/2021 :OOO: FAQ: Do other teams see your shellcode? Yes, if it takes the hill! :OOO: FAQ: How often is history.txt synced? Very often. ^ both for shooow-your-shell :OOO: Game launch imminent; just doing final checks. :OOO: FAQ: Do teams get PCAPs though the game is frozen? Yep! :OOO: The password for the qcow that will eventually replace what we lovingly call "rantman" for hyper-o is OLCXJNQUMVPTXSLJIKWNVSYPAYMDQYZFLKNTOXTFAQFOHKONKYEFTPPOGXGYSUGH. Check it out! We plan to launch that at 100, 200, 300, or 400 max flags, depending on how much it's being exploited. If everyone starts grilling it right from the beginning, it'll get swapped in earlier. :OOO: FAQ: How often does the history get synchronized for shooow-your-shell? Constantly in a tight loop. :OOO: FAQ: What happens with concurrent, but incompatible histories? The later one should win, but both shellcode submissions will get points. In other words, the /score file is never invalidated, only updated with new submissions. :OOO: ATTENTION TEAMS! DB restore is taking longer than anticipated. Hoping to start at 10:30am! Zardus — 08/08/2021 :OOO: The database has been bribed and is ready to roll. Launching at 10:30! :OOO: 1 minute until launch! :OOO: GAME ON! Zardus — 08/08/2021 :OOO: ATTENTION TEAMS! We've resolved an issue with hyper-o patching. Please try your patches again! :OOO: FIRST BLOOD! StarBugs solidifies their virtualization reputation by solving hyper-o! :OOO: We're looking into broadcooom stability. Zardus — 08/08/2021 :OOO: The sync bot for shooow-your-shell is working just fine, in the sense that it is properly reading, picking, and writing data. I'm about to push a little update that'll let you see your own score, so that you can panic less :slight_smile: adamd — 08/08/2021 :OOO: ATTENTION TEAMS: broadcooom is back up!!!!! Zardus — 08/08/2021 :OOO: ATTENTION TEAMS! Want to see your current shooow-your-shell score? The newly-deployed version shows it to you! Diff: def print_status(): + print("# Current score:", open("/score").readlines()[0].strip()) print("# Current hill:") print("GLORIOUS VICTORY") for entry in reversed(history[-10:]): if entry['winner']: break - print(f"... under that, code from team {entry['team']}: {entry['code'].hex()}") + print(f"... under that, code from team {entry['team']} at {int(entry['time'])}: {entry['code'].hex()}") crowell — 08/08/2021 :OOO: to make it easier to launch OOOWS with the new hyper-o hypervisor, please see this script to make your life easier https://gist.github.com/crowell/1ec1cb0a5244efea75c2c08207273e7b adamd — 08/08/2021 :OOO: ATTENTION TEAMS: FIRST BLOOD on ooows-broadcooom to Katzebin ! :clap: :clap: :clap: Special mention to PPP who was also impacted in the race to first-blood by a broken ooows-broadcooom instance this morning Zardus — 08/08/2021 :OOO: Attention teams! hyper-o is hyper, but frail. If you're hitting it more than once every few seconds, you're going to have a bad time. The good news is that with private instances, you'll only bring things down for your own attacks, so we're totally okay letting you step on your own toes if you want. THat being said, I'm deploying some mitigations for the load, so it'll get better :slight_smile: Zardus — 08/08/2021 :OOO: To be very clear on shooow-your-shell (and spoil it a bit): there are quite a few intended (and several unintended!) ways to mess with history.txt. That being said, as long as you pass the constraints imposed by the history.txt you're running under, you will get points for your shellcode. Please stop asking about the history sync: it's working fine, but "garbage in, garbage out". You can confirm your current score by simply connecting to the service. :OOO: ATTENTION TEAMS! Given the late start, we'll extend the CTF by 30 minutes. We'll end at 2:30pm Las Vegas time! :OOO: ATTENTION TEAMS! The full hyper-o image will go into place soon! Be ready! :OOO: ATTENTION TEAMS! We're resolving some flag setting issues; should be much better soon! :OOO: ATTENTION TEAMS! hyper-o has achieved its ultimate form! Connect, and enjoy OOO's next-generation virtualization stack! Zardus — 08/08/2021 :OOO: ATTENTION TEAMS! Please reapply your hyper-o patches with this re-deployment ^ :OOO: ATTENTION TEAMS! The new hyper-o interface is HTTP. Zardus — 08/08/2021 :OOO: ATTENTION TEAMS: The new hyper-o deployment (posted early this morning: https://mega.nz/file/h5VQhJCI#9_uqmdNME7SMmVUeL2dBl9GaU_V7uCSq9eg_8tQ9QAs, password OLCXJNQUMVPTXSLJIKWNVSYPAYMDQYZFLKNTOXTFAQFOHKONKYEFTPPOGXGYSUGH) is the same hyper-o.ko and the same kernel image, wrapped around the OOO VMM stack. 707.44 MB file on MEGA :OOO: The New hyper-o's serial console is null-yeeted; use VGA for output! Zardus — 08/08/2021 :OOO: So... PCAPs are flying for broadcooom! Really sorry about this; I thought people were complaining about stealthing, not about actual missing pcaps. My fault, and I apologize. Zardus — 08/08/2021 :OOO: Hyper-o patching is FIXED! Please resubmit your patches: we can't requeue them without causing other issues :slight_smile: Zardus — 08/08/2021 :OOO: FIRST (RE)BLOOD! StarBugs pwns the NEW AND IMPROVED hyper-o! True VMX gods. Zardus — 08/08/2021 :OOO: hyper-o having some problems; working on it ASAP :OOO: hyper-o patches will need to be redeployed if this fix works Zardus — 08/08/2021 :OOO: hyper-o might be flying! Grill it up fast! :OOO: 4 MINUTES LEFT!!!! :OOO: GREAT JOB!!! Let's have a quick captain's meeting in voice and meatspace