Welcome traders, now the Tick Mail Charter at New Patrick Monthly, want to draw your attention to the Aussie Dollar on the daily timeframe and we're still tracking this five-way sequence, one, two, three, four, and we're looking now for a fifth-way extension to develop, to ultimately bring us down to test monthly range support down to 69.97, we've got these prior lows over here and we've got the yearly pivot just below at 69.82, so what I've been looking for now is a bearish close today and either at or below current levels and then I'd be looking to enter short positions on the close this evening, looking for that extension down to getting to just below this 70 figure. As always, traders, plan the trade, trade the plan and most importantly manage your risk. Until next time, thanks very much.


Good morning folks Steve Rhodes coming to you live from the shores of sunny Delray Beach, Florida. This is your 11 a.m. update and we've got a mixed bag out there the mix goes like this. It's the Nasdaq and the semis that are trading lower they're pulling the markets lower out there. That's not really what you want to see in bullish market conditions but you have the Dow trading up 161 points about a half percent two tenths for the S&P or nine points six tenths for the Russell 2000 that's an 11 point move gold is trading up 12 bucks that's straight out of 1965 silver's up 32 cents one and four tenth percent moved there lights recruiters up 13 pennies natural gas down 10 cents and a 30 year treasury printed out at 1 18 22 that's up a half a point. Let's go take a look at what all that means by looking at that nine panel market update chart the upper left hand corner we're going to see the ESP and what do we have we got a good old fashioned consolidation and this really the consolidation with inside the weekly profiles that's between the levels of forty four twenty four to the bottom and actually only have the center of the weekly profile that's the resistance level that's up at the forty five ninety eight area now yesterday we had that spot follow till next test and reject that fifty day exponents moving average was doing that when we're on the air as really as we're going off the air out there we can see that price reject that level markets went ahead and took back some of those losses yesterday the NQ it is trading has support perhaps it has support I should say really at the bottom of its weekly profile fifteen one ninety one price remains below the bottom of its daily profile this could be for consecutive sessions below that it really is suggesting lower price the US dollar index is pulling back it has formed a new profile is really new to new profile levels we use the one here in the black background chart looks like the US dollar index wants to make a test of the one oh four thirty five level one over thirty five is the bottom of that daily profile close below that would likely indicate to you and I a change in trend Goldilocks right now to eleven oh one is taking on resistance that's the top of its daily profile in nineteen fifty four sixty we're trading out in nineteen sixty five a close of nineteen fifty four sixty should get us up towards the most recent swing point and that would be up at the nineteen eighty twenty level close of that could trigger an A to be equal seeding the upside now in the case of silver it only has two profile areas both the center and bottom are the same level twenty three thirty two that should be strong support we take a good resistance that's a twenty three seventy four trade above right now we're trading out at twenty three eighty a close above twenty three seventy four would suggest a further move higher a further move higher should take us up in that descending trend line of the twenty five area late sweet crude it's got a new profile it's attempting to form as well resistance here up at ninety one seventeen a natural gas just a consolidation as is with the thirty year treasury bond with inside their respective profiles folks they do for the traders and show but if you have to start your Wednesday please have a wonderful one thanks for joining us we look forward to speaking with you again soon take care now


