|
Problem IC84170
|
Status: Closed |
REDUCTION IN PERMISSIONS ON THE NODES.REG FILE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Currently the DB2 file nodes.reg is set to have world writable
permission's enabled by default upon installation. The world
writable permission is unnecessary for normal operations and
does not pose a security exposure. This APAR is to remove
the world writable permission from this file because it may
trigger security audit alerts for some customers.
This file is located in the sqllib of the instance owner's home
directory:
ex: /home/db2inst1/sqllib/nodes.reg. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2 file nodes.reg is set to have world writable permissions *
* enabled by default upon installation. Non-admin users have *
* the ability to update the file and cause data corruption and *
* / or loss. *
* *
* This file is located in the sqllib of the instance owner's *
* home directory: *
* ex: /home/db2inst1/sqllib/nodes.cfg. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.5 Fix Pack 9. *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 9.5 Fix Pack 9. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.06.2012
27.03.2013
27.03.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
