If you entered the URL manually please check your spelling and try again. If you think this is a server error, please contactTools and firmware for AX206 photo frames, from http://sourceforge.net/projects/dpf-ax/ DPF remote display software distribution (dpf-ax) This is a free software package to: * Patch or reprogram digital picture frames (DPFs) based on the AX206 CPU * Make them display system information using lcd4linux, VDR (Video Disk Recorder) and other linux based software. This is a chaotically growing README. You'll have to gather some information from here and there and probably use google, too. AX206 DPF firmware (also referred to as BSOH - blue screen of hack) Read all the firmware details in src/README or src/README.developer Firmware detection & flashing - A proper Linux system with GCC, libusb-dev, Python 2 (note: Python 3 will *NOT* work!) and python-dev. - The dpf-ax tools: dpf-ax_YYYYMMDD.tgz from http://sourceforge.net/projects/dpf-ax/files

("YYYYMMDD" is a timestamp - always use the newest one) IMPORTANT: identify.py will put a copy of your dpf's firmware in the fileIt is strongly recommended to make a backup of this file, so you can re-flash the original firmware if something goes wrong. Alternatively you can make a dump of the entire flash using the fulldump.py script.Kenworth Air Cleaners For Sale LET ME SAY IT AGAIN: make a backup of your dpf's original firmwarePitbull Lab Mix Puppies For Sale In Illinois 1. Run 'make' to build the dpf access library, python modules and helpers.Soft Close Toilet Seat Plastic Hinges If you get an error that "usb.h" could not be found: install libusb-dev. 2. Connect your frame and enable USB transfer

(Press "MENU" -> select "USB Connect", "Connect to PC" or whatever its called). 3. Wait a while and check dmesg for the /dev/sgX assignment (e,g. 'tail /var/log/syslog'.) Look for line containing something like .. Attached scsi generic sg2 type 5 .. --> X=2 here ;) 4. Go to the tools directory and run './identify.py /dev/sgX' as root. Replace 'X' with the number you found under 3. 5. If your dpf is supported, download the firmware package "dpf-ax_firmware_YYYYMMDD.zip" from http://sourceforge.net/projects/dpf-ax/files, extract it and use the fw_TYPE.bin that matches the TYPE identify.py detected. 6. Put your dpf in boot mode (press & hold MENU, press & release RESET, release MENU) and run as root/src/fw_.bin -f If your dpf is not supported, have a look at the picframe wiki at or you can try to contact me (superelchi) at sourceforge or post a request in If restore.py is not working (or you prefer windows :-o), see tools/README.windows

for instructions howt to do the detection & flashing. Verify that you have a decent development system (GCC, development libraries, subversion -- if you want to build lcd4linux) installed. You can build different targets, depending on your needs. * The dpf access library, python modules and helpers: * The curren SVN version of lcd4linux with dpf-ax support: You need an internet connection. because lcd4linux is pulled from their server. You might also have to install the package "pkg-config", or else the configure procedure will likely fail. * The firmware for all known frames: Note: read src/README for more information about prerequisites for firmware building. * The full monty: There is no Windows driver for hacked frames. But there is partial support for firmware detection and backup. There is experimental Cygwin support. You need python and libusb-devel CygwinCompile and install sg3_utils yourself because no Cygwin pacage is

To access DPF when it appears as a drive, run as Administrator and specify the drive letter. To access DPF in bootloader mode, install libusb-win32 filter driver for that USB device. There is no need to run as Administrator for bootloader mode. * Configure lcd4linux: normally, the default settings will do. to use other drivers or cross compile, check build-dpf-lcd4linux.sh > cd lcd4linux; ./lcd4linux -f .. Notes about the lcd4linux dpf driver: - Property 'Backlight': Set the dpfs backlight/brightness. Values: 0-7 (0 = off, 7 = max). - Property 'Orientation': Set the dpfs *LOGICAL* orientation. Note: *PHYSICAL* orientation does not matter. Rotation is done in the driver. Value (height != width): 0 = landscape, 1 = portrait, 2 = reverse landscape, 3 = reverse portrait. Value (height == width): 0 = standard, 1 = rotate 90° CW, 2 = rotate 180°, 3 = rotate 90° CCW If the lcd4linux build process fails, you may want to start over without