Hi everyone, my name is Abzal Hassan from Foundry Software Team of Samsung Semiconductor India Research. Me and my colleague Priyadikshit present today on this topic, enhancing system security by integrating Zafir Bookloader and MCUBoot. So in today's agenda, we present the importance of system security in Zafir Bookloader, system architecture of Zafir, integration process of Zafir Bookloader and MCUBoot, secure boot process of proposed bootloader, on-ware update process of proposed bootloader, rollback protection and bootloader recovery, threat model, limitations and challenges along with the future development. In today's digital landscape, system security is of paramount importance. To bolster the protection of embedded systems, the integration of Zafir Bookloader and MCUBoot emerges as a promising solution. Zafir Bookloader and open source scalable and secure bootloader provide a robust foundation for system bootloader. It incorporates advanced features such as secure boot, digital signatures, verification and measured boot ensuring the integrity and authenticity of critical components during the startup process. By integrating Zafir Bookloader with MCUBoot, a highly flexible and customizable firmware update framework, system security reaches new heights. MCUBoot offers secure firmware update utilizing cryptographic mechanisms and authentication protocol to safeguard against unauthorized modification. This integration empowers embedded system with a comprehensive security framework. Zafir Bookloader establishes a trusted chain of attribution verifying the authenticity of each component through digital signatures. Furthermore, MCUBoot ensures secure firmware update mitigating the risk of vulnerability and enhancing resilience against evolving threat. Together the Zafir Bookloader and MCUBoot amalgamate the power of secure boot and robust firmware update, fortifying system security and protecting against malicious attacks. This integration is a significant strive towards safeguarding embedded systems in diverse domains such as IoT, industrial automation and automotive where security is of paramount concern. Enhancer systems security by embracing the integration of Zafir Bookloader and MCUBoot are ensuring a resilient foundation for secure and trusted operations. Next we will discuss about Zafir Actors system architecture. Now in this slide we will discuss about Zafir system architecture along with its security components. A real-time operating system Zafir stands out as a robust and versatile platform for embedded applications. Its system architecture not only enables real-time responsiveness but also prioritizes security to protect against emerging threats. At the core of Zafir's architecture is a modular microkernel design. The lightweight approach allows for efficient resource utilization enabling the real-time operating system to run on a wide range of devices from resource-consuming microcontrollers to more powerful processors. The modularity also promotes code visibility, flexibility and flight-facilitating customization to suit specific application requirements. The Zafir real-time operating system incorporates several security features to fortify system resilience. It embraces the principle of defense in depth by implementing security mechanisms at multiple levels. This includes secure boot, encrypted communication, access control and memory protection. Secure boot ensures the integrity and authenticity of system firmware and software components during the boot process. It employs digital signatures to verify the authenticity of these components regarding against tampering and unauthorized modification. To protect data and transit, the Zafir real-time operating system offers various communication protocols with built-in encryption capabilities such as transport layer security. This ensures the confidentiality and integrity of sensitive information exchange between devices or network. Access control mechanism improves permissions and restrictions limiting the actions and privileges of different software components and users. By employing rule-based access control and other access management strategies, the Zafir real-time operating system mitigates the risk of unauthorized access and potential bridges. Memory protection mechanisms such as memory segmentation and other isolation techniques prevent unauthorized access or corruption of critical data and code, improving the system security portion. The system architecture of Zafir R2S combines scalability, flexibility and a robust security frame. Its modular design promotes resource efficiency and customization, while security features like secure boot, encrypted communication access control and memory protection mitigate risk and safeguard against threats. Embracing the Zafir real-time operating system empowers embedded system with a reliable foundation ensuring both real-time performance and robust security in a rapidly evolving digital landscape. In this slide, we'll discuss about the importance of system security in embedded world. In today's interconnected world, embedded systems play a vital role in powering critical infrastructure such as industrial control systems, IoT devices and automotive systems. With this increasing reliance, ensuring robust system security becomes paramount. Embedded systems control essential operation, monitor sensitive data and manage critical functions. Without proper security measures, the system is susceptible to cyber threats including data bridges, unauthorized access and malicious attacks. The consequences can be devastating, leading to operational disruptions, financial losses and compromise of user safety. System security in embedded systems is crucial for several reasons. Firstly, it safeguards the confidentiality and integrity of sensitive data. Industries handling financial transactions, personal information or intellectual property must prevent and raise access and protect against data bridges to maintain trust and regularity compliance. Secondly, system security ensures the availability and reliability of embedded systems. Industries relying on real-time operations such as manufacturing or healthcare cannot afford system failures or disruption. By implementing robust security measures, these systems remain resilient against attacks and maintain uninterrupted functionality. Furthermore, embedded systems operate within interconnecting environments, making them potential entry points for broader network attacks. Standards system security helps prevent compromised embedded devices from being used as gateways to infiltrate larger networks, thus protecting the integrity of entire ecosystem. Additionally, ensuring system security in embedded devices enhances user trust and confidence and users expect these devices to be secure. Whether it is a smart home device, a medical implant or a vehicle, robust security measures inspire confidence and reduce concerns regarding privacy, safety and the potential misuse of personal information. System security in embedded systems is essential for regularity compliance. Various industries must adhere to strict standards and regulation concerning data protection and system security. Maintaining these requirements not only avoids legal consequences but also demonstrates a commitment to maintaining the highest standards of security and reliability. Security in embedded systems is of utmost importance to protect critical infrastructure, sensitive data and user trust. By implementing robust security measures such as eco-boot, encryption, access control and continuous monitoring, embedded systems can withstand evolving cyber threats, ensuring the integrity, availability and reliability of essential operations in today's interconnected world. In this slide we will discuss about concept of integrating the Fireboot Loader and MCO. Integrating the Fireboot Loader with MCO would presence a powerful concept enhance firmware update security. By combining the strengths of these two components the system gains a comprehensive solution for secure and reliable firmware updates. As a Fireboot Loader known for its scalability and security features, establishes a trusted boot process ensuring the integrity of critical components during startup. It incorporates secure boot mechanism, digital signature verification and major boot establishing a chain of trust and safeguarding against sampling and unauthorized modification. On the other hand, MCO boot provides a flexible and customizing framework for secure firmware updates. It utilizes cryptographic techniques, authentication protocols and secure communication channels to ensure that only authorized and verified firmware updates are applied. The integration of the Fireboot Loader and MCO boot combines the benefit of secure boot It allows for seamless secure and efficient updates of firmware on embedded devices mitigating the risk of vulnerability and ensuring system resonance against evolving threats. This concept embedded system can confidently embrace secure firmware updates protecting against unauthorized modification, maintaining system integrity and delivering enhanced functionality to use. Integrating the Fireboot Loader and MCO boot presents a compelling concept that enhances firmware updates security. It combines the trusted boot process of the Fireboot Loader with the secure update capabilities of MCO boot providing a powerful solution for maintaining the integrity and security of embedded systems to reliable and secure firmware updates. In the next sections, we will discuss about the Fireboot Loader and MCO boot individually. In this slide, we will discuss about some of the Fireboot Loader features. It is famous for its lightweight design. It has a secure booting feature. It has firmware update support and cryptographic verification. Flexible configuration, error handling and the capability compatibility with the Fireart players and its integration. In this slide, we will discuss about the Fireboot Loader boot flow. As we know, the Fireboot Loader is responsible for initializing the system and loading the main application into memory on the Firebase devices. So, we can discuss about the high-level overview of the Fireboot Loader boot flow. So, on the Power On reset, when the device is Power On or reset the processor begin executing code from a predefined memory address, typically the bootloader's entry point. Then we will move on to the bootloader initialization. The bootloader code initializes essential hardware components such as clocks, memory and peripherals required for the devices operation. Then bootloader configuration. The bootloader may have parameters such as boot till a boot source selection or communication interface. It reads this communication option either from a dedicated configuration area in non-volatile memory, for example, dash or through other things to determine the boot period. Then we have the boot source selection. The bootloader determines the source from which to load the main application. The source can vary based on the system design and configuration, but common options include external flash memory, internal flash memory or an external storage device like an SD card or a network interface. Then we move on to the loading of the application. The bootloader reads the main application image from the selected boot. It typically verifies the integrity and authenticity of the image using pictographic signature or checksums to ensure that the application has been tampered with or any overwritten thing is happening. Optional authentication is also possible if the main application image is signed with the digital signature, the bootloader may perform additional authentication steps. This involves verification of the signature against a trusted key or to certify it to ensure that the application is authentic and hasn't been modified. Next, we have the main application execution. Once the bootloader has successfully loaded and authenticated the main application, it transfers control to the application in trip 1. The main application then begins its execution taking over the device's functionality. It has bootloader update as an option. In some cases, the bootloader itself may be updatable. If an updated bootloader is available, the main application can initiate the update process by requesting the new bootloader image or updating a bootloader in memory. It's important to note that the boot flow of this fire bootloader can vary depending upon the configuration and customization implemented by the device manufacturer or system developer. These steps outlined above provide a general understanding of the typical boot flow for the fire-based system. Moving on to the MCU boot, we'll discuss in this slide some of the features of the MCU boot. It has secure boot, firmware update, cryptographic verification, better than the Fire Bootloader, flexible configuration, error handling and recovery, time for resistance and compatibility, and integration possibilities with other microprocessor, microcontrollers and the RTOs, like the Zafire RTOs. I will discuss about the MCU boot. The MCU boot engine is an open source bootloader specifically designed for microcontrollers and is often used in the fire-based systems. The high-level overview boot flow of the MCU boot is from the power-on or reset. When the MCU is power-on or reset, the MCU bootloaders start executing a predefined memory address, typically the bootloaders, in three points. Then it jumps through the bootloader initialization. MCU boot initializes the essential hardware components such as clock, memory, peripherals required for the bootloader's operation. Then it scores for bootloader source selection. MCU boot determines the source from which to load the main application. This can be based on predefined configuration options or runtime checks depending upon how the system is configured. Then it scores for the primary slot execution. MCU boot initially moves the primary application slot, assuming its contents are valid and authenticated application image. Then it scores for the image validation. MCU boot validates the image in the primary application slot using cryptographic signatures or checksum. It verifies the integrity and authenticity of the image to ensure it hasn't been tampered with. Then it's based on the result of the image validation MCU boot determines the boot execution. Every primary application image is valid and authenticated. MCU boot transfers control to the primary applications in three points and the application begins executed. If the application image is invalid or not present, MCU boot falls back to the secondary application slot. The secondary slot execution will discuss about the secondary slot execution. If the primary slot is invalid or doesn't contain a valid application, MCU boots the secondary application slot. Image swap is an optional feature. If the secondary slot contains a valid and authenticated application image, MCU boot can perform an image swap to make the secondary slot the new primary slot. This allows seamless and atomic updates of the application. If there is an optional image update feature as well, MCU boot provides functionality to update the application image in either the primary or secondary slot. The update process can be initiated by the main application or through external means such as over-the-air update mechanism. So in this case, it's important to note that the MCU boot flow is highly configurable and customizable, allowing for various strategies in terms of image storage, security features, and update mechanism. The boot flow described just provides a general understanding of the typical boot flow in the MCU boot. But actual implementation detail may vary depending upon the specific MCU or platform and the configuration chosen for the MCU boot flow. So in this slide, we'll discuss about the integration process of the Fire Boot Floater and MCU. Integrating this Fire Boot Floater with MCU boot involves configuring and building both components to work together seamlessly. So as a step-by-step guide to help you with the integration process, first we have to set up the development environment, install the required development tools including Fire and MCU boot. Set up the necessary build systems such as Themeek to compile the bootloader and the Fire application. Next step is to configure the Fire Boot Floater. Identify the specific Fire Boot Floater configuration you want to use, such as the one provided by the Fire's samples bootloader directory. Customize the bootloader configuration according to your specific requirements. This may include selecting the appropriate boot source, defining slot sizes, enabling future boot features, configuring communication interfaces and more. Integrate MCU boot with the Fire Boot. Show that MCU boot is installed and available in your development environment. Configure MCU boot integration into the Fire Boot loader configuration file. This typically involves defining the MCU boot every department. Specifying the required MCU boot APIs and configuring the slot file. Next step is the integration process of the Fire Boot loader and MCU boot is building the bootloader and the Fire application. Build is a Fire Boot loader using the Fire Boot system. This will compile the bootloader code and generate the bootloader image file. Build is a Fire application that you want to boot using the bootloader, ensuring that the application will be built with the necessary MCU boot integration and may require configuration options. Flash the bootloader and the Fire application. Flash the compile bootloader image to the appropriate memory location on your target. The flashing process may vary depending upon your specific hardware and tools. Flash is a Fire application image ensuring that it is placed in the appropriate memory location. According to this load layout, define the boot loader. Verify the integration power on or reset the device to observe the boot process and ensure that the bootloader execute successfully. Verify it is a Fire application image and transfers control to the application input. Next step and the last step is to test and hydrate where you get the integrated the Fire bootloader and MCU boot as functioning as expected. Perform tests to verify secure boot functionality. Image updates and other desired features. Hydrate on the integration and configuration as needed. These are your specific requirements and feedback on tests. You can see some code snippet in the slides as said how to proceed with the integration process. We have to develop a boot support packet for our boot as per our own configuration. In this slide, we can see a basic bootloader flow chart. So as we know as the boot loader initiative the initialization of hardware starts and it's load user config data from bootloader customizing area then configure clocks, peripherals and memory. If any update is required then the boot pin got asserted and it can go for the firmware update. Otherwise, it will check if the user app is valid or not to check some or through some cryptography verification and then it can go for direct boot or through the timeout. If we call as the boot time. So in this slide we will discuss about the benefits of integrating the Fire bootloader and MCU boot. Integrating the Fire bootloader with MCU boot brings single benefits to the development and deployment of embedded system. There are some advantages of combining these two options. First advantage is secure boot. MCU boot provides sober security features such as proof-to-graphic image authentication and secure boot capabilities. By integrating MCU boot with the Fire bootloader you can enhance the security of the system by ensuring that only trusted and authenticated firmware images are recreated. Next advantage is dual image slots. MCU boot's dual image slot strategy allows for seamless firmware updates and reliable fallback mechanism. By integrating this feature into the Fire bootloader you gain the ability to perform safe and atomic image swap ensuring that your device can always boot into a known boot firmware image. Next advantage is efficient image updates. MCU boot supports in-place image updates allowing you to update the firmware without requiring a full chip erase. This results in faster and more efficient updates preserving critical data and configuration settings during the update process. Next advantage is over-the-air updates. By integrating MCU boot with the Fire bootloader you can leverage the over-the-air update mechanism to remotely update and manage firmware on your device. This enables convenient and efficient firmware updates over wireless networks reducing maintenance costs and improving device management. Flexibility and portability improve by this integration and MCU boot's hardware extraction layer allows for easy porting of different microcontroller platforms. While the Fire's smaller and configurable architecture provides flexibility to adapt to various use cases. Next advantage is open source and community support. Boots of Fire and MCU boot are open source projects with active communities. Integrating these components allow you to leverage the collective knowledge, expertise and support from the developer community ensuring ongoing maintenance, bug fixes and security updates. Another advantage of this integration is extensibility and customization. Integrating the Fire bootloader with MCU boot provides a foundation for extensibility and customization. You can build upon the bootloader stack to add custom features and security mechanisms to your requirements and integrate additional functionality based on your application's needs. By integrating this Fire bootloader with MCU boot you can benefit from a powerful and secure bootloader solution with enhanced update capabilities improve security and the flexibility to adapt to different hardware platforms and development scenarios. Now I'll pass you over to my colleague Priya Dixit to take you further in this session. Thanks Abzal. Hello everyone. My name is Priya Dixit and I work as a staff engineer at Samsung Semiconductor India Research. I will continue from secure booting in Zifier RTOS. We will first understand PKI that is a public key infrastructure and digital signatures to understand secure boot and to get the idea about secure booting. Public key infrastructure is used to ensure the authenticity and the integrity of systems boot sequence using cryptographic keys. These cryptographic keys are used in algorithm to encrypt and decrypt data or for signing and verifying which can be a symmetric or symmetric. Here in symmetric exceptions we use a single key to encrypt and decrypt data while in asymmetric encryption we use two different keys to encrypt and decrypt. For implementing secure boot we preferably use asymmetric cryptography that has two types of keys private key and public key as the key management is easy in this case. So here the private key is kept secret and is securely held by the trusted system whereas the public key is derived from the private key that is distributed. Now let's talk about digital signature. So a digital signature is a mechanism that is used to verify the authenticity of software using cryptographic keys. For secure boot the digital signature is created by using a private key that is responsible for signing the software and the digital signature and then verified using the corresponding public key which is typically embedded into the system's firmware or is securely stored in a hardware component such as TPM. So secure boot is a mechanism where we verify the digital signature of bootloader and OS before executing. So when the part of the system is signed using a private key the corresponding public key is used to verify the signature and if this verification process succeeds this will ensure that the content of the file has not been modified since it was signed. This way using cryptographic keys and digital signature we establish a chain of trust ensuring like the boot is secure also this ensures that the hardware is trusted and authorized with software components which help in protecting against unauthorized modifications and forms of foundation for establishing a secure environment. In the case of firmware that initiate the boot process using private key we sign the cryptographic hash of the firmware and bootloader that will generate digital signatures. So as the boot progresses the firmware verifies the digital signature of the component it loads in the file that is stored in the firmware. The public keys are pre-installed in the system if the digital signatures are valid then the boot process will continue but if the digital signature is not valid the firmware holds the boot process signaling that something is fishy. Then the verified bootloader will initialize the operating system the digital signature of OS is verified and if it is secure then it is allowed to proceed otherwise the boot process is halted. So when secure boot is enabled the firmware will verify the digital signature of each of the executable file from the firmware to bootloader then to operating system before allowing them to run and this will guarantee that the executables are from trusted source and has not been modified. Here we see a term have which means high assurance boot library and this is a secure boot library for IMX processors that are designed to protect the system against various forms of attacks. This can be done by establishing a chain of trust from initial power on of the system to the operating system execution so that each component loaded during the boot process is cryptographically signed and has not been modified. This is an example of the system which ensures that the system start up securely and only runs authorized and verified software components providing a foundation of trust. In secure boot the first stage bootloader is programmed into non writable storage location on the device. The first stage bootloader then calculate the hash value of the second stage bootloader and verify it against this stored hash value for the bootloader. Similarly depending on the hierarchy for example if we have two stage bootloader then we will repeat this process and verify this in the same way. Then we will verify if the operating system is working or is valid and the operating in the sequence are valid. So here in chain we validated each layer and once it is trusted we proceed to validate the next layer in the chain. We will now check how secure boot is implemented in MCU boot. So Zafire RTOS is PSA certified with trusted firmware and implementation that is based on root of trust architecture in the case that we can use directly in integration of Zafire after TFM integration. Also there is a choice among three isolation levels based on the boundary rigidness between a secure and non secure region. Along with this Zafire provide the support for trusted execution environment TWE using TPM. And here TPM is a trusted platform module that provides hardware security module that provide storage of cryptographic keys and other security related data to verify the boot related informations. In MCU boot the binary image suffix with TLV pair that is type length value pairs. This is where we store the information about how the image is signed. Also here we can add metadata for custom data to add to an image. Here we can see that hash key value is defined and for example here we are using 0x02 as the public key. So based on the configurations we choose the security of MCU boot will get affected. For example we can use SHU 256 base validation to check for image corruption. There are many macros available to choose from the digital signatures like config boot signature type RSA and config boot signature type ECDSAP 256 which will control the type of signature the MCU boot uses to verify the image. And if we do not define any signature algorithm then the image is not protected against the intentional modification but it will just act as a checksum preventing a corrupted image from booting. Also there is one macro config boot validate slot that ensures that MCU boot validates the signature of the image on every boot. Although this feature makes the booting process a bit lengthy but it always verifies that the running image is trusted. With this secure boot process in place we can check during reboot will identify the unauthorized executables and prevent it from running further. And in background it may initiate remedial actions. The firmware upgrade process in Zephyr RTOS is secure procedure that ensures the installation of updated firmware on the target device by writing the new image to the flash and replacing the previous image. So whenever some new features are added to the firmware to do any bug fixes then to update the system with those changes we do a firmware upgrade by preparing a new firmware image. So on a regular interval we can check if new firmware update is available for the device or not. Here we may use versioning to check if any higher version image for the firmware update is available. If the new firmware image is available then we can proceed to download it securely or we can in regular interval schedule the recheck to check if any higher version image has come. So this new feature, this new firmware image is then securely downloaded to the target device through interfaces like UART or SD card or via cloud we can download the new firmware image to some partition or to some partition in the target device. We will then verify the firmware using digital signatures or checksum to ensure that it has not been corrupted during transfer before applying the update. So here also the firmware is signed using private key and verification is done by public key as in case of secure boot. So Zafair Atoz leverage MCU boot to do firmware update. Here MCU boot will conduct further verification of image and perform integrity checks. And if the new firmware image passes these checks then MCU boot safely updates the image guaranteeing a secure and reliable firmware upgrade. And if this fails we may try to initiate the upgrade again because there might be some issues with download or there may be some issue that was there but it might have been solved now. So once the device is authenticated we can download the image to the secondary slot of the flash from where it will start installing the fresh firmware upgrade. So there are many direct APIs we can call for example a call to boot request upgrade will perform firmware upgrade on the next boot. So let's now talk about rollback protection and the advantages it offers. So rollback protection is used to perform the upgrades in a fault tolerant manner and it is also used to recover the system if a bad firmware image is installed. So this is a essential security feature provided by the Zafair Atoz to ensure that once the device has been upgraded to a specific version it cannot be reverted that is less secure. So Zafair Atoz implements rollback protection via MCU boot which includes a firmware image storage mechanism here we maintain the record of the firmware image versions we have installed along with this the associated metadata we also record so when performing the firmware upgrade the MCU boot checks the version and metadata of the currently installed firmware and if the incoming firmware image is older or has less secure metadata then we reject that update and this will prevent the rollback. There is a macro config boot upgrade only that controls how upgrades are performed. So if this macro is unset MCU boot uses a swapping algorithm to exchange the new upgraded image with the old image allowing an easy reward to the system if the image is not booting and if this macro is enabled the image will overwrite the old image and if the new image does not boot there is no fallback image. As we see here the major steps remain same for the firmware upgrade process but the rollback protection provides an additional benefit of switching to the previous secure firmware image in case the new firmware that is downloaded is not working properly. So rollback protection is the FireArtox guarantees that the device will only run on the latest and more secure firmware versions. Bootloader recovery. In the events of bootloader corruption or failures the FireArtox offers a method to restore ensuring a continued operation of the device. So bootloader recovery process uses secondary bootloader or dedicated recovery mode that allows the device to boot again. So as FireArtox provides tools such as DFU that is device firmware upgrade and SWD that is serial via debug interface that helps in reflashing the bootloader firmware or performing other recovery procedures to restore the device boot functionality. So depending on specific implementation there are various mechanism to recover from the failure including the options such as falling back to the known image or restoring the bootloader to a default or factory state initiating a firmware update using the trusted and validated image or reconfiguring the bootloader settings or parameters. A threat model help us in identifying potential adversaries by analyzing different threat scenarios we can develop an effective security measure. Common threats include unauthorized access, insider threats from individuals with privileged access and we can have the firmware level attacks, the supplier chain attacks physical tampering and denial of service attacks. Considering these threats prior help us to prioritize security efforts and implement appropriate measures for enhancing the overall system security. So following are the best practices that can be used for integrating secure Zafire bootloader and MCU boot into the system. Understand the requirement for integration process and optimal performance. Develop a secure boot architecture that incorporates the Zafire bootloader and MCU boot using secure boot stages like using cryptographic signatures key management and secure storage of firmware images and verification data. Implement a secure firmware transferred by using secure channels and protocols for transferring firmware image sources to the target device as discussed in the previous slides and develop a secure mechanism for updating firmware. Implement a firmware verification and authentication mechanism within the bootloader. Implement firmware verification and then we can also deploy the error handling last is to validate thoroughly the test of integration of Zafire bootloader and MCU boot by doing rigorous testing to ensure that the boot process securely enabling firmware updates roll gas protections and overall system security. Future development so following are the some of the future scopes for integrating Zafire bootloader and MCU boot system security. Advancement of hardware security like integration of secure elements or trusted execution environments directly into the microcontroller. Cryptographic algorithms may evolve ensuring stronger encryption. Machine learning and artificial intelligence can be used to identify threats and may provide advanced protection solutions. There can be an enhancement in the security of OT updates using the macro using some macros over a more secure channel and providing additional verification mechanism. With growing concerns over data privacy we may include a stronger data protection methods in future. Future developments may involve real-time monitoring by providing the timely alerts and responses to the security builds. In the future we may provide tools guidelines and best practices that promote a secure system design and development. Thank you for attending the presentation. Please let us know if you have any questions. Thank you.


