Dаrren Kitchen

Just wanted to test some stuff. ?ͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬͤͩͬͧͫͬ

I've not done charging.

I've powered mine before with a 3v watch battery.

It's worked well for me, the only problem I ever had was when I told the compiler I had an SD adapter hooked to it, but I did not. That caused Windows to blue screen when I used some of the switched I had hooked to those pins. :)

It seemed to go over pretty well, thanks. :) I added quite a bit of stuff post Outerz0ne.

Damn, Monta Elkins' URFUKED talk at Defcon seems similar to mine. He does RF, I do some other things. His talk precedes mine, this depresses me since it sort of steals my thunder. Also, the similar name is interesting.

I made a quick video that will show you the basics of setting up the Teensyduino environment in Windows so you can make PHUKD devices: http://www.irongeek.com/i.php?page=videos/...syduino-arduino

Hi all, I've be doing some work on locking down Windows Vista/7 against malicious USB devices: http://www.irongeek.com/i.php?page=securit...ous-usb-devices Anyone have guidance on doing the same in Linux? I imagine there are udev rules that can be set? Adrian

I'd imagine it would effect all operating systems since it seems to be an issue with CPU time on the Teensy. Also, the SD will only be at 1.1 speeds. If you plan to copy files to storage, use a hub and a USB 2.0 device, like I did in my Trojaned mouse.

Paul explained it to me, seems using the SD takes a lot of CPU time on the Teensy, and causes the clock to have issues.

Ok, more info on the problem. It only happens when I use the SD card, and USB type "Disk(SD Card)+Keyboard". Just "Keyboard+Mouse" does not have the time drift.

I've encountered a problem with millis() function in Teensyduino.It seems that after my program runs for awhile, the clock on the Teensy seems to slow down and not give accurate results. It seems to be a side effect of me using my "CommandAtRunBarMSWIN" function, but the only time related function I use in it is delay() and when I tested with just that it the loop did not seem to skew the clock. I'm using the latest alpha to my knowledge. Ideas? Adrian void CommandAtRunBarMSWIN(char *SomeCommand){ //digitalWrite(ledPin, HIGH); // set the LED on Keyboard.set_modifier(MODIFIERKEY_RIGHT_GUI); //Windows key Keyboard.set_key1(KEY_R); // use r key Keyboard.send_now(); // send strokes Keyboard.set_modifier(0); //prep release of control keys Keyboard.set_key1(0); //have to do this to keep it from hitting key multiple times. Keyboard.send_now(); //Send the key changes delay(1500); Keyboard.print(SomeCommand); Keyboard.set_key1(KEY_ENTER); Keyboard.send_now(); Keyboard.set_key1(0); Keyboard.send_now(); }

I've updated the PHUKD Library to 0.2. The main changes are that I've added two functions for the Gnome desktop under Linux: ShrinkCurWinGnome() CommandAtRunBarGnome(char *SomeCommand) you may also see something about OS X, but it does not work. Can anyone tell me a run bar equivalent that works in OS X? I've also changed the library so that it goes in the normal libraries folder, and not the same folder as your sketch.

Posted it here: http://www.irongeek.com/i.php?page=securit...y_PHUKD_library I've also added some functions to make it easy to set traps with the CAPS/NUM/Scroll Lock keys. :)

I've not done much work with the SD yet, best ask Paul. My understanding is you will need the experimental version of Teensyduino http://www.pjrc.com/teensy/experimental.html

Quick demo of the tronjaned Mouse I soldered up with a PHUKD device, hub and storage: Hope to put some more code, and an Arduino library up soon: http://www.irongeek.com/i.php?page=securit...eystroke-dongle

I can, but I'd like to have it so my code is all you have to touch, and you don't have to change Paul's code. That way, when he updates Teensyduino, you don't need to change his headers again.

I can edit these lines in usb_private.h to change the value: #define VENDOR_ID 0x16C0 #define PRODUCT_ID 0x0482 But is they a way to change them/redefine them in my own code? I tried to use #undef and then use #define again, but to no avail.

Damn. need to proof read. Ney should be New. :)

One unit is a Teensy 2.0 with an on board SD adapter for storage. The other is a larger Teensy 2.0++. I'm working on making swappable shields for both so that they can be re-purposed with little trouble (better to burn up a 50 cent piece of perf board/headers than a $20 microcontroler). I'm doing this by soldering male/female headers to both so I can just snap them together to make electrical contact. Notice on the back side of the boards I've made a line for common ground for the DIP switched and other inputs. Also, I'm working on packaging the units by making a jacket out of heat shrink plastic I can snap on and off.

Good idea, capslock can be annoying enough to force the users to send a message that says "Hey, I'm here".

Looks like I'll be speaking at Defcon on this subject: http://www.defcon.org/html/defcon-18/dc-18...s.html#Crenshaw Should be fun, and I'm planing on releasing a library for those that want to include something.

This is hit or miss, since it depends on the numlock key changing states. If you put: #include "usb_private.h" #include "usb_api.h" in your code, you can then look at the variable keyboard_leds, which has a tendency to change as someone logs in. Nifty. http://www.irongeek.com/i.php?page=securit...eystroke-dongle

Damn dude, we are not the only ones who thought the idea was cool.

I plan to bring the units I've been working on to Notacon if anyone else will be there.