The ruby version of EyeWitness was just released, so it could (ideally) be included with the EyeWitness package. Also, the setup script was updated to include the necessary ruby gems.

Thanks for the update. Any update script that changes files outside of a debian packaging system is a huge no-no for us, and makes integrating this into a package much more difficult. It might take a while for us to sift through the code and disable this feature.

Is there a different way this could be packaged on my end to make it easier? The reason for the setup script is that it does require a few libraries/gems which weren't installed by default with Kali.

I saw you had asked about submitting the Ghost updates upstream to the maintainer. I have not done that as I don't believe it would provide significant value. The modifications were specific to allow EyeWitness to recognize when a website presented an invalid SSL cert. This is through making ghost generate a log, but then continue viewing the web page with the invalid cert. Additionally, I had to make a few changes to how xvfb is used within Ghost. While both changes are needed to best use EyeWitness, I don't necessarily believe they would work best for the typical use case of the library.

If that causes an issue, and you guys aren't able to include it, no worries. Users can still clone the repo to themselves locally if they want it. If there's some modifications I could make that would make life easier for you guys, don't hesitate to let me know. I'd be happy to look into the modifications that would help you all out.

ideally, you could tell us what pre-requisite gems are needed, and we would package them properly for Kali, thus being able to add them as proper, managed dependencies to the package.

Updated to new version 2.2-0kali1