Cybersecurity of Firmware Updates DISCLAIMER

Total Page:16

File Type:pdf, Size:1020Kb

Cybersecurity of Firmware Updates DISCLAIMER DOT HS 812 807 October 2020 Cybersecurity of Firmware Updates DISCLAIMER This publication is distributed by the U.S. Department of Transportation, National Highway Traffic Safety Administration, in the interest of information exchange. The opinions, findings, and conclusions expressed in this publication are those of the authors and not necessarily those of the Department of Transportation or the National Highway Traffic Safety Administration. The United States Government assumes no liability for its contents or use thereof. If trade or manufacturers’ names are mentioned, it is only because they are considered essential to the object of the publication and should not be construed as an endorsement. The United States Government does not endorse products or manufacturers. Suggested APA Format Citation: Bielawski, R., Gaynier, R., Ma, D., Lauzon, S., & Weimerskirch, A. (2020, October). Cybersecurity of Firmware Updates (Report No. DOT HS 812 807). National Highway Traffic Safety Administration. Technical Report Documentation Page 1. Report No. 2. Government Accession No. 3. Recipient's Catalog No. DOT HS 812 807 4. Title and Subtitle 5. Report Date Cybersecurity of Firmware Updates October 2020 6. Performing Organization Code 7. Authors 8. Performing Organization Report No. Russ Bielawski, Ron Gaynier, Dr. Di Ma, Sam Lauzon, and Dr. André Weimerskirch 9. Performing Organization Name and Address 10. Work Unit No. (TRAIS) Transportation Research Institute 11. Contract or Grant No. University of Michigan (Ann Arbor, MI) DTNH22-15-R-00104 Vehicle University of Michigan-Dearborn Electronics Systems Safety IDIQ Volkswagen Group of America (Herndon, VA) 12. Sponsoring Agency Name and Address 13. Type of Report and Period Covered National Highway Traffic Safety Administration Final Report 1200 New Jersey Avenue, SE 14. Sponsoring Agency Code Washington, DC 20590 15. Supplementary Notes 16. Abstract Over-the-Air (OTA) software and firmware updates are widely considered essential for networked devices. In the automotive industry, OTA firmware updates are anticipated to increase the efficiency and decrease the time in updating the critical firmware in vehicles’ electronic control units (ECUs). This project had these objectives: understand the scope and relevant attributes of firmware updates, understand their vulnerabilities and update solutions, understand mitigation methods for those vulnerabilities, and learn from adjacent industries. The report first presents a literature and technology review of the state-of-the-art of software updates in industries related to automotive, including the commercial aviation, medical, and consumer electronics industries. Next it identifies and assesses software update functionality risks in current and near-term future automobiles. Finally, it reviews mitigation methods to address those risks. In addition, this report describes the SAE AS5553A voluntary standard for the detection of and protection against counterfeit electronic parts in the aerospace industry and how it relates to the automotive industry. 17. Key Words 18. Distribution Statement Over-the-Air, Updates, Firmware, Software, This document is available to the public through ECU (Electronic Control Unit), Automotive, the National Technical Information Service, Network, Theft, Counterfeit, SAE AS5553A www.ntis.gov. 19. Security Classif. (of this report) 20. Security Classif. (of this page) 21. No. of Pages 22. Price Unclassified Unclassified 103 Form DOT F 1700.7 (8-72) Reproduction of completed page authorized i Executive Summary Over-the-Air (OTA) software and firmware updates are widely considered essential for networked devices. In the automotive industry, OTA firmware updates are anticipated to increase the efficiency and decrease the time in updating the critical firmware in vehicles’ electronic control units (ECUs). There is a demand to better understand firmware and software updates, particularly for embedded systems, and how to implement them securely. This work had the following objectives. • Understand the scope and relevant attributes of firmware updates • Understand the vulnerabilities of firmware update solutions • Understand the mitigation methods for those vulnerabilities • Learn from adjacent industries The report first presents a literature and technology review of the-state-of-the-art of software updates in industries related to automotive, including the commercial aviation, medical, and consumer electronics industries. Next it identifies and assesses the risks presented by software update functionality in current and near-term future automobiles. Finally, it gives a review of the mitigation methods to address those risks. In addition, this report describes the SAE AS5553A voluntary standard for the detection of and protection against counterfeit electronic parts in the aerospace industry and how it relates to the automotive industry. Summary of Lessons Learned in Adjacent Industry: Common existing defense mechanisms (e.g., signing, fortification, and intrusion detection) and vulnerabilities are noted in the body of the report as are potential defenses for secure vehicle firmware updates. Risk Assessment Conclusions: In identifying risks at both the vehicle-level and the technological design and implementation level, the researchers have identified the biggest risk with software update mechanisms as malware installation. Mitigation Methods Conclusions: In-field software updates are a necessity in the automotive industry to fix flaws without replacing hardware that is already deployed in the field. The current generation of automobiles primarily uses OTA software updates for telematics and infotainment ECUs only. While software updates are a boon for security, the mechanism, particularly the remote mechanism, creates a new avenue for attackers to exploit. A matrix of specific mitigations versus risks appears in the report (see Table 17). Intellectual Property Theft Risks and Mitigations Conclusions: Intellectual property theft, particularly software theft, can be enabled and made easier with software update mechanisms, particularly OTA mechanisms. In discussions with the original equipment manufacturer (OEM) and tier-1 supplier employees, the majority opinion is that protecting the software binaries is not a priority. The prevailing opinion in the industry is that ii there are too many other ways for an adversary to obtain a software binary to justify the cost of adding encryption to the software update process. Counterfeit and Fraudulent Electronic Parts and Products Conclusions: Fraudulent and counterfeit parts can pose a safety and monetary liability risk. SAE AS5553A is an aerospace standard for the creation of processes for detection, prevention, mitigation, and disposition of suspect, fraudulent, and counterfeit electronic parts. In general, SAE AS5553A should apply to the automotive industry quite readily. It is designed to be flexible and risk- informed. The requirements themselves should be applicable to the automotive industry; however, a more tailored collection of best practices might be reasonable to develop for the automotive sector specifically (not developed within this project). Final Conclusions: Secure in-field software updates are nearly universally considered to be essential for any networked computer system. However, software update functionality creates a new attack surface for attackers to potentially exploit. The installation of malware is one of the biggest risks for software updates. There is no singular, perfect reference model for securing software updates. Every system has different requirements and user experience targets that shape the design enough to require security to be at a minimum analyzed and usually designed with an application-specific approach. While software updates have a large surface from which vulnerabilities can potentially spring, many of the mitigations are known. Software update functionality can be attacked at many different places in the distribution process. And, while technical risks exist, many of the risks are social (such as lost passwords, etc.) in nature. The benefit of reliable, prompt software updates for in-field electronics is significant. iii Table of Contents Executive Summary ........................................................................................................ ii Summary of Lessons Learned in Adjacent Industry: ............................................... ii 1. Introduction ............................................................................................................... 1 2. Background, Definitions, and Literature Review ....................................................... 2 2.1 Background ......................................................................................................... 2 2.2 Software Update: Overview and Definitions ........................................................ 2 2.2.1 Current automotive software update mechanism and best practices. ............ 3 2.3 Step-By-Step: The OTA Software Update Process ............................................... 5 2.3.1 Packaging. .................................................................................................. 6 2.3.2 Transport. ................................................................................................... 6 2.3.3 Reception. ................................................................................................... 6 2.3.4 Installation. ................................................................................................
Recommended publications
  • Enhancing Plug and Play Capabilities in Body Area Network Protocols
    Enhancing Plug and Play Capabilities in Body Area Network Protocols A Major Qualifying Project Report: Submitted to the Faculty Of the WORCESTER POLYTECHNIC INSTITUTE In partial fulfillment of the requirements for the Degree of Bachelor of Science By: ____________________________ Ryan Danas ____________________________ Douglas Lally ____________________________ Nathaniel Miller ____________________________ John Synnott Date: March 10, 2014 Approved: ____________________________ Prof. Krishna Kumar Venkatasubramanian, Advisor ____________________________ Prof. Craig A. Shue, Co-Advisor 1 Abstract This project aimed to create a plug-and-play protocol for Body Area Networks (BANs). This protocol enables communication between a diverse number of devices and a base station, regardless of equipment manufacturer. Previous BANs rely on either proprietary software, or protocols that are specialized to the physical device. This protocol takes a more universal approach, allowing any arbitrary device to participate in a BAN without introducing any significant overhead or running cost to the operation of that BAN. Unlike previous approaches, any existing motes and the base station will not have to be updated. Only new devices being added to the BAN will have to implement the protocol before connecting. Our protocol introduces overhead that reduced the performance and lifetime of the motes used in our BAN. 2 Table of Contents Contents Abstract ........................................................................................................................................................
    [Show full text]
  • Timing Comparison of the Real-Time Operating Systems for Small Microcontrollers
    S S symmetry Article Timing Comparison of the Real-Time Operating Systems for Small Microcontrollers Ioan Ungurean 1,2 1 Faculty of Electrical Engineering and Computer Science; Stefan cel Mare University of Suceava, 720229 Suceava, Romania; [email protected] 2 MANSiD Integrated Center, Stefan cel Mare University, 720229 Suceava, Romania Received: 9 March 2020; Accepted: 1 April 2020; Published: 8 April 2020 Abstract: In automatic systems used in the control and monitoring of industrial processes, fieldbuses with specific real-time requirements are used. Often, the sensors are connected to these fieldbuses through embedded systems, which also have real-time features specific to the industrial environment in which it operates. The embedded operating systems are very important in the design and development of embedded systems. A distinct class of these operating systems is real-time operating systems (RTOSs) that can be used to develop embedded systems, which have hard and/or soft real-time requirements on small microcontrollers (MCUs). RTOSs offer the basic support for developing embedded systems with applicability in a wide range of fields such as data acquisition, internet of things, data compression, pattern recognition, diversity, similarity, symmetry, and so on. The RTOSs provide basic services for multitasking applications with deterministic behavior on MCUs. The services provided by the RTOSs are task management and inter-task synchronization and communication. The selection of the RTOS is very important in the development of the embedded system with real-time requirements and it must be based on the latency in the handling of the critical operations triggered by internal or external events, predictability/determinism in the execution of the RTOS primitives, license costs, and memory footprint.
    [Show full text]
  • Rootfs Made Easy with Buildroot
    Kernel Recipes 2013 Rootfs made easy with Buildroot How kernel developers can finally solve the rootfs problem. Thomas Petazzoni Bootlin [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/1 Thomas Petazzoni I CTO and embedded Linux engineer at Bootlin I Embedded Linux development: kernel and driver development, system integration, boot time and power consumption optimization, consulting, etc. I Embedded Linux training, Linux driver development training and Android system development training, with materials freely available under a Creative Commons license. I We're hiring! I http://bootlin.com I Contributing the kernel support for the new Armada 370 and Armada XP ARM SoCs from Marvell (widely used in NAS devices). I Major contributor to Buildroot, an open-source, simple and fast embedded Linux build system I Living in Toulouse, south west of France - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/1 Doing kernel development is awesome, but... - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/1 A kernel without a root filesystem is kind of useless input: ImExPS/2 Generic Explorer Mouse as /devices/fpga:07/serio1/input/input1 Root-NFS: no NFS server address VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "(null)" or unknown-block(2,0) Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 4/1 Solutions often used by kernel dev I A complete Linux distribution + Readily available - Large (can hardly be used as an initramfs) - Not available for all architectures - Not easy to customize.
    [Show full text]
  • Comparing Embedded Linux Build Systems and Distros
    Comparing embedded Linux build systems and distros Drew Moseley Solutions Architect Mender.io Session overview ● Review of embedded Linux development challenges. ● Define build system and criteria. ● Discuss a few popular options. ● Give me an opportunity to learn about some of the other tools. Goal: Help new embedded Linux developers get started About me Drew Moseley Mender.io ○ 10 years in Embedded Linux/Yocto development. ○ Over-the-air updater for Embedded Linux ○ Longer than that in general Embedded Software. ○ Open source (Apache License, v2) ○ Project Lead and Solutions Architect. ○ Dual A/B rootfs layout (client) [email protected] ○ Remote deployment management (server) https://twitter.com/drewmoseley https://www.linkedin.com/in/drewmoseley/ ○ Under active development https://twitter.com/mender_io Challenges for Embedded Linux Developers Hardware variety Storage Media Software may be maintained in forks Cross development Initial device provisioning Simple Makefiles don't cut it (anymore) Facts: ● These systems are huge ● Dependency Hell is a thing ● Builds take a long time ● Builds take a lot of resources ● Embedded applications require significant customization ● Developers need to modify from defaults Build System Defined _Is_ _Is Not_ ● Mechanism to specify and build ● An IDE ○ Define hardware/BSP ● A Distribution components ● A deployment and provisioning ○ Integrate user-space tool applications; including custom ● An out-of-the-box solution code ● Need reproducibility ● Must support multiple developers ● Allow for parallel
    [Show full text]
  • The Simple Firmware Interface
    The Simple Firmware Interface A. Leonard Brown Intel Open Source Technology Center [email protected] Abstract Moorestown cannot run in ACPI mode because its chipset does not include the required ACPI hardware, The Simple Firmware Interface (SFI) was developed as and it cannot run in legacy mode because the PC- a lightweight method for platform firmware to commu- compatible elements of the system simply do not exist. nicate with the Operating System. Intel’s upcoming “Moorestown” hand-held platform will be deployed using SFI. 3 SFI vs. ACPI Here we summarize the motivation for SFI, summarize the contents of the SFI specification, and detail choices System platforms are either “SFI-platforms” support- made in the Linux kernel implementation. ing SFI firmware tables, or “ACPI-platforms” support- ing ACPI tables. 1 Introduction An Operating System (OS) kernel that supports SFI is an “SFI-OS.” An OS that supports ACPI is an “ACPI- The SFI project home page is http:// OS.” simplefirmware.org. An SFI-platform requires an SFI-OS to boot and run op- This paper starts by briefly summarizing the site’s con- timally. An ACPI-platform requires an ACPI-OS to boot tent, including the content of the SFI specification. Then and run optimally.2 we describe the implementation of SFI on Linux. For more details, readers are encouraged to look over the A single OS binary can boot and run optimally on both specification, to read and participate on sfi-devel@ SFI-platforms and ACPI-platforms. It simply includes simplefirwmare.org, and to review and suggest the capabilities of the SFI-OS and ACPI-OS, making an enhancements to the source code.
    [Show full text]
  • Firmware for IA240 Series (Linux) Release Notes
    Firmware for IA240 Series (Linux) Release Notes Version: v1.10 Build: Build_19010911 Release Date: Jan 09, 2019 Applicable Products IA240 Series Supported Operating Systems Linux Kernel 2.6.x New Features N/A Enhancements • Includes cfi_cmdset_0001.c MTD device driver in the kernel to support both the Micron and MXIC NOR flash memories. Bugs Fixed • The gethostbyname_r() command returns an error. Changes N/A Notes N/A Firmware for IA240 Series (Linux) Release Notes Page 1 of 11 Version: v1.9 Build: Build 18033016 Release Date: Mar 30, 2018 Applicable Products IA240-LX, UC-7112-LX, IA240-T-LX, UC-7112-LX Plus Supported Operating Systems Linux 2.6.x New Features N/A Enhancements • Web server supports both HTTP and HTTPS services. • The SSH host key is generated at first system bootup. • Supports the MXIC NOR flash. Bugs Fixed • The iptables external module link path issue. • Busybox v1.13.3 issues: stty support for 921600, empty option issue (modprobe fixes empty option). • Login timeout leads to system reset. • Timezone configuration change is not applied. Changes N/A Notes N/A Firmware for IA240 Series (Linux) Release Notes Page 2 of 11 Version: v1.8 Build: Build 17060512 Release Date: Jul 07, 2017 Applicable Products IA240-T-LX, IA240-LX, UC-7112-LX, UC-7112-LX Plus Supported Operating Systems Linux 2.6.x New Features N/A Enhancements N/A Bugs Fixed • The vfork issue in the cron daemon. • Links to non-existent libraries /lib/libstdc++.so and /lib/libstdc++.so.5. • The sshd configuration is missing after firmware is upgraded from v1.4 to v1.5.
    [Show full text]
  • TCG Guidance for Secure Update of Software and Firmware on Embedded Systems
    R E TCG Guidance for Secure Update of Software and Firmware on F Embedded Systems E R Version 1.0 Revision 72 E February 10, 2020 N Contact: C [email protected] E Published TCG Guidance for Secure Update of Software and Firmware on Embedded Systems | Version 1.0 | Revision 72 | 2/10/2020 | Published © TCG 2020 TCG Guidance for Secure Update of Software and Firmware on Embedded Systems DISCLAIMERS, NOTICES, AND LICENSE TERMS THIS DOCUMENT IS PROVIDED "AS IS" WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE, OR ANY WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL, DOCUMENT OR SAMPLE. Without limitation, TCG disclaims all liability, including liability for infringement of any proprietary rights, relating to use of information in this document and to the implementation of this document, and TCG disclaims all liability for cost of procurement of substitute goods or services, lost profits, loss of use, loss of data or any incidental, consequential, direct, indirect, or special damages, whether under contract, tort, warranty or otherwise, arising in any way out of use or reliance upon this document or any information herein. This document is copyrighted by Trusted Computing Group (TCG), and no license, express or implied, is granted herein other than as follows: You may not copy or reproduce the document or distribute it to others without written permission from TCG, except that you may freely do so for the purposes of (a) examining or implementing TCG documents or (b) developing, testing, or promoting information technology standards and best practices, so long as you distribute the document with these disclaimers, notices, and license terms.
    [Show full text]
  • Consumer Response to Versioning: How Brands Production Methods Affect Perceptions of Unfairness
    Consumer Response to Versioning: How Brands’ Production Methods Affect Perceptions of Unfairness ANDREW D. GERSHOFF RAN KIVETZ ANAT KEINAN Marketers often extend product lines by offering limited-capability models that are created by removing or degrading features in existing models. This production method, called versioning, has been lauded because of its ability to increase both consumer and firm welfare. According to rational utility models, consumers weigh benefits relative to their costs in evaluating a product. So the production method should not be relevant. Anecdotal evidence suggests otherwise. Six studies show how the production method of versioning may be perceived as unfair and unethical and lead to decreased purchase intentions for the brand. Building on prior work in fairness, the studies show that this effect is driven by violations of norms and the perceived similarity between the inferior, degraded version of a product and the full-featured model offered by the brand. The idea of Apple gratuitously removing fea- been recommended by economists as a production method tures that would have been actually easier to that benefits both firms and consumers (Deneckere and leave in is downright perplexing. McAfee 1996; Hahn 2006; Varian 2000). Firms benefit by reducing design and production costs and by increasing profits The intentional software crippling stance they have taken with the iPod Touch is disturbing through price discrimination when multiple configurations of at best. (Readers’ responses to iPod Touch re- a product are offered. Consumers benefit because versioning view on www.engadget.com) results in lower prices and makes it possible for many to gain access to products that they might otherwise not be able to afford (Shapiro and Varian 1998; Varian 2000).
    [Show full text]
  • Igel Os the Next-Gen Edge Os for Cloud Workspaces
    DATASHEET IGEL OS THE NEXT-GEN EDGE OS FOR CLOUD WORKSPACES IGEL OS is IGEL’s platform-independent Linux-based endpoint operating system designed for simple, smart, and secure access to virtual apps, desktops, and cloud workspaces. IGEL OS turns any compatible x86-64 device (PC, laptop, tablet, or thin client) into a secure IGEL-managed endpoint. It provides outstanding audio, video, interactive graphics, and unified communications. Constantly updated with the latest versions of the most popular codecs and client protocols, users from engineers to designers to gamers can experience rich, immersive multimedia experiences. Hardware Agnostic A highly secure Linux-based operating system for x86-64 machines built with industry-standard components, regardless of manufacturer, platform- independent IGEL OS is designed to become the standard enterprise managed operating system for PCs, laptops, tablets, thin clients, and most every other compatible x86-64 device accessing virtualized apps and cloud workspaces. Cost Effective Extending the life of existing hardware assets, in some cases by many years, eliminates the disruption and cost of investing in new hardware. Future-proofing your infrastructure further reduces unnecessary IT expenditures and ensures easier scalability. Built-in Enterprise-level Security Security-conscious organizations can finally be confident that the core operating system on endpoint devices has not been compromised. Support of two-factor authentication, smart card readers, biometric scanners, and trusted execution are already included. Additionally, as a modular, read- only, highly secure Linux-based operating system, IGEL OS is resistant to manipulation, as well as viruses and other malware. Easy Customization From specialized functionality to corporate branding to screensavers that display corporate messaging, IGEL OS is designed for managed customization and cloud-based environments.
    [Show full text]
  • Chapter 1 Concepts for Developing Portable Firmware
    Jacob Beningo Chapter 1 Concepts for Developing Portable Firmware “A good scientist is a person with original ideas. A good engineer is a per- son who makes a design that works with as few original ideas as possible. “ – Freeman Dyson Why Code Reuse Matters Over the past several decades, embedded systems have steadily in- creased in complexity. The internet’s birth has only accelerated the process as our society has been in a race to connect nearly every device imaginable. Systems that were once simple and stand-alone must now connect through the internet in a secure and fail-safe manner in order to stream critical in- formation up into the cloud. Complexity and features are increasing at an exponential rate with each device generation forcing engineers to reevalu- ate how to successfully develop embedded software within the allotted timeframe and budget. The increased demand for product features along with the need to connect systems to the internet has dramatically increased the amount of 3 Confidential – ©2016 Jacob Beningo, All Rights Reserved, DRAFT A08 Developing Reusable Firmware software that needs to be developed to launch a product. While software complexity and features have been increasing, the time available to devel- op a product has for the most part remained constant with a negligible increase in development time (2 weeks in 5 years) as can be seen in Figure 1. In order to meet project timelines, developers are forced to either pur- chase commercial off-the-shelf (COTS) software that can decrease their development time or they need to reuse as much code as possible from previous projects.
    [Show full text]
  • Diseño E Implementación De Actualizaciones Over the Air (OTA) Para Redes De Sensores Inalámbricas
    Diseño e implementación de actualizaciones Over The Air (OTA) para redes de sensores inalámbricas David García Fernández GRADO EN INGENIERÍA INFORMÁTICA FACULTAD DE INFORMÁTICA UNIVERSIDAD COMPLUTENSE DE MADRID Trabajo Fin de Grado en Ingeniería Informática Curso 2018-2019 Director: Joaquín Recas Resumen en castellano El objeto de este trabajo es el estudio de la viabilidad de las actualizaciones de firmware Over The Air (OTA) utilizando una red LPWAN, en concreto LoRaWAN. Dar soporte para actualizaciones de firmware OTA a día de hoy resulta fundamental y más todavía cuando estos nodos se encuentran en lugares remotos o sitios donde el acceso es muy limitado o peligroso. Tener implementada la funcionalidad para actualizaciones vía OTA permite corregir errores o añadir nuevas funcionalidades a distancia. Uno de los objetivos prioritarios consiste en que la misma actualización pueda llegar a un conjunto de nodos a la vez evitando tener que actualizar los nodos uno por uno, ya que esto supondría el envío de gran cantidad de información duplicada. Para llevar a cabo esta tarea, se ha realizado un estudio en profundidad sobre las características y el funcionamiento de la red LoRaWAN teniendo en cuenta que las redes LPWAN en general dificultan llevar a cabo este tipo de actualizaciones debido a sus conocidas limitaciones en cuanto a tamaño de payload y elevada latencia. Finalmente, este trabajo demuestra la viabilidad de las OTA mediante la aplicación de parches de actualización de firmware a conjuntos de nodos. Palabras clave OTA Over The Air Pycom Lopy STM32L475 LoRa LoRaWAN Bajo consumo Firmware OTA LoRa Server Red de sensores Abstract The aim of this work is the study of the feasibility of firmware updates Over The Air (OTA) using an LPWAN network, specifically LoRaWAN.
    [Show full text]
  • July 20 2020 Linux Documentation
    Linux SAFR® Documentation Linux SAFR® Documentation Documentation Version = 2.016 Publish Date = July 20, 2020 Copyright © 2020 RealNetworks, Inc. All rights reserved. SAFR® is a trademark of RealNetworks, Inc. Patents pending. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. 1 Contents 1 What’s New 5 2 SAFR Overview 6 3 SAFR System Requirements 9 4 Licensing 15 5 Getting Started with SAFR Platform on Linux 17 6 Camera Best Practices 20 7 Manage People in the Person Directory 28 8 Importing and Registering People 29 9 Image Quality Metrics Guidance 31 10 Actions Overview 35 11 Actions Relay Event Service (ARES) 37 12 SAFRActions.config 38 13 Large Scale Deployments 49 14 Database Redundancy 53 15 Object Storage Service Redundancy (CVOS) 58 16 SSL Certificate Installation 63 17 SAFR Support Tools and Scripts 67 18 SAFR Server Backup and Restore 69 19 SAFR Platform Command Line Install
    [Show full text]