red hat

ARMONK, N.Y. and RALEIGH, N.C. Red Hat and IBM officials entered into a definitive agreement, under which IBM will acquire all of the issued and outstanding common shares of Red Hat for $190.00 per share in cash, representing a total enterprise value of approximately $34 billion.

Part 1 of this blog on blockchain for embedded systems (see July/August 2018 issue) explored one way of using blockchain technology for sensor data, especially where the integrity and provenance of the data must be verified. Blockchain is also useful for the other part of embedded systems: command and control. In many cases, the “control” [...]

The recent KRACK (Key Reinstallation Attacks) attack on the Wi-Fi WPA2 security protocols (CVE-2017-13077 through CVE-2017-13088) highlights the requirement to actively maintain and update embedded systems, especially long-life systems deployed in hostile environments. KRACK is interesting because it is a flaw in a mature, widely used security protocol. KRACK exploits a flaw in the four-way [...]

Where did the software on your embedded system come from? Can you prove it? Can you safely update systems in the field? Cryptography provides the tools for verifying the integrity and provenance of software and data. There is a process as to how users can verify the source of software, if it was tampered with in transit, and if it was modified after installation.

Quis custodiet ipsos custodes? – “who will guard the guardians?” – is a question as old as the Roman Empire. This question, with its underlying bearing on trust in general, is still relevant today. And it is directly applicable to computer systems.

WASHINGTON. The Department of the Navy has signed a five-year blanket purchase agreement (BPA) with DLT Solutions for the government IT contractor to provide the Navy and Marine Corps with Red Hat software and services. The $133.4 million agreement includes a one-year base ordering period with four one-year optional ordering periods, to be in force through December 2021.

Our most popular blogs on Mil-Embedded.com from 2016 covered by guest bloggers from Milsource, VITA, Red Hat, Abaco Systems, and by our editorial staff on subjects such as potential wars with Iran, with China, and with Russia as well as military Internet of Things (IoT), Ethernet networks, Department of Defense (DoD) budget requests, Wind River/Intel integration and more.

THE OPEN SOURCE WAY BLOG. Secure, real-time communication technology is an essential requirement for military Internet of Things (IoT) solutions. There are numerous protocols for communication between IoT devices, and between the devices and back-end systems. Messaging solutions should be able to to support these various protocols across heterogeneous, physically distributed systems while enabling the security and integrity of information flows. They should also be highly scalable, able to accommodate potentially hundreds of millions of devices. And since delay or loss of data is not an option, they should feature strict availability and reliability requirements.

Interactions with the physical world can be tricky – even dangerous! Let's say you have an Internet of Things (IoT) application controlling a chemical process - perhaps exotic chemicals for an aerospace mission. The IoT devices include sensors for temperature, pressure, flow rate, and tank levels and actuators for pumps, heaters and valves – including a dump valve ready to vent high pressure. In this situation it's likely you would have analysis and reporting software running, be receiving sensor readings, and have control of the various pumps, heaters and valves. With IoT, computing can be pushed to the edge via gateways and controllers often running sophisticated applications.

OPEN SOURCE WAY BLOG: In many ways, embedded systems are the progenitor of the Internet of Things (IoT) – and now IoT is changing key aspects of how we design and build military embedded systems. In fact, the new model for embedded systems within IoT might best be described as design, build, maintain, update, extend, and evolve.