| Reference |
Article |
Found in Version |
Resolved in Version |
Description |
| 928400 |
- |
6.5.1 |
- |
Issue: A user might notice kernel debug messages on kernels with configuration CONFIG_PROVE_LOCKING enabled when the Embedded Control for Linux driver gets loaded. |
| 949005 |
- |
6.5.1 |
- |
Issue: The Embedded Control for Linux Agent isn't supported on kernels with the configuration CONFIG_PAX_KERNEXEC enabled. |
| 601728 |
- |
6.5.1 |
- |
Issue: According to the NFS protocol, if a file present on the NFS share is opened once on the NFS client, it can't be reopened until the file attributes are changed. So, if a read-protected file on an NFS share is opened on the client side in update mode, the user can read it on the client even in enable mode (after coming out of the update mode). This ability is the case until the file attributes are changed on the server. |
| 601734 |
- |
6.5.1 |
- |
Issue: Changing a hard link might cause the name of the link or program to display in events. |
| 601914 |
- |
6.5.1 |
- |
Issue: For daemon processes, the reported username and original username are the same. |
| 602653 |
- |
6.5.1 |
- |
Issue: A write-protected file can be changed through its hard link if the hard link has already been created. |
| 602772 |
- |
6.5.1 |
- |
Issue: Scripts without the #! tag can't act as updaters. |
| 602977 |
- |
6.5.1 |
- |
Issue: For loopback file systems, some features, such as updater and monitoring, don't work correctly when the loopback path is used instead of the physical path in the sadmin commands. Example: If /opt is mounted as a loopback file system at /mnt, to add /mnt/abc as an updater, you must add the path /opt/abc as an updater. |
| 602990 |
- |
6.5.1 |
- |
Issue: Some features, such as updaters and mon-proc-exec, don't work properly for unsupported file formats. Only executable binaries and #! scripts are supported file formats. |
| 603490 |
- |
6.5.1 |
- |
Issue: You observe the following issues when an updater calls another updater:
- If the child process is added as an updater, the non-inheritable option (-d) of the parent process is overridden.
- If the parent process is added as an updater, the non-inheritable option (-d) of the child is overridden.
|
| 604780 |
- |
6.5.1 |
- |
Issue: For processes that aren't directly associated with a terminal, the original_user field is a replica of the user field. For example, when you run a script through Runlevel/init scripts, original_user is the same as the user. |
| 605062 |
- |
6.5.1 |
- |
Issue: The mmap system call at the NFS client doesn't work if the file is read-protected. |
| 606674 |
- |
6.5.1 |
- |
Issue: A write-protected file can be changed or deleted if the file system is mounted to a different directory. |
| 607014 |
- |
6.5.1 |
- |
Issue: Adding a script as an updater twice (once on its own and again with its parent) can lead to ambiguous behavior. |
| 607024 |
- |
6.5.1 |
- |
Issue: By default, the deny-read feature is disabled. A read-protect rule is immediately applied but is effective only after the deny-read feature is enabled. |
| 601763 |
- |
6.5.1 |
- |
Issue: Process information can't be determined for those processes that are invoked before the Embedded Control for Linux driver is loaded. This issue has the following implications:
- If such a process makes file changes, these changes might not be reported.
- For processes that start before the driver is loaded, only the partial program names are reported.
- For NFS, for the changes made by the client, the change events displaying on the server have only the relative name for the NFS daemon (in other words, nfsd or nfsktcpd).
- No Process Start and Process Stop events are generated for already running processes.
|
| 604604 |
- |
6.5.1 |
- |
Issue: Write or read protection doesn't work on files added using cachefs/lofs. |
| 613214 |
- |
6.5.1 |
- |
Issue: If the installation path is a mount point, forcibly unmounting (for example, using the umount –f command) might lead to non-deterministic behavior. |
| 762449 |
- |
6.5.1 |
- |
Issue: Events are generated if a special device file is renamed. |
| 774493 |
- |
6.5.1 |
- |
Issue: Change of a binary in Update mode doesn't change or update the corresponding hard-link in the allow list. |
| 797363 |
- |
6.5.1 |
- |
Issue: The sadmin xray command doesn't list the attr-specific configurations for the running process. |
| 798843 |
- |
6.5.1 |
- |
Issue: You might observe unexpected behavior if a process exits without closing one or more changed files. |
| 602174 |
- |
6.5.1 |
- |
Issue: When you log on to a system using Telnet as a non-root user, the original_user name displays as root. |
| 607245 |
- |
6.5.1 |
- |
Issue: No events are generated for changes to a file with the string solidcore.log in its name. For example, mysolidcore.log. |
