Jump to content

muhfugen

Members
  • Content Count

    0
  • Joined

  • Last visited

Community Reputation

323 Excellent

2 Followers

About muhfugen

  • Rank
    Newbie

Recent Profile Visitors

158 profile views
  1. Could an admin here give me rights to respond to private messages? I developed a couple cracks and posted them here, for Cisco Firepower Threat Defense and Palo Alto Network's firewall that other people keep on PMing me about but I cant respond because I dont have rights.
  2. Hey guys, I got bored and developed a crack for Palo Alto Networks virtual firewall. Just like my crack for Cisco Firepower Threat Defense, you do it all yourself so there is no question about wether or not malware has been installed. This assumes you have enough experience with the Linux command line to be able to edit text files, and understand the basics of using a hex editor. And although these instructions are for vSphere they should be easily adaptable for other hypervisors. I dont have a physical device to play with so i'm not sure if you can crack hardware appliances with these instructions. [Hidden Content]
  3. The steps are literally in the instructions you quoted, and which you werent supposed to quote.
  4. You run the commands I specified in the command prompt of the 2nd picture you posted
  5. Any chance someone could share AIR-CTVM-K9-8-5-140-0.aes
  6. No idea, I dont have a physical ASA and have no intention of purchasing one. If someone wants to send me Bitcoin to buy one so I can play with it I could give it a shot. But take note that I cracked this when I was out of work, and since have a new job and significantly less free time. Also it would probably cost the same amount for you to just buy a old server and run the virtual appliance on there.
  7. You should be presented with the option to do so when you add the FTD to the FMC. If you clicked past it already, go to Devices->Device Management and click the pencil icon for your FTD device (or HA pair), then click the Summary tab, and the pencil next to where it says Licenses. This of course assumes you've followed my instructions on applying the crack
  8. Yeah i've encountered this problem before, the way I fixed it was to delete all the vNICs from the FTD in vCenter, then re-add them using VMXNET3 vNICs, then rebooting the FTD. After this happens it should show your static address assigned to eth0 rather than br0 if you run ifconfig. 've also encountered issues that after reboots the pairing between vNICs and interfaces in the FTD will get mixed up forcing you compare MAC addresses inside the FTD to vNICs in vCenter and then reassign the vNICs to whatever port groups they should be attached to.
  9. Updated the crack instructions on page 10 for FMC 6.2.3.4 Updating the vulnerability database will not, updating the FMC may as it has in the 6.2.3 and 6.2.3.4 updates. The only things it will likely break though is export controlled features (which VPN and SSL platform features rely upon), and the bug fix for CSCve97160 to use SMB/CIFS v2 and v3. All the stuff involving the MySQL database and the unlimited evaluation should not be effected by a update to the FMC. Also I would not expect updates to the FTD devices to break anything. Even if the FMC gets broken, just follow my instructions on what to search for in the files and you should be able to fix it yourself barring a major change to the licensing system. In case it takes me a while to update the instructions as has happened recently because the 6.2.3 update never showed up in my console and I had to download it elsewhere. No idea, I dont have a physical FTD or (modern) ASA appliance, just a very old ASA 5510 which cant run firepower services. If someone has one in a test environment they wouldnt mind me playing with, or wants to send me ~$250-$300 in bitcoin so I can get a 5506X off eBay, I could try to support physical appliances with this crack. No guarantees I would be successful though. I haven't verified this, but if I had to guess it may only be created when you enable evaluation mode in the FMC. And as other people have said you may have to register a FTD with the FMC as well before this file is created. I have not tried using the FTD at all without a FMC, sorry.
  10. Updated the crack instructions on page 3 for FMC 6.2.3.4
  11. GoldenTulip, I can't respond to private messages because of my post count so i'll post it here. Unfortunately cracking the classic licenses for NGIPSv would be far more involved than what I did with the evaluation crack. It uses a compiled code rather than just perl scripts which makes figuring out what it is doing far more difficult, and I generally avoid dealing with assembly code as much as I can. As I have no use for NGIPSv I dont plan on sinking a ton of time in to cracking it. Sorry.
  12. GoldenTulip, I can't respond to private messages because of my post count so i'll post it here. Unfortunately cracking the classic licenses for NGIPSv would be far more involved than what I did with the evaluation crack. It uses a compiled code rather than just perl scripts which makes figuring out what it is doing far more difficult, and I generally avoid dealing with assembly code as much as I can. As I have no use for NGIPSv I dont plan on sinking a ton of time in to cracking it. Sorry.
  13. GoldenTulip, I can't respond to private messages because of my post count so i'll post it here. Unfortunately cracking the classic licenses for NGIPSv would be far more involved than what I did with the evaluation crack. It uses a compiled code rather than just perl scripts which makes figuring out what it is doing far more difficult, and I generally avoid dealing with assembly code as much as I can. As I have no use for NGIPSv I dont plan on sinking a ton of time in to cracking it. Sorry.
  14. You need to have devices added to your FMC, if there aren't any FTD devices registered to the FMC then there wont be any evaluation licenses Read the manual on deploying a device, this is covered there.
×
×
  • Create New...