So, early this morning, we received notification of a weather briefing by the National Weather Service at 10 a.m. The weather forecast has changed, and now the National Weather Service is calling for a moderate risk of severe storms for eastern Kentucky, including Pike County, with a chance of hail up to an inch and a half in diameter, wind gusts over 80 miles an hour, which is essentially hurricane force winds, and also risk of isolated tornadoes. The National Weather Service has stated that this weather event is highly uncommon for this season. If we have winds that are 80 miles an hour as forecast, we expect a lot of trees down, a lot of power lines and other utilities to be impacted. If there's a line down, please assume it's energized, don't touch it, don't try to drive through water if you can't see the road, turn around. Are you ready for a new school year? There's a better way to start a new school year off right than with a new device on the network that keeps our students and teachers connected, Appalachian Wireless. Whether you need a new smartphone, wearable, or an iPad, we have your back to school solution. Visit AppalachianWireless.com or go into one of our 26 retail locations for our back to school deals that will help you show up and show out this school year. We are you. We are Appalachian Wireless. Individuals urge residents to remain cautious and vigilant during the watch period. In case of any road emergencies such as blockages or hazardous situations, individuals are encouraged to report them by calling<PHONE_NUMBER>. The emergency alert system has been activated, which is something we typically don't see very often. There is a thunderstorm watch in place for the remainder of the afternoon and also a tornado watch until 6 p.m. They're saying that most of the bad weather should be out of here by around 4 o'clock. However, the tornado watch is going to be until 6 p.m. Residents are advised to stay indoors during the watch period and avoid unnecessary travel until the weather situation stabilizes. Get everything that you can put up secured in case we do have the winds and be prepared because we don't know exactly what form the storm is going to take in terms of how strong the winds are going to be. The risk of hail is there. The risk of flash flooding is there and also the risk of tornadoes. Reporting from Mellon Top News, I'm Ethan Miller.


