[Version 1] The Hak5 Standard

[Jerico_Tyler]

I've noticed many people suggesting a modular ducky that allows you to select code depending on the binary input from a dip switch.

The main problem I can see with this is people designing systems based off of one control scheme and other's trying to make it work with their's. While this isn't that hard of a problem to fix I think it would be best if we go ahead and assign certain switch ranges to certain roles.

For example the toggling of the most significant bit in an 8-bit DIP could toggle into the halfbyte loader.

OR

We could make it where all low bits equals the half byte loader being accessed.

These of course are just suggestions and can be ignored if you want. The Standard would be more of a suggestion really in order to provide a safe and happy coding experience for all.

+EDIT+

I guess this isn't as of good of an idea as I thought o.o

Edited May 4, 2010 by Jerico_Tyler

[Mr-Protocol]

There really cannot be a standard even with the simplest code. Delays need to be changed depending on the system it's being plugged into. If someone is savy enough to code the Ducky. They should have no issues adding delays or making functions work on their Ducky from someone's code.

And as most open source, there is no standard really. So people have the flexibility to do what they want with it. Break out of standardized environments... like Windows :-s. sorry for the mini-rant lol.

Edited May 4, 2010 by Mr-Protocol

[Jerico_Tyler]

!EDITED!

Now that I think of implementing a standard isn't quite what I want to mean

I'm Suggesting a way to organize your modular ducky.

Something like this is what I'm talking about:

MULTIPLE OS DUCKY AKA GLOBETROTTER

DIP Switches
===============
A:B:C:D:E:F:G:H
===============
-----------------------------------------------------------------
A    : 0=PC, 1=MAC
-----------------------------------------------------------------
B    : If A is 0 then 0=Windows 1=Linux
     : If A is 1 then 0=intel   1=PPC
-----------------------------------------------------------------
CD   : OS version [4 per OS] (Too Long to Write out right now)
-----------------------------------------------------------------
EFGH : Payload [16 per OS Version]
-----------------------------------------------------------------
DEBUG: Can be added by adding another switch  
       but for applications where the top  
       of the board is accessible, it is not needed
-----------------------------------------------------------------

This would only Denote how the ducky would decided what code to run.

If you want I'll put up Example code on how this system would work Code wise.

Edited May 4, 2010 by Jerico_Tyler

[Deevd]

Hi jerico_tyler,

I do understand what you would wan't to create.

But I do have to say I don't really understand the CODE you posted up here...

Could you maybe show some Example code?

thx

[Jerico_Tyler]

Hi jerico_tyler,

I do understand what you would wan't to create.

But I do have to say I don't really understand the CODE you posted up here...

Could you maybe show some Example code?

thx

I'll get to it after this week! @_@ I'm a high school senior and I've got finals

[Deevd]

Starting my finals next week too :)

I wish you good luck ! Post them when you have some time...

[BITS1]

Hi! I saw your post and I'm very interested in seeing how we can make it so that the Teensy can identify what system its on and carry out certain command based on whether its on a Mac, Linux, or Windows computer. Has any one done that before? I know we could determine ourselves what type of computer it is and just select certain dip switch combo to execute certain commands but I wonder if we can actually have Teensy identify that for us.

Bits1

[Jerico_Tyler]

Sorry for the delay! I had a fun time last semester @_@;; I'll be writing up the code examples during my free time this semester.