**********************************************************************************************Riot*Freedom*Hacks**********************************************************************************************
Note:
 This is an article, Ezine, or whatever written by Žndless Nameless. The title of this paper is Riot Freedom Hacks, basically it is me (Žndless Nameless) expressing myself and what I believe. 

Disclaimer: 
 I am not responcible for anything anyone does after reading this paper REMEMBER THAT! 
If you are offended by anything please go away and read a Disney comic (available at DUH! www.disney.com).
If your a JOCK fuck off! I dislike jocks very much, reason being, though I am not a small person (6'2 160lbs) Jocks seem to target me for fights and such, and when I kick their asses they go and get more of their jock friends to pester me, becomes rather annoying when I have to kick 8 or 9 guys asses before they leave me alone.
I am going to be taking things from several other documents and sticking it in here so that this becomes an all around good paper that lotsa people will want to read. I will give all other authors their due credit. I dont take credit for shit I didnt do or write so if you wrote one of these things and I forgot to give you credit send me an email and I will include a formal apology in the next issue, if there is one. (my email address is pbot1@hotmail.com, all mail sent to me will be read and most likely i will respond to it.)
ok well on with the real shit.
If you are still here YAY FOR YOU! :)

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Contents: 
here is the basic structure of this paper. it may differ from whats actually here but i doubt it unless some lamer went and changed it. (lamers do NOT include people who correct my spelling, since I am writing this at 2:00am on a school night expect some errors and if you see one please CORRECT IT! .. and if you do correct something please add your handle at the end of this paper before passing it on to someone else.)

1. Anti School Chapter
2. Hacking Chapter.
3. Phreaking Chapter.
4. Miscelaneous Anarchy Chapter.
5. Websites/BBS/FTP/Newsgroup Chapter.
6. Credits Chapter.
 

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

														Anti-School Chapter
If you are in school, and most likely you are in some form or other, you probably hate it just as much as I do (well did since I am not really in real school any more, but anyways). Here are some ways to fuck up your school.

1. put a smokebomb in the store room/boiler room. (recipies below)
                         recipies for good smoke bombs.
4 parts sugar
6 parts potassium nitrate (Salt Peter)
Heat this mixture over a LOW flame until it melts stirring well. Pour it
into a future container and before it solidifies imbed a few matches into
the mixture to use as fuses. One pound of this stuff will fill up a whole
block with thick white smoke!

                               OTHER SMOKE MIXTURES

[Black]

Hexachloroethane......... 60%
Anthracene............... 20%
Magnesium (powder)....... 20%

[Brown]

Pitch.................... 29.2%
Potasium Nitrate......... 47.4%
Borax.................... 10.6%
Calcium Carbonate......... 4.9%
Sand...................... 4.0%
Sulfur.................... 3.9%

[Grey]

Hexachloroethane......... 50%
Zinc Powder.............. 25%
Zinc Oxide............... 10%
Potassium Nitrate........ 10%
Colophony Resin........... 5%

[Grey]

Hexachloroethane......... 45.5%
Zinc Oxide............... 45.5%
Calcium Silicide.......... 9.0%

[White]

Potassium Chlorate....... 20%
Ammonium Chloride........ 50%
Naphthalene.............. 20%
Charcoal................. 10%

[White]

Potassium nitrate........ 48.5%
Sulfur................... 48.5%
Realgar................... 3.0%

[White]

Potassium Nitrate........ 50%
Sugar.................... 50%

[Yellow]

Potassium Nitrate........ 25%
Sulfur................... 16%
Realgar.................. 59%



[White]

Potassium nitrate......... 6%
Antimony sulfide.......... 1%
Powdered sulfur........... 1%

[Yellow]

Potassium nitrate......... 4%
Powdered sulfur........... 1%
Charcoal.................. 2%
Sodium chloride........... 3%

[Yellow]

Powdered sulfur........... 4%
Charcoal.................. 1%
Potassium nitrate........ 24%
Sodium carbonate.......... 6%

[Red]

Strontium nitrate......... 4%
Powdered orange shellac... 1%

[Red]

Strontium nitrate........ 11%
Powdered sulfur........... 4%
Charcoal.................. 1%
Calcium carbonate........ 11%
Potassium nitrate......... 1%

[Purple]

Copper sulfate............ 1%
Strontium nitrate......... 1%
Powdered sulfur........... 1%
Charcoal.................. 1%
Potassium nitrate......... 3%

