On Fri, May 29, 2015 at 4:03 PM, Jonathan Bennett <[email protected]> wrote:
> I am making decent progress on the android implementation of fwknop. I > have rewritten the user interface nearly from scratch. I do have a couple > questions, though. > Excellent. > First, the existing android app is on the marketplace under the company > Maximum Idea. It would seem more appropriate for the app to be distributed > by Cipherdyne. I am certain there is some history there, but we should > consider pulling the old apps and publishing under the Cipherdyne name. > Agreed - sounds like you are suggesting an official marketplace account where fwknop apps are distributed, and your rewrite could serve as the basis for the client app. This assumes you are ok with distributing your app via the Cipherdyne account with you as the author, etc. > Also, in regards to capturing qr codes. There is an open source project, > https://github.com/zxing/zxing. This is Apache 2 licensed. I can call > their play store app. If it is not installed, the user is sent to the play > store to install it. This is not a terrible solution, but it seems that we > could include their library with our source and capture the qr code without > calling an external app. I prefer making this work for not only the ease of > use, but it also seems it would be more secure to stay within the fwknop > process. Thoughts? > Hmm, not sure about this one. There is precedent in fwknop currently for calling external programs from both fwknop and fwknopd, but it is done via execvpe() when available with no environment, and calling external programs generally allows fwknop to minimize library dependencies. fwknop executes wget in -R mode in order to resolve the external IP via SSL/TLS when wget offers this feature, and means that fwknop does not itself have to link against an SSL library. fwknopd executes firewall control binaries directly (iptables, ipfw, etc.) instead of linking against libraries the firewall projects may provide, and also even libpcap is an optional library dependency and can be eliminated at compile time if one is willing to run in --udp-server mode. But, the above is for the C implementation of fwknop, fwknopd, and libfko. On Android, would the zxing integration be done with their java code into your fwknop client java code? I see they seem to have a C++ component, but I'm assuming you're referring to the Java stuff, correct? If so, then integrating their java code into your client code would be a nice win for ease of use for sure. Or are you thinking of integrating the C++ code into libfko, and having a Java extension of this code like the current Android app? > With any luck, I might have a working prototype done this weekend. > Very cool. Thanks, --Mike > ~Jonathan Bennett > >
------------------------------------------------------------------------------
_______________________________________________ Fwknop-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fwknop-discuss
