khan: fix pointer reference
khan: fix pointer reference

Using offsetof is very gross and probably suggests something is wrong
somewhere. Maybe we should store the server configuration on a separate
object from the khan configuration? But in the case of khan there isn't
really a concept of multiple servers...

N.B. We still have memory corruption.

urbit/urbit,ngzax/urbit,urbit/urbit,ngzax/urbit,ngzax/urbit,ngzax/urbit,urbit/urbit,ngzax/urbit,ngzax/urbit,ngzax/urbit,urbit/urbit,urbit/urbit,urbit/urbit,urbit/urbit