As part of normal operation, Flexnet Publisher may create and delete folders under /dev/shm with names beginning 'FlexNetFs.'. These folders are associated with the implementation of the new secure file anchoring functionality on Linux. They are not designed to be accessed other than by Flexnet Publisher, consequently, errors as below may be reported when trying to list such a folder are to be expected:  ls /dev/shm/ -al ls: cannot access /dev/shm/FlexNetFs.43054: Transport endpoint is not connected total 99 drwxrwxrwt 3 root root 120 Mar 14 12:10 . drwxr-xr-x 18 root root 3760 Mar 14 11:10 .. d????????? ? ? ? ? ? FlexNetFs.76491 So, it is suggested to customers to configure their monitoring tool (if any) to ignore any folders matching the name "/dev/shm/FlexNetFs.*" ... View more

Observation: When starting the server with the command /opt/FNPLicenseServerManager/lmadmin, the below occurred ./lmadmin: error while loading shared libraries: libldap-2.4.so.2: wrong ELF class: ELFCLASS64 However, in the path /opt/lib64/, libldap-2.4.so.2 does exist Root Cause: The error log "libldap-2.4.so.2: wrong ELF class: ELFCLASS64" indicates that the "ldap" libraries installed in system are for 64 bit but for v11.14.0 there was no 64-bit lmadmin available (it was only released starting FNP-11.15.1). So, try by installing the 32 bit variant of libldap and test. ... View more

At couple of customer sites, internal technical audit tools are complaining about the world-level read/write access to /dev/shm/.flexnetFS file system. The ask is if that's necessary and can not be avoided? Report: SoC ID: 3.65-9/2.0 No world writable files may exist. World writable files are files that can be accessed by all users of a system. Such files must be identified and the rights of the corresponding files must be adjusted to an adequate level. Motivation: Data in world writable files can be read, changed and possibly compromised by any user of a system. The following threats are relevant to this requirement: Unauthorized viewing or access to data Unauthorized modification of data command to check: find / -type f ! -path "/proc/" ! -path "/sys/" ( -perm -o+w ) -exec ls -adl {} \; rw-rw-rw. 1 nuance nuance 0 Feb 24 11:26 /dev/shm/.flexnetfs Please check the access rights of this file and if this can be subject of change to meet the requirements.    Answer:   /dev/shm/.flexnetFS is a lock-file located in transitory shared memory. It is used in the initialization and maintenance of the FlexNet file-system. Any Flexnet-enabled process, owned by any user, could potentially access or recreate this lock-file. Typically it contains no content but would not be affected even if the content were added. If deleted, it will simply be regenerated by the next Flexnet-enabled process that tries to access it. For that reason, it is required to have full-world access and poses no security risk.   Also, it is important to note that  FNP is having its own bespoke security protocols that do not rely on the host operating-system's native user privileges/file permissions.   ... View more

Problem Statement: During the FNP-11.13.0 release timeline, it was noticed that RHEL  6.4 doesn't have any inbuilt support for 32 bit. So, as conventionally lmadmin was always a 32 bit executable, hence for lmadmin to run, we need to install the 32 bit rpm "redhat-lsb-core-4.0-7.el6.i686". which could lead to issues on the production server since it might conflict with other applications they have. FNP-11.15.1 : 64-bit lmadmin was provided to overcome this issue. Release Note Statement: The FlexNet Publisher Licensing Toolkit supplies a 32-bit lmadmin installer that can be used for 32- and 64-bit platforms. For 64-bit Linux, the toolkit provides a specific 64-bit lmadmin installer.   FNP-11.16.0 Support for 64-bit lmadmin was added for other platforms. Release Note Statement: Previously, FlexNet Publisher 64-bit toolkits contained 32-bit lmadmin binaries which were supported on 64-bit platforms. FlexNet Publisher 64-bit toolkits now include only 64-bit lmadmin binaries. While the 32-bit lmadmin binaries (contained in the relevant 32-bit toolkits or separately available) continue to be supported on 64-bit systems, Flexera recommends using the 64-bit lmadmin binaries on 64-bit systems. (FNP-18383, FNP-17125; Salesforce case 01270591)     ... View more