Ticket #167 (closed defect: wontfix)

Opened 13 years ago

Last modified 11 years ago

debathena-lert-server binds only to localhost

Reported by: broder Owned by:
Priority: trivial Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description (last modified by broder) (diff)

debathena-lert-server uses gethostbyname(uname().nodename) as the address to bind to. Unfortunately, on most Ubuntu systems, this works out to being 127.0.1.1 instead of the actual IP address, thanks to Ubuntu's /etc/hosts hacks.

More fun, the krb4 code needs the destination address of incoming packets for the encryption of the reply, so we can't simply switch to listening on INADDR_ANY with no other changes.

I see two options:

  1. Change the code to use recvmsg instead of recvfrom, in which case you can get at the destination address of the incoming packets at the expense of substantially increased complexity. See  http://tinyurl.com/d79x9r for an example of how to do this.
  1. Tear out the krb4 code. The krb5 protocol was introduced in 2002, and it seems pretty unlikely that krb4 clients are still around. It's already nicely conditionalized out so that it'll build on squeeze.

Change History

comment:1 Changed 13 years ago by broder

(Marked as low priority because nobody actually cares about this package)

comment:2 Changed 13 years ago by broder

  • Keywords proposed added
  • Description modified (diff)
  • Summary changed from debathena-lert-server is completely dysfunctional to debathena-lert-server binds only to localhost

debathena-lert 10.0.2-0debathena1 fixes the paths that debathena-lert-server uses, and includes an init script. It's going into -proposed with everything else.

There is one remaining issue, and I've updated the description to document that.

comment:3 Changed 13 years ago by broder

  • Keywords proposed removed

There's not a fix for the remaining issue here in -proposed.

comment:4 Changed 12 years ago by jdreed

  • Milestone set to Summer 2010

comment:5 Changed 12 years ago by broder

  • Milestone changed from Summer 2010 (Lucid Deploy) to The Distant Future

Nobody is running a lertsrv from Debathena, so nobody is going to care if it continues to not work come Lucid deploy.

Bumping to the distant future.

comment:6 Changed 11 years ago by jdreed

  • Status changed from new to closed
  • Resolution set to wontfix

krb4 is dead, and lert itself is dying, as we do not plan to load the Nov 2011 deactivation list into lert.

Note: See TracTickets for help on using tickets.