[Green]

Barium nitrate............ 7%
Powdered sulfur........... 4%
Charcoal.................. 1%
Potassium nitrate......... 1%

[Green]

Barium chlorate........... 9%
Powdered orange shellac... 1%

[Blue]

Anitmony sulfide.......... 2%
Powdered sulfur........... 4%
Potassium nitrate........ 12%


[Blue]

Potassium nitrate........ 12%
Powdered sulfur........... 3%
charcoal.................. 1%
Copper sulfate............ 2%
Powdered rosin............ 1%

                            CHLORINE & TURPENTINE
Take a small cloth or rag and soak it in turpentine. Quickly drop it into
the bottle of chlorine. It should give off a lot of black smoke and probably
start burning...This one is good for Art class when the teacher isnt looking since turpentine is easily obtained. Have fun!

2. Find the MAIN fuse box, most times its in the Restricted Area places, such as Janatorial areas and the such. Smash ALL the fuses, bring a Flashlight though cause chances are its gonna be dark.

3. Find your principals Stash cause you know he doesnt flush the confiscated shit. Dont go smokin it just yet, well you can but this is much more fun. steal his stash for about a week, not all of it though just a good portion of it and hide it somewhere that is relatively close to where he hides his so that it is easily accessable when you are stealin his.. and your gonna want it close to his in about a week. also smuggle some paper and matches down there, and if he keeps his rolling papers on him smuggle some down there too.. ok now in about a week, or a couple days or till you think your new stash is big enough to fill the school with that sweet stench. place the paper you smuggled down there on a hard surface or whatever you got. grab a handfull of that pot and plop it down in the middle of the paper.. make sure you get a bit on there but not too much... now use your skilled hands and wad that paper into a swan like those ones you get at expencive restraunts. no wait.. ok just wad it up so that there is a fuse length of twisted paper at one end and a big wad of pot at the other,, ill try a diagram at the end of this paragraph. anyways you have an oversized badly rolled joint.. well what are you waiting for spark it up and run like hell!!!

Diagram (if it sucks DRAW ME A BETTER ONE FUCKING CRITIC!)

          /---\
 -====|****| -pot goes here (for more effect add match heads)
 |    |   \---/
 |    |      |
 |    |      paper wrapped around pot
 |    | fuse (if you think you are a fast runner add some match heads in here,reliable +1)
 | light it here

ok well I hope you got the basic idea from that diagram

