zardus/idalink

Some glue facilitating remote use of IDA (the Interactive DisAssembler) Python API.

idalink's Issues

using screen vs.TVHEADLESS

Any reason why you use screen and not set the TVHEADLESS env variable to 1?

GPLv3 vs. BSD license contradictions

Despite the LICENSE file having been changed to BSD-2-Clause as part of issue #7, all idalink/*.py files still have headers indicating they're under GPL-3.0+ license.

Can you please clarify whether those files are intended to be under BSD now and, if so, fix all the files to say so?
Otherwise the GPLv3 license text will be needed, too.

BSD License

Would you mind dual-licensing idalink with the BSD license?

A py3k question has appeared

Hello @zardus,

do you have any idea on how to enable idalink, or more specific rpyc to talk to ida again after angr hits py3k? We're having a complete self developed idarpc service with which we generated thousands of CFG's through rpyc, transform them to angrs understanding of basic blocks and use sym exec on them. With the upcoming changes, I think that's it - using IDA as a backend for angr won't be possible anymore.

By any chance, any thoughts on that? Personally, I don't see IDAPythong going to py3k anytime soon. Angr backwards supporting py2k is also out of question and rpyc being able to bridge py2k and py3k has been tried and burried deeply underground.

OS X/macOS and/or virtual environments

Is this known to work on OS X/macOS? If so, is it known to work if installed in a virtualenv?

The reason I ask is of course that I don't seem to get a connection and I know from experience that getting a launched process to run the right python can be tricky on OS X.

0.11 on pypi vs 0.10 here?

What I'm "really" trying to do is use angr with the ida loader, so my original idalink install was done with pip install angr. This repo appears to be clearly a further development, but at the same time cle used by angr seems to rely on argument names that are different in the two sources. Is the intention for cle to work with the latest idalink should the used by cle/angr/pypi be considered a fork?

idalink will loop forever if idal is ran for the first time

idalink will loop forever if idal is ran for the first time. There is an agreement window shown at the start of idal if this is the first time of its startup. idalink doesn't handle that.

License is too restrictive

The current license, GPLv3, is too restrictive for widespread adoption.

A move to a less restrictive license, so that others can incorporate idalink more easily into proprietary software and then improve idalink naturally instead of being forced to GPL-license it or not use idalink at all might be a good idea. Under the current GPLv3 license, many of the companies that use IDA (which clearly is a requirement) might not be using idalink because they cannot easily distribute it as part of their own proprietary software. A too restrictive license can be cause for software not being adopted (carmaa/inception#105). We should preemptively improve on this situation.

I'd love to see idalink move to BSD (or MIT), or at least LGPL.