BSidesPDX 2015 Badger Badge
The BSidesPDX 2015 Badger badge is a conservative source-backed badge-hacking board record tied to the official Electronic Taxidermy: Badger Hacking workshop and the public PDX Badgers 2015 PCB and firmware repositories.
BSidesPDX
The October 16, 2015 Portland Security BSides edition whose official schedule lists the Electronic Taxidermy: Badger Hacking workshop with Michael Leibowitz and whose PDX Badgers repositories preserve the public Badger PCB and firmware archive.
Portland, Oregon · United States · 2015
The BSidesPDX 2015 Badger badge is a conservative source-backed badge-hacking board record tied to the official Electronic Taxidermy: Badger Hacking workshop and the public PDX Badgers 2015 PCB and firmware repositories.
Lifecycle
The firmware maps monochrome tail, back-foot, front-foot, and nose LEDs plus one RGB eye LED and groups them for badge display modes.
The official BSidesPDX schedule places Electronic Taxidermy: Badger Hacking in the workshop track with Michael Leibowitz on October 16, 2015.
The README and firmware document `/leds` and `/leds/` routes for status, all/none/blink/chase/twinkle modes, individual LED state, and RGB color updates.
The README and firmware document `/flag` and `/flag?newflag=...` behavior, with source code initializing the default flag as BADGERMASTER.
The firmware source includes ESP8266 Wi-Fi, WiFiClient, ESP8266WebServer, and mDNS support and serves a BSides PDX 2015 Badger web UI.
The PCB repository preserves Eagle board and schematic files, a project library, scripts, OSH Park design rules, and multiple Gerber ZIP archives.
The firmware defines BadgerNet as both preferred infrastructure SSID and hotspot basename, with retry behavior before badge-hosted service fallback.
Operational history
The catalogue models the artifact conservatively as a BSidesPDX 2015 badge-hacking board archive rather than a universal attendee badge claim.
The record cites code and hardware sources but does not reuse repository artwork or social/event imagery as a hero image.
The entry remains source-backed and image-free rather than copying logos, board-art files, event-page imagery, screenshots, or generated visuals.
Hardware and firmware claims remain limited to the public repository files and official schedule wording.