[Ubertooth: pyside-tools not found Backtrack5 R3]

thanks guys, naive of me to think a later version of Kismet would work :-). Will try Kali as suggested, needed to get it installed, just had Kismet all working nicely. (go a TP-Link WDR4300 working as a drone (Open-wrt), looking at all frequencies - awesome)

I was compiling from source, good practice.....

[Ubertooth: pyside-tools not found Backtrack5 R3]

E: Couldn't find package pyside-tools

following instructions from http://ubertooth.sourceforge.net/usage/build/

when I type in

at apt-get install libusb-1.0-0-dev make gcc pyside-tools python-numpy

I get

E: Couldn't find package pyside-tools

using kismet-2013-R1b,

any suggestions please,

many thanks

[[Info] Usb Rubber Ducky Source Code]

JTAG is certainly an effective way to go about debugging, albeit a little slow depending on the controller. Depending on the complexity of what you are trying to accomplish, you may find it easier to debug code in a simulator. Or on the much lighter end, adding logging features to the firmware might help you get what you want. This could look for a "DEBUG" file in the root of the MicroSD card filesystem. If that exists, then write logging output to another (or the same) file on the card.

What does bus enumeration look like on your system? Does broadcast Ack/Nack timing returning to your keyboard give away your password to neighbouring USB devices? Can has class 09h? The Ducky has so much untapped potential. I'm really looking forward to seeing what people come up with.

A Simulator would be good, but I don't think ther is one for the AT32UC3B1256, unless you know otherwise. Looks like one has to use something like the JTAGICE to debug (http://www.atmel.com/tools/AVRJTAGICEMKII.aspx) Any recommendations anyone? This connects to a jtag connector, do we have a pin out yet of jtag connecter on the duck? (I can't see one....)