[Pkg-anonymity-tools] RFS: libfte and fteproxy

[Kevin P Dyer]

On Tue, Mar 17, 2015 at 5:44 AM, Jérémy Bobbio <lunar at debian.org> wrote:

> Rolf Leggewie:
> > Kevin P Dyer, author of FTE had approached me in the past and together
> > we've put up a Debian package (well, two in fact) for inclusion in
> > Debian.  I am DM, my usual sponsor has been busy since the window on
> > jessie threatened to close.  So, here I am looking for a sponsor.
> >
> > https://fteproxy.org/
> > https://bugs.debian.org/770603 (libfte ITP)
> > https://bugs.debian.org/746554 (fteproxy ITP)
>
> I had a quick look. I did not try to build the packages.
>
> >
> http://mentors.debian.net/debian/pool/main/libf/libfte/libfte_0.1.0-1.dsc
>
> I'm not sure that the long description would be helpful to someone
> wondering "do I need this?"
>
> There's a README and a README.md, but only the first one is shipped. Not
> sure which is really useful in the context of Debian.
>
> >
> http://mentors.debian.net/debian/pool/main/f/fteproxy/fteproxy_0.2.19-1.dsc
>
> I see tests in fteproxy/tests. Any reasons not to run them at build
> time?
>
> I must say I'm a bit surprised to see fteproxy depends on obfsproxy.
> obfsproxy is for me an end-user application and not a library. Should we
> architecture things differently somewhere in the chain? I would assume
> more things should be moved in pyptlib but that's from an outsider.


I agree that, at a high-level, fteproxy shouldn't depend on obfsproxy.
However, obfsproxy contains some logic for how it interfaces with Tor when
in something called "managed" mode. This code is currently in obfsproxy,
but it should probably be in pyptlib. I can start a discussion with the Tor
folks about this.

-Kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-anonymity-tools/attachments/20150317/b9bd49a6/attachment.html>