32-000105 – Create PUBLIC Room
32-002185 – The SPAM Area (Link to ARC)
32-002326 – The America Online Guide Area (JADE)
32-002411 – Change Software Version Numbers
40-005060 – Sales and Service Forum
40-009366 – Request-O-Rama
40-011549 – TOS Area (Detailed
32-000029 – Blank Mail (NF)
32-000030 – Update Welcome screen
32-000040 – Catch Hidden (NF)
32-000056 – Continue? (NF)
32-000105 – Create PUBLIC Room
32-000158 – On Stage Screen (NF)
32-000270 – Untitled Auditorium (NF)
32-000274 – Blank IM
32-000292 – Network News (NF)
32-000295 – Covers buttons
32-000296 – Uncovers Buttons
32-000300 – End of Account (NF)
32-000350 – Works for Macs
32-000351 – Microsoft Stuff
32-000754 – Send Question (NF)
32-001612 – Mercury Sign-On Screen
The AOL Protocol
When you hear the phrase “The AOL Protocol”, I bet most of you immediately think of FDO, right?
Although FDO is a part of the AOL protocol, it in no way encompasses the big picture. When I use
the term “The AOL protocol”, I refer to how the AOL client and server interact with each other,
how data is prepared, how it is sent, and how it can be manipulated.
There currently exists no formal documentation of the AOL protocol, or at least one that is
publicly available. For this reason, I have taken it upon myself to strip the bits of
information from my feeble mind and write a document with at least basic information about
the AOL protocol. The information included in this document is what I have learned, from
exploration, help from others, and just stumbling upon it. I in no way guarantee the accuracy
of the information contained herein. That said, here is what I know.
Subj: Fwd: º^º^( InSide WaReZ Issue #2 (Part 1)^º^º
Date: 97-07-27 15:21:53 EDT
From: SPYER2000
To: BeAwareX1
Forwarded Message:
Subj: º^º^( InSide WaReZ Issue #2 (Part 1)^º^º
Date: 97-07-27 14:35:28 EDT
From: BuBBLe HoP
«–¥(TRauMaTiZeD MassMailer²·º ßy: ßaNiCKuLa)¥–»
«–¥(This one is Dedicated to TaSHa, BaNiCKuLa’s True Love!)¥–»
«–¥(This Mail took 33.61719 Seconds to send)¥–»
«–¥(There are 69 out of 73 people on the MM)¥–»
«–¥(There have been: 0 Un-Retrievable Mails on This MM)¥–»
«–¥(This is Mail Number: 6 of 19 Mails)¥–»
Bath Township man wanted ex-girlfriend to know that money has no value to him
By Gina Mace
Special to the Beacon Journal
BATH TWP. – In an effort to prove to his ex-girlfriend that money means nothing, a 20-year-old Granger Road man smashed an SUV and sent another luxury vehicle into a creek, township police said.
A 2-month-old Volkswagen Touareg blaring rock music from the sound system sat in the front yard of Ryan Johnson’s home Monday — severely damaged from smashing through the security gate, uprooting a tree, then being assaulted by golf clubs and boulders. A Mercedes SL500 was parked in Yellow Creek, under the driveway bridge leading to Johnson’s mansion.
The two vehicles were worth more than $100,000, police said.
Johnson told police he did it for his ex-girlfriend. Last week, she asked police to accompany her to the home so she could remove some belongings.
Police were called to Johnson’s home around 3 p.m. Monday by neighbors who thought they heard an explosion.
One neighbor, who asked not to be identified, said he went outside after hearing the noise.
People were running around, making sure everyone was OK,'' the man said.A kid was out there with huge boulders, breaking out windows. He was throwing stones at it. Later he came out with a set of golf clubs and was teeing off on it.”
The “kid,” identified by police as Johnson, was still smashing the SUV when police arrived.
a1m fear
accuracy
afextz
africanninjas
aim tempy
aimbionet
aimnymike
airtuh ily
almost tipsy
ambidextrism
atb
azz
WinShell v5.0 £ A finished telnet server for windows
Author : janker
Homepage: http://www.janker.org
About
=====
WinShell was a telnet server for windows platform. Main program was just a 5k bytes stand-alone executable file, Could run stably without any third dll, Although it was so thin, it had many of functions, such as custom port, password protect, muti-user logon, NT Service mode, download file£¬user-defined message, special anti-ddos and etc. Detail to see the following:
ACK Tunneling Trojans
– Arne Vidstrom, arne.vidstrom@ntsecurity.nu
Summary
Trojans normally use ordinary TCP or UDP communication between their client and server parts. Any firewall between the attacker and the victim that blocks incoming traffic will usually stop all trojans from working. ICMP tunneling has existed for quite some time now, but if you block ICMP in the firewall you’ll be safe from that. This paper describes another concept, that I call ACK Tunneling. ACK Tunneling works through firewalls that don’t apply their rule sets on TCP ACK segments (ordinary packet filters belong to this class of firewalls).
——————————————————————————
FPipe v2.1 – Port redirector.
Copyright 2000 (c) by Foundstone, Inc.
http://www.foundstone.com
——————————————————————————
FPipe is a source port forwarder/redirector. It can create a TCP or UDP stream
with a source port of your choice. This is useful for getting past firewalls
that allow traffic with source ports of say 23, to connect with internal
servers.
