home *** CD-ROM | disk | FTP | other *** search
-
- ****NETRIP SOFTWARE PRESENTS****
-
-
- ======= BOGUS PACKET EDITOR DOCUMENTATION =======
-
- PURPOSE OF THIS PROGRAM:
-
- Bogus packet editor is a mail processing utility designed for
- your cross linking pleasure. It will take any mail packet (that meets
- fidonet standards) and change: 1) The tear line, 2) The seen-bys, 3)
- The origin lines, 4) The path statement, 5) The originating and des-
- tination node, to anything you desire.
-
- ============================================================================
-
- Files in this archieve:
- PR.EXE Packet viewer.
- BPP.EXE Bogus Packet Packer.
- BPP.CFG Bogus Packet Packer config file.
- BOGUS.DOC This file dummy.
- A59B27F0.PKT Sample PKT to play with.
- ============================================================================
-
-
- HOW IT WORKS:
-
-
- First off a bit about how mail processors work. When a mail packet
- comes into a BBS's inbound directory the mail processor unpacks it and tosses
- it in the proper area and sends it to any downlinks (other BBS's) in its
- Area.bbs. The mail processor really does not care who it gets it's mail from
- rather it looks at the Onode (originating node) in the packet header (or if
- the processor is running in the unsecure mode it does not care who it gets
- it's mail from). The implications of this are very interesting. It means it
- is very easy to get around basic fidonet security to send anything you want
- in to any echo you want. Example: I know that 1:13:13 gets its mail from
- 1:106/116. I also know that 1:13/13 and 1:106/116 are session level pass-
- worded. Therefore I use Bogus Packet Editor to make the Onode 1:106/116
- and the Dnode 1:13/13, I pick a echo that I know they exchange to hack into.
- I then configure my mailer for a third system say 1:315/1 (a system I think
- that they would have no reason to be passworded with) and send the mail to
- 1:13/13 as this node. 1:13/13 gets the packet in it's inbound directory and
- it's mail processor "looks: at the Onode of 1:106/116 and goes ahead and
- tosses it (unless the system has packet level passwords or secure inbounds,
- more on that latter). You bundle of bogus mail gets tossed into the echo(s)
- in question.
-
- When Bogus Packet Editor is used this way, session level passwords
- do not even slow it down. However protected inbounds and packet level pass-
- words are a problem. However, Front Door does not have protected inbounds
- (Binkley does) and many mailers do not have the ablity to do packet level
- passwords (most noteably I-Mail). So find a system that runs both Quick or
- SuperBBS and runs FD and you know this person can not stop you. In any case
- very few people use packet level passwords, they mistakeingly believe that a
- system is protected using session level password protection. This belief
- will change. Always remember that a net is only as secure as it's weakest
- link. In other words, used properly this program can not be stopped. Myself
- and my beta testors have proved that time and time again.
-
- BTW if you use this program with Binkley you will need to
- call your finished product a .OUT file instead of a .PKT file.
-
- To use the Packet Reader (PR.EXE) you type pr and the name of
- the packet. Example: PR.exe a59b2f0.pkt.
-
-
- HAPPY CROSS LINKING TO YA!!!!
-
-
-
-
-