-
Notifications
You must be signed in to change notification settings - Fork 137
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
ESX back-end support #30
Comments
That would be really cool! If I were you, I would check for Packer templates as it is the main tool we wrap around. You could check this for example: https://github.com/tsugliani/packer-vsphere-templates. Don't hesitate if you have any questions! |
So I pretty much have it working. I'm trying to go through and figure out the past way to do this, if we want to merge this in with the current malboxes code. I currently only implemented it on the win10_64_analyst.json profile, it requires pretty much a complete change. Also, the Autounattended.xml need a small change in the DiskConfiguration section. Lastly I had to change box_win.rb file, but that shouldn't be a big deal because we can add logic in there to do the vmware piece of it only if the provider is vmware-iso. Here's my proposal:
Does that make sense? Would love any sort of discussion on possible other ideas or options. In reality malboxes should work with VirtualBox, VMWare Workstation, ESX - which are probably the 3 most popular. |
I agree with the additionnal provider option in |
Really? It should be here: https://github.com/gleblanc1783/malboxes I will commit my changes once I am done testing tonight. Then will work on making the other changes to the other profiles and any edits to malboxes.py. |
Yeah, my bad, I should buy glasses I think eheh. Cool! I look forward to review that! |
Your proposal sounds great @gleblanc1783! I would also be interested in hearing performance numbers. How fast is using ESX versus VirtualBox? |
Okay a solid first pass at this is done. You can view the changes here, and I will have a PR submitted sometime this week after we review. Sorry it took me so long, between the time it took to consistently try and create the windows images and working through some non-specific bugs and gotchas with Packer and Vagrant it's working now. Description 1. Config changes
2. New builder
3. Vagrant
Requirements
Usage
Note: If you're not using paid/commercial version of vSphere, you can still use this. Just log into your ESXi server, and clone the VM yourself OR use the base image created by TODO
Please let me know if this works for you and any bugs/concerns! |
Everything you say sounds fine. Send the pull-request! Let me know if you need a hand in doing that. |
Was this pulled in? @obilodeau @gleblanc1783 |
No PR was made and no commits have been done after February 27th on his fork so I don't know what is the status of this. |
Even if @gleblanc1783 is no longer interested, I am. I will get back to it and merge his stuff. I now have access to an ESX server with enough resources to do some tests. |
Sorry, all. I've been busy with work and sidetracked with fixing my ESX Server to test this again. @obilodeau -- feel free to take my code and run with it. I was pretty close. Will be following this thread to see how it makes out. |
I got it working today, for the most part. Couldn't get winrm to connect
though
…On May 31, 2017 2:56 PM, "Gregory LeBlanc" ***@***.***> wrote:
Sorry, all. I've been busy with work and sidetracked with fixing my ESX
Server to test this again.
@obilodeau <https://github.com/obilodeau> -- feel free to take my code
and run with it. I was pretty close.
Will be following this thread to see how it makes out.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGffqsPoOX2U-PxygEwLE4YRZo4oL5nBks5r_bfVgaJpZM4MDgXD>
.
|
@treed593 have you tried increasing the timeout limit? |
Not yet, that's the next thing I plan on trying in the morning. It didn't
look like the script to enable winrm had run either
…On May 31, 2017 10:58 PM, "Hugo Genesse" ***@***.***> wrote:
@treed593 <https://github.com/treed593> have you tried increasing the timeout
limit
<https://github.com/GoSecure/malboxes/blob/master/malboxes/profiles/snippets/builder_virtualbox_windows.json#L8>
?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGffqph78HnLC203mjfTx6BqfB5j49LXks5r_ijxgaJpZM4MDgXD>
.
|
I extended the timeout, so we will see but the VM still seems to just be sitting on the desktop with the Network "Do you want to allow sharing" window open @Svieg |
What version of windows are you trying to install? Might be something wrong with the |
win10_64, I didn't but @gleblanc1783 may have in his fork. I will compare the one from malboxes/master to gleblanc1783/master |
Looks like the issue was a network issue with the ESX server. I am working through some other issues now with chocolatey |
I was able to get winrm and chocolatey to build correctly, the last issue I am facing is: ==> vmware-iso: Keeping virtual machine registered with ESX host (keep_registered = true) ==> Some builds didn't complete successfully and had errors: ==> Builds finished but no artifacts were created. |
Sorry for not saying that earlier but can you run malboxes with the |
2017/06/02 11:11:14 ui error: Build 'vmware-iso' errored: lstat malboxes: no such file or directory ==> Some builds didn't complete successfully and had errors: ==> Builds finished but no artifacts were created.
|
Any ideas @Svieg |
Not really, it doesn't seem to find the malboxes file and and I don't why it is looking for it honestly as it the host script. I don't have access to an ESX server too. Maybe @obilodeau can save the day |
Yea it is strange, hope @obilodeau or @gleblanc1783 can help |
I'm finishing another project and I have a presentation coming up this week, I don't h ave time to reproduce right now, unfortunately. For some reason, the vmware-iso plugin doesn't have access to the malboxes files. This might be due to several reasons. I would search for packer related problems with missing files removing references to "malboxes" and try to find the root cause. |
Did you pull my code from my repo? I think I got around this, trying to remember. In your config file for packer did you change the format to "ovf"? |
Yea, I pulled from you and it was over, yes
…On Jun 5, 2017 4:17 PM, "Gregory LeBlanc" ***@***.***> wrote:
Did you pull my code from my repo? I think I got around this, trying to
remember.
In your config file for packer did you change the format to "ovf"?
hashicorp/packer#3087 <hashicorp/packer#3087>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGffqtK1MMKmErCQbTRUhWVj-w4c4Hj7ks5sBGI7gaJpZM4MDgXD>
.
|
I love this! I tend to use my own ESX server for malware analysis. I am thinking about integrating ESX into malboxes with the Vagrant ESX plugin.
Any interest?
The text was updated successfully, but these errors were encountered: