Archives week 44 of 2004

The apparatus described here is intended to allow you to transfer, for instance, a server computer from one electrical connection to another without interrupting power to the machine. The apparatus consists of a flexible set of prongs arranged in such a way that they can slide between a North American-style power plug and socket (from ...

Just realised that Shtoom will have the authentication mechanism already written (somewhere), since it acts as a client to normal (authenticating) servers. Should have just wandered over there and pulled out the authentication-generation code.

I've developed a bit of a blind spot there I guess, wanting to avoid learning a large package while on a ...

Not able to do much on it yet, but setting up an SSH session was so much faster it's almost scary. Hopefully with just the demo server running on it we'll retain some of that snappiness.

This little detour trying to get authentication working has taken way more time than it should have. Thinking I may just back the changes out and ignore the question for the demo. Blah.

It's interesting talking with people who are watching the US slide deeper and deeper into unsustainable debt while ticking off just about everyone else in the world. There's talk of massive recession, complete devaluation of the dollar, and basically a collapse of what passes for society down there.

The problem, of course, is that as ...

"So," figures I, "really should have at least some user authentication in the SIP server." Little did I realise that the Twisted code, while it supports authentication quite simply on the server, doesn't seem to have any code on the client side.

That is, the server can handle a client that knows how to authenticate, ...

AFAICT, the SIP protocol has no agreed upon conventions for registering display-names or other meta-data. That is, while you can attach display-names to just about every URI, there's nothing stating which URI's display name should be considered canonical when parsing a registration request. For now I'm assuming I should display the contact field's display name. ...

Have discovered why it is that the dratted x-lite refuses to log in to my registration server despite the fact that clients written in Twisted work perfectly well. x-lite automatically searches for and finds the NAT firewall, then configures it's return address as the address of the firewall. Result is that the registration server responds ...