Code confiscator won't prevent it from being cracked.
PS. I have no intention to release the cracked binary or key or the core algorithm of your program.
But the protection is really weak, just to let you know.
This statement sounds approximately like: "Hey people, look, I broke someone's door and stolen his work."
Is it the reason for pride anyhow?
Absolutely not.
It is something shameful.
This is an entirely different thing, and blueskill's crack doesn't fit in the context of a burglary. He actually helped you quite a lot, he did you a favour, and some developers actually pay a lot of $$$ for people to crack-test their protection mechanisms and report back on success/failure and methods used. He didn't steal anything from you and openly told you what he's done, and still promised not to make the crack public.
Please don't be so hostile about this. See it as someone telling about a failure in your program, and one failure that actually might prevent you from having revenue from your program. Be thankful you now know your program can be easily cracked, there is no crack in the wild for it, so you have the time to improve your licensing mechanism.
Think of blueskill's action as free software engineering consultancy!
I might also give it a try with ollyDBG (my favorite for this kind of stuff).
When you invite somebody to your home, you don't expect, that he will broke your windows, saying:
"look, how easily I broke them, and now go and improve it, so I can broke it again".
Still with the burgraly analogies. It's not the same thing. His crack cost you nothing.