ChangelogDownloads
HomeGuidesChangelog
ChangelogDownloadsSupportMulti-service IoT Edge GatewaysEUROTECH
SupportMulti-service IoT Edge GatewaysEUROTECH
Back to All

ESF 7.0.1 - Release

over 2 years ago by Cristiano De Alti

Eurotech Everyware Software Framework ESF 7.0.1 (Eclipse Kura - 5.0.1) - December 2021

Description:
This service release of ESF fixes the Log4J vulnerabilities CVE-2021-44228, CVE-2021-45046 and CVE-2021-45105
by updating the Log4J dependencies to 2.17.0. Slf4J has been updated as well to 1.7.32.
Upgrade path available from ESF 6.2.0, 6.2.1 and 7.0.0 to 7.0.1.

New and Noteworthy:

  • Target Platform Updates
    • log4j.version=2.17.0
    • slf4j.api.version=1.7.32

Breaking Changes:

  • ESF 7.0.1 is compatible with ESF 7.0.0.
  • Breaking changes from previous ESF versions still apply

Target Environments:

  • ESF supports the following Devices and Everyware Linux (EL) versions:
    • ReliaGATE 10-12;
      • EL 27.0.1
      • EL 27.1.0
    • ReliaGATE 10-20;
      • EL 27.0.0
    • ReliaGATE 20-25;
      • EL 23.0.0
    • BoltGATE 20-25;
      • EL 21.4.0
    • ReliaGATE 10-14;
      • EL 27.0.3
      • EL 27.1.0
    • BoltGATE 20-31;
      • EL 20.1.0
      • EL 30.0.0
    • DynaGATE 20-30;
      • EL 20.1.0
      • EL 30.0.0
    • BoltGATE 10-12;
      • EL 27.1.0
    • Raspberry Pi 2/3/4 with Raspberry Pi OS Buster (32bits) and Raspberry Pi OS Bullseye (32bits);
  • ESF is also available as a pre-built Docker container based on:
    • Centos 8 x86_64 and aarch64
    • ubi-minimal latest x86_64 and aarch64

Known Issues (ESF):

  • After an upgrade from ESF 6.2.0 when the Command Service user is configured with limited privileges,
    the commands executed from the Command Service may return with the following error: "su: must be run from a terminal"
  • Release only validated against the HE910 version of the ReliaCELL
  • ReliaCELL Dual SIM option not supported
  • Hardware watchdog: not implemented on all platforms
  • On Reliagate 10-20 the watchdog cannot be disabled ("watchdog no-way-out")
  • During ESF shutdown, an error stacktrace can be shown in the log from the Jetty server. This does not affect the success of the procedure
  • #872: Provisioning Service: provisioned flag not reset if provisioning is re-enabled
  • #786: Connection Failed on Snapshot Rollback
  • #624: [Serial] RXTX fails to set 38400 bauds
  • #509: [ESF 5.2.0 QA] Check message verification failed with diagnostics ping
  • #423: [Terminal Services] socat resets the tty configuration on TCP client disconnect
  • #395: ESF on RG 20-25 reports wwan0 interface with LE910 V1 modem.
  • #358: [20-25] jdk.dio.properties digital in/out gpio numbers are incorrect
  • #81: [Security - Message Signing] ESF verifies the signature of every control message
  • #64: Message signature propagated to application bundles
  • Trying to connect to a WI-FI network with a special character in the SSID results in an error.

Known Issues (Kura):

  • The intel-up2-centos-7, intel-up2-ubuntu-18 and rock960-ubuntu-16 don't support the Unprivileged Command Service (see #3598)
  • An update to the sslmanagerservice where the pid of the keystoreservice is updated can lead to an error in the following reconnection.
    The issue impact is limited, if the dataservice reconnect option is enabled.
  • The implementation of the CryptoService performs encryption using a
    password that is hardcoded and published.
  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • BLE also tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection will encounter a failure.
  • WiFi on Raspberry Pi 2 has only been tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • The rock-960-ubuntu-nn does not support chrony features.
  • The rock-960-ubuntu-nn does not support writings to the hardware clock.
  • The rock-960-ubuntu-nn does not support the download of the journald logs.
  • #3176: Modem interface number management
  • #3005: Kura Gets Stuck in Loading View if Services Clicked Too Fast
  • #2843: Access Banner Content All in One Line
  • #2747: No Spacing Between "Wire Components" and Error in Wire Graph
  • #2728: WireGraph Component Description Windows Too Wide
  • #2725: Different Pop-up Windows for Warnings
  • #2702: Error Message For Long Item Names Not Displayed Properly
  • #2696: Component Name Inteferes With Wire Graph Border
  • #2695: Component Names in Wires Not Limited
  • #2410: Deployment handler and URLs with many query parameters
  • #2038: [Kura 3.2.0 QA] Package uninstallation log
  • #1993: Search Domains Are Not Supported
  • #1663: Authentication Issue with Deploy V2
  • #1572: serial modbus has errors on some hardware
  • #1529: OSGI console is not redirected to Eclipse IDE with Kura 3.0
  • #1201: Wifi password incorrectly read from snapshot in Access Point mode
  • #1161: Incorrectly configuring a component can be irreversable.
  • #1128: [Kura 3.0.0 M1 QA] Unable to delete manually added CamelFactory services
  • #1016: ConfigurationServiceImpl creates duplicate instances
  • #797: Design of ServiceUtil is broken
  • #771: Web UI fails with INTERNAL_ERROR when WireHelperService is not registered
  • #654: Clean up static initialization around "modem" functionality
  • #645: Clean up internal dependencies in Kura
  • #522: [Net] Modem monitor should monitor interfaces, not modems
  • #486: Build environment broken on Windows
  • #406: Replace System.get* with calls to SystemService.getProperties
  • #348: WpaSupplicantConfigReader.getWifiClientConfig() should support cases where key_mgmt scheme is not set
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #297: [Status led] What connection instance controls the status led?
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation

Changelog (ESF):

  • 678750971 - Fix gpsd.socket failure disabling ipv6 configuration in its service. (#1547) (salvatore-coppola)
  • a6248f297 - Start ESF7 log4j and slf4j versions during upgrade (#1542) (nicolatimeus)
  • 53ed09fb0 - Disabled rsyslog and ModemManager during installation (#1536) (Pierantonio Merlino)
  • a65ead18c - Updated versions for 7.0.1 release. (#1533) (Matteo Maiero)
  • b5fbbc04f - Updated upgrader to support 7.0.0 to 7.0.1 (#1530) (nicolatimeus)
  • cee176bbf - Exported JVM bin to PATH (#1527) (#1528) (github-actions[bot])
  • c08f88940 - Updated reference to newer security managers (#1531) (Matteo Maiero)
  • e9a8ad8ad - Preparing for 7.0.1 development (#1529) (Matteo Maiero)

Changelog (Kura):

  • 6a27f148f6 - [Backport release-5.0.0] Updated log4j to 2.17.0 (Maiero)
  • 0162a25372 - Preparing for 5.0.1 release (#3716) (Matteo Maiero)
  • f4347753d3 - Updated log4j2 to 2.16.0 (#3713) (Matteo Maiero)
  • 805aad63d4 - Updating log4j version to 2.15.0. (Maiero)
  • 33e5e73170 - Updating Kura 5 for next development round (Maiero)