From: | Marc Renouf renouf@********.com |
---|---|
Subject: | Gearheads: The Nature of the Matrix |
Date: | Wed, 1 Dec 1999 17:06:40 -0500 (EST) |
> -------------WARNING, IN CHARACTER DISCUSSION FOLLOWS-----------
>
> *****But waittasec! Your deck does all the translation for the signals!! And
> it's all simsense!*****
> "Wrong chummer, if the Matrix was set up in a constant realtime simsense
> feed nothing would work beyond a slow crawl."
>
> "Instead your deck simply has a "library" of pre-recorded simsense
> "sensations" stored in it that are played in various orders and strengths
to
> simulate reality at least partially."
>>>>>[Right, and better decks will be able to store much larger
"libraries" of emotive blocks, and will be faster at combining them to
achieve subtle effects.]<<<<<
> *****Hey, I thought that's how that "Black ICE" stuff worked?*****
>
> "You up past your bedtime kid? Black ICE is something the trid shows use
> to scare away decker wanna-bes. You can't force an open simsense link and
> only the truly sickest user would have a set of samples that could actually
> harm him. If anything the safety toggles would kick in. So your mythical
> Black ICE could not hit your "Open File" sample and jack it to Level 10000
> strength. Does not work that way."
>>>>>[Are you tryin' to get this kid killed? Look kid, it works like
this: Your deck has a certain set of signals that it can give you. If it
encounters an emotive that it doesn't have a signal for, it gives you the
raw stuff coming in from the system. That raw signal is modulated by your
deck, sure. And if you're smart, you'll be running and ICCM filter to
keep the simsense feed from peaking out to dangerous levels. But
filtering slows you down. Limiting your ASIST levels means that you have
less mental feedback from the system, which in turn means you need to
concentrate more intently on soemthing to get it to happen.
It's like trying to type with gloves on. You can't feel where
your fingers are or how hard you're hitting the heys, so your typing is
slower and less accurate. ASIST levels are the same way. If you want
your concentration to get the biggest bang for its buck, you need to be
able to really feel what's going on. Unfortunately, that means opening
yourself up to getting hammered by something that corrupts your deck's
sense-routines (which is exactly how Black IC operates).]<<<<<
> "Yeah, yeah, I've seen the stories about drek like "Black-Hammer".
Listen
> kid it's all bogus. You have a lot more things to worry about then getting
> your brain fried by a program. Like them tracing your sorry hoop and sending
> the not-so-friendly Lone Star chappies over to say hello."
>>>>>[Speaking as someone who's done network wetwork, I can't disagree
more. There are a lot of guys who will push their ASIST drivers to the
max just to shave that extra nanosecond off their concentration-response
time. These guys are vulnerable, and if you have some clever code that
can exploit their open emotive tracks, you can put the hurt on 'em.
What you won't do is "fry their brain." There won't be smoke
coming from their jack, or any drek like that. The easiest way to put the
jam on someone is to mess with their medullar functions. Those same
simsense feeds that make you feel all jazzed and excited when you're
bangin' a virtual Maria Mercurial can be used to much more dangerous ends.
Sending your bloodpressure through the roof, stopping your breathing.
These are the ways Black IC will kill you.]<<<<<
> *****And sculpted systems are essentially using their own custom simsense
> libraries?*****
>
> "Well, among other things. Usually nonstandard simsense is just one of the
> differences. In some of the REALLY bizarre sculpted systems they use
> realtime generated simsense feeds for system operation. Why they waste all
> that bandwidth is beyond me! But it does pretty much limit system use to
> local users due to system load and reaction penalties/lag from non-local
> clients."
>>>>>[Actually, if they're smart about it, they can "sculpt"
their system
by combining UMS Default emotives carefully. Visually, there will always
be a drain, because how things "look" will depend on point-of-view,
lighting, shading, texture, etc. A good system can do all the necessary
calcs and just send you a "picture" though. With the recent advances in
processor speed, bandwidth, and compression of the data it takes to convey
a virtual environment, a lot more people have the juice to do it. It used
to be that only the big boys could afford it, but now I swear every
mom-and-pop joint on the net has some level of sculpting. It's just too
easy to do nowadays.]<<<<<
> "Not related to simsense per se is that some of the higher-end sculpted
> systems (I'm not talking of Mom and Pops so-called "sculpted systems" limit
> access through their utilization of nonstandard protocols. In many they have
> a standard UMS compliant section with limited capability and another layer
> on top of that with their own sculpted code. Without being able to interpret
> their data you can't do JACK chummer. You have to do things THEIR way. The
> UMS standards for pulling files, opening datastores, etc won't work in most
> sculpted systems. If you're unfamiliar with the system you're out of luck.
> And a lot of the operations you won't be able to emulate by watching other
> visibile users either, not that easy. Don't expect any but the best Sensor
> program suites to help either - those rely on UMS complient system calls and
> exploits to work."
>>>>>[Ditto what the man said.]<<<<<
> "An even nastier variation of sculpted systems are what I call
"two-tier"
> or "cloudy" systems.
>>>>>[I'm gonna cut through all the bulldrek and doublespeak. What the
man's talking about are virtual machines. Two worlds at once, with you
none the wiser that what you're seeing isn't what it really is. You
should always check a host to see if it's running as a virtual machine.
There are a few ways to do that, but as protocols change, so do the
methods of determining your environment state.]<<<<<
> *****You said some sites require simsense links to operate, could they use
> 'Black ICE' effects on you?*****
>
> "A good question actually. Unless you are a truly clueless chummer you
> don't make your ASIST any "hotter" then you need to. Contrary to common
> belief, experiencing the Matrix at better then real intensity does NOT make
> you a faster or better decker. Only the truly clueless believe that. Are you
> a better musician just because you blast your instruments louder?"
>>>>>[The man's talkin' out his ass again. He just doesn't want any
competition. He's running hotter than hell right now, I'd put money on
it. Remember what I said earlier about concentration-response time, and
how hot ASIST gives you finer mental control? That's exactly what we're
talking about here. It's not playing your instrument louder, it's
listening to the music in stereo. There's just more information there for
your brain to use, and control goes both ways.]<<<<<
> "REALLY REALLY worried about black ICE? <display_big sigh> Well then
run
> a filter program like those cheap import sensedecks use. Or buffer, then
> downsample the simsense feed to smooth it out and block out nonstandard
> information.
>>>>>[Yeah. Get yourself an ICCM. This is *exactly* what it's designed
to do. With one of these babies running, you'll never have to worry about
terminal biofeedback. The ICCM unit will filter out anything it deems
"dangerous." It'll slow you down a titch, though. You don't get safety
for nothin'.]<<<<<
> *****In Netrunner I can prevent a trace by moving from RTG to RTG before
> hacking a site.*****
>
> "HAHAH. Only on the trideo...."
>>>>>[Are you *trying* to get this kid busted?
Jeez...]<<<<<
> "Still not getting it? Ok. To use a 20th century allegory doing the
> Mexican Jumping RTG trick would be like visiting a succession of webpages
> all over the world and then expecting to outwit goverment attempts to ID you
> when you then attacked their servers.
>>>>>[Okay, now I'm starting to suspect this guy works for the 'Star.
This is a load of bulldrek. When you hop LTG's it's not like surfing a
series of pages from home. When you access those LTG's you're logging on
to them. That is, you're making a call that gets routed. When you do a
redirect, you're actually hacking the phone company's list. You're
altering your slot in their lookup table without altering where the data
is going. It's subtle. It's integral to the telecom grid. It's like
telnetting from one host to another but changing all the tty records on
each machine to give the wrong connection. When a trace is initiated,
it's going to go to that lookup table to try to figure out where the call
is getting routed from. If that table lies, it's harder for the trace to
figure it out (although they'll use cross-checking and adaptive searching
to try to find you). It's a bitch to sort out, and will make you harder
to trace to your actual real-world location. Make it a standard
practice.]<<<<<
> "This is why if I flit from RTG A to B then C then D, and then back to A
> and drop to an LTG to attack a system my path still only leads from that
> LTGs RTG right to my home RTG. It does NOT still travel through B,C, or D."
>>>>>[Not so. When you make that last call, the LTG you've dropped into
thinks it's getting a call from Bangladesh. So it queries the Bangladesh
RTG's lookup table for your signal. But as I said before, that lookup
table lies if you've done the Redirect correctly. So the Bangladesh RTG
will have to figure out just what went wrong and which signal you're
actually using. Lo and behold, it's from the Berlin RTG. So it queries
the Berlin RTG's lookup table (which is a lie), and so on.
This wouldn't work if you were just making a call, but you're
actually spoofing the telecom system to think you're making a call from
someplace you're not. You faking out a router and sliding your signal
in from an unauthorized channel. Look at the source code of your Redirect
utility and you'll see what I mean. Pay special attention to the telecom
system calls and router edits.]<<<<<
> "Well playtimes over. Same bat time same bat channel!"
>
> ******Huh?*****
>>>>>[Yeah, it is. Get smart kid, or this cop-in-decker's clothing is
gonna apprehend your naive little behind.]<<<<<
<chuckle>
Marc Renouf (ShadowRN GridSec - "Bad Cop" Division)
Other ShadowRN-related addresses and links:
Mark Imbriaco <mark@*********.html.com> List Owner
Adam Jury <adamj@*********.html.com> Assistant List Administrator
DVixen <dvixen@****.com> Keeper of the FAQs
Gurth <gurth@******.nl> GridSec Enforcer Division
David Buehrer <graht@******.net> GridSec "Nice Guy" Division
ShadowRN FAQ <http://shadowrun.html.com/hlair/faqindex.php3>