The only reason any corporation I worked for purchased IDA Pro licenses was because I recommended it. The only reason I recommended it is because I could (barely) afford a personal license, and play with it in my own time.
Going forward they're going to miss out on this word-of-mouth marketing, which I expect will negatively affect sales expansion going forward.
Having paid for a home license last year (mostly for the ability to run Python scripts) and discovering the home version has a sabotaged python implementation (can only run scripts individually from the GUI instead of running them from the command line, and you don't get the toolkit to develop scripts/plugins), it seems kind of hilarious that the free version is so close in feature set to Home. What's the difference even? They're both for "non-commercial use only", is the (limited) python script interface the only reason to pay $365 a year now? That, Lumina, and email support?
I'd buy Home if it came in C167, not because I want to but because $365/year is still a lot less time than I'd spend writing/finishing a C167 module for Ghidra.
Anyway, the pricing model doesn't actually make any sense no matter how you slice it, and this latest announcement is even more bizarre. I really wonder how long for this world Hex-Rays products are, the always glacial development pace is still quite slow and as a new generation of people start by using Ghidra, there will IMO be less drive to buy corporate IDA renewals going forward.
If you're an exec at Hex-rays and you believe that Ghidra will eventually out compete you, then it makes sense to squeeze every penny you can before you're irrelevant.
To this very day, whenever I'm stuck slogging through the build or debug process of a Ghidra plugin that has a more mature alternative in the IDA universe, I occasionally let a tiny bit of that resentment bubble to the surface to propel me across the finish line.
Speaking of which, last time this came up on HN ilfak cruised into the comments a week later, all "I can not find your nickname in our database," and I didn't see the reply until a year later. Well, the HexRays database had no problem finding my-nickname-at-gmail for the purposes of bugging me to renew, and just in case anyone thinks I'm making this up, here's the order. I also have an email with the download link and serial number -- the ones that didn't work -- and the ghosted support requests spread throughout the following year.
I'm sure this is a Hanlon's Razor thing, I just want to make sure that any naive young hackers considering the possibility of a last-time-buy on a perpetual license understand what they are getting into.
************************************************************
* Your order has been accepted.
************************************************************
Please retain this receipt for your records.
This e-mail confirms your order placed with Hex-Rays.
Payment data
------------
Beneficiary : Hex-Rays
Address : Rue Rennequin Sualem 34
BE-4000 Liege
Website address : http://www.hex-rays.com
General conditions : https://www.hex-rays.com/products/ida/t&c.pdf
Order date : 15/05/2016 22:40:05
Order reference : deWerd_4732_20160515
Ogone Payment reference : 3016168801
Order description : IDA license
Total : 1129.00 USD
Charging method : MasterCard XXXXXXXXXXXX----
Sub-brand : UNDEFINED
Status : Authorised
Authorisation code : ------ Sorry for the English, I do not speak well -- so, some idioms
may be translated directly and be incorrect for understanding for
native.
This release should serve as a life lesson to those who consider
themselves as "people 'blue' blood." It aims - in some ways
to bring down pride (swallow their pride), to tell these people
where to get off. Show that, besides them, there are other people
who should at least respect, appreciate their work and consider to
their opinions (or at least listen to).
This release is dedicated to one man and one company, which behave
antisocial, defiant, arrogant, are not considered to anybody or
anything, and therefore need to conduct a little "educational" work
from the community.
*** Let's start in order: one man - Ilfak Guilfanov.
I wanted to write a lot, then I thought - it makes no sense.
And so, in principle, nothing much to tell. Those who are "in" know
a lot about this person. It is impossible to buy IDA even if you
really want to do. I described some details about this in my blog,
'ida' tag (do not linking here, if you need - you will find it).
Also, you can read some more here (Russian only):
I apologize to crackers who were recruited in HexRays SA, you are
in some measure also falls under attack. But your head, sadly,
leaves no other choice.
In December 2007, after a memorable revelations of Ilfak in the
topic http://www.idapro.ru/forum/viewtopic.php?t=463, occurred
after warez-release of the IDA v5.5, I created another topic
http://www.idapro.ru/forum/viewtopic.php?t=458. In it I outlined
some thoughts about "double standards" of the author of IDA. Just
a small example. Struck up a brief conversation, which resulted in
Ilfak behaved absolutely inadequate (in his usual manner) and I was
banned on the forum. But that's not all. Before I was banned, he is
sent me a private message (PM):
I recommend to reconsider your attitude to people and to express
your thoughts in dealing with them.
In any case, at the moment you "reap" is what you had "sow" by
yourself.
I do not soft-pedal such things.
*** Next: company - ESET - NOD Antivirus developer
There is a saying: "Curses like chickens come home to roost"
(I have already voiced it in relation to you in 2008-2009th years).
Now it's time.
So, the characters from ESET (a minimum):
* J M - the main short-sighted and po-faced personage
* M Z (Customer [Un]Care; [email protected])
* D N (Virus Researcher)
The ESET company treats software developers (small companies and
individual developers of shareware-products) as a shit, and does
not hide this.
Full version: https://pastebin.com/2EXSaq11hahaha I knew it was legendary NFO.
https://reverseengineering.stackexchange.com/questions/22676...
I find Ghidra to be much better at this, since people actually write loafers for it and you get a decompiler “for free”.
For the obscure architectures Ghidra does support, it's way better than IDA by virtue of having a decompiler alone. Even if the decompilation is subtly wrong, the broad strokes are so much easier to navigate that finding the right method to go through by hand is much easier.
And once you dive into Ghidra's P-Code IR and more advanced plugin support and move beyond existing IDA plugins, it's honestly better than IDA for things nobody has done before.
Now, there are some obscure architectures like C167 for which we still lack a working Ghidra processor model, but this is only a matter of time - and once it comes, it will already be way ahead of IDA!
Disclaimer: BN founder, so biased of course but I'm pretty up-front about our strengths/weaknesses.
Thanks for the post though, as I did look into adding a new Architecture and the setup for defining a new ISA is much simpler than it is in even Ghidra/SLEIGH, so kudos to that. Maybe if I find myself with a lot of free time I will try adding something.
EDIT: But yeah, we designed our lifting to be as simple as possible. Specifically the way we handle flags tends to simplify much of the normal tedium around what's required for other decompilers. If you do decide to build a C167 module, give us a look again. :-)
You guys should try and get someone to write a book kind of like the IDA / Ghidra books that Chris Eagle did.
There could be something out there I just missed. Got any advice?
But more importantly, there are video excerpts for some basic features which should at least help with understanding how to use BN:
https://www.youtube.com/watch?v=xKBQatwshs0&list=PLCVV6Y9Lmw...
We've got a few more in the editing queue I need to clear out as well.
That said, I agree in terms of needing more intro tutorials would be helpful. Part of the problem with producing something like the IDA books is that we are under far too active development. Our UI and features have grown exponentially over the past few years so there was just never a good time to make something that wouldn't be out of date before it was even done.
You might be interested in joining the Binary Ninja slack which is a great community for getting questions answered. https://slack.binary.ninja/
There's also the free cloud version which doesn't have quite the same features but is an easier introduction without paying. https://cloud.binary.ninja/
You don't even need to describe the whole instruction set, just all the instructions that your target binary uses.
Such an amazing thing. And or1k is a nasty architecture with delay slots, which makes manual assembly reading quite tedious, etc. So the decompiler "C" output is very useful in this situation. I was in awe.
There's this new trend that big players (vendors with the size enough to appear in Gartner), that are investing heavily in bridging the gap between them and the end user, at the expense of the small players (independent IT Security consultants and boutique firms).
Their new SaaS offerings are marketed as next generation, while making it seem that their previous product is just legacy and no longer recommended. However, it's the legacy product what got them the growth to be there today.
Their On-Prem offering is still for sale, but at a cost very hard to justify. Almost no small player can afford such a cost.
I understand the business rationale behind a product management decision like this. But not because it was the right decision at the moment, automatically I have to feel great about it.
Unfortunately this leaves the hobbyist and individuals behind. ~$1K/year isn't out of the realm of what I pay for other tools, but it's really hard to justify it when I can open Ghidra and get 95% of the way there without the subscription model.
IDA really is great for handling edge cases and obscure architectures, but I hope this last switch-up by Hex-Rays pushes even more developer attention toward improving the open-source alternatives.