On Tue, Dec 11, 2007 at 02:01:03PM -0500, j...@tla.org wrote:
> How many bits (not just data, also preamble/postamble, sync bits, etc.)
> is the keyboard sending for each keystroke anyway?
FWIW, it is likely sending keyboard scan codes:
http://en.wikipedia.org/wiki/Scancode
It doesn't send the
"James A. Donald" <[EMAIL PROTECTED]> writes:
>At every block boundary, keyboard transmits a special signal in the clear
>that signifies block boundary. Any time that no key has been pressed for a
>while, then when a key is finally pressed, keyboard transmits a bunch of no-
>ops sufficient to ens
Steven M. Bellovin wrote:
> Believe it or not, I thought of CFB...
>
> Sending keep-alives will do nasties to battery
> lifetime, I suspect; most of the time, you're not
> typing. As for CFB -- with a 64-bit block cipher (you
> want them to use DES? they're not going to think of
> anything differ
On 12/10/07, Steven M. Bellovin <[EMAIL PROTECTED]> wrote:
> Believe it or not, I thought of CFB...
What about PCFB to get around the block issue? I remember freenet
using it that way...
--
Taral <[EMAIL PROTECTED]>
"Please let me know if there's any further trouble I can give you."
-- Unkno
How many bits (not just data, also preamble/postamble, sync bits, etc.)
is the keyboard sending for each keystroke anyway?
Cheers,
/ji
-
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to [EMAIL
On Tue, 11 Dec 2007, Steven M. Bellovin wrote:
| On Tue, 11 Dec 2007 13:49:19 +1000
| "James A. Donald" <[EMAIL PROTECTED]> wrote:
| > Use CFB mode. That takes care of all the above problems...
| Believe it or not, I thought of CFB...
|
| Sending keep-alives will do nasties to battery lifetime, I
On Tue, 11 Dec 2007 13:49:19 +1000
"James A. Donald" <[EMAIL PROTECTED]> wrote:
> Steven M. Bellovin wrote:
> > It's moderately complex if you're trying to conserve bandwidth
> > (which translates to power) and preserve a datagram model. The
> > latter constraint generally rules out stream cipher
Steven M. Bellovin wrote:
It's moderately complex if you're trying to conserve bandwidth (which
translates to power) and preserve a datagram model. The latter
constraint generally rules out stream ciphers; the former rules out
things like encrypting the keystroke plus seven random bytes with a
6
| > Exactly what makes this problem so difficult eludes me, although one
| > suspects that the savage profit margins on consumables like
| > keyboards and mice might have something to do with it.
| >
| It's moderately complex if you're trying to conserve bandwidth (which
| translates to power) and
On Mon, 10 Dec 2007 08:20:44 +0800
"Ian Farquhar (ifarquha)" <[EMAIL PROTECTED]> wrote:
> Exactly what makes this problem so difficult eludes me, although one
> suspects that the savage profit margins on consumables like keyboards
> and mice might have something to do with it.
>
It's moderately c
pting Microsoft wireless keyboard communications
http://www.dreamlab.net/download/articles/Press%20Release%20Dreamlab%20T
echnologies%20Wireless%20Keyboard.pdf
Computerworld coverage at
http://www.computerworld.com/action/article.do?command=viewArticleBasic&;
articleId=9051480
The main protectio
http://www.dreamlab.net/download/articles/Press%20Release%20Dreamlab%20Technologies%20Wireless%20Keyboard.pdf
Computerworld coverage at
http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9051480
The main protection against interception is the proprietary protocol,
12 matches
Mail list logo