running the entire build procedure. See build-dpf-lcd4linux.sh for the single steps. Right, this could also be in a makefile to be more fool proof.. For features of this firmware, see Changelog Find updates, documentation and some help here: For our german users, explanations can be found here:Security researchers have found a fundamental flaw that could affect billions of USB devices. This flaw is so serious that, now that it has been revealed, you probably shouldn’t plug a USB device into your computer ever again. There are no known effective defenses against this variety of USB attack, though in the future (months or years, not days) some limited defenses might be possible. This vulnerability, which allows any USB device to take over your computer, mostly exists due to the USB Implementers Forum (the USB standards body) eschewing security in favor of maximizing the versatility, and thus the massively successful adoption, of USB. The USB IF itself notes that your only defense against this new attack vector is to only use USB devices that you 100% trust — but even then, as we’ll outline below, this won’t always protect you.

This flaw, dubbed BadUSB by Security Research Labs in Berlin, leverages the fact that every USB device has a controller chip. Whether it’s your PC, smartphone, external hard drive, or an audio breakout box, there’s a USB controller chip in every device that controls the USB connection to other devices. It turns out, according to SR Labs, that these controllers have firmware that can be reprogrammed to do a whole host of malicious things — and, perhaps most importantly, this reprogramming is almost impossible to detect. This vulnerability mostly stems from the fact that USB, by design, is incredibly versatile. USB can be used to connect just about any kind of peripheral to a host machine — an ability that is only possible because of USB classes and class drivers. Basically, every USB device under the sun has a class — a classification that defines the device’s function. Some common classes are human-interface devices (HIDs; keyboards, mice), wireless controller (Bluetooth dongles), and mass storage (thumb drives, digital cameras).

On the host (your PC, your smartphone) there are class drivers that manage the functions of that particular class of devices. This is why you can plug a USB keyboard into just about any device and it’ll work flawlessly.The problem, according to SR Labs, is that these USB controllers can have their firmware reprogrammed so that they announce themselves as a different class. For example, you could reprogram a mass storage device so that it masquerades as a network controller, so that all of your network communications (websites, passwords) get redirected to the device. Or, even worse, you could reprogram the firmware of a thumb drive so that it becomes a HID, and can thus issue keyboard and mouse commands to the host machine. These commands might be used to install malware, or to rewrite the firmware of other attached USB devices. Suddenly you are sitting on a computer worm of Conficker proportions that could take down most of the world’s devices.While finding a security hole in USB isn’t exactly a surprise, the main issue here is that there’s no immediate fix.

As of today, there could be billions of USB devices out there with firmware that could be reprogrammed by a computer virus — and, according to SR Labs, it’s impossible to spot the modified firmware unless you know exactly where to look. (It took months for SR Labs to reverse engineer the controller firmware, and it doesn’t sound like they’re giving up their secrets any time soon.) The security researchers also say that malware scanners can’t access the firmware of a USB device — so you can forget about that angle, too. SR Labs says it will release more details and proof-of-concept tools at Black Hat 2014 on August 7. [Read: How USB charging works, or how to avoid blowing up your smartphone.] It would be possible to mitigate against this attack in the future if every device maker signed their firmware, and then your computer checked that signature every time you plugged the device in — but I suspect, given the scale of the USB device ecosystem, such a change would take months or years to adopt.

Another option would be designated USB ports on your computer — so, you might have a port that only accepts mass storage devices, and is completely incapable of handling other classes of USB device. [Read: How to watch hacking, and cyberwarfare between the USA and China, in real time.]Ultimately, though, the only real mitigation is ensuring you only use USB devices that you trust. It’s basically like unprotected sex: If you plug your USB memory stick into another computer, you should then assume that your memory stick is forever compromised. The problem with this approach, though, is that your own computer could infect your USB devices without you knowing — and unless you’re a very careful surfer, it’s very hard to keep your computer completely malware-free. Which brings us back to the beginning of the story: Maybe it’s just best if you don’t use USB for a while.Fortunately my cupboard is full of PS/2 keyboards, parallel printers, and stacks of rewritable DVDs for exactly this kind of apocalyptic occasion…