Problems: 1) Recompiled Kernel with XXX configuration. The average signal data taken during a boot sequence might reveal what is in the kerel! 2) Hacked Kernel. It would be very hard to decipher anything if the scheduler didn't follow the *regular* rules for running process'. However, most people run stock kernels and would be succeptable to this... I'm almost tempted to try this out:) 3) What if they aren't running some for of *NIX? We resort to the trivial solution;) patofiero
1) Malicious program sending signals from your machine. (The scenario you suggest)
2) Eavesdropping on signals coming from your machine. (The scenario I was thinking of)
The first insinuates that you *already* have access to the critical data! There has to be easier and more secure ways to send that data then through the generation and leaking of radio frequency signals (watermark the data in a jpg and email it to your yourself?).
The second scenario, being more likely, involves gathering leaked signals and doing some form of analysis to decipher the internal state of the machine. You could in theory create a clone of the target machine and use it to train the signal analysis software to recognize certains actions by pattern matching?
...patofiero turns his head to hear a short burst of low frequency blips... "hrm, that sounds like my nfs server dumping core."
I think the solution to all things is "Run rc5des" I'm sure this creates enough random white noise that *no* one will be able to decode the crap coming out off your bus and cpu!
patofiero
"Hokey religions and ancient weapons are no match for a good blaster at your side, kid" - Han Solo
Slashdot Mirror
Problems: 1) Recompiled Kernel with XXX configuration. The average signal data taken during a boot sequence might reveal what is in the kerel! 2) Hacked Kernel. It would be very hard to decipher anything if the scheduler didn't follow the *regular* rules for running process'. However, most people run stock kernels and would be succeptable to this... I'm almost tempted to try this out :) 3) What if they aren't running some for of *NIX? We resort to the trivial solution ;) patofiero
There are two scenarios:
1) Malicious program sending signals from your
machine. (The scenario you suggest)
2) Eavesdropping on signals coming from your machine. (The scenario I was thinking of)
The first insinuates that you *already* have access to the critical data! There has to be easier and more secure ways to send that data then through the generation and leaking of radio frequency signals (watermark the data in a jpg and email it to your yourself?).
The second scenario, being more likely, involves gathering leaked signals and doing some form of analysis to decipher the internal state of the machine. You could in theory create a clone of the target machine and use it to train the signal analysis software to recognize certains actions by pattern matching?
...patofiero turns his head to hear a short burst of low frequency blips...
"hrm, that sounds like my nfs server dumping core."
Patofiero.
I think the solution to all things is "Run rc5des" I'm sure this creates enough random white noise that *no* one will be able to decode the crap coming out off your bus and cpu!
patofiero
"Hokey religions and ancient weapons are no
match for a good blaster at your side, kid"
- Han Solo