Solutions:

• Hidden keyboard shortcuts
• Keyboard emulation

Should this be filed under USB keyboard payloads?

A non-nefarious use for this device could be a device that records and plays back keyboard macros. The user could type a key combination or use a special key to automatically record / playback keystrokes. It would serve as an automation tool for programs that don't allow software macros, or to string together various program keyboard shortcuts.

Example: Altium's "jump to component" command takes the key combination E-J-C to execute. The darkwing could map the '1' key on the num pad to that key combination to execute the command more directly.

Tracker issue for feature

Tracker issue for feature

Will likely require further documentation as I didn't really understand it on first look.

Tracker issue for feature

Tracker issue for feature

So one of the first things that we need for this project to be viable is the ability to interpret existing USB Rubber Ducky payloads. Payloads are plaint text files loaded onto the Rubber Ducky via an SD card. This raises an architectural question: how do we get scripts onto the device if it's too small to support an SD card?

One idea is a portable C library that can parse strings, interpret the Ducky Script, and then provide hooks to whatever is doing the execution. We then have a way to put the DARKWING into a mass storage device mode and load the text files onto it.

Another option is to have a script in the Makefile that will look at a payloads directory, parse the Ducky Script, and then generate a C file that is included in the build during compile time. This has the downside of requiring a full toolchain to modify the payload but it means we don't need any file system middle-ware, mass storage USB code, on-device interpreters, etc.

Prior art using Arduinos and SD cards:
https://github.com/ernesto-xload/ducky_interpreter/
https://github.com/Creased/arducky

I think it's worth considering an open source hardware license separate from the MIT License since it currently applies only to intellectual property where where copyright applies (like firmware, schematics, etc.), not physical objects themselves.

As far as the particulars, we have a few options:

• CERN OHL
• TAPR OHL
• Make a Hashbang OHL (Do we need lawyer$ for this?)

This should probably be part of a larger discussion for all the projects that come out of the Space but Darkwing is a good test case for it.

Tracker issue for feature

Tracker issue for feature

Will probably require further documentation

Tracker issue for feature

Problem

Clicking USB Type C DIY cable ends results in a redirect to a page with the following:

{"message":"Page Not Found"}

Solution

Update the link to a working endpoint.