Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

KeySweeper – Arduino-based passive wireless keyboard sniffer

samy.pl

Post reply on HN
Print view View original

1–10 of 61 posts

Re: KeySweeper – Arduino-based passive wireless keyboard sniffer

#5

Post by jamiek88 »

codelitt wrote: post #3
pjonesdotca wrote: post #2

Looking at the list of projects also done (by going to root of url) is quite impressive. http://samy.pl/

Very much so. Seeing my user name populated in the bottom task bar was a little unnerving.

Being marked 'you have nothing to worry about' was somehow equally as unnerving.

I love that 'desktop as website' theme, gonna steal it.

Re: KeySweeper – Arduino-based passive wireless keyboard sniffer

#6

Post by edwintorok »

Does this apply to all bluetooth keyboards?

Sounds like some public-key crypto could make it safe: embed some unique keys at manufacturing time and use some small crypto library (like tweetnacl) to communicate and have mutual authentication. For the paranoid there could be a way to update the keys so that not even the vendor can sniff the keystrokes. Isn't there a RFC for something similar?

Re: KeySweeper – Arduino-based passive wireless keyboard sniffer

#8

Post by egeozcan »

edwintorok wrote: post #6

Does this apply to all bluetooth keyboards? Sounds like some public-key crypto could make it safe: embed some unique keys at manufacturing time and use some small crypto library (like tweetnacl) to communicate and have mutual authentication. For the paranoid there could be a way to update the keys so that not even the vendor can sniff the keystrokes. Isn't there a RFC for something similar?

I'm curious if something like this could affect the battery life significantly.

Re: KeySweeper – Arduino-based passive wireless keyboard sniffer

#9

Post by mathetic »

edwintorok wrote: post #6

Does this apply to all bluetooth keyboards? Sounds like some public-key crypto could make it safe: embed some unique keys at manufacturing time and use some small crypto library (like tweetnacl) to communicate and have mutual authentication. For the paranoid there could be a way to update the keys so that not even the vendor can sniff the keystrokes. Isn't there a RFC for something similar?

That's the entire point. The crypto is not very good. Also it doesn't apply to all bluetooth keyboards because Microsoft uses a proprietary protocol to communicate apparently (at least this series of keyboards).
Post reply on HN