OzSec

OzSec 2025

The OzSec 2025 Wichita information-security conference represented by the organizer's CRASHANDBURN badge-design archive. The current event archive identifies the venue and badge USB-data-cable context but contains conflicting date text, while the public repository remains explicitly work in progress and does not prove final production or distribution.

Hyatt Regency Wichita, Wichita, Kansas · United States · 2025

OzSec 2025 CRASHANDBURN Badge

A source-conservative OzSec 2025 badge record: the organizer-linked repository calls itself the code and supporting-document archive for the CRASHANDBURN badge, while retaining work-in-progress hardware alternatives and MicroPython game source.

Lifecycle

Add-ons & Upgrades

OzSec 2025 CRASHANDBURN Badge source-backed work in progress

development workflow

Host flashing and upload workflow

The README calls for VS Code, Python, mpremote, and a boot-select flash procedure, using a Raspberry Pi Pico 2 on a breadboard for current firmware development rather than documenting a final deployed attendee workflow.

Compatibility: OzSec 2025 CRASHANDBURN development source snapshot

OzSec 2025 CRASHANDBURN Badge source-backed work in progress

firmware prototype

MicroPython selectable game set

The current main script selects HiLo, DTMF, Kode, and Rock-Paper-Scissors games, updates associated LEDs, registers buttons, and restores a random idle blink mode.

Compatibility: OzSec 2025 CRASHANDBURN firmware source snapshot

OzSec 2025 CRASHANDBURN Badge planned reference design

hardware planning

USB-C, charging, and power-path planning

The work-in-progress BOM lists USB-C connector and protection parts, a charge-controller section, power switch, AA connectors, regulator parts, and charge/status LEDs without documenting the final board or battery assembly.

Compatibility: OzSec 2025 CRASHANDBURN Badge design archive only

OzSec 2025 CRASHANDBURN Badge planned alternatives

hardware planning

Work-in-progress controller and display alternatives

The BOM documents alternative display modules, an RP2350 section, and an ESP32-S3-WROOM-1-N8R8 option, while the separate pinout is explicitly for an ESP32 version. These are development choices, not a confirmed final badge configuration.

Compatibility: OzSec 2025 CRASHANDBURN Badge design archive only

Operational history

Issues & Camp Impact

event-date archive inconsistency · primary organizer-hosted archive · needs dated archive recovery

The current OzSec 2025 archive contains October 23-24 wording in its headline and FAQ but October 10-11 wording in its schedule, indicating that the retained page mixes date fragments. This record therefore associates the badge archive with OzSec 2025 and the Hyatt Regency Wichita venue without asserting an exact event date.

The record avoids turning a stale or mixed archive page into an incorrect precise date claim and leaves the date open for a dated official programme, ticket, or post-event report.

final delivery and distribution gap · organizer-linked repository and historical event archive · event record and design archive not reconciled

The current repository describes the badge as work in progress and says it will be built, while the event archive identifies OzSec 2025. The reviewed public sources do not confirm a final manufacturing run, ticket or attendee allocation, pickup, shipment, firmware deployed at the event, or individual receipt.

The catalogue preserves the real design/archive trail without treating a planning repository as proof of a final issued conference badge.

firmware release and validation gap · primary source repository · prototype source visible; production release unrecovered

The repository includes current MicroPython source and ESP32-S3/Pico 2 target files, but the README describes breadboard development and work in progress. No tagged final firmware, reproducible production build, test result, challenge outcome, or evidence that this source ran on conference units was recovered.

The game and flashing material remains valuable development evidence, but not a claim about production behavior or a supported owner-update path.

hardware configuration and BOM gap · primary work-in-progress repository · final configuration unconfirmed

The public BOM identifies alternative displays, an RP2350 section, an ESP32-S3 option, and an ESP32-specific pinout, while its own header calls the BOM work in progress. It does not establish the controller, display, PCB revision, battery, enclosure, component population, or electrical behavior of a final artifact.

The record can show the documented development directions without collapsing alternatives into an invented production specification.

missing rights-cleared image · local project policy · needs licensed original replacement

No OzSec 2025 CRASHANDBURN badge image is published because the organizer event archive and public repository do not pair a specific badge image with a reusable license or explicit permission basis, attribution, and processing notes.

The record remains source-backed and image-free rather than copying event media, repository previews, social-media images, screenshots, placeholders, or generated approximations.

repository licensing gap · public repository root review · no explicit root license identified

The reviewed public repository root lists source, hardware, scripts, firmware, and documentation but no explicit LICENSE file or license declaration was identified. Public visibility is not treated as permission to redistribute hardware, firmware, documents, or embedded visual material.

The catalogue links the source trail for research while preserving the separate requirement for explicit reuse terms, especially for any future local image asset.

Resources

Sources