Difference between revisions of "ECE497 Project BoneSAW"
(Edited section to reflect current project status) |
(edited exec summary) |
||
Line 28: | Line 28: | ||
== Executive Summary == | == Executive Summary == | ||
− | Network utility to detect vulnerabilities in networked BeagleBones. Typically these will be a misconfiguration of some sort. We will also apply this to specific networked examples found on shodan | + | Network utility to detect vulnerabilities in networked BeagleBones. Typically these will be a misconfiguration of some sort. We will also apply this to specific networked examples found on shodan. |
− | + | What Works: | |
− | + | Our web application connects to the Shodan API and can pull down a list of IP addresses for Beaglebones that are connected to the internet. It can also take an IP address as an input and either send it to the Shodan API and display the information Shodan returns like open ports and headers or use our own scanning utility to check for certain open ports and certain programs and return those results along with a security rating. The security rating is shown by changing the color of that part of the page where red is a high risk, yellow is a medium risk, and green is a low risk. | |
+ | |||
+ | What doesn't work: | ||
− | |||
− | |||
End with a two sentence conclusion. | End with a two sentence conclusion. |
Revision as of 19:53, 13 November 2017
Embedded Linux Class by Mark A. Yoder
Team members: Charles E. Beard and Luke Craig
Contents
Grading Template
I'm using the following template to grade. Each slot is 10 points. 0 = Missing, 5=OK, 10=Wow!
00 Executive Summary 00 Installation Instructions 00 User Instructions 00 Highlights 00 Theory of Operation 00 Work Breakdown 00 Future Work 00 Conclusions 00 Demo 00 Late Comments: I'm looking forward to seeing this. Score: 10/100
(Inline Comment)
Executive Summary
Network utility to detect vulnerabilities in networked BeagleBones. Typically these will be a misconfiguration of some sort. We will also apply this to specific networked examples found on shodan.
What Works: Our web application connects to the Shodan API and can pull down a list of IP addresses for Beaglebones that are connected to the internet. It can also take an IP address as an input and either send it to the Shodan API and display the information Shodan returns like open ports and headers or use our own scanning utility to check for certain open ports and certain programs and return those results along with a security rating. The security rating is shown by changing the color of that part of the page where red is a high risk, yellow is a medium risk, and green is a low risk.
What doesn't work:
End with a two sentence conclusion.
The sentence count is approximate and only to give an idea of the expected length.
Packaging
If you have hardware, consider Small Build, Big Execuition for ideas on the final packaging.
Installation Instructions
Give step by step instructions on how to install your project.
- Include your github path as a link like this to the read-only git site: https://github.com/MarkAYoder/gitLearn.
- Be sure your README.md is includes an up-to-date and clear description of your project so that someone who comes across you git repository can quickly learn what you did and how they can reproduce it.
- Include a Makefile for you code.
- Include any additional packages installed via apt.
- Include kernel mods.
- If there is extra hardware needed, include links to where it can be obtained.
User Instructions
Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.
Highlights
Here is where you brag about what your project can do.
Include a YouTube demo.
Theory of Operation
Give a high level overview of the structure of your software. Are you using GStreamer? Show a diagram of the pipeline. Are you running multiple tasks? Show what they do and how they interact.
Work Breakdown
List the major tasks in your project and who did what.
Also list here what doesn't work yet and when you think it will be finished and who is finishing it.
Future Work
Suggest addition things that could be done with this project.
Conclusions
Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.
Embedded Linux Class by Mark A. Yoder