User Ratings

★★★★★
★★★★
★★★
★★
1
0
0
0
1
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 1 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 1 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 1 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 1 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • The two VMs (holynix v1 and v2) weren't able to get an IP adress with VirtualBox or VMWare Player (latests versions). I tried Bridged mode, host-only, I regenerated MAC address, tried to remove the network adaptor and re-create it... nada. Website of the project doesn't exists anymore and there is no way to report a bug except as a review...
  • While Holynix2 was released as a VMware appliance, it is possible to get Holynix2 working under Oracle VirtualBox. The holynix2.vmdk virtual hard disk is directly usable by VirtualBox. Just refer to it as an "existing" disk in VirtualBox's storage setup options, when you define a new guest. After using the disk image under VirtualBox, beware porting it back to a VMware environment. To get networking working, just open the file holynix2.vmx in a plain text editor. Use the MAC address in line 45, ethernet0.generatedAddress = "00:0c:29:13:21:b3", to force set the MAC address of the network adapter you assign to the Holynix2 virtual guest (hint: edit out the colons). Make sure also that the adapter is set to "VirtualBox Host-only" network. With this set up, you should see the Holynix2 guest respond to pings at address 192.168.1.88. DHCP on the host-only network is not required, as Holynix2's IP address is set statically. You can then run your exploits either on another virtual guest, or on the virtual host, as long as they have a network adapter on the host-only network. Other files in the Holynix2 distribution serve no purpose for, are not required by, Oracle VirtualBox. Good luck.
  • Previous
  • You're on page 1
  • Next