-=> Quoting Bob Lawrence to John Tserkezis <=-

Hello Bob,

 BL> At the time we used to talk to a bikie-trucker-psycho-crazy who
 BL> drove down Parramatta Road every day and was not long out of Long Bay
 BL> so we gave him Lame Duck's address and he put him in hospital. We
 BL> never heard Lame Duck again!

 I've heard of similar things happening too.  I even heard about one guy who
never got caught, everyone called him the organ player.  He used a dick smith
"learn electronics" kit organ, and used to play that over the air causing
general riot.
 They never did catch him, last I heard that guy and his cousin (who told me
about it) were working on a mod to a phillips uhf radio, to muck around with
the selcall feature.  He said they managed to read in the selcall codes, and
then re-transmit them to cause havoc.  It was only a prototype arrangement at
that time, but probably pissed everyone off anyway...

 BL> it would be a simple matter to use false PATH: lines.
 
 JT> Wouldn't work (or be effective rather). In the case of the
 JT> gating from PEnet, the first path line would be added by the
 JT> first non-point fido node handling the mail, me.

 BL> Not if you doctor your software, it won't. Your only problem is that
 BL> your boss could trace the mail though his logs and your password.
 BL> You'd have to work out a way to get past the 8-character password (not
 BL> too hard), or better still, obviate the Fido "hello"
entirely. You're
 BL> not breaking into Fort Knox here...
 
 It STILL would be tracable to your node.  Firstly it would take you to your
host node, and then the host sysop would look at the packets as they come into
his system.  They look at who actually delivered "those" packets,
and bingo,
they've got you.
 The only other way around it would be to fake your system so you look like
another node.  The only "weird" thing would be is that node would
be calling
two times a day rather than just one.  That and, you need the session level
password, and the packed password too.
 If that were the case, you wouldn't need to bodgey up your software, you can
use it as-is.
 This isn't like the internet where you fake a message and send it into the
wild blue yonder for all to marval at your geniuse hacking skills.

 JT> If I were to
 JT> fake it, it would still go via my uplink, either way, the
 JT> origin line reads 3:712/610.20. Policy 4 also states if you are
 JT> gating mail, you must clearly identify the gating system, so
 JT> you can't remove the origin line and expect to get away with it
 JT> for any extended amount of time.

 BL> ROFL! I'm talking about rooting the system here, not obeying it!
 BL> I'm talking about feeding AVT into Fido so it seems to be coming from
 BL> somewhere else. 

 It would still only stop wankers inc.  Once they actually question the node
that it *seems* to be coming from, they would of course claim ignorance, and
then they would look further into it.  It depends on how cluey the sysop is
though, some don't understand the inner workings of the system and were content
with following the vague instructions to make it work.
 OTOH, some do know what is going on, and will sus out quite quickly who is at
the bottom of it.
 
 JT> Stuff them I say.

 BL> The way to stuff them properly is the go around then as if they
 BL> aren't there. That's what I thought Paul intended... gate AVT onto the
 BL> Internet as a newsgroup and then pick it up from the Internet all over
 BL> the planet, gating it back into Fido as required.

 Ahh, it presently exists only in PEnet, but you can gate it.  Some actually
gate some fido echos into the net anyway.

John Tserkezis, Sydney, Oz. Fidonet: 3:712/610  Internet: jt{at}suburbia.com.au

... Your proctocologist called...  Your head is ready!
---