Keelog.com has a really concise description of how to build a PS/2 based keylogger. The main components are an AT89C2051 microcontroller and a 24C512 serial EEPROM. Once it is plugged in, the device begins recording all of the codes generated by the keyboard. The data can then be dumped using their keygrab software.
[thanks Boss]
Actually the web address is http://www.keylog.com….
My bad, actually it’s http://www.keelog.com/
i saw this project here some minutes ago … good one …. i’ll do it tomorrow … this is very usefull :D
There’s a commercial aspect to this.
http://www.keyghost.com/ordering.htm
Nice to know i can finally make my own now.
Here is a wireless keystroke data tap that transmits the data to a remote location:
http://gbppr.trighost.org/mil/keystroke/index.html
looks like hackaday has already started to suffocate keelog.com; or maybe their server was already mollasas. :)
Whoo Im so doing this tomorow or sometime this weekend. But how many keystrokes is 65536 bytes? And is there anyway that there diagram could be altered to increase capacity?
@ abseeley:
“Although the keyboard logger has 64kbytes of memory, this doesn’t mean 64 thousand keystrokes can be memorized. One key-press-release sequence requires 3 bytes for a standard key and 5 bytes for an extended key.”
65536 / 3 = whatever.
ditto on increasing capacity. How?
@joelanders
Ok i’ve been checking out other EEPROMs and If you go parralell instead of serial then you can get up to about 512kb I think at least. But I dont know how this would effect the circuit im going to look into it more and revise. I’m still kinda getting my feet wet with the hole electronics thing but im wading through it ok. Oh and its 21000 approx keystrokes.
Don’t go parallel!
Since the 24C512 memory they are using is I2C, there are two ways you can go. The quickest way might be just to replace the chip with a 24xx1025, which Microchip sells and is twice as large.
The more extensible option is to add more 24xx512 chips. Because they are I2C devices, up to *EIGHT* can be connected using the same two data lines. Each eeprom needs to have a unique id, which is set by connecting each of A0, A1 and A2 on the eeprom to either it’s ground or Vcc pin (the Keelog logger has them floating, which is probably a bad idea.) Then the microcontroller can select which chip to use by sending the corresponding ID.
Both of these require the microcontroller code to be altered, good thing they supplied source code :)
Another source for 24c256’s is old printers, quite a few HP ones use them.
-A
For those with more money than time and/or electronics skills:
http://www.thinkgeek.com/gadgets/security/5a05/
They also have a USB version:
http://www.thinkgeek.com/gadgets/security/7af2/
Nevermind me. Looks like the same thing. Saw the rest of the site where they sell a 256Kb version for half what ThinkGeek wants for the 128…
anyone who’s got the programmer wanna sell me a programmed AT89C2051?
You can get SOIC-8 I2C eeproms/flash up to around 4Mb (512kB) for $3 or so.
If you have access to the PC like this project requires you, than there are more easy an convenient software solutions to do it.
Mabye the Dupe patrol should get their own badges and T-shirts and stuff!
Anyway thats pretty cool, I might try this later on
Mike,
Still need that chip programmed?
Mike Coles
‘bluelip’
As I know http://www.keelog.com will release outstading USB version of their logger soon…
How do they do it guys. Lets do it too we can make big bucks. HEEEEHEEE. Just kidding.
Just thought if any has a idea how they do it. Looks complicated
if i had to buy a hardware keylogger,
which would you recommend?
is the one in keelog good enough?
i like the fact it’s cheaper than http://www.thinkgeek.com/gadgets/security/5a05/
can’t you use a radio transmitter with it instead (or with) memory. something like this: http://sci-toys.com/scitoys/scitoys/computers/radio/computer_controlled_transmitter.html
this could be done with pics (with different source code), right?
holas
The connector pinout shown in their schematic is wrong. I have all theparts and the chip is programmed and now I am getting ready to build one…was double checking pinouts on web to verify everything so I don’t screw anything up…
I’ll double check by this weekend once I build and test but all indications are that Keelog’s schematic is wrong.
I’ll let everyone know.
Jdog
The connector pinout shown in their schematic is wrong. I have all theparts and the chip is programmed and now I am getting ready to build one…was double checking pinouts on web to verify everything so I don’t screw anything up…
I’ll double check by this weekend once I build and test but all indications are that Keelog’s schematic is wrong.
I’ll let everyone know.
Jdog
Sorry for the double post…
I figured it out. Keelog site reversed the pin numbers for male and female connectors in their DIY schematic.
As labeled and shown in their schematic…if you just swap only the numbering (computer connector numbering to keyboard connector numbering and vice versa) then it correctly corresponds to PS/2 pinouts as:
1 = data
2 = N/C
3 = Gnd
4 = +5 (Vcc)
5 = CLK
6 = N/C
Hope this helps!
Jdog
here is the new DIY project form KeeLog, now it’s wireless:
http://www.keelog.com/wireless_keylogger.html
Does anyone use PS/2 anymore?
dep zaj khong thang khon
Hardware keyloggers give very few information, you might consider a softare keylogger as well. I found following comparison (Use google translate) http://www.spy3k.be/spyblog/172/a-software-keylogger-a-hardware-keylogger/