FTE support for uProxy

[iislucas]

Tracking issue; this will live in the FTE repository (https://github.com/kpdyer/libfte).

[kpdyer]

I'll have to give this some thought, I have an impulse to create a uProxy/libfte repo. At the moment, [1] exposes a python API [2] only. I'm worried that, at least for the next month or two, it might be too chaotic to use [1] for uProxy work.

My thoughts:

1) Currently, all commits are going to [3]. 2) We move [3] to uProxy/libfte. 3) Once uProxy/libfte is stable, I can integrate it into [1] in a single atomic commit.

When 3) is complete, [1] will be a repo that provides a Python and C++ API. (Actually, I'm still worried that it might be too confusing if I have a single repo that provides a pure-python API, a C++-backed python API, and a pure C++ API.)

Thoughts?

-Kevin

[1] https://github.com/kpdyer/libfte [2] https://pypi.python.org/pypi/fte [3] https://github.com/uProxy/obfuscation/tree/master/transformer_fte

[iislucas]

I'd be ok with the code living in [3] until you merge it in one go back into [1].

If you have some good unit tests, then I'd be inclined to leave the 3 interfaces in the same repo ([1]) as the code that implements those interfaces. Helps to have it all in one place and know that there are indeed 3 interfaces for the code -- don't feel too strongly here -- probably best to proceed with edits in [3] and see what it looks like down the road?

[kpdyer]

Done!

Please raise all issues in: https://github.com/uproxy/libfte.

[dborkan]

Will be done in https://github.com/uProxy/uproxy/issues/247 (Support Obfuscation in uProxy)