The Deck: a portable, low-power, full-on penetrating testing and forensics system. The Deck runs on the BeagleBoard-xM and BeagleBone. It provides hundreds of security tools
Some recent claims have been made concerning the ability to remotely hijack airplanes. This talk examines those claims.
Videos for slides are now available:
https://www.youtube.com/watch?v=dOlM1weOF8g
https://www.youtube.com/watch?v=-6IW-vJSHeU
https://www.youtube.com/watch?v=LHqnUUiowjs
Slides from ThotCON 0x04 presentation on penetration testing with an army of small, low-powered devices running The Deck connect by 802.15.4 and/or Zigbee mesh networking.
DEFCON XX presentation on how to use a simple microcontroller device to make your USB mass storage device look like one that is authorized to be mounted. Also provides the ability to write block the drive to prevent deletion of security tools during use.
Rapidly developing IoT (Internet of Things) applications - Part 2: Arduino, B...Raul Chong
These are the slides used in the Toronto-SMAC meetup:
"Rapidly developing IoT (Internet of Things) applications - Part 2"
http://www.meetup.com/Toronto-SMAC-Social-Mobile-Analytics-Cloud-Meetup/events/195132732/
Topics covered:
- Arduino and sensors: Bus simulation project
- Freakduino and solar panels: Vibrometer project
- Raspberry-Pi: Home security system (part 2)
- Oculus Rift: Developing an Educational game (part 2)
- Beacons: Tracking customer patterns at a retail store
- Introduction to Node-Red
Kernel Recipes 2017 - HDMI CEC: Status Report - Hans VerkuilAnne Nicolas
The HDMI connector features a CEC (Consumer Electronics Control) pin that allows connected devices to detect and control one another. A new framework to handle CEC was added to the kernel in 2016.
This talk describes the current state of the CEC support, how to implement new CEC drivers and the various complications you will encounter when using CEC.
Hans Verkuil
Beagle bone black by Boddukuri venkata saitejaSai Charan
This document provides an overview of the Beaglebone Black development board. It describes the board's hardware specifications which include a ARM Cortex-A8 processor, 512MB RAM, PRU microcontrollers, and various interfaces. It also outlines the software environment including supported Linux distributions and languages. Setup instructions are provided to configure the board by connecting it to a PC via USB, enabling SSH access, and setting the root password. Key features of the ARM processor and pin diagrams are summarized as well.
The presentation deals with the range of features of the Linux sound subsystem — Advanced Linux Sound Architecture (ALSA). During the presentation, the participants were provided with case studies of the difference it makes for the development of audio drivers for PC and embedded systems. Also, it was
shared an overview of the state-of-the-art tendencies in the development of audio drivers for embedded systems.
This presentation by Vadym Shovkoplias (Senior Software Engineer, GlobalLogic Kharkiv) was delivered at GlobalLogic Kharkiv Embedded TechTalk #1 on March 13, 2018.
Some recent claims have been made concerning the ability to remotely hijack airplanes. This talk examines those claims.
Videos for slides are now available:
https://www.youtube.com/watch?v=dOlM1weOF8g
https://www.youtube.com/watch?v=-6IW-vJSHeU
https://www.youtube.com/watch?v=LHqnUUiowjs
Slides from ThotCON 0x04 presentation on penetration testing with an army of small, low-powered devices running The Deck connect by 802.15.4 and/or Zigbee mesh networking.
DEFCON XX presentation on how to use a simple microcontroller device to make your USB mass storage device look like one that is authorized to be mounted. Also provides the ability to write block the drive to prevent deletion of security tools during use.
Rapidly developing IoT (Internet of Things) applications - Part 2: Arduino, B...Raul Chong
These are the slides used in the Toronto-SMAC meetup:
"Rapidly developing IoT (Internet of Things) applications - Part 2"
http://www.meetup.com/Toronto-SMAC-Social-Mobile-Analytics-Cloud-Meetup/events/195132732/
Topics covered:
- Arduino and sensors: Bus simulation project
- Freakduino and solar panels: Vibrometer project
- Raspberry-Pi: Home security system (part 2)
- Oculus Rift: Developing an Educational game (part 2)
- Beacons: Tracking customer patterns at a retail store
- Introduction to Node-Red
Kernel Recipes 2017 - HDMI CEC: Status Report - Hans VerkuilAnne Nicolas
The HDMI connector features a CEC (Consumer Electronics Control) pin that allows connected devices to detect and control one another. A new framework to handle CEC was added to the kernel in 2016.
This talk describes the current state of the CEC support, how to implement new CEC drivers and the various complications you will encounter when using CEC.
Hans Verkuil
Beagle bone black by Boddukuri venkata saitejaSai Charan
This document provides an overview of the Beaglebone Black development board. It describes the board's hardware specifications which include a ARM Cortex-A8 processor, 512MB RAM, PRU microcontrollers, and various interfaces. It also outlines the software environment including supported Linux distributions and languages. Setup instructions are provided to configure the board by connecting it to a PC via USB, enabling SSH access, and setting the root password. Key features of the ARM processor and pin diagrams are summarized as well.
The presentation deals with the range of features of the Linux sound subsystem — Advanced Linux Sound Architecture (ALSA). During the presentation, the participants were provided with case studies of the difference it makes for the development of audio drivers for PC and embedded systems. Also, it was
shared an overview of the state-of-the-art tendencies in the development of audio drivers for embedded systems.
This presentation by Vadym Shovkoplias (Senior Software Engineer, GlobalLogic Kharkiv) was delivered at GlobalLogic Kharkiv Embedded TechTalk #1 on March 13, 2018.
The Arm Beetle IoT evaluation board is built around the Arm CoreLink SSE-100 Subsystem, which allows design teams to create IoT endpoints faster and with lower risk. Arm’s scalable IP solutions are designed to target across the value chain, from sensors to servers. Arm’s IoT subsystem with Mbed OS is a complete reference system, that reduces the complexity and risk of a SoC design for IoT endpoints. The subsystem features a range of peripherals and interfaces. It is specifically designed for use with Cortex-M processors and Arm Cordio Bluetooth Smart Radio IP. Arm has taken this subsystem and generated a proof of concept test chip called Beetle.
The document discusses how USB devices contain hidden microcontrollers that can run malicious firmware. The firmware can be reversed engineered and patched to carry out attacks like diverting network traffic or emulating keyboard input. No effective defenses against USB attacks currently exist since the firmware is hidden and can be updated.
The document discusses the BeagleBone Black single-board computer. It notes that the BeagleBone Black is a fast, powerful, and portable computer with 512MB of RAM, 4GB of flash storage, and runs operating systems like Debian, Ubuntu, and Android. It can be used for programming and connecting to devices via its Ethernet, USB, HDMI ports and 46-pin headers. The document compares the BeagleBone Black favorably to the Raspberry Pi, noting it has more processing power, memory, ports and is open source hardware. It provides sources to purchase a BeagleBone Black and learn more about programming and using it.
BeagleBone Black is one of the most popular open hardware that is available to learn Embedded Linux. This versatile platform helps you to explore different set of peripherals and helps you to load a custom Embedded distribution. This presentation briefly introduces you with BeagleBone Black.
PiFlash: Linux utility to flash SD cards for Raspberry Pi computersIan Kluft
Presentation by Ian Kluft at Silicon Valley Perl (SVPerl) on Feb 7, 2019 on "PiFlash: Linux utility to flash SD cards for Raspberry Pi computers". This tool is for use on Linux systems in place of manual procedures to write SD cards to boot a Raspberry Pi board. Safety features for newcomers include checking the destination device and refusing to erase any device that isn't an SD card. Handy automation for experience users includes automatically extracting the OS image from a tar/zip archive and uncompressing it to the SD card in one step.
Linux Conference Australia 2018 : Device Tree, past, present, futureNeil Armstrong
Since the switch of the ARM Linux support from the stable PowerPC Device Tree support, it became an important piece of software used to describe all sorts of devices based on very different hardware architectures.
Currently, BSD* Unixes and even the Zephyr RTOS has switched to Device Tree to describe the hardware. U-boot has also a file format using the Device Tree blob format.
Neil will present you the history of Device Tree from its origins, how it has been used for ARM from the PowerPC codebase, all the very different current usage and an overview of its future application and evolutions.
This document discusses using routers and Internet of Things devices running the OpenWrt operating system. It provides examples of OpenWrt configurations and projects using OpenWrt, such as community wireless networks. The document also mentions using OpenWrt on single board computers and developing code for OpenWrt packages.
Kernel Recipes 2017 - An introduction to the Linux DRM subsystem - Maxime RipardAnne Nicolas
Every modern multimedia-oriented ARM SoC usually has a number of display controllers, to drive a screen or an LCD panel, and a GPU, to provide 3D acceleration. The Linux kernel framework of choice to support these controllers is the DRM subsystem.
This talk will walk through the DRM stack, the architecture of a DRM/KMS driver and the interaction between the display and GPU drivers. The presentation is based on the work we have done to develop a DRM driver for the Allwinner SoCs display controller with multiple outputs, such as parallel display interfaces, HDMI or MIPI-DSI. The work done to make the ARM Mali OpenGL driver work on top of a mainline DRM/KMS driver will also be detailed, as well as the more traditional, Mesa-based, solution used in a variety of other platforms.
Maxime Ripard, Free Electrons
BeagleBone Black - Open Source Development Platform
Introduction :
The BeagleBone black is an embedded Linux development board that’s a credit card sized linux computer. It’s a smaller, more barebone version of BeagleBoard. Both are open source hardware and use Texas Instruments’ processors with an 1 GHz Sitara AM335x ARM® Cortex™-A8 processor, which are designed for low-power mobile devices. This BeagleBone Black Boot Linux in under 10-seconds and get started on processor development in less than 5 minutes with just a single USB cable.
BleagleBone Black comes with Angstrom Linux distrubution in onboard FLASH to start evaluation and developement. Angstrom Linux is Opkg Package based operating system, Opkg is a lightweight package management system based up on ipkg. It is written in C and resembles APT/dpkg in operaton. It is intended for use on embedded Linux devices and is used in this capacity in the OpenEmbedded and OpenWrt project and which are belongs to Google Code repository.
The software platform is based on the Angstrom GNU/Linux distribution and is equipped with a distributed file system to ease sharing data and code among the nodes of the cluster, and with tools for managing tasks and monitoring the status of each node.
Features:
The BeagleBone Black as nothing more than a small, standalone Linux computer, but the hardware is designed for use as an embedded system – a computer installed inside of a large electronics project.The main evidance of theis is in the two rows of GPIO ( general puropose Input/ Output) pins moujnted along either side of the board. These pins allow the Beaglebone Black to communicate with a wide range of sensors, servos, outputs and other hardware, letting it act as the brain of a large, complex project.
The BeagleBone Black features:
•TI Sitara AM3359 1-GHz superscalar ARM Cortex™-A8
•2x 200MHz ARM7 programmable real-time coprocessors
•512-MB DDR3L RAM
•2GB eMMC
•PowerVR SGX 530 GPU, LCD expansion header, micro HDMI
•Stereo audio-out via HDMI
•1x USB 2.0 host port
•1x USB 2.0 device port
•On-chip 10/100 Ethernet, not off of USB
•MicroSD slot
•Add-on "capes" for expansion, compatible with original Bone capes
•1 power LED and 4 user controllable LEDs via GPIO
•Industry standard 3.3V I/Os on the expansion headers with easy-to-use 0.1" spacing
•Multiple I/O bus: GPMC (nand), MMC, SPI, I2C, CAN, McASP, MMC, 4 Timers, XDMA interrupt
•5 serial ports (1 via debug header, 4 more on side headers)
•65 GPIO pins
•8 PWM outputs
•7 12-bit A/D converters (1.8V max)
•Board size: 3.4” × 2.1”
Pinout:
Beagle Bone Black’s Capabilites can be extended using plug-in boards called “capes” that can be plugged into BeagleBone Black’s two 46-pin dual-row expansion headers. Capes are avilable for, VGA, LCD, motor control, prototyping, battery power and other functionality. Power consumption is also lower, with the board only req
Fear and Loathing on your Desk: BadUSB, and what you should do about it
Presented at Kiwicon 9, 10-11 December 2015, Wellington New Zealand.
For over 15 years USB has been the universal computing peripheral interface. In simpler times the host computer and the USB device trusted each other, and so USB implementations historically placed little emphasis on security issues. But what if malicious firmware were loaded into a USB device? How can you protect yourself from BadUSB?
This talk will review public implementations of BadUSB, and (the distinct lack of) available defensive techniques. A hardware gadget will then be presented to make most of your problems...disappear.
This document provides an overview of the Arduino and BeagleBone Black microcontroller boards and how to get started with the BeagleBone Black. It compares the specifications of the Atmel328 microcontroller in the Arduino to the AM335x microcontroller in the BeagleBone Black, noting the BeagleBone Black has more memory, processing power, and I/O pins. It also explains how to set up the BeagleBone Black by SSHing in and updating the time, and introduces using pulse width modulation and servo control with the Adafruit Python library. Links are provided for beginner, intermediate, and advanced resources on using the BeagleBone Black.
The Beagle Bone Black is a low-cost development platform that allows developers to boot Linux in under 10 seconds and get started on development quickly using just a USB cable. It has an ARM Cortex-A8 processor, 512MB RAM, and connectivity options like USB, Ethernet, HDMI. The Beagle Bone Black supports software like Angstrom Linux, Android, and Cloud9 IDE. It can be used for physical computing, robotics, and running programs like OpenCV for image analysis. Capes expansion boards can add functionality like motors, sensors, and cameras.
Claudio Scordino - Handling mixed criticality on embedded multi-core systemslinuxlab_conf
This talk illustrates how to use the Jailhouse hypervisor for running Linux alongside an RTOS on modern ARM multi-core SoCs, aiming at building smarter devices for the automotive market.
Recently, the industry has shown a growing interest for executing activities with different levels of criticality on the same multi-core SoC. These could consist, for example, of non-critical activities (e.g., monitoring, logging, human-machine intefaces) together with safety-critical tasks. The rationale behind this interest is the continuous need for reducing the time-to-market as well as the design and hardware costs. This is particularly suitable for the automotive market, where new infotainment functionalities might be coupled with traditional safety-critical tasks (e.g. engine/brake control). In this talk, we will present our experience (grown through the HERCULES EU project) in using the Jailhouse hypervisor for executing the Linux general-purpose OS alongside an automotive RTOS on modern ARM multi-core platforms. Besides providing useful instructions for using Jailhouse, we will illustrate a library designed for easing the communication between the two OSs as well as some mechanism for limiting the interference on shared hardware resources. Finally, a short video of a simple demo will show the effectiveness of the proposed approach.
This document discusses using a Raspberry Pi for various amateur radio projects. It begins by explaining what a Raspberry Pi is - an inexpensive single-board computer running Linux. It then provides examples of using a Raspberry Pi for software defined radio with an RTL-SDR dongle, receiving ADS-B aircraft signals, using WSPR for weak signal propagation reporting with the WsprryPi software, acting as a D-STAR access point with a DVAP dongle, using it for packet radio with software like Direwolf and hardware TNCs, setting up a packet BBS with PiLinBPQ, and using it for APRS with clients like Xastir and YAAC.
U-boot provides a multistage boot process that initializes the CPU and board resources incrementally at each stage. It begins execution on the CPU in a limited environment and hands off to subsequent stages that gain access to more resources like memory and devices. U-boot supports booting an operating system image from storage like SSD or over the network and offers features like secure boot and hypervisor support.
This document discusses various generations of HID attack devices that can inject keystrokes and payloads without detection from antivirus or DLP tools. It covers 1st gen devices like Teensy and Rubber Ducky, 2nd gen techniques like BadUSB, and advanced 3rd gen tools like WHID Injector and P4wnP1 that add WiFi capabilities and ways to bypass airgapping. It also discusses mitigation techniques for Linux and Windows like usbguard and duckhunt as well as resources for further information.
U-Boot project has evolved in the time span of over 17 years and so as its complexity and its uses. This has made it a daunting task in getting started with its development and uses. This talk will address all these issues start with overview, features, efforts created by community and future plans.
The U-Boot project has evolved in the time span of over 17 years and so as its complexity and its uses. This has made it a daunting task in getting started with its development and uses. This talk will address all these issues and share development efforts created by the U-Boot community.
In this talk Jagan Teki(Maintainer for Allwinner SoC, SPI, SPI FLASH Subsystems) will introduce U-Boot from scratch with a brief overview of U-Boot history, U-Boot Proper, SPL, TPL, Build process and Startup sequence. He will talk about other preliminaries such as Image booting, Falcon Mode, Secure Boot and U-Boot features like device tree, device overlays, driver model and DFU, etc.
Once giving enough introduction, he will also talk about steps to port U-Boot to new hardware with a demo, along with U-Boot testing process. Finally, he will address and review ongoing development work, issues and future development regarding U-Boot.
Kernel Recipes 2017 - The Serial Device Bus - Johan HovoldAnne Nicolas
UARTs and RS-232 have been around since the 1960s, and despite the advent of technologies like USB and PCIe, it seems UART-attached devices are not going away anytime soon. In embedded systems, UARTs are a
commonly used peripheral interface (e.g. for Bluetooth, NFC, and GPS) even if the kernel infrastructure for dealing with such devices has been both limited in what it can provide (e.g. in terms of power management) and cumbersome to use (e.g. requiring user-space daemons).
This presentation will give an introduction to the recently merged Serial Device Bus, which aims to overcome some of these limitations by making UART-attached devices fit better into the Linux device model. After providing some historical background, the design and interfaces of the new bus will be reviewed, and some known limitations and possibilities for future enhancements will be discussed.
Johan Hovold
ELC North America 2021 Introduction to pin muxing and gpio control under linuxNeil Armstrong
In the last 10 years, the GPIO and PINCTRL subsystem matured to support almost every possible handling of Programmable Input/Outputs and more generally multiplexing of multiple functions on single "Pins" or group of "Pins". However, what is a "Pin"? What is a multiplexed "Function"? How programmable I/Os and pin functions are designed on the majority of System-On-Chips? Neil will describe this from the Hardware design Point-Of-View, the constraints and the requirements. Then Neil will explain how this particular subject was handled over the years in the Linux kernel, to finally get to the current GPIO & PINCTRL subsystems, and how it articulates with the Device Tree and other Firmware based protocols.
The Watershed-based Social Events Detection Method with Support from External...MediaEval2012
The document proposes a method for detecting social events from photo metadata by applying watershed segmentation techniques to cluster images into events based on similarity of user annotations, with images assigned to the same event if they share common markers like username, date, tags or nearby GPS locations. The watershed transform treats each unique annotation as a marker and floods image regions from these markers using merging conditions to group images into homogeneous event segments, with boundaries between non-overlapping user involvement preventing images from being assigned to multiple events. External data sources on keywords, locations and semantic relatedness could help prune markers and improve precision and recall of identified social events.
The Arm Beetle IoT evaluation board is built around the Arm CoreLink SSE-100 Subsystem, which allows design teams to create IoT endpoints faster and with lower risk. Arm’s scalable IP solutions are designed to target across the value chain, from sensors to servers. Arm’s IoT subsystem with Mbed OS is a complete reference system, that reduces the complexity and risk of a SoC design for IoT endpoints. The subsystem features a range of peripherals and interfaces. It is specifically designed for use with Cortex-M processors and Arm Cordio Bluetooth Smart Radio IP. Arm has taken this subsystem and generated a proof of concept test chip called Beetle.
The document discusses how USB devices contain hidden microcontrollers that can run malicious firmware. The firmware can be reversed engineered and patched to carry out attacks like diverting network traffic or emulating keyboard input. No effective defenses against USB attacks currently exist since the firmware is hidden and can be updated.
The document discusses the BeagleBone Black single-board computer. It notes that the BeagleBone Black is a fast, powerful, and portable computer with 512MB of RAM, 4GB of flash storage, and runs operating systems like Debian, Ubuntu, and Android. It can be used for programming and connecting to devices via its Ethernet, USB, HDMI ports and 46-pin headers. The document compares the BeagleBone Black favorably to the Raspberry Pi, noting it has more processing power, memory, ports and is open source hardware. It provides sources to purchase a BeagleBone Black and learn more about programming and using it.
BeagleBone Black is one of the most popular open hardware that is available to learn Embedded Linux. This versatile platform helps you to explore different set of peripherals and helps you to load a custom Embedded distribution. This presentation briefly introduces you with BeagleBone Black.
PiFlash: Linux utility to flash SD cards for Raspberry Pi computersIan Kluft
Presentation by Ian Kluft at Silicon Valley Perl (SVPerl) on Feb 7, 2019 on "PiFlash: Linux utility to flash SD cards for Raspberry Pi computers". This tool is for use on Linux systems in place of manual procedures to write SD cards to boot a Raspberry Pi board. Safety features for newcomers include checking the destination device and refusing to erase any device that isn't an SD card. Handy automation for experience users includes automatically extracting the OS image from a tar/zip archive and uncompressing it to the SD card in one step.
Linux Conference Australia 2018 : Device Tree, past, present, futureNeil Armstrong
Since the switch of the ARM Linux support from the stable PowerPC Device Tree support, it became an important piece of software used to describe all sorts of devices based on very different hardware architectures.
Currently, BSD* Unixes and even the Zephyr RTOS has switched to Device Tree to describe the hardware. U-boot has also a file format using the Device Tree blob format.
Neil will present you the history of Device Tree from its origins, how it has been used for ARM from the PowerPC codebase, all the very different current usage and an overview of its future application and evolutions.
This document discusses using routers and Internet of Things devices running the OpenWrt operating system. It provides examples of OpenWrt configurations and projects using OpenWrt, such as community wireless networks. The document also mentions using OpenWrt on single board computers and developing code for OpenWrt packages.
Kernel Recipes 2017 - An introduction to the Linux DRM subsystem - Maxime RipardAnne Nicolas
Every modern multimedia-oriented ARM SoC usually has a number of display controllers, to drive a screen or an LCD panel, and a GPU, to provide 3D acceleration. The Linux kernel framework of choice to support these controllers is the DRM subsystem.
This talk will walk through the DRM stack, the architecture of a DRM/KMS driver and the interaction between the display and GPU drivers. The presentation is based on the work we have done to develop a DRM driver for the Allwinner SoCs display controller with multiple outputs, such as parallel display interfaces, HDMI or MIPI-DSI. The work done to make the ARM Mali OpenGL driver work on top of a mainline DRM/KMS driver will also be detailed, as well as the more traditional, Mesa-based, solution used in a variety of other platforms.
Maxime Ripard, Free Electrons
BeagleBone Black - Open Source Development Platform
Introduction :
The BeagleBone black is an embedded Linux development board that’s a credit card sized linux computer. It’s a smaller, more barebone version of BeagleBoard. Both are open source hardware and use Texas Instruments’ processors with an 1 GHz Sitara AM335x ARM® Cortex™-A8 processor, which are designed for low-power mobile devices. This BeagleBone Black Boot Linux in under 10-seconds and get started on processor development in less than 5 minutes with just a single USB cable.
BleagleBone Black comes with Angstrom Linux distrubution in onboard FLASH to start evaluation and developement. Angstrom Linux is Opkg Package based operating system, Opkg is a lightweight package management system based up on ipkg. It is written in C and resembles APT/dpkg in operaton. It is intended for use on embedded Linux devices and is used in this capacity in the OpenEmbedded and OpenWrt project and which are belongs to Google Code repository.
The software platform is based on the Angstrom GNU/Linux distribution and is equipped with a distributed file system to ease sharing data and code among the nodes of the cluster, and with tools for managing tasks and monitoring the status of each node.
Features:
The BeagleBone Black as nothing more than a small, standalone Linux computer, but the hardware is designed for use as an embedded system – a computer installed inside of a large electronics project.The main evidance of theis is in the two rows of GPIO ( general puropose Input/ Output) pins moujnted along either side of the board. These pins allow the Beaglebone Black to communicate with a wide range of sensors, servos, outputs and other hardware, letting it act as the brain of a large, complex project.
The BeagleBone Black features:
•TI Sitara AM3359 1-GHz superscalar ARM Cortex™-A8
•2x 200MHz ARM7 programmable real-time coprocessors
•512-MB DDR3L RAM
•2GB eMMC
•PowerVR SGX 530 GPU, LCD expansion header, micro HDMI
•Stereo audio-out via HDMI
•1x USB 2.0 host port
•1x USB 2.0 device port
•On-chip 10/100 Ethernet, not off of USB
•MicroSD slot
•Add-on "capes" for expansion, compatible with original Bone capes
•1 power LED and 4 user controllable LEDs via GPIO
•Industry standard 3.3V I/Os on the expansion headers with easy-to-use 0.1" spacing
•Multiple I/O bus: GPMC (nand), MMC, SPI, I2C, CAN, McASP, MMC, 4 Timers, XDMA interrupt
•5 serial ports (1 via debug header, 4 more on side headers)
•65 GPIO pins
•8 PWM outputs
•7 12-bit A/D converters (1.8V max)
•Board size: 3.4” × 2.1”
Pinout:
Beagle Bone Black’s Capabilites can be extended using plug-in boards called “capes” that can be plugged into BeagleBone Black’s two 46-pin dual-row expansion headers. Capes are avilable for, VGA, LCD, motor control, prototyping, battery power and other functionality. Power consumption is also lower, with the board only req
Fear and Loathing on your Desk: BadUSB, and what you should do about it
Presented at Kiwicon 9, 10-11 December 2015, Wellington New Zealand.
For over 15 years USB has been the universal computing peripheral interface. In simpler times the host computer and the USB device trusted each other, and so USB implementations historically placed little emphasis on security issues. But what if malicious firmware were loaded into a USB device? How can you protect yourself from BadUSB?
This talk will review public implementations of BadUSB, and (the distinct lack of) available defensive techniques. A hardware gadget will then be presented to make most of your problems...disappear.
This document provides an overview of the Arduino and BeagleBone Black microcontroller boards and how to get started with the BeagleBone Black. It compares the specifications of the Atmel328 microcontroller in the Arduino to the AM335x microcontroller in the BeagleBone Black, noting the BeagleBone Black has more memory, processing power, and I/O pins. It also explains how to set up the BeagleBone Black by SSHing in and updating the time, and introduces using pulse width modulation and servo control with the Adafruit Python library. Links are provided for beginner, intermediate, and advanced resources on using the BeagleBone Black.
The Beagle Bone Black is a low-cost development platform that allows developers to boot Linux in under 10 seconds and get started on development quickly using just a USB cable. It has an ARM Cortex-A8 processor, 512MB RAM, and connectivity options like USB, Ethernet, HDMI. The Beagle Bone Black supports software like Angstrom Linux, Android, and Cloud9 IDE. It can be used for physical computing, robotics, and running programs like OpenCV for image analysis. Capes expansion boards can add functionality like motors, sensors, and cameras.
Claudio Scordino - Handling mixed criticality on embedded multi-core systemslinuxlab_conf
This talk illustrates how to use the Jailhouse hypervisor for running Linux alongside an RTOS on modern ARM multi-core SoCs, aiming at building smarter devices for the automotive market.
Recently, the industry has shown a growing interest for executing activities with different levels of criticality on the same multi-core SoC. These could consist, for example, of non-critical activities (e.g., monitoring, logging, human-machine intefaces) together with safety-critical tasks. The rationale behind this interest is the continuous need for reducing the time-to-market as well as the design and hardware costs. This is particularly suitable for the automotive market, where new infotainment functionalities might be coupled with traditional safety-critical tasks (e.g. engine/brake control). In this talk, we will present our experience (grown through the HERCULES EU project) in using the Jailhouse hypervisor for executing the Linux general-purpose OS alongside an automotive RTOS on modern ARM multi-core platforms. Besides providing useful instructions for using Jailhouse, we will illustrate a library designed for easing the communication between the two OSs as well as some mechanism for limiting the interference on shared hardware resources. Finally, a short video of a simple demo will show the effectiveness of the proposed approach.
This document discusses using a Raspberry Pi for various amateur radio projects. It begins by explaining what a Raspberry Pi is - an inexpensive single-board computer running Linux. It then provides examples of using a Raspberry Pi for software defined radio with an RTL-SDR dongle, receiving ADS-B aircraft signals, using WSPR for weak signal propagation reporting with the WsprryPi software, acting as a D-STAR access point with a DVAP dongle, using it for packet radio with software like Direwolf and hardware TNCs, setting up a packet BBS with PiLinBPQ, and using it for APRS with clients like Xastir and YAAC.
U-boot provides a multistage boot process that initializes the CPU and board resources incrementally at each stage. It begins execution on the CPU in a limited environment and hands off to subsequent stages that gain access to more resources like memory and devices. U-boot supports booting an operating system image from storage like SSD or over the network and offers features like secure boot and hypervisor support.
This document discusses various generations of HID attack devices that can inject keystrokes and payloads without detection from antivirus or DLP tools. It covers 1st gen devices like Teensy and Rubber Ducky, 2nd gen techniques like BadUSB, and advanced 3rd gen tools like WHID Injector and P4wnP1 that add WiFi capabilities and ways to bypass airgapping. It also discusses mitigation techniques for Linux and Windows like usbguard and duckhunt as well as resources for further information.
U-Boot project has evolved in the time span of over 17 years and so as its complexity and its uses. This has made it a daunting task in getting started with its development and uses. This talk will address all these issues start with overview, features, efforts created by community and future plans.
The U-Boot project has evolved in the time span of over 17 years and so as its complexity and its uses. This has made it a daunting task in getting started with its development and uses. This talk will address all these issues and share development efforts created by the U-Boot community.
In this talk Jagan Teki(Maintainer for Allwinner SoC, SPI, SPI FLASH Subsystems) will introduce U-Boot from scratch with a brief overview of U-Boot history, U-Boot Proper, SPL, TPL, Build process and Startup sequence. He will talk about other preliminaries such as Image booting, Falcon Mode, Secure Boot and U-Boot features like device tree, device overlays, driver model and DFU, etc.
Once giving enough introduction, he will also talk about steps to port U-Boot to new hardware with a demo, along with U-Boot testing process. Finally, he will address and review ongoing development work, issues and future development regarding U-Boot.
Kernel Recipes 2017 - The Serial Device Bus - Johan HovoldAnne Nicolas
UARTs and RS-232 have been around since the 1960s, and despite the advent of technologies like USB and PCIe, it seems UART-attached devices are not going away anytime soon. In embedded systems, UARTs are a
commonly used peripheral interface (e.g. for Bluetooth, NFC, and GPS) even if the kernel infrastructure for dealing with such devices has been both limited in what it can provide (e.g. in terms of power management) and cumbersome to use (e.g. requiring user-space daemons).
This presentation will give an introduction to the recently merged Serial Device Bus, which aims to overcome some of these limitations by making UART-attached devices fit better into the Linux device model. After providing some historical background, the design and interfaces of the new bus will be reviewed, and some known limitations and possibilities for future enhancements will be discussed.
Johan Hovold
ELC North America 2021 Introduction to pin muxing and gpio control under linuxNeil Armstrong
In the last 10 years, the GPIO and PINCTRL subsystem matured to support almost every possible handling of Programmable Input/Outputs and more generally multiplexing of multiple functions on single "Pins" or group of "Pins". However, what is a "Pin"? What is a multiplexed "Function"? How programmable I/Os and pin functions are designed on the majority of System-On-Chips? Neil will describe this from the Hardware design Point-Of-View, the constraints and the requirements. Then Neil will explain how this particular subject was handled over the years in the Linux kernel, to finally get to the current GPIO & PINCTRL subsystems, and how it articulates with the Device Tree and other Firmware based protocols.
The Watershed-based Social Events Detection Method with Support from External...MediaEval2012
The document proposes a method for detecting social events from photo metadata by applying watershed segmentation techniques to cluster images into events based on similarity of user annotations, with images assigned to the same event if they share common markers like username, date, tags or nearby GPS locations. The watershed transform treats each unique annotation as a marker and floods image regions from these markers using merging conditions to group images into homogeneous event segments, with boundaries between non-overlapping user involvement preventing images from being assigned to multiple events. External data sources on keywords, locations and semantic relatedness could help prune markers and improve precision and recall of identified social events.
Violence Detection in Video by Large Scale Multi-Scale Local Binary Pattern D...MediaEval2012
The document discusses a multi-scale local binary pattern (MSLBP) dynamics approach for detecting violence in video streams. It downsamples video to 5Hz, generates an MSLBP vector for each image, and computes the average and variance of changes in M over 20 second sections. A linear SVM is trained on the 20480 dimensions to classify sections as violent or not. Results on one movie were misleading due to feature errors, and the model struggles with desynchronization, but can distinguish fast movements from violent events.
QMUL @ MediaEval 2012: Social Event Detection in Collaborative Photo CollectionsMediaEval2012
This document describes QMUL's approach for social event detection in collaborative photo collections at the MediaEval 2012 challenge. The approach aims to find and detect social events and retrieve associated photos with the help of external information. It involves gathering external data like expanding topics and handling geographic locations. It also includes preprocessing steps like matching locations, translating terms, and composing textual features from photos. The approach then retrieves photos for detected events using classification and techniques like limiting the search space and expanding features. It evaluates this approach on the MediaEval 2012 dataset and achieves an F-score of 72.6% for detecting events and retrieving photos.
This document describes a study that tested using a combination of low-grade rock phosphate and human urine as a novel fertilizer for chickpea plants. The study found that applying this fertilizer combination directly to soil resulted in similar plant growth performance as applying commercial diammonium phosphate fertilizer at the same ratios. Using a waste product like low-grade rock phosphate enriched with human urine holds promise for sustainable agriculture by enabling waste utilization and minimizing waste while improving resource-use efficiency for food production. Crop trials were conducted on chickpea plants in trays with different soil treatments to evaluate the effects on plant growth responses.
Brave New Task: Musiclef Multimodal Music TaggingMediaEval2012
The document describes the Multimodal Music Tagging Task evaluation organized by MediaEval. The task involves categorizing songs from a commercial music library according to tags for their usage in TV and radio. It utilizes multiple modalities including audio features, social tags, and webpages. The test collection includes 1355 songs annotated with 355 tags. A reference implementation in MATLAB serves as a baseline, evaluating individual modalities and their combination. Participation was low with only one group submitting runs. The task aims to further evaluation of multimodal approaches to music tagging.
How INRIA identifies Geographic Location of a VideoMediaEval2012
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
DCU Search Runs at MediaEval 2012: Search and Hyperlinking TaskMediaEval2012
This document summarizes the DCU Search runs submitted to the MediaEval 2012 Search and Hyperlinking task. It describes the segmentation method used, which segmented audio into 180 second segments with 60 seconds of overlap and included pauses. It also provides details on the sub-corpora used, including the number of documents and terms for runs using the LIUM and LIMSI transcripts with and without pause segmentation and overlap. The runs used the Terrier IR system with a standard language model.
Mentor Strategy Session: Business Plan and VideoGrow America
This document provides guidance to participants advancing to Round 2 of a business plan competition. It outlines the key elements of Round 2, which includes updating the business plan and creating a 2-minute video. The business plan should demonstrate the management team, financial projections, and sales and marketing strategy. The video should supplement the written plan and showcase the business concept visually to persuade the judges. Advice is given on focusing the video on critical elements and why an investor should fund the idea. Participants are in an elite group for making it to Round 2 and have an opportunity to validate their idea and prepare for communicating with customers and investors.
Secrets of Storytelling by Candace KleinGrow America
The document provides an overview of the 5-minute pitch for startups seeking funding. It outlines the key topics investors look for, including the products/services, market, sales strategy, management team, intellectual property, finances, and capital needs. The document also warns of common pitfalls to avoid, such as having no exit plan or unrealistic projections. An example pitch is then provided for a peer-to-peer commercial lending platform called SoMoLend, covering its market opportunity, management team, financial projections, capital raised and milestones.
This research paper investigates the adsorption behavior of biochar derived from napier grass towards urea in aqueous solutions. Experiments were conducted to understand the effect of process parameters like temperature, agitation speed, and initial concentration on urea uptake. Equilibrium, kinetics and mass transfer models were applied to describe the adsorption. The results showed that low temperature, moderate agitation, and high initial concentration favored greater urea adsorption. Adsorption was found to be exothermic, physical, spontaneous and followed pseudo-second order kinetics. Both surface and intra-particle diffusion influenced removal and immobilization of urea, with film diffusion limiting the mass transfer process. The Dubinin-Radushkevich model best
John Richards: My Life Lessons As An EntrepreneurGrow America
This document profiles John E. Richards, an entrepreneur, investor, and professor. It outlines his professional roles including Managing Partner of UtahAngels Venture Investment Group and positions at BYU. Richards has founded several organizations including BoomStartup and Utah Student 25. He has had success investing in startups like Omniture and Oakley Networks. Richards teaches entrepreneurship and mentors students. He is also the founder of BoomStartup, a startup accelerator based on the TechStars model.
The document summarizes the MediaEval 2012 multimedia benchmark workshop. Some key points:
- MediaEval is in its 5th year of evaluating new algorithms for multimedia access and retrieval, emphasizing the "multi" aspects of multimedia.
- The 2012 workshop saw 6 tasks and over 30 participant teams.
- MediaEval has grown its community to over 140 participants and has generated over 100 academic papers since 2008.
- The workshop highlights included keynote speakers from BBC research and Yahoo research, as well as a filmmaker documenting the event.
The MediaEval 2012 Affect Task: Violent Scenes DetectioMediaEval2012
This document summarizes the MediaEval 2012 violent scenes detection task. The goal is to detect violent segments in movies to help users choose child-appropriate content. Violence is defined as physical injury or pain. Participants were provided 18 movies annotated at the shot-level for violence. Runs detecting violence at the shot and segment level were submitted. Evaluation used mean average precision and a cost-based metric. 11 teams from 9 countries participated, submitting 36 runs total. The best performing run achieved a MAP@100 of 65.05. Participation was higher than the previous year with more joint submissions and workshop attendance.
Telefonica Research System for the Spoken Web Search task at Mediaeval 2012MediaEval2012
The document describes two spoken web search systems proposed by Telefonica Research - Segmental-DTW (S-DTW) and IR-DTW. Both systems use the same frontend processing and feature extraction but differ in their matching algorithms, with IR-DTW aiming to reduce memory usage and speed up retrieval compared to S-DTW. The systems are evaluated on the Mediaeval 2012 Spoken Web Search task and results show IR-DTW achieves similar accuracy to S-DTW but with improved efficiency.
Event Detection via LDA for the MediaEval2012 SED TaskMediaEval2012
The document describes the MediaEval2012 Social Event Detection task which aimed to discover social events from photos on social media. It outlines the methodology used which included preprocessing text, classifying photos by city, identifying topics with LDA, selecting relevant topics, detecting events by identifying peaks in photos per day, and optimizing events. Evaluation results showed high precision and F-measure for detecting technical events in Germany and soccer events in Hamburg/Madrid, and moderately high scores for protest events in Madrid by the Indignados movement.
CERTH @ MediaEval 2012 Social Event Detection TaskMediaEval2012
This document describes CERTH's approach to the MediaEval 2012 Social Event Detection task. It involved creating a graph connecting photos likely from the same event, clustering the graph to detect events, and filtering events. Step 1 created the graph using a classifier on image features. Step 2 clustered the graph into candidate events. Step 3 filtered events based on location and tags to get the final events. Evaluation showed moving to a larger training set did not improve performance, and the approach struggled on one challenge due to differences from the training data.
The JHU-HLTCOE Spoken Web Search System for MediaEval 2012MediaEval2012
The document summarizes the JHU-HLTCOE Spoken Web Search System. It uses a technique called Randomized Acoustic Indexing for Logarithmic-Time Search (RAILS) to allow searching large audio collections 1000x faster than real-time. It extracts frequency domain linear prediction and cepstral features from audio and performs segmental dynamic time warping search. Results on development and evaluation sets show it achieves mean term-weighted value scores between 0.336-0.439 and actual term-weighted value scores between 0.321-0.369.
LIG at MediaEval 2012 affect task: use of a generic methodMediaEval2012
The document summarizes the LIG Quaero consortium's system for detecting violent scenes in videos submitted to the MediaEval 2012 evaluation. The system uses a hierarchical classification pipeline that extracts multiple audio, visual, and motion descriptors from video shots. It applies optimization techniques to the descriptors and uses multiple support vector machine and k-nearest neighbor classifiers. The classifiers and descriptor variants are fused at different levels of the hierarchy. Techniques like conceptual feedback and temporal re-ranking are used to improve performance. The best performing run achieved a MAP@100 score of 0.3138 on the test data.
This document discusses hacking and forensics using small, low-power devices like the Beagleboard and Beaglebone. It describes choosing the Beagleboard as a platform due to its small size, low power usage, and features like built-in Ethernet and USB ports. It outlines selecting Ubuntu as the base OS and leveraging existing repositories to obtain forensics and hacking tools. It also covers building tools from source by either natively compiling on the device or cross-compiling from a desktop. The document demonstrates using udev rules to automatically mount external USB drives in read-only mode for forensics purposes when connected to a special USB hub. It concludes by discussing future directions like optimizing more packages and port
The default applications on an embedded Linux system include many common command line utilities from BusyBox, such as cat, cp, grep, ls, mkdir, more, mv, ping, ps, rm, top, and vi. BusyBox provides minimal versions of many common UNIX commands in a single executable to reduce the size of the system. Other default applications may include services like bootchartd, crond, and syslogd.
Strategies for developing and deploying your embedded applications and imagesMender.io
We will delve into multiple strategies you can use for developing and deploying code to embedded devices. We will compare and contrast the following:
– Lightweight package managers: ipkg/opkg
– Desktop package managers: rpm/deb
– Configuration Management Tools
– Smart Package Manager
– Yocto Runtime Package Management
– PXE boot
– OTA updaters: Mender
As with any decision, it is rarely black-and-white and we will cover some of the benefits and the limitations of all the different methods mentioned, to make sure you have the most critical information needed to decide for yourself whether a given strategy would be a good fit for your embedded application development.
This talk will cover how different mechanisms are implemented in the real world and how choosing the right strategy, understanding its benefits and drawbacks, can speed up and improve the whole development process.
Presentation covers Embedded Linux systems basics including hardware, software and architectural concepts. Yocto, Raspberry Pi, Electronics Hardware, and Embedded Architecture.
The document discusses two solutions for automating the deployment of FreeBSD and PC-BSD systems. Solution 1 involves writing custom installation scripts and configuring networking by hand, while Solution 2 uses the pc-thinclient utility included with PC-BSD and TrueOS. The document then provides details on setting up and customizing automated installs using pc-thinclient, including installing packages and customizing user accounts. It also discusses scaling the solution and provides tips for optimizing install performance.
This document discusses two solutions for automating the deployment of FreeBSD and PC-BSD systems. Solution 1 involves writing custom installation scripts and configuring networking by hand, while Solution 2 uses the pc-thinclient utility included with PC-BSD and TrueOS. The document then provides details on setting up and customizing automated installs using pc-thinclient, including installing packages and customizing user accounts. It concludes by discussing tips for improving scalability and speeding up installations.
The document discusses two solutions for automating the deployment of FreeBSD and PC-BSD systems. Solution 1 involves writing custom installation scripts, while Solution 2 uses the pc-thinclient utility included with PC-BSD and TrueOS. The utility allows deploying diskless clients that PXE boot and connect to a server, simplifying management. Customizing the automated install process is covered, such as changing packages, user setup, and running commands. Tips for improved scalability and speeding up installations are also provided.
The document discusses two solutions for automating the deployment of FreeBSD and PC-BSD systems. Solution 1 involves writing custom installation scripts and configuring networking by hand, while Solution 2 uses the pc-thinclient utility included with PC-BSD and TrueOS. The document focuses on Solution 2 and provides steps for setting up an automated installation server using pc-thinclient, including installing required software, customizing installations, and improving scalability. Examples are given for configuring disk layouts, installation archives, user management, and more.
The document discusses automating the deployment of FreeBSD and PC-BSD systems using the pc-thinclient utility. Solution 2 uses pc-thinclient to automate network installations of systems using PXE boot and allows customizing install scripts and archives. Key steps include installing the thin-client server, enabling PXE boot on clients, and customizing installation options in /home/thinclient directories. The approach provides scalable, automated deployment of systems.
Lightweight Virtualization with Linux Containers and Docker | YaC 2013dotCloud
This document provides an overview of lightweight virtualization using Linux containers and Docker. It begins by explaining the problems of deploying applications across different environments and targets, and how containers can help solve this issue similarly to how shipping containers standardized cargo transportation. It then discusses what Linux containers are, how they provide isolation using namespaces and cgroups. It introduces Docker and how it builds on containers to further simplify deployment by allowing images to be easily built, shared, and run anywhere through standard formats and tools.
Lightweight Virtualization with Linux Containers and Docker I YaC 2013Docker, Inc.
Docker provides a standardized way to build, ship, and run Linux containers. It uses Linux kernel features like namespaces and cgroups to isolate containers and make them lightweight. Docker allows building container images using Dockerfiles and sharing them via public or private registries. Images can be pulled and run anywhere. Docker aims to make containers easy to use and commoditize the container technology provided by Linux containers (LXC).
This document discusses tools for managing large scale computing environments: Cobbler, Puppet, and Func. Cobbler is a provisioning system that automates OS installation and configuration. Puppet is a configuration management tool that defines system configurations and ensures consistency. Func provides a Python API to manage systems, allowing them to be treated as Python objects. It includes modules to control services, run commands, and integrate with monitoring tools like Nagios. These tools help reduce complexity and enable consistent configuration of large numbers of systems.
Cobbler, Func and Puppet: Tools for Large Scale EnvironmentsMichael Zhang
This document discusses tools for managing large scale computing environments: Cobbler, Puppet, and Func. Cobbler is a provisioning system that automates OS installation and configuration. Puppet is a configuration management tool that defines system configurations and ensures consistency. Func provides a Python API to manage systems, allowing them to be treated as Python objects. It includes modules to control services, run commands, and integrate with monitoring tools like Nagios. These tools help reduce complexity and enable consistent configuration of large numbers of systems.
The document discusses automating the deployment of FreeBSD and PC-BSD systems using pc-thinclient utility. It describes using PXE to boot clients over the network and install operating systems from a server. Key steps include setting up the server with DHCP, ports tree and installation files. Customizations like disk layout, packages and scripts allow automating varied installations for multiple clients from a centralized management point. Tips provided optimize the process like using ZFS, SSD and tmpfs for improved scalability.
The document discusses the Linux boot process and management tools Grub and Dracut. It provides an overview of the BIOS and UEFI boot methods, the kernel loading process, and the role of the initramfs and systemd. It describes Grub fundamentals like the multi-stage boot process and configuration via grub.cfg. Diagnostic tools like the Grub shell, initramfs shell, and systemd targets are covered. The document concludes with demonstrations of BIOS vs UEFI boot and recovering from a boot failure.
The document discusses building an emulation environment called MIPS-X for analyzing MIPS-based IoT devices. It introduces the presenters and their backgrounds in IoT and embedded security research. It then covers challenges in emulating MIPS CPUs and building toolchains, kernels, and filesystems to support running IoT firmware. The talk agenda is outlined which includes demos of using QEMU and Docker for MIPS emulation. Next steps discussed are refining emulation of device NVRAM and developing automated build systems for analyzing IoT firmware.
This document introduces Docker and provides an overview of its key concepts and capabilities. It explains that Docker allows deploying applications into lightweight Linux containers that are isolated but share resources and run at native speeds. It describes how Docker uses namespaces and cgroups for isolation and copy-on-write storage for efficiency. The document also outlines common Docker workflows for building, testing, and deploying containerized applications both locally and in production environments at scale.
Introduction to Docker at SF Peninsula Software Development Meetup @GuidewiredotCloud
This document provides an introduction and overview of Docker and containers. It discusses that Docker is an open source tool that allows applications to be packaged with all their dependencies and run as isolated processes on any machine. Containers provide lightweight virtualization that improves efficiency by sharing resources but still isolating processes. The document outlines how Docker uses containers powered by Linux namespaces and cgroups to package and deploy applications easily and consistently across environments.
The document discusses automating the deployment of FreeBSD and PC-BSD systems using the pc-thinclient utility. It describes how to set up a server running PC-BSD to PXE boot clients and install them using configuration files. Customizing installations for different disk layouts, packages, and archives is covered. Tips on performance and future improvements are also provided.
This document provides an introduction to Linux, including its history and architecture. It describes Linux's origins from Unix in the 1960s and the development of the Linux kernel by Linus Torvalds in 1991. It outlines the key components of a Linux system, including the kernel, shell, file system, processes, networking, and desktop environments. It also discusses booting a Linux system and provides resources for learning more about Linux distributions and building your own operating system.
Similar to The Deck by Phil Polstra GrrCON2012 (20)
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Digital Marketing Trends in 2024 | Guide for Staying Ahead
The Deck by Phil Polstra GrrCON2012
1. Hacking and Forensics on the Go
Philip A. Polstra, Sr.
@ppolstra
DrPhil@polstra.org
http://ppolstra.blogspot.com
2. What is this talk about?
● Hacking and/or forensics with small, low-
power devices
● ARM-based Beagleboard & Beaglebone
running full suite of security/forensics tools
● Porting tools to a new platform
● USB forensics (now at high speed!!)
3. Why You Should Care
● A full set of tools that can fit in a child's lunch
box
● A full-featured Linux install for flexibility
● Low-power devices can run for days or weeks
on battery power
● Small devices can be planted for later retrieval
● Did I mention high-speed USB?
4. Who is this handsome man anyway?
● Professor and Hacker in Residence at a medium
size (1800 student) private university in
Dubuque, Iowa
– Programming from age 8
– Hacking hardware from age 12
– Also known to fly and build airplanes
5. Roadmap
● Choosing a platform
● Selecting a base OS
● Building a base system
● The easy part – leveraging repositories
● The slightly harder part – building tools
● Building your own accessories
● Demonstrations
● Future directions
6. Choosing a Platform
● Small
● Low-power
● Affordable
● Mature
● Networking built in
● Good USB support
● Convenient input and output
7. And the Winning Platform is...
● Beagleboard
– 3.25” square
– <10 Watts
– $149
– Based on Cortex A8
– 100 Mbs Ethernet built in
– 4 high-speed USB plus USB-on-the-go
– DVI-D, S-video, and LCD output
– RS-232, webcam, audio, and microSD
9. Selecting a Base OS
● Angstrom comes in the box
– Optimized for hardware
– Nice package management
– Poor repository support for our purposes
● Ubuntu is available
– Backtrack is based on Ubuntu
– Ubuntu is very popular
– Good repository and community support
10. Building a Base Device
● Upgrade to 16GB or 32GB microSD (8GB
would work, but go big)
● Download an image for microSD card
– Canonical image or
– Robert C. Nelson demo images
– I used Nelson's because they are tweaked for
Beagleboard and updated frequently
● Good instructions available at
http://elinux.org/BeagleBoardUbuntu
11. The Easy Part – Using Repositories
● Many of the tools we want are available in the
standard Ubuntu repositories
● Some are also available as .deb files
– Packages written in interpreted languages
(Java, Python, PERL, Ruby) usually work out
of the box
– C-based packages depend on libraries that may
or may not be available/installed
12. The Harder Part – Building Your
Own Tools
● Native or cross-compile?
● Native
– Straightforward
– Can be slow on 1GHz ARM with 512 MB
RAM
● Cross-compile
– A bit more complicated
– Take advantage of multi-core desktop with
plenty of RAM
13. Native Compilation
● “Sudo apt-get install build-essential” is about
all you need to be on your way
● Something to keep in mind if you SSH in and
use DHCP: Ethernet is via USB chipset and
MAC address varies from one boot to next
which leads to different address being assigned
14. Cross-Compile Method 1
● Download a toolchain “wget http://angstrom-
distribution.org/toolchains/angstrom-<ver>-armv7a...”
● Untar toolchain “tar -xf angstrom-<ver>-armv7a-linux-gnueabi-
toolchain.tar.bz2 -C”
● Setup build environment “. /usr/local/angstrom/arm/environment-setup”
● Download source
● Configure with “./configure --host=arm-angstrom-linux-gnueabi –
prefix=/home/...”
● Build with “make && sudo make install”
● Copy binaries to BB-xM
● Could have problems if there is a kernel mismatch between setup and what
is installed to BB-xM
15. Cross-Compile Method 2
● Install a toolchain as in Method 1
● Install Eclipse
● Install C/C++ Development Tools in Eclipse
● Download software
● Use makefile to create Eclipse project
● Create a Build Configuration in Eclipse
● Compile
● Move binaries to BB-xM
16. Create a Project from the Makefile
● Can have a makefile based project
– Simple
– Requires slight modification of makefile
● Can use makefile to create Eclipse project
– Slightly more involved
– Dependencies and special compile flags can be
divined from makefile
– More flexible if you want to make
modifications
17. Create a Build Configuration
● Right-click project in Project Explorer select
Build Configurations-Manage
● Click New to create new configuration
● Set the paths to point to cross-compilation tools
for installed toolchain
– Set compiler, linker, and assembler commands
– Set include and library paths
– Good tutorial on http://lvr.com
18. Cross-Compile Method 3
● Same as Method 2, but with the addition of
remote debugging
● Has advantage of easy transfer of binaries
● In Eclipse under Mobile Development add
– C/C++ DSF GDB Debugger Integration
– C/C++ Remote Launch
– Remote System Explorer End-User Runtime
– Remote System Explorer User Actions
19. Cross-Compile Method 3 (contd.)
● Create /etc/hosts entry for BB-xM IP
● On BB-xM install SSH & GDBServer
– “sudo apt-get install ssh”
– “sudo apt-get install gdbserver”
● Manually SSH to BB-xM to make sure it works
and to set up key cache
● In Eclipse create a connection
● Create .gdbinit file
● Create debug configuration
20. Create a Connection
● Open Remote System Explorer view
● Select Connection->New->Linux
● Use BB-xM IP with options ssh.files,
processes.shell.Linux, ssh.shells, and
ssh.terminals
● After creating connection enter IP, user, and
password under properties
21. Create .gdbinit
● Change to the directory with your source code
● “touch .gdbinit”
● Go forth and have fun
22. Create Debug Configuration
● Run->Debug Configurations->C/C++ Remote
Configurations
● Main tab – set configuration
● Set remove absolute path
● Commands to execute before “chmod 777”
● Set path to GDB debugger
● Set the GDB port to an appropriate value
41. WTF – I thought you said there would be
forensics in this talk!
42. USB Forensics – Now at High
Speed!!
● Use a magical USB hub
– Everything connected to magic hub
automatically mounted read only
– Everything not connected to the magic hub is
mounted normally (probably with a prompt,
etc.)
● Initially wanted to dive in and hack USB
drivers
– But there is a better way! ...
43. Enter Udev Rules
● Udev rules allow you to handle what happens
when devices are connected, disconnected, etc.
● Every block device connected downstream of
magic hub (parent with appropriate VID/PID)
is automatically mounted read only
● Suitable for hard disks and ANYTHING that
can be mounted via USB
47. Future Directions
● Continue to add useful packages as need arises
● Optimize some packages for BB-xM
● Other output devices
● Custom printed case now available
● Associate with a standard pentest distro
● Port to another platform
● Full on weaponization (aviation twist?)