Back to the main page

Mailing List Logs for ShadowRN

From: The Wyrm Ouroboros <oroboros@******.COM>
Subject: Re: Idea to bounce off people
Date: Fri, 15 Sep 1995 14:27:15 -0700
> In the peice I'm currently working on, I've included a peice of tech
> called a fiber-optic tap. This isn't a standard tap as one you attach
> across a line and read from it (everybody swears that's impossible, but
> read "Shadowplay" by Nigel Findly) but a device where you must cut the
fiber
> optic, and stick each end into it. The device then filters out the channels
> you want to listen to, and sends the data via some means (wire, radio, etc..)
> to a computer (...cyberdeck, trid, etc..).

First off -- 'piece'. Second, okay, I can see your 'modified' version Very
doable.

> I'd like some discussion on it. For example, would the standard data
> protocal used in the SR universe be able to detect the line being cut?
> Or would it dismiss it as a "problem" and tempoarly re-route it (much the
> same way the internet does). Would the security routines detect the drop
> in resonance caused by the tap in the lines, much the same way a bug detector
> detects the increased resistance of a bug on a copper line.

Detect the line being cut? Depends. Is the fib-op line the only one leading
out from that location? Then obviously, yes. If it's one of a few, then it'll
still be detected -- but all you'll get is a 'Optic line #4 temporarily offline,
successful reroute.' If the person's paying attention, they might be tipped
off, esp. if they're suspicious. Yes, the security routines would detect the
tap; that's what a rating for the routines (and for the tap) is for.

> Would anything detect the tap if it were to be placed on a line that was
> shut down? (Like between a switched off trid and the wall.)

Depends. If the tap is in place before the routines have taken a baseline,
then the tap would be _included_ in the baseline -- and thus effectively
invisible. But if the baseline has already been taken, well, then.....


--
Ouroboros
The (Dead) Wyrm of the .Net

Disclaimer

These messages were posted a long time ago on a mailing list far, far away. The copyright to their contents probably lies with the original authors of the individual messages, but since they were published in an electronic forum that anyone could subscribe to, and the logs were available to subscribers and most likely non-subscribers as well, it's felt that re-publishing them here is a kind of public service.