Datasets:
Devilishcode
/
hacking

Dataset card Data Studio Files
xet
Community
text
stringlengths
0
1.99k
social engineering leaves something to be desired).
What is OSL:
Actually it has been termed as Operating Systems Location, Off Site
Location and a lot of other names. Which? I'm not sure. What I can tell
you is that it's an operating system running on an IBM (?) that does
remote maintenance operations on a ROLM PBX (Referred to as CBX I
believe). As I said, this file is not too complete, and I was unable to
get very much information about the system, or the PBX system itself. I
believe Celtic Phrost wrote a file on ROLM PBX systems, and you might want
to read that or other ROLM files for more information.
Getting In:
If you have trouble logging in, try changing your parity. Also, this
system will only except uppercase. The first thing you should see when you
get a carrier is the following:
MARAUDER10292 01/09/85(^G) 1 03/10/87 00:29:47
RELEASE 8003
OSL, PLEASE.
?
MARAUDER10292 is the system identification. Most of the time, this will
be the name of the company running the OSL system, but occasionally you
will find a system, you will not be able to identify. CN/A it. It might be
your only chance of gaining access to that particular system.
01/09/85. This is a mystery to me. It could be the time that the system
first went up (but sounds unlikely), the date of the current version of
the OSL operating system...etc.
The ^G is a Control-G, and rings a bell at your terminal. I do not know
why, but it does...
The rest of the text on that line is the current time and date.
RELEASE 8003 could be, again, the revision number of the software
package. I don't know.
OSL PLEASE means that you can now attempt to login.
The ? is your prompt. Remember the uppercase only. Naturally we are
going to type "OSL" to login. Once this is done, we will receive this
prompt:
KEY:
This is the password prompt, and so far as I can tell, can be anything
up to, say, 20 characters long. Obviously we are going to try MARAUDERS or
MARAUDER as a password. Here's the tricky part. Some systems do not tell
you whether the password was right or not. Sometimes, if it's right, you
will get a ? prompt again. If not, you will get an ERROR msg. It depends
on the system. Each system is set up a different way. Also, some systems
require all alphabetics, while others require alphanumerics and sometimes
they will require both. Again, you may or may not get an ERROR message.
You can ABORT anything at any time by sending a BREAK. One good thing
about the system is that you have, so far as I can tell, unlimited
attempts at guessing the "KEY". Also, Druidic Death says that "," is a
default, or is commonly used (I don't remember which). Unfortunately, I
have never been able to get this to work myself.
Your IN!:
Okay, first thing we need to do is type HELP. If you have access, which
again, differs from system to system, you will get a menu that looks like
so. (Maybe not, but I am through telling you how strange this system is.)
PLEASE ENTER ONE OF THE FOLLOWING COMMANDS
LREP - DISPLAY REPORT MENU
LST - LIST REPORT COMMANDS CURRENTLY STORED
ACD - ADD AN ACD COMMAND
DEL - DELETE AN ACD COMMAND
MOD - MODIFY AN ACD COMMAND
SUS - SUSPEND AN ACD COMMAND
ACT - ACTIVATE AN ACD COMMAND
LREP: This lists a menu of reports you can view.
LST : This lists all the commands that have been stored in the buffer.
ACD : This activates a command.
DEL : This deletes a command in the buffer.
MOD : This modifies a command in the buffer.
SUS : This suspends a command in the buffer.