[JDEV] 1.4.2-test tarball, HTTP proxy, and zero-k auth case sensitivity

Piers Harding piers at ompa.net
Wed Oct 17 05:24:55 CDT 2001

 Hi Jeremie,

Hows tricks?

I have tried building this on HP-UX 11.0 ( 32 bit and 64 bit ), but I still get that problem with the pth. - not sure what it is, but I remember mucking about with the pth test suite a few weeks back, and I got to a point where it seemed to me that setting thread priorities was a problem?

Any ideas?


On Tue, Oct 16, 2001 at 01:31:28PM -0500, Jeremie wrote:
> I'll just roll a few things into one message...
> First, anyone interested in helping test the 1.4.2 server before release
> to make sure it works on their platform or just for general functionality,
> please grab the tarball at:
> http://download.jabber.org/dists/1.4/final/jabber-1.4.2-test.tar.gz
> The only changes in cvs so far is a HUP fix and smart admin auto-reply.
> I've tested personally on linux, solaris, and darwin/OSX.  The build is
> supposed to work for the latest cygwin on win32 as well, but it's not
> quite right, so if you have cygwin and can fix Makefiles and get it to
> build many would appreciate it :)
> Send any problem reports, platform fixes and warnings, or even if it just
> works on a new platform, to jer at jabber.org, and I'll get it into cvs for
> the 1.4.2 release.  If your testing functionality, the only major changes
> were to the presence management and auth/reg code, so look there for any
> oddities.  I'll have a full changelog available soon.
> On the HTTP proxy bit, yes the existing hack in 1.4.1 is just that, and
> only works with some proxies, as well as it's not in the new CCM running
> on jabber.org.  Yes, the only real way to get through any proxy is with
> polling HTTP requests, and yes there is experimental support out there for
> it, check out "wcs" in cvs (which uses the "http" component as well) or
> look at the original announcement at http://jabber.org/?oid=1102 which is
> being used in a few places... I'm planning on spending some time upgrading
> and doing another release of wcs/http after 1.4.2 is out.
> On the 0k auth hash case sensitivity, the spec is to blame, it should make
> it very clear that the exact use requires the hashing always to be of the
> lower-case hex string.  It can't be case-insensitive since hashing an "A"
> isn't the same as hashing an "a", and when validating 0k auth on the
> server, it must first re-hash the given hash to validate it.
> Jer
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev

More information about the JDev mailing list