#Masteropc universal modbus server 64 Bit#
#Masteropc universal modbus server serial#
#Masteropc universal modbus server update#

Improved: SourceTimestamp of values in the OPC UA address space now reflects the time when the value was retrieved from the Modbus device Improved: Improved support for features of the OPC UA MonitoredItem Service Set and Read Service in accessing Modbus data Improved: Major improvements in performance of accessing data from Modbus devices New: Device-wide setting for the default byte transfer order of new variables (swap bytes and swap words) New: New right-click menu commands for performing actions on Modbus devices, tables and variables in the Configuration Mode UI New: Option to use BIT data type for Input and Holding Registers.

#Masteropc universal modbus server 64 Bit#

New data types include 8 bit and 64 bit integers (SINT, USINT, LINT, ULINT), 64 bit floating-point decimal (LREAL) and character strings encoded in ISO 8859-1 and UTF-16 (CHAR, WCHAR) New: Extended support for different IEC 61131-3 data types. New: Possibility to import and export device-specific variable configurations from/to a CSV file through the Configuration Mode UI

#Masteropc universal modbus server serial#

New: Support for Modbus serial protocol (ASCII and RTU) If for some reasons it won’t work on your distro, let us know, but you can chmod the exec bits as a workaround. zip option uncompressed retaining exec bits on start scripts on Linux, which was the only reason keeping tar.gz. Not recommended for public networks.Ĭhanged: Removed portable tar.gz option, based on our latest tests the.

They are considered to be non-secure by OPC UA 1.04, but can be enabled in the Endpoints view if needed. sh script (like our Browser/SimulationServer/Monitor have).Ĭhanged: MessageSecurityMode None is no longer enabled by default (unless migrated from old configuration file).Ĭhanged: SecurityPolicies Basic128Rsa15 and Basic256 are no longer enabled by default (unless migrated from old configuration file). New: Added support for reverse connections.įixed/Changed: Transport protocol opc.https disabled by default.įixed: UI could freeze if 'Open Certificate in OS viewer' option was used on Linux.įixed: Application’s own Certificates can now be opened in the Certificates view.įixed: Selecting serial port based Modbus Device did freeze the application if run in portable mode.Ĭhanged: Linux installer is now a. New: Docker Image as distribution option. Uses Prosys OPC UA SDK for Java version 4.5.2: NOTE! for the 'portable install' and docker distributions, there could be more impact if the user running the application differs from the one unzipping the distribution and/or if that user has higher privileges on the system.

#Masteropc universal modbus server update#

Thus, this CVE in practice has no impact, but we still do recommend to update just in case. Thus the created configuration files at the first startup are admin-owned, thus there is nothing to escalate to, the attacker could just do already everything they could do via Modbus Server in a more complicated way. Typically this kind of vulnerability could be used for a privilege escalation attack, but Modbus Server for better or worse requires admin priviledges to run. In general our applications do not expect a hostile (local) environment.

So the filesystem would have to be compromised for this to happen. For the CVE-2021-44832, per apache’s page: '(previous versions) are vulnerable to a remote code execution (RCE) attack where an attacker with permission to modify the logging configuration file'.