home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Hacker Chronicles 2
/
HACKER2.BIN
/
887.PRMDOC.98T
/
PRMBS98S.UPD
< prev
Wrap
Text File
|
1988-02-12
|
6KB
|
130 lines
PRMBS Version 0.98 Revision S
This a purely maintanenece release which fixes several small
bugs in Revision R plus one large bug, which prevented remote
connections ... yeah I know tsk tsk!!!
PRMBS Version 0.98 REvision R
This release has several bug fixes for 0.98P and adds remote
security for the Remote REQ command and RMAIL command. The
details are in the revised documentation.
PRMBS version 0.98 Revision P
The PRMBS version 0.98 revision P contains a number of fixes to the
revision O code plus several new features;
- KX command was 'broke' and it is now fixed
- if a user entered his name via the 'name firstname lastname' and
the sum of the strings' lengths is in excess of 20 bytes it will
cause unpredictable results, at the least when that user logs out his
user record will not write. If the total is up past 128 byes in will
crash the system or worse. FIXED
- if a script is requested that is not in the CALLDIR file it
returned true and went on an tried to connect with the last good
script you executed. FIXED
- version 98 user files that had the residue of my earlier abortive
BULLETIN command had trash in the DU display, that will be corrected
by using a GU command.
- the 'permission denied' message had an extraneous '$V' prefixed to
it and it was corrected also. Same was fixed for an erroneous 'not
found' message.
- the 'extended send' commands (i.e. SBF ALL @ KA1XXX ) was sending
to non-PRMBS systems when it was not supposed to , this has been
corrected.
- there were about 6 small fixes that have no apparent effect on
operations but reduce code size, optimize the I/O and reduce
probabilities for hang-ups in certain key spots.
The new features include some minor and some major. NO CHANGES to the
CONFIG file are required other than to update the version/date string to
read "098p 01/27/88". These new features are;
- the revision N/O feature which copies the TO field to the @ field for
Traffic with NO @ BBS has been enhanced to make the copy not only for
'numerical' TO designators, but for anything matching "NTS" as the
first 3 characters.
- 'staggered hours' selection for the EVENT file is implemented. You
may place a single character after the hours window in the EVENT
file, this character may be any of the following;
E,O - even, odd 3,4,6,8 - hours divisible by #
the purpose of this is to allow specification of a general time
window for execution, and then permit , odd hour only, even hopur
only, or every hour evenly divisible by one of the numbers shown.
(Please refer to the sample EVENT file included with the update.
- the remote request functions (through revision O, REQDIR and
REQFIL) have been enhanced to provide for remote message request. The
format is to send to REQMSG @ KA1XXX with a title of 12345 @KA2XXX.
Which will got to KA1XXX and get a copy of message number 12345 and
send it back encapsulated in a new RFC822 header to the requester at
KA2XXX BBS. (*** There is no security on this for now, I am working
on that ... A person could request a message that he technically is
not permitted to see and get a copy .... I am not worried about this
for the moment as a simple mycall change will achieve the same
security breach.)
There is also the corresponding 'get' command to go with this feature
to allow users easy composition of the request. The form is ;
GETMSG 12345@KA2BQE
which when issued at your local BBS composes the message to REQMSG at
KA2BQE to get message # 12345.
- I have implemented an RMAIL command which is analogous to the MAIL
command executed remotely. For example, a user enters the following;
RMAIL @KD6TH N2DSY N1CUI@N1CUI KB7UV@N2MH W2VY@KD6TH
(here it will be prompted for title)
COSI Code design review
(here it will prompt for text)
The meeting will be .....
.....
.....
/EX
One message will be generated, it will be addressed to RMAIL@KD6TH
and it will have on the "To: " line in the RFC 822 internal header;
To: rmail@kd6th n2dsy n1cui@n1cui kb7uv@n2mh w2vy@kd6th
This message will travel through all system (PRMBS 0.98P or not)
innocuously as a simple message UNTIL it hits KD6TH where the 'RMAIL'
with KD6TH stripped out will be decoded. The message will now
'explode' into 4 copies, individually addressed to N2DSY, N1CUI,
KB7UV and W2VY. I should not need to explain the benefits of
eliminating 3 of the 4 copies of the message for transmission to the
point of divergence on their respective paths.
The feature also supports remote alteration of message types in
the following manner;
RMAIL @KD6TH -TB N2DSY N1CUI@N1CUI KB7UV@N2MH W2VY@KD6TH
The "-TB" says make all the messages following type 'B'. Now you can
mix types with the 'type change' command being in effect until its is
superseded by an additional type chnage command.
RMAIL @KD6TH -TB N2DSY N1CUI@N1CUI -TF KB7UV@N2MH W2VY@KD6TH
This will make the first two messages as type B and the last two as
type F.
I am working on the REQLST command now, it is designed and mostly
coded but has been shelved while I re-write the list command to allow
the list output to be re-directed to a file and make some mods requested
by various users.
73 de brian