>>
|
701a19.jpg
Spice Candy
701a19
>>268004
You need to mod that thing so it'll keep the autonomics going while you're out. It's bad enough that it knocked you out for two thirds of a day, but being impaired afterward? That's just unacceptable!
You can work on those mods while you're traveling. It's not like you can't code and walk at the same time, right?
Still, there has to be a way to neuter the basilisk. Our best bets are probably going dumb, pigeonholing it, or abstracting it.
On the dumb end the basilisk can't damage a storage medium that's too simple for the basilisk to damage; it would not, for example, be possible for the basilisk to damage notches in a block of wood. By the same token it can't damage a read/write mechanism that lacks some minimum amount of internal storage.
Alternatively, we could exploit the Shannon limit by compressing (and possibly encrypting) the data until it no longer damages systems that store it. This results in a catch-22 situation for the worm; if it remains functional when archived then the archive will be corrupted and we can use that information to precisely identify what portions are the basilisk, at which point we can hose down those areas with random bit corruption and damage if beyond functioning. If the archive isn't infectious, then the problem of storing it is solved.
Working in the opposite direction, we can have a bit of code go through and verbosely describe the data well enough to reconstruct it without actually recording any of the data directly. If that remains infected then we can compare the original with the copy to find matching or similar strings.
If it's redundant or fractal then pattern matching will easily catch it. Beyond that there's little left besides superpolymorphism, and since that requires that the code be 'live' to adapt we can use dumb tools to exploit its inactive state to get a clean copy.
OR you could start work on a Weasel to hunt and kill the Basilisk and consume its remains.
|