I am going to eventually do a whole video on why antivirus, just the concept of it doesn't make any sense.  And it's just there to make you feel better, but really it just runs in the background, makes your computer run worse. So I was recently out of Windows Machine and I'm going to, I've already recorded these videos. I'm going to do a little voice over here, but here we go. So here is a project of mine on GitHub or GitLab. It's my bin.  If I go into this one, which allows me to play some Nintendo games and I go into the bin folder, I have an exe file here, a play NES exe. When I go to download it, and this is something I wrote, it pops up here and says failed. It's a virus.  Well, it's not. Let me copy that. It's a virus total, which is a website that will scan files for you against a whole bunch of antivirus software. Look, all these antivirus programs think it's fine. So why do these antivirus programs think it's fine? But Windows Essential doesn't think it's fine because they're just guessing and it guessed differently. Let's go back and look at the actual source code for this binary. Because again, I wrote this and I compiled it. If we go into the Win32 file and click on the main C file, all it does is call a PowerShell script from a URL. Well, maybe that PowerShell script, which I also wrote, is malicious. Let's grab its URL and have a look at it. Load it up in the web browser here and just look at the text of it. All it does, the first thing it does is it loads up a media player and tries to stream Mario Brothers music from a website as it's downloading on the files. What files are downloaded? I have a function here, basic download function from an example tutorial on how to download stuff with PowerShell. And I have two URLs in here that downloads. One from Dropbox, which is a zip file, which contains a Nintendo emulator, a very common one, F-C-E-X. So if we take that and I go to download it, the computer has no problem with it. So if that was the issue with my script, it should have an issue with the actual file that's being downloaded and apparently not. Let's go ahead and look at the other file, which is just a text file that has a long list of URLs to Nintendo ROMs so that you can download a Nintendo ROM and play it with that emulator we just downloaded. So yeah, that's not going to be the issue. It's just a text file with a long list of URLs. Let's look at this a little deeper. Here is that long list of URLs that are zip files. Let's just try to download one of those and see if there's an issue. And I'm going to tell you there is, but it's a different issue. It's Chrome trying to tell me that this program could be malicious. I'm assuming just because it's a zip file, I'm not really sure it's dangerous. I thought maybe it was because I just did HTTP, but I add the HTTPS and it still said that. If I run that through VirusTotal again, it's clean. It's a clean file called all these. It's not saying it's a virus. It's just saying that it may contain something. It just might contain something malicious. So Chrome is not letting me download it. I can go to my shell and type in Wget and download that same exact URL, even without the HTTPS, which could be an issue. But I did it with the HTTP and I downloaded it. Look, I'll open up here. It's telling me that this it doesn't recognize this emulator. Again, this is a very commonly used open source emulator. And it's telling me, oh, we don't know who it is. I click on the wrong file. It seems to run fine. There's nothing wrong with any of the files, any of the URLs, any of the links that I was trying to learn, but anti virus was having a hissy fit and Windows fake security where they oh, we don't recognize this. Oh, so Microsoft doesn't know who this is. So right away, we're going to assume that it's bad.  It doesn't make sense. And I will do a video going into depth on this, but don't don't fall for it. It doesn't matter what operating system run. The only thing you have to do is don't download malicious software. That's it. Have a great day.


