home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 35 Internet
/
35-Internet.zip
/
tserve11.zip
/
TSERVE.USR
< prev
next >
Wrap
Text File
|
1996-01-25
|
5KB
|
94 lines
; Did you see The Naked Lunch? Weird movie, worth the rent.
; This is the sample user file... I used this exact file for testing
; on my system before releasing TSERVE. Comments begin with a
; semicolon and continue to the end of the line. All of the user
; lines in this file have been commented out after testing. The only
; one that is not commented out (with a semicolon) is this one:
NAKEDLUNCH, MUGWUMPJOY ; This login code has to be here for a while.
; You know, the really fun part about TSERVE is that you can change
; so many things about it so easily.
;
; FOR Example, if you want to assign fixed IP addresses to your users
; or perhaps just some of them, you can do it by including an address.
; The first example includes all of the possible settings for a user
; record. Each user record should be on a single line. All of these
; records have been commented out with a semicolon at the start of
; the line... Valid user entries must NOT have the semicolon at the
; beginning of the line, although it's perfectly fine to place a comment
; at the end of a line.
;
; USER ID, USER PASSWORD, HOST IP : USER IP
;
;Full Name User, Their Password, 123.123.123.123:231.231.231.231
;
; The above record includes all of the possible user parameters. It is
; NOT typical. For example, you would almost always allow the host IP
; address to be decided by the configuration file. However, it's good
; to know you can override it for a user if you need to. BE CAREFUL WHEN
; DEFINING IP ADDRESSES IN THE USER FILE! You must not allow any spaces
; between IP addresses and the colon. The colon is used to identify
; where the IP addresses are located, and which one's are defined. If
; you include spaces, you will confuse TSERVE and it will default to
; one or more of the IP addresses in the configuration file.
;
; The following listings are examples of one way you could assign fixed
; IP addresses to users. The HOST address would be set by the configuration
; file, while their individual IP addresses would over-ride the config
; file for each user.
;
;Fixed User1, Fixed1Password, :123.123.123.100
;Fixed User2, Fixed2Password, :123.123.123.101
;Fixed User3, Fixed3Password, :123.123.123.102
;
; NOTE: The HOST IP address is left off, but the colon remains! THERE
; ARE NO SPACES IN THE IP ADDRESS OR BETWEEN IT AND THE COLON.
;
; For more typical dynamic IP addressing, you need not include any IP
; addresses at all. In these cases, the IP addresses assigned to the
; host connection and user conection will come from the configuration
; file alone.
;
;My Cousin Vinnie, Vinnies Words
;My Uncle Sammy, GoshIHopeHeDoesntShowUpThisYear!
;Why Not Have 5 names, You Can If you Want
;
; It's important to note that TSERVE will allow you to specify spaces
; and punctuation in your login id's and passwords except for the
; comma, the colon, and the semicolon. You can put just about any other
; character you want in the login id's and passwords, but it's not a
; good practice since it can get very ugly and confusing.. also, you
; may want to use a login or password in PAP or CHAP verification and
; these special characters will make that difficult. Any spaces before
; or after a login code or password will be removed before they are
; compared with a user's inputs... For example, the password for
; "My Cousin Vinnie" is "Vinnies Words". If you accidently use a colon
; semicolon, or comma in a login or password, you will confuse TSERVE
; and get upredictable results. BE VERY CAREFUL... TSERVE uses these
; characters to figure out what you've typed in. If they're in the
; wrong places, TSERVE will not be able to properly interperate what
; you mean.
;
; If you want to make things simpler, you can omit a password. If you
; do, TSERVE will not ask for one and will assume that if the user has
; the login code right, they must be a valid PPP user. I DON'T reccomend
; this as most people's standard connection scripts will expect to be
; asked for both a login and password... besides, it's not very secure
; since most people's login codes can become public very easily. Any
; way, here are some examples.
;
;VeryUgLyLongPassWORD093994#455skstdyTHATisODD
;My Very Own Login Without A Password
;My Login Without A password that includes addressing :123.123.123.23
;
; It is possible to have addressing without a password, but as I said,
; it's not a good idea to not include a password for each user.
;
; LOGIN CODES and PASSWORDS are CaSe SeNsItIvE in this program and
; shoule be no longer than about 60 characters. In fact, if you have
; a login code or password that's longer than about 20, you really
; should come up with something a little smaller... Not because the
; program won't handle it, but because it just doesn't make a whole
; lot of sense.