From: Marc Horowitz <marc@GZA.COM>
To: peb@PROCASE.COM
Message Hash: c3bfd9229c50207723a2e76a1acc531cecc55996789e55921982849e7587dfa4
Message ID: <9305122149.AA11140@dun-dun-noodles.aktis.com>
Reply To: <9305122047.AA09694@banff>
UTC Datetime: 1993-05-12 21:49:10 UTC
Raw Date: Wed, 12 May 93 14:49:10 PDT
From: Marc Horowitz <marc@GZA.COM>
Date: Wed, 12 May 93 14:49:10 PDT
To: peb@PROCASE.COM
Subject: Re: The Halting Problem
In-Reply-To: <9305122047.AA09694@banff>
Message-ID: <9305122149.AA11140@dun-dun-noodles.aktis.com>
MIME-Version: 1.0
Content-Type: text/plain
>> Consider that the cyphertext is a program for an abstract machine
>> called the cyphercracker which returns TRUE if a message is encoded
>> otherwise FALSE. Such a system for determining message-ness could
>> take an arbitrary amount of cpu time and no amount of static
>> analysis could determine the return value quicker.
Nope. Such a system will take no more than O(2^n) time, where n is
the number of bits in the key. You can never do worse than
brute-force. Now, you still might not be able to determine if a
message is encoded, since maybe I was just encoding true random noise
from a radioactive source. And you might have false positives, too,
esp. with one-time pads. But it will always halt. The failure modes
have nothing to do with the halting problem, they have to do with the
fact that is-encoded(message) cannot be formally defined.
Marc
Return to May 1993
Return to “peb@PROCASE.COM”