Nuclear energy and nuclear technology are extremely important in today's society. Around 10% of the world's electricity is generated from nuclear power plants. And despite increases in renewable energy over the last decade, nuclear power is going to play a continued role for a long time yet. And that's because nuclear power is a form of power technology that doesn't actually produce carbon dioxide. Nuclear technology is also important in other areas. A particular example is nuclear medicine. Many of you over the course of your lifetime are likely to have a nuclear medical procedure. You may have an x-ray or a CAT scan or a technetium scan to diagnose some problem.  Another thing you may not know is that nuclear power is responsible for life on earth as we know it. The heat from the sun is generated from nuclear fusion reactions. Another thing you may not know is that all of the things that the earth is made of, all of the elements, the atoms, the molecules were all created in thermonuclear explosions in stars billions of years ago. We are actually made of the ashes of thermonuclear explosions that happened all that time ago. If you stop and think about that, it's actually pretty freaky. What I hope to do in this series of videos is tell you some of the physics of nuclear radiation. To do that, we need to go back and we need to understand first the structure of the atom and in particular the structure of the heart of the atom, the atomic nucleus. The question we are interested in is what are atoms and nuclei actually made of? It was actually back in the 5th century BC that the Greek philosophers came up with the idea of atoms. The word atomos is the Greek word for indivisible. And they theorized that if you broke matter down into smaller and smaller pieces you'd eventually reach a point where you couldn't break it down any further and they called this thing an atom. This was the state of play for nearly 2500 years until the French scientist Henry Becquerel discovered in 1896 the phenomenon of radioactivity. Becquerel made his discovery by accident. He was investigating fluorescence with photographic plates and one day he wrapped up a photographic plate in black paper and stored it in a drawer and inside the drawer he had some uranium salts. When he exposed the photographic plate he saw an image despite the fact that it had been protected by the black paper. News of Becquerel's discovery spread quickly through Europe and it was another famous French scientist Marie Curie who showed that the intensity of these uranium rays depended proportionally on the amount of uranium that was present. This observation implies that the uranium is actually emitting some type of particle and if the uranium atoms are emitting some type of particle then atoms must be made up of even smaller objects. After these initial discoveries the scientific community in Europe quickly started work on trying to identify what this radiation was. It didn't take long before they realized that there were three different types of radiation and they called them alpha, beta and gamma radiation after the three first letters in the Greek alphabet.


