-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please check my install.sh version; error catching #51
base: master
Are you sure you want to change the base?
Conversation
adding content of getfirmware into download.sh directly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Automation and implementation of a zenity gui to make the ./run.sh more user friendly (optional).
See github.com/n0s3y/FirmwareAnalysisSpace for a Vagrant & Virtualbox prebuilt box with FirmAE.
"Vagrant is an open-source software product for building and maintaining portable virtual software development environments;[5] e.g., for VirtualBox, KVM, Hyper-V, Docker containers, VMware, and AWS. It tries to simplify the software configuration management of virtualization in order to increase development productivity. Vagrant is written in the Ruby language, but its ecosystem supports development in a few other languages."
Nice work! I would recommend using a different demo firmware. This one only gets reachable via ICMP. There are plenty of others with web and/or other services available. |
Will do! Thanks for the feedback.
…On Thu, Oct 20, 2022, 13:43 Michael Messner ***@***.***> wrote:
Nice work! I would recommend using a different demo firmware. This one
only gets reachable via ICMP. There are plenty of others with web and/or
other services available.
—
Reply to this email directly, view it on GitHub
<#51 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZGUHM3QQNCV5QQNXB5MCKLWEEV7XANCNFSM6AAAAAAQ3AMAZQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sorry for the late and thank you for your hard work and passion. Also, I appreciate all comments. However, the Pull Request was updated many times. So, I wonder if this Pull Request was finished. Is this the final commit state for this Pull Request? |
Dear Mingeun,
The latest version on my FirmAE clone is the correct version. Sorry for
the many commits. I wanted to perfect this repo for my students
…On Sun, Oct 30, 2022, 13:43 Mingeun Kim ***@***.***> wrote:
Sorry for the late and thank you for your hard work and passion. Also, I
appreciate all comments.
However, the Pull Request was updated many times. So, I wonder if this
Pull Request was finished.
Is this the final commit state for this Pull Request?
—
Reply to this email directly, view it on GitHub
<#51 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZGUHMZQ7FBVZKH7BWSRCDLWFZUOLANCNFSM6AAAAAAQ3AMAZQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Yes this is the final commit state! |
Please take a look at my install.sh version considering the error handling.