4. start a riot at the anual superentendant visit. or just any assembly. this is always fun if you can get enough people to go along with you, wether by choice or just by your manipulation. (an idea for those of you who arent too popular, if there are gangs in your school, prefferably 2 or more that are rivals. start passin some notes to the blacks with swasticas on them (if there are skinhead/black gangs as an example.)
 Use your Brain.. remember these are only ideas. 

5. all practical jokes are great..
egg the school/staff cars/Jocks cars
piss in the gastanks
sugar is your best friend (not just cause it gives you a cool buzz)
stinkbombs in washrooms and changerooms (specially after yer done changin after gym class and the jock fags are still in there jerkin each other off)
etc. etc.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

                                               Hacking Chapter
CHAPTER NOTE: you must have BRAINS to read this chapter (which i know you do, or atleast i hope you do.)
Dont EVER use your abilities to attack newbies or people who do not deserve to ve attacked. even if you have a gripe with them. use your own good judgement.

since I am not really a hacker (well not advanced or anything) I did not write any of these papers.. i am just including them because they are a very good form of information.
THIS ISSUE PICKS ON MOSTLY WINDOWS NT SYSTEMS CAUSE THEY ARE A GOOD EXAMPLE OF A SECURITY JOKE!

this chapter (since it is sooo robust) has its own little table of contents
							Basic hacking
							Moderate hacking
							Advanced hacking
							Applied hacking (otherwise known as usefull information about stuff that is not intended to be used to hack, but is sooo juicy that it becomes something that every hacker wants.) this issue exploits Windows NT (cause its such a shitty OS)
******************************
*                Basic Hacking                  *
******************************
this is the most basic thing i could find, there was no names on the document i took this from so i will expand on it and take credit for only what I write.

          All Windows (or microsoft for that matter)
          network services (NetWare, NT, Samba, SLIP/PPP service) are
          automatically and permanently stored in
          C:\WINDOWS\<USERNAME>.PWL. Microsoft claims they are encrypted
          securely.
and since we are hackers (or called hackers.. i personally dont believe that anyone can call themselves a hacker because the word Hacker is a word that the United States government and CIA and other people depicted crackers and curious teenaged guys to be.) we know that all Windows security is a Joke! haha. any user on a windows network has access to ALL the .pwd files for all the other users on the network. all you need to do is obtain a program to crack these files.. or if you are good,, write one. have fun!
well i guess i wrote this one! so im gonna give myself credit for it.

******************************
*              Moderate Hacking               *
******************************
THIS PORTION IS PROVIDED "AS IS" cause i dont feel like editing it.

Cracking the Windows 95 Screen Saver Password Article Extracted from 2600 Magazine Volume 13 #4 =============================================  Defeating the Windows 95 Screensaver by rdpzza  While many may consider this a trivial exercise, cracking the password scheme for Win95 may be useful to some of  you out there.  Some may even find ways to have phun with it as well.  To start with, you need to know where to look.  In 3.1, the password was kept in  the control.ini.  Although 95 also uses the control.ini, it does not use it for keeping the password information.  Foe 95, you will have to look in each of the user.dat files.  I say each because if you have multiple users, each user may have a profile saved on the hard drive.  The default user.dat file is in the \windows directory.  The other user.dat files can be found in the directory \profiles\username where username changes.  As you may know, user.dat is one of the two files used for the registry and its is very important.  User.dat will carry the attributes "shr" so you will have to look accordingly.  Also, since it is so important, a backup is  kept, namely user.da0.  This may be the previous user.dat, say when the user changed  passwords...  Anyway, now that you have the file, where is it?  If you scan the file for passowrd, you will come up with the setting of whether or not the screen saver is password protected.  This may be enough for you so you can just change it and be done.  While this little change will be noticed, it will get you by the password.  If, however, you wish to actually find out the what the pass phrase is, read on.  Why find out what the pass phrase is, you ask?  Because a lot of times users are stupid,  lazy, have bad memory or any combination of these and reuse passwords or schemes any time a key is needed.  This is especially true in network environments and even more so when 95  is used as the workstation OS.  In such systems, there is the possibility of changing the  logon password and the screen saver password at the same time.  I wonder how that can be useful?  Back to finding out what the phrase is.  95 has been rumored to use dual case.  Let me  clear this rumor.  It does not.  It uses the "all upper" coding for the password like 3.1.   The maximum length of the screen saver password is 14 characters long.  It will allow you to enter longer passwords, but 95 will act screwy; it won't require the password from screen saver, it will hang, etc.  OK, so we have the file.  Look for the string "ScreenSaver_Data".  After this is an even string of numbres and letters ending in 00.  THere is the encrypted pass phrase.  The  pass phrase is different from 3.1 in that 95 uses what I call "encrypted-couplets" meaning that for every character in the phrase, there are two encryption values.  The first  encrypted couplet (EC) is the first hex digit of the unencrypted ascii value, and the second EC is the second hex digit.  For example, say the first two hex digits after the string "ScreenSaver_Data" are 31 41 (1A in ASCII). The 31 represents (after decryption) 5 and  the 41, 2.  Put the digits together and you have 52h, R in ASCII.  Keep this concept in mind while decoding the EC's because the decryption scheme is the same for each value, only the key changes.  Example of Screen Saver EC's decoded to password.  1AAAA26473D28  <- code in the user.dat RDPZZA <- Win95 SS password   Try it out.  Text file downloaded from the HackerZ Hideout @ www.hackersclub.com/km/

******************************
*            Advanced Hacking                *
******************************
AGAIN provided "AS IS"

                                Httpd Hole

----------------------------------------------------------------------------

December 22, 1995

  I stumbled upon a security risk in NCSA's httpd Version 1.42.
Under certain conditions, you can force the daemon to return the
source code for any scripts contained in /cgi-bin.  This behavior
is not exhibited by Netscape's, or CERN's daemon.  It appears that
this behavior is also present in Version 1.5 as the pertinent
source code is identical.  I do not have that version running, so
it is not possible to test it directly.
  This security hole only presents itself for systems with cgi-bin
directories contained within their DocumentRoot directories.  You
can access the source code by adding multiple "/" preceeding the
cgi-bin portion of the URL.  If indexing is turned on, you can
get a full listing of all files within the cgi-bin directory.
Example URL's follow:

     URL:    http://www.foo.com//cgi-bin/
     URL:    http://www.foo.com///cgi-bin/man.pl

  The daemon fails to detect this as a cgi-bin redirect, then
parses the file ///cgi-bin/man.pl from your document root.  Since
the multiple slashes are legal syntax in UNIX, the daemon returns
the file as straight text.  This provides potential hackers a
glimpse at what measures you have taken (or haven't taken) to
thwart their access.
  In perusing the httpd source, the problem appears located in
routine "translate_name" in file "http_alias.c".  An alias table
is built up for string comparisons with the incoming URL.  At
startup, this table is loaded with the value of ScriptAlias in
your configuration files, generally "/cgi-bin".  Comparing
"/cgi-bin" with "//cgi-bin" fails, and the file is returned to
the browser as straight text.
  The short term workaround is listed below.  Basically, the URL
is scanned for multiple slashes as far up the processing pipeline
as possible.  As far as I can determine, this is within function
"unescape_url" in file "util.c".


void unescape_url(char *url) {
    register int x,y;
/*
 *  Remove multiple slashes in URL in place.
 */
    char *src  = url;
    char *dest = url;

    for (; src && *src; src++) {
      if (*src == '/' && *(src+1) == '/') continue;
      *dest++ = *src;
    }
    *dest = '\0';
/*
 *  End Modification
 */

    for(x=0,y=0;url[y];++x,++y) {
        if((url[x] = url[y]) == '%') {
            url[x] = x2c(&url[y+1]);
            y+=2;
        }
    }
    url[x] = '\0';
}

Remember, this hole is ONLY seen if your cgi-bin directory is
located in your DocumentRoot directory.  For those of you with
systems configured like this, and I have seen a lot, sorry to
ruin your plans for cutting out early for Christmas.

--
(the author of this document is unknown.)

******************************
*            Applied Hacking                   *
******************************
Windows NT Security

Jim Frost
May 4, 1995
----------------------------------------------------------------------------

Table Of Contents

   * Why security is important for the average user
   * Security objects
        o The Security Identifier
        o The Access Control Entry
        o The Access Control List
        o The Security Descriptor
        o The Access Token
   * C++ Classes For Manipulating NT Security
   * Example Applications
        o The WHOAMI Program
        o The ACCESS Program
        o The RESTRICT Program
        o The PROTECT Program

----------------------------------------------------------------------------

Why security is important for the average user

In part because of the "personal" nature of personal computers, most
computer users do not believe they want or need security. In truth, there
are many ways in which security is useful even to the home or individual
user.

While most people believe that security is only used for denying other
people access to your files, it has a far more important purpose -- to keep
you or others from accidentally or deliberately destroying something
important.

For example, almost everyone has accidentally deleted all the files in the
current directory only to find that they were not in the directory they
expected. Security makes it possible (although not mandatory) to protect
critical files from accidental deletion in this manner.

Another use for security mechanisms becomes obvious when a single computer
is shared between several users (a very common occurrence in business
environments, and almost universal in home environments). While most often
it is acceptable for users to look at the contents of each others' files,
you probably don't want your son, daughter, or roommate to accidentally
delete your term project when they meant to delete their letter to mom.

But possibly the most important potential use for security on personal
computer systems is protection from malice. Few would argue that the scourge
of personal computers is the virus, yet most viruses can be stopped cold
with even the most primitive security features. By disallowing changes to
system files and executables by normal users a virus that is not run by an
administrator cannot possibly invade the system. This is, in part, why
viruses are unheard-of on UNIX systems -- a virus complicated enough to
overcome the system security is big enough to be noticed immediately and so
difficult to write that few will even attempt the effort.

Security objects

Windows NT's security is based on just five security objects which are used
to identify and subclass users, indicate permissable operations, and relate
ownership and permissions to system objects.

The security objects are:

   * The Security Identifier (SID)
   * The Access Control Entry (ACE)
   * The Access Control List (ACL)
   * The Security Descriptor
   * The Access Token

Each of these objects builds upon the others in order to provide certain
security features.

The Security Identifier

The most basic security object in Windows NT is the security identifier, or
SID. An SID is a unique identifier used to identify a user or group of users
that exist on a particular computer or in a particular domain (group of
computers):

 Security
 Identifier

 Account
 Domain

NT provides two API calls that can be used to map between SIDs and user and
group names. They are:

 Function           Description
 LookupAccountName()Given an account name, find its SID.
 LookupSidAccount() Given an SID, find the account name and its domain.

The Access Control Entry

An Access Control Entry, or ACE, is the most basic unit of permission in NT.
ACEs come in two types, access allowed and access denied, which are used to
grant or refuse access respectively(1).

An ACE contains an SID which indicates which user or group of users the
permission applies to, and a permission mask that indicates exactly what
kind of permission is being granted or refused.

   Access Control
        Entry

 Type
 Security Identifier
 Permissions Mask

The permission mask is broken into parts which indicate permissions specific
to a particular object type (called specific rights) and generic permissions
(generic rights) that apply to all objects.

The standard rights, which control the accessibility and exclusivity for all
objects, are:

 Right       Description
 DELETE      The ability to delete the object.
 READ_CONTROLThe ability to inspect the object's security information.
 WRITE_DAC   The ability to change the object's list of permissions.
 WRITE_OWNER The ability to change the owner of the object
 SYNCHRONIZE Force mutual-exclusion of object accesses.

While each object type has its own list of specific rights, the filesystem
rights are the most frequently encountered. They are:

 Right                Description
 FILE_READ_DATA       The ability to read the file.
 FILE_LIST_DIRECTORY  The ability to list the contents of a directory.
 FILE_WRITE_DATA      The ability to modify the file's data.
 FILE_ADD_FILE        The ability to add a new file to a directory.
 FILE_APPEND_DATA     The ability to append data to a file.
 FILE_ADD_SUBDIRECTORYThe ability to add a subdirectory to a directory.

 FILE_READ_EA         The ability to read the extended attributes(2) of a
                      file.

 FILE_WRITE_EA        The ability to change the extended attributes of a
                      file.
 FILE_EXECUTE         The ability to run an executable.

 FILE_TRAVERSE        The ability to open a file or run an executable
                      within a directory.

 FILE_DELETE_CHILD    The ability to delete a file or directory within a
                      directory.

 FILE_READ_ATTRIBUTES The ability to read a file's attributes (e.g. system
                      or hidden).
 FILE_WRITE_ATTRIBUTESThe ability to change a file's attributes.

The Access Control List

While an ACE is the basic unit of permission on NT, a single ACE is seldom
enough to fully describe the accessibility of an object to different users
or groups on the system.

Consider, for example, a source code file. You need to be able to manipulate
your source files in any way you like -- read them, modify them, delete
them, etc. You would also like the members in your development group to be
able to look at your source files, but not to change them since everyone
else in your group is an incompetant dweeb who can barely understand your
code, much less change it in any useful way. Lastly, you would like to keep
your manager from even looking at your code lest he find out that you spent
last week playing DOOM rather than working.

To maintain multiple privilege levels for different users or groups of users
in this way, ACEs are grouped into Access Control Lists, or ACLs. Simply
put, an ACL describes all of the users and groups who are either allowed or
denied some sort of access to a particular object.

 Access
 Control
 List

 ACE
 ACE
 ACE
 ...

When a thread requests access to an object (by opening a file, for
instance), the system performs two passes over the ACL.

In the first pass the system inspects every "access denied" ACE in the list.
If it finds an SID that matches the thread's SID, or an SID of a group that
the thread's owner is a member of, access is immediately denied.

Once all "access denied" ACEs have been inspected the system proceeds to
check all "access allowed" ACEs. For each matching ACE, the permission mask
in the ACE is added to a growing list of permissions granted to the thread's
SID for access to the object. Once the list of permissions matches or
exceeds the group of permissions that was requested permission is granted.
If the end of the ACL is reached before enough permissions are accumulated
access is denied.

NT provides a number of functions for managing ACLs:

 Function           Description
 AddAce()           Add a new ACE to the access control list.
 DeleteACE()        Remove an ACE from the access control list.
 InitializeAcl()    Create a new ACL structure.
 IsValidAcl()       Determine validity of an ACL structure.
 GetAclInformation()Retrieve information about the ACL.
 SetAclInformation()Set the ACL revision information.

Even with these functions the variable-length nature inherent in ACLs makes
them tedious to deal with.

The Security Descriptor

While an ACL describes the accessibility of an object, it does not
completely describe the security attributes of an object. The complete group
of security attributes is kept in an object called a security descriptor,
which contains:

 Object                      Description
 The owner SID               The SID of the user who owns this object
 The object's primary group  The group of users to which this object
 SID                         belongs

 The system ACL              The access control list used for auditing
                             features

 The discretionary ACL       The access control list that specifies which
                             users or groups may access an object.

When you want to view or change the security attributes of an object, you
must do so through the object's security descriptor.

The following functions are used to manage the security descriptor:

 Function                      Description

 IsValidSecurityDescriptor()   Determine the validity of a security
                               descriptor
 InitializeSecurityDescriptor()Create a new security descriptor

 GetSecurityDescriptorControl()Retrieve control information about the
                               security descriptor

 GetSecurityDescriptorDacl()   Retrieve the security descriptor's
                               discretionary ACL

 SetSecurityDescriptorDacl()   Change the security descriptor's
                               discretionary ACL

 GetSecurityDescriptorGroup()  Retrieve the security descriptor's primary
                               group

 SetSecurityDescriptorGroup()  Change the security descriptor's primary
                               group

 GetSecurityDescriptorOwner()  Retrieve the owner from the security
                               descriptor
 SetSecurityDescriptorOwner()  Change the owner in the security descriptor

 GetSecurityDescriptorSacl();  Retrieve the security descriptor's system
                               ACL
 SetSecurityDescriptorSacl();  Change the security descriptor's system ACL

The Access Token

An access token is essentially NT's identification card for a user. Every
process, and potentially every thread, has a related access token which
identifies the user account that the process is running under and a lot of
default values to be used when creating new objects.

An access token contains a lot of security information about the user,
including their SID, their primary group SID, their current privilege set,
the SIDs that should be used to indicate the owner and group of new objects
and files, and the default discretionary ACL used when creating new objects
and files.

Access tokens are created through login services (e.g. the login dialog or a
network share login), through impersonation (temporary assumption of a
user's security attributes by a service's thread), or through the NT login
API(3,4).

C++ Classes For Manipulating NT Security

While the concepts behind NT's security are fairly simple, the variable size
of the data structures makes management tedious at best and therefore is a
prime target for encapsulation. The accompanying C++ classes (which should
be self-explanatory) attempt to simplify the interface by providing a
straighforward interface to the relevant objects.

Example Applications

The WHOAMI Program

The simplest of the sample applications is WHOAMI, which finds the current
user's SID and translates it into the related domain and account name
through the use of the SecurityIdentifier class.

The ACCESS Program

The ACCESS program is useful for inspecting the security information of
NTFS(5) files. Users familiar with the Security functionality of the NT File
Manager will notice that ACCESS shows considerably more information about
the security attributes of the file than is shown (or even possible to
manipulate) using the File Manager. While the File Manager's security
management is flexible, it actually supports only a small subset of the
security functionality available in NT. ACCESS demonstrates the use of the
SecurityDescriptor, AccessControlList, and AccessControlEntry objects for
querying the security information of a filesystem object.

The RESTRICT Program

To demonstrate the modification of a file's discretionary ACL, the RESTRICT
program builds an ACL that permits read-only access to the indicated files
by all but the owner of the file. This is conceptually similar to the ATTRIB
-R command found in MS-DOS, but shows the additional flexibility of NT's
security subsystem. RESTRICT demonstrates the use of the AccessControlList
class to build a new ACL.

The PROTECT Program

As mentioned at the beginning of this document, it's possible to harden your
system against viruses through the use of security mechanisms. The PROTECT
program, when run by an administrator, changes the owner and permissions of
all executable files in such a way as to make it difficult or impossible for
a virus to alter executables. Provided that users normally work without
administrator privileges a system protected in this manner should be
relatively invulnerable to infection.

----------------------------------------------------------------------------
Footnotes

(1) Actually there are two more ACE types: system audit, used for generating
logs of accesses; and system alarm, which is not yet implemented.

(2) As with the Macintosh, NTFS provides multiple data streams in each file
which are useful for storing additional file information such as icons.
Extended attributes refers to all of the data streams except for the default
(normal file data) stream.

(3) This API was not publicly available prior to NT 3.51.

(4) Since the access token API is new, and is not yet on my system, no class
is provided for managing access tokens.

(5) NTFS is the only filesystem currently supported by NT which implements
security.
***********************
much appreciation Jim!! good paper!
***********************

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
                                          Phreaking Chapter
Phreak: Noun
(1) A person who uses phones in ways they were not intended to be used by the public.
(2) Hackers of Telephones.
(3) People who outsmart phone companies and governments by using shit from radioshack. :) 
Freak: verb 
(1) See Jock
      I hope you thought that was as amusing as i did when i wrote it.
Continued in RFH2.txt