home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
network
/
bindump1.zip
/
BINDDUMP.DOC
next >
Wrap
Text File
|
1992-04-11
|
6KB
|
180 lines
Some brief notes for BINDDUMP.EXE
Bug reports, questions, suggestions, postcards and comments to
rml@extro.ucc.su.OZ.AU
Preamble :-
BINDDUMP is hereby released into the public domain in the spirit of Dave
Harris's free email package for netware (Pegasus), which is much bigger
and better and if you don't already use it, you payed too much. Get it
from splicer.cba.hawaii.edu via anonymous ftp.
This package may be freely distributed and used on condition that no fee
ever changes hands at any stage for distribution or use, and that the
executable and this documentation travel together.
Any one game to use this package does so at their own risk.
No guarantee of fitness for purpose of any kind is expressed or implied -
in fact, quite the opposite. This package is only guaranteed to take up
space wherever it is stored.
If this software or documentation break anything of yours, the only other
guarantee that the author can give is that you still own all of the
broken parts.
Description :-
This is a very simple utility for Novell netware which lists objects known
to the bindery. If you don't know much about netware security and file server
organization, here's a quick free course in the basics.
The bindery is where netware keeps most of the security information. Items
like Users, passwords and priveleges. Amongst other things, the objects
known to the bindery are of 4 main flavours :-
1) Users - these have userid's (such as ROSS) which are associated with
passwords and realnames (such as Dr. Ross Lazarus) which we can snaffle with
this programme
2) Groups - these have names (such as EVERYONE) and are the way users are
quickly associated with applications and file access needed to run them by
the Supervisor on a netware server. Usually the Supervisor will have made
a variety of groups, each of which has specific access and permission to
get at various files and directories on the server. For example, WPUSER
might be the group for wordprocessor users - these people may have access
to the appropriate software and directories. Group membership can be tested
in the process of login so that special steps can be taken for members of
each group. The Supervisor can change group membership quickly and easily.
3) Print servers - these have names (such as R204HPL3). Each print server
usually has a specific physical printer associated with it. Since a netware
network can have several print servers hanging off the file server and any
number of remote print servers hanging off workstations, these are a
convenient way to spread printing physically around the network.
4) File servers - these have names (such as ADMIN) and are netware file
servers other than your own which are accessible via some sort of
internetwork connection. Many small networks may be bridged on a VAX
ethernet backbone for example,
How to use it :-
The number above for each of these flavours has the same meaning for BINDDUMP
and there is a special one, the wildcard "*" which means ALL object types.
BINDDUMP will make a simple list of the object types specified as a command
line parameter. So, to get a list of USERS, try
BINDDUMP 1
To get a list of every object of each of the 4 types, try
BINDDUMP *
BINDDUMP returns a DOS errorlevel which may be useful in a batch file
Return Codes: 00h successful
01h Netware not found
96h server out of memory
EFh invalid name
FCh no such object
FEh bindery locked
FFh bindery failure
A sample output :-
A typical call of
BINDDUMP *
produces output like this on my netware file server
User: SUPERVISOR Realname: Ross Lazarus
User: NATALIE Realname: Natalie Wong Tang
User: SHANTHI Realname: Dr Shanthi Kathir
User: CHEY_ARCHSVR Realname: Tape drive
User: ROSS Realname: Dr Ross Lazarus
User: MICHAEL Realname: Michael Jansen
User: POSTMAN Realname: GMU Postman.
User: PETER Realname: Dr Peter Landau
User: CAROLYN Realname: Carolyn Robinson
User: CHRIS Realname: Chris Benson
User: MARLENE Realname: Marlene Mills
User: MARILYN Realname: Marilyn Dodd
User: PALI Realname: Palitha Siriwardana
User: ROXY Realname: Roxana Ortega
User: CAROL Realname: Carol Murphy
User: JUDY Realname: Judy Sandilands
User: MAUREEN Realname: Maureen Dorahy
User: MICHELLE Realname: Michelle Purcell
User: DILYS Realname: Dilys Stockley
User: ELEANOR
User: SMICHAEL Realname: Michael Jansen
User: SROSS Realname: Dr Ross Lazarus
User: MAIL Realname: Mail man for GMU
User: MG Realname: Dr Michael Gliksman
User: MAXLOGIN Realname: Special login for bbs
User: TEMP Realname: Temporary Secretary
User: FIONA Realname: FIONA
User: CDUSER
Group: EVERYONE
Group: SASUSER
Group: PMIATS
Group: WSUSER
Group: WPUSER
Group: REALGAT
Group: EVALUNIT
Group: GROUPMAIL
Group: PROG
Group: EDUCATION
Group: TODAYUSER
Group: THOUGHTS
Group: GAMERS
Group: TALKUSER
Group: NOMAIL
Group: BIRTHDAYS
Group: DRAWPERFECT
Group: PARADOX
Group: DNCB
Group: CDUSER
PrintServer : HPNORMAL
PrintServer : DOM
PrintServer : LABEL
FileServer : COMPUTER_SERVICES
FileServer : GMU
FileServer : MEDICAL_ADMIN
FileServer : DOM_MID_PROG
FileServer : RENAL_MED
FileServer : RADONC
FileServer : DENTAL_SCHOOL
FileServer : WSAHS_ADMIN
FileServer : HEMONC
FileServer : COMMUNITY_MEDICINE
FileServer : WEST04
FileServer : WEST05
FileServer : WEST06
The semicolon should enable most anything to be done to the output by a
filter like awk or a language like perl.
Note that the output can be redirected to a file by using the DOS trick of
adding a ">" and a filename to the command line - so to get a list of all
users known on your current default file server sent to a DOS text file
called "BINDDUMP.OUT" try
BINDDUMP 1 > BINDDUMP.OUT
BE WARNED, if a file of that name already exists, it will be replaced and the
original contents PERMANENTLY LOST - except that since you always backup
everything of importance, this won't matter, will it ? (ha ha).
A double > (>>) will APPEND the output to the specified file if it exists.
To page the output nicely, try
BINDDUMP 1 | MORE.