Category : Network Files
Archive   : SEC286.ZIP
Filename : README.TXT

 
Output of file : README.TXT contained in archive : SEC286.ZIP
A very rare security shortcoming has been identified by Novell. It has been
fixed with this patch. For most Novell customers who have intruder detection
set on - this security weakness will not pose a problem. Novell recommends
that all customers turn intruder detection on and if the customer has greater
concerns for security, they should apply this corrective patch.

This program fix should only be applied to released copies of 286 NetWare
version 2.15C. Any previous or subsequent versions of 286 NetWare do not have
this problem, and should not have this program fix applied to them.

The manner in which you apply the program fix to your 286 NetWare 2.15c
installation depends upon the media in which the NetWare OS generation
facility (NETGEN or ELSGEN) was received (3.5" or 5.25" diskettes), and
whether or not the OS is ELS-II NetWare. A separate set of instructions is
given below for each case.

For those who generate their OS from floppies, all references to subdir-
ectories in these instructions should be interpreted as references to
diskettes whose labels have the specified name. Also, if there is not enough
room for those who generate their OS from floppies to duplicate the object
file on the diskette specified, the new .OBJ files will need to be created
on the drive containing this program fix, then copied to a new working copy
of the diskette.

3.5" MEDIA, NOT ELS-II:

1. In the ADOBJ, ANDOBJ, SFTOBJ, and TTSOBJ subdirectories, rename the
corresponding .OBJ files to have a .SAV extension.

2. In each of these subdirectories, apply the program fix to the newly-
renamed .SAV file, creating a new .OBJ file.

For example, assume that the PASSFIX.FIX and the ZAPOBJ program reside
on floppy drive A:. To apply the program fix to the SFT object file,
execute the following command while in the SFTOBJ subdirectory:

A:ZAPOBJ SFT.SAV SFT.OBJ A:PASSFIX.FIX

You would then apply the program fix to object files in the ADOBJ,
ANDOBJ, and TTSOBJ subdirectories in the same manner. If the
ZAPOBJ program indicates that errors were encountered in applying the
program fix to any of these files, call LANSWER for assistance.

3. Using NETGEN, regenerate a new NET$OS.EXE file as you have always
done.

4. If the OS works satisfactorily, you may delete the .SAV files that
you renamed in Step 1. Otherwise, call NetWare support provider for
assistance.


5.25" MEDIA, NOT ELS-II:

1. In the ADOBJ, ANDOBJ, SFTOBJ, and TTSOBJ subdirectories, rename the
corresponding .OBJ files to have a .SAV extension. Also rename all
.OBJ files in the OSOBJ subdirectory to have a .SAV extension.

2. In each of these subdirectories, apply the program fix to the newly-
renamed .SAV file, creating a new .OBJ file. Apply the PASSFIX1.FIX
program fix directives to object files in the ADOBJ, ANDOBJ, SFTOBJ,
and TTSOBJ subdirectories, and the PASSFIX2.FIX directives to object
files in the OSOBJ subdirectory.

For example, assume that the PASSFIX1.FIX, PASSFIX2.FIX and ZAPOBJ.EXE
files reside on floppy drive A:. To apply the program fix to the SFT
object files, you would execute the following commands from the
directory just above the SFTOBJ subdirectory:

CD SFTOBJ
A:ZAPOBJ SFT_1.SAV SFT_1.OBJ A:PASSFIX1.FIX
CD ..\OSOBJ
A:ZAPOBJ SFT_2.SAV SFT_2.OBJ A:PASSFIX2.FIX

You would then apply the program fix to object files in the ADOBJ,
ANDOBJ, and TTSOBJ subdirectories in the same manner, along with their
counterparts in the OSOBJ subdirectory. If the ZAPOBJ program
indicates that errors were encountered in applying the program fix to
any of these files, call your NetWare support provider for assistance.

3. Using NETGEN, regenerate new NET$OS executable file(s) as you have
always done.

4. If the OS works satisfactorily, you may delete the .SAV files that
you renamed in Step 1. Otherwise, call your NetWare support provider
for assistance.


3.5" MEDIA, ELS-II:

1. In the EDOBJ-1 and ENDOBJ-1 subdirectories, rename the corresponding
.OBJ files to have a .SAV extension.

2. In each of these subdirectories, apply the program fix to the newly-
renamed .SAV file, creating a new .OBJ file.

For example, assume that PASFXE_1.FIX, PASFXE_2.FIX, and the ZAPOBJ
program reside on floppy drive A:. To apply the program fix to the
dedicated ELS object files, execute the following commands while in
the EDOBJ-1 subdirectory:

A:ZAPOBJ ELS2_1.SAV ELS2_1.OBJ A:PASFXE_1.FIX
A:ZAPOBJ ELS2_2.SAV ELS2_2.OBJ A:PASFXE_2.FIX

You would then apply the program fix to object files in the ENDOBJ-1
subdirectory in the same manner. If the ZAPOBJ program indicates that
errors were encountered in applying the program fix to any of these
files, call your NetWare support provider for assistance.

3. Using ELSGEN, regenerate a new NET$OS.EXE file as you have always
done.

4. If the OS works satisfactorily, you may delete the .SAV files that
you renamed in Step 1. Otherwise, call your NetWare support provider
for assistance.


5.25" MEDIA, ELS-II:

1. In the EDOBJ-1, EDOBJ-2, ENDOBJ-1, and ENDOBJ-2 subdirectories, rename
the .OBJ files to have a .SAV extension.

2. In each of these subdirectories, apply the program fix to the newly-
renamed .SAV file, creating a new .OBJ file. Apply the PASFXE_1.FIX
program fix directives to object files in the EDOBJ-1 and ENDOBJ-1
subdirectories, and the PASFXE_2.FIX directives to object files in the
EDOBJ-2 and ENDOBJ-2 subdirectories.

For example, assume that the PASFXE_1.FIX, PASFXE_2.FIX and ZAPOBJ.EXE
files reside on floppy drive A:. To apply the program fix to the
dedicated ELS object files, you would execute the following commands
from the directory just above the EDOBJ-1 subdirectory:

CD EDOBJ-1
A:ZAPOBJ ELS2_1.SAV ELS2_1.OBJ A:PASFXE_1.FIX
CD ..\EDOBJ-2
A:ZAPOBJ ELS2_2.SAV ELS2_2.OBJ A:PASFXE_2.FIX

You would then apply the program fix to object files in the ENDOBJ-1
and ENDOBJ-2 subdirectories in the same manner. If the ZAPOBJ program
indicates that errors were encountered in applying the program fix to
any of these files, call your NetWare support provider for assistance.

3. Using ELSGEN, regenerate new NET$OS executable file(s) as you have
always done.

4. If the OS works satisfactorily, you may delete the .SAV files that
you renamed in Step 1. Otherwise, call your NetWare support provider
for assistance.

***************************************************************************
DISCLAIMER

Novell, Inc. makes no representations or warranties with respect to
this software patch, and specifically disclaims any express or implied
warranties of merchantability or fitness for a particular purpose.
Novell's intentions for this software patch is to provide a temporary
work-around or fix to the anomalies described in this file.
Novell will not be responsible for any data loss that may result from
implementing this patch. Novell strongly recommends a backup be made
before any patch is applied. Technical support for this patch is
provided at the discretion of Novell.

***************************************************************************



  3 Responses to “Category : Network Files
Archive   : SEC286.ZIP
Filename : README.TXT

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/