I have no insight into the procurement process for the HitBox software and can't speak to that. I do know that it just added to my stress level when trying to troubleshoot a problem with our intranet web site. I never followed the entire thing through because I just undid the parts that I needed to. Another hour and I would have had the rest of the package (I think. There were many nasty eval tricks in use at the time). Regarding your software and my deobfuscator. The only other feature I'm aware of in your software is the replacement of constant strings with encoded values (either as hex codes or as join/map/chr expressions). I'm not asserting that there aren't, I just don't know of them. So of those two features B::D handles one and the other may or may not be handled by the perl interpreter depending on how aggressively it optimizes the optree. Also, when I say B::D "handles" symbol renaming it only does it in the sense that if your original symbol was $good_stuff and it became $g1235324 then it is useful to re-rename it to something like $progaganda merely to keep it distinct from @interrupts which became @g1243424. So in no case does B::D reconstruct information that isn't already present in the source to begin with.
| 