-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 While testing with the HTTP_proxy stuff, I believe I've stumbled upon a bug in the server side.
I started fwknopd by hand with the --debug switch, and watched the stream. I then pushed a known good fwknop packet from a remote host. I found it in the output spew. Fwknopd complained that it contains non-base64 characters. I thought of this in the client : ### change "+" chars to "-", and "/" to "_" When we're pushing over http, we have to make this modification. I don't see that fwknopd allows for that modification when checking for base64 only chars. ~ Jonathan Bennett incomsystems.biz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkrhLl0ACgkQhFXk1UR7Wbd4XwCdHjdhgMU8mYaq/fkU+jndKy6F sQQAnjOK0QD/Qej0Y3J1deJY+czzOvcX =FZm1 -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Fwknop-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fwknop-discuss
