| From: | GMPax@***.com GMPax@***.com |
|---|---|
| Subject: | People from another world |
| Date: | Tue, 16 Mar 1999 17:14:59 EST |
int.com writes:
> Not so. Just because you can track my runaway, rogue, chip-snatching
> satellite doesn't mean you can necessarily *do* anything about it. "Yes,
> sir, we're pretty sure the chip landed in Aztlan."
>
That assumes the chip-return system is unmanned. I was picturing quarterly or
monthly shuttles to a station in nearer orbit; exchange of personell, the data
chips, and so on. And yes, if I know your sattelite tried to intercept it ...
a missile, hypervelocity (Gauss delivered) kinetic-kill round, or even
powerful laser, from the Moon, SLAGS the sattelite, and YOU, Mr-would-be-thief
SIR, are out one multibillion nuyen sattelite. <g> hehehe.
> > Sorry, no. 4-8 minute LAG [...]
>
> Um, that 8 minute lag is to the sun. The moon is significantly
> less (seconds), though I agree it would impose modifiers in excess of
> those normally associated with decking via satellite.
No. It's 8.5 to 9 minutes EACH WAY to the sun. Communicating at that
distance would impose a 17 to 19 minute (!!) lag on the decker. Remember, we
are talking ROUND TRIP here. :-)
Even if it's all of +2 minutes each way. You'd have to be INSANE to jack in
from anywhere but on-site. Put a heavy, ugly, nasty Red-12 (or even UV-
hideous) bottleneck on it. Vanishing SAN's off the corporate PLTG.
Hell. DON'T ANSWER SATTELITES; only use a tightbeam link to ONE sattelite,
say a polar-geostationary one with a direct tight-beam link to a ground
station.
Run the Ground station as Red-12. Run that one sattelite as Red-12. Run the
Bottleneck Red-12 host on the moon. THREE Red-12 bottlenecks to get through,
with the last one perhaps running a Virtual Machine as a double-blind trap.
Then put Black IC, always active, on the Virtual Machine. No have proper
passcode, Black IC squishes you. <g>
> But even still, you're really only in trouble if you get into a situation
where your
> initiative is needed. If you're just running programs (i.e. you haven't
> been discovered yet), then there's no reason it would be any harder to run
> say a "Browse" program. VR2.0 already reflects this by decreasing your
> initiative for satcom rather than increasing your target numbers.
> So if you don't get busted by active IC, you're pretty much in the
> clear.
Satcom decking involves lags in (at MOST) seconds. Round trip for a radio or
laser signal to the moon would be measured in MINUTES, and that's FROM a
sattelite.
Your hot-asist reality-filtered Fairlight just turned into a TURTLE. A _slow_
one.
That kind of lag is _itself_ an added matrix security feature. :-)
Sean
GM Pax