Welcome, this is Melissa Armo with the Stock Swoosh and I'm reviewing LLY second later train today that I called and I mean this went to the dream target what can I say it actually went past it because I had 112 and it went down to 1190 I think was the low 1187 and if anyone is still in this it looks good again I don't know why you would be would ten minutes left into the close but if you this is one of these very very unusual unusual moves for a stock where it will close there the low you've got a weak market here today this was weak and again I called this late so let's just go over the call again this one to the dream target kind of just incredible here's right around here so anyways I saw this set up in here dropped called it 1350 wherever you could get in here boom beautiful beautiful stop in this as well I really felt that it had to be tight in order to hold because at this point I'm just going to show this over here was that it was like here 1350s right here like I really felt like if that this was going to work it was going to just go and not back up and at that point again market was red and I was right it worked went and what a huge trade with the stock so this was a really nice trade for two reasons one well actually for three reasons one had the market with us to it was straight down in other words you took it in your wrap every second since you took it which is great and then three the stop the stop in the move sorry small stop big move beautiful beautiful beautiful so from tip to top if you got the whole thing a buck 60 plus if you got a dollar 50 fantastic if you get anywhere between a dollar and 130 that's still fantastic so very very very big move in here for Lily with the stop just a perfect die for me to see this and call this at the right point today so thrilled that it worked out again if you have any questions email me at Melissa at the stocks wish calm the next golden gap course is June 22nd and 23rd I would not wait until the very last minute to sign up the class gets filled and I will be cutting off sign ups I I'd like to take a set amount of people each class and so I added a class for June because there's a lot of interest this month and earning season begins in July so now is a good time to do the class prepare to trade then in the earning season in July and August so if you have any questions email me at Melissa at the stocks wish calm have a great day everyone


Hello and welcome back to the craft box. My name is Brinton today. We're an episode 21 of the Privateer Walkthrough last time if you haven't checked it out already we did a bunch of stuff we stormed the prison and Defeated people in another place and all the things so go and check that out if you haven't already Really? But today we are starting by finding Don Rodrigo in the manor Which isn't here When it loads hello, it's also Christmas. So it's got Christmas stuff in El Dorro has sent you with good news. I see it in your eyes Santa Rana is defeated. It warms my heart to know that even tyrants are no match for this strength and cleverness of El Dorro And this pirate ally of course Don Rodrigo, I might have known I find you at the root of this rebellion You will pay dearly for your treason Hello, okay First battle here we go Been a while since I've played So let us just remember What we're gonna do. I'll do that. We'll move up there and we will sure So yeah in between and not in between the episode last episode we also got this new companion and I think that one's wrong No, no just um So yeah, that was cool. He's good Yeah Pretty much know all that is Hello, thank you for a lot these guys. It's not good. Okay, there we go minus their movement, which is good Double-tap fantastic that is fantastic amazing Okay, oh overwatch hello, nice resource there Cast dodge there nice resist Alcora, what are you doing? Cheeky Let us Do this and we will hit you sure why not you and we will go to you Done, okay That looks good Flanking nice super as well. That's fantastic Look at that amazing Amazing There we go, that's good mega nice In that doing some work Chill boy chill chill man chill chill Just chill. Thank you It's a lot Let me speak that one jeez we're nearly dead that is not good Unlucky that dodge always gets you What are we gonna do? Let us just go for you?  I just get him out. I suppose Okay chill boy Have to heal Yeah, okay cool one down Two down actually Okay, half-health fantastic Sweet Just chill boy chill we are going to have to kill with in it Probably this in it would be good Fantastic that was good. Okay Look at that amazing Do that done amazing he did bye Bye, and you're not quite dead, but we got a few so that's always nice Okay, good you didn't do anything. That's good Yes, there we go fantastic There we go. Yay, we did it. We did it. We did it. We did it amazing I would not listen to dog. I think I'll listen to some of the dialogue before Yeah, I always forget that we're not actually listening to dialogue She after recording the death with her So yeah, sorry about that live a lot Stiff Let's say you can probably be trained. Yes, you can yes, you can Yes, you can Yes, you can Yes, you can No, you can't Yes, you can yes, you can and that's what we have, okay We're gonna go What do we want you? This is a hard decision. I might go for some maybe I go for Spirit of none really We'll go tough for now and we'll see because I would give them some 40 which is good and you can definitely have rough Okay, that looks good. I'll be back once I'm at Eagle Caller. Okay. I am back Hello defender of the defenseless I love that badge actually that sounds like a great title. Let us put that one on We can use that one Where is that that'll be quest badges probably There it is I saw it just here fantastic Amazing That's our new badge Yes, so we are now That's what we're up to here. Okay We need to find Basically, we're on the search for duck of death, which is cool.  We're going to go to Cooper's Roost I Just love the stagecoach so much. It just makes it so much easier Best thing added to the game in my opinion other than the ones you're part two that was also good Not that I liked it. It's just that it was good for the game Yeah, this one I actually like though. So I mean, that's what's good. I remember going around cool ranch before Actually, no, I don't actually because I never was I never actually was in cool ranch when there was no stagecoach So, I mean, I don't really see I Didn't feel the pain of having to travel all the way through I think I literally got into cool ranch two days after it got released So that's fun. Well for the first time that is so, yeah, we know That's what I was gonna do. I'm gonna send some of my companions. We are just gonna chill in the sky way And this Get companions companions companions. Let's send some of them to do some sailing for us Just because we need an order call XP Because we're desperately low. Um, we might also give you guys balling and get you sailing and None and I know you can be brawling begin. Okay Just because we need to get them leveled up a bit and that's a good way to do it So, yes, let us find the silver stallion which is over here This is where we first meet the duck of death I think we have to defeat duck more ships So I might be back, but I can't remember if that's before or after. I'm pretty sure it's before But we'll see I think we can pick these up for a second. We're still here again What we do so captain my captain Be after the stallion we've got to fight them off Okay, well, I'll be back in just a bit once I have defeated some of these Okay, I am back that took forever not gonna lie. We are my captain, but we are now Doing this them quicker we be doomed Yes, so Gotta defeat these fires Yes, we can okay, that's good. Sometimes you just can't Like do that.  So yeah Gonna be careful, Billy Um, these guys are hard I Often die a lot in this battle not gonna lie not gonna lie at all Yeah, we just gotta be careful Hopefully we should be good That's good double block is fine. It's fantastic in fact That's awkward Okay, I need to get someone down there to destroy these things so he is immune I believe So he can't hit him to set theory I don't actually want to set theory. We're just gonna do that just because we can Um Okay Yes, here's and basically we get left with the We have to defeat them. So yes, that is what happens. He was immune Okay We okay, that's good. Hopefully we can do this Or don't know if we can I often don't do this on the first try which is bad Thank you blocking a lot, which is good Step to success Three of them We're gonna do that We're gonna do that and That Sure, why not Okay Hopefully we can get this guy out Okay, no We should be fine Steve Thanking nice we can get some crits on that would be fantastic Yeah Too much block They have really bad accuracy which is good Milly's here, which is also good We're gonna do that we can do that Do that done, okay Oh That's close He's dead. Thank you and bladestorm into you perfect If I plan that out Okay, we'll try and get Steve out and then we'll focus on the last one Already got dug down, which is good bill. They will have weird kind of funny. I just generic names. It's quite funny actually Um Yes, we're a fire. What are we gonna do? We will hit you Yeah Do that we'll just get him out. Hopefully Hopefully maybe There we go look at that Okay, not quite which is unfortunate, but we should be fine Alyssa that is not good Okay, that's fine Mm-hmm Mega nice, there we go. Look at that half-elf great I'm gonna heal because I don't really like being half-health We will go for you and you and you can hit him. Hopefully hitting 80 and if not that is unfortunate Okay, we should be full health in no time which is good Okay, and Thank you double tap on to you amazing Look at that nearly done. We didn't even die one of our companions died. That's a start. That's the first I should say Privateer OP. Um, maybe I live a little okay. So quick Done fantastic Look at that amazing. I can't believe we did that. That's so good need your help. We're not listening to dialogue. Good job We've no time to lose to bison village. Um, I didn't leave a mark So I'll be back once I'm at bison village. Okay. I am back Bring him this I need raw mandrake from our burial ground blood-bath teeth the warriors of the black storm tribe where Sun pollen that blows through the skies.  So I'm going to Actually, we'll go over to one time and see what he wants even though I know that there's a defeating collect of like a billion things Which I won't do on camera and I probably won't do in this episode. I'll probably do it in between Just to yeah, just do it Yeah So probably we'll be ending off the episode here I mean we did quite a bit defeating the well Battling facing finding seeing the duck of death for the first time, which is cool Yeah, so that's always fun So yeah, we will head over to the burial ground quickly and Then probably end off the episode there just because They want me to do a whole bunch of things and I don't want to do the whole bunch of things now Essentially is how it goes Burial ground is over here. Yes, it is Hello Be careful of the buffaloons. I say that getting pulled into a buffaloon battle Good job Brent Okay, I'll be back in just a bit. Okay. I'm back I finished that battle and it turns out I was going to the wrong place anyway here is one Let's forget that I'm not listening to that look. Oh my god So, yeah, this is what I was talking about where we have to defeat and collect and collect and defeat all of the things So yeah, I'll be doing that in between episodes So, yeah, thank you for watching Like and subscribe and if you're very subscribed press the bell so you know exactly when I post another video and remember craft outside box