Re: odd problem, unreference key: 0x84fc6a0 (none)

-----BEGIN PGP SIGNED MESSAGE-----


| From: Paul Wouters <[email protected]>

| To: [email protected], [email protected]

[I've moved this to the design list -- it is important to the
developers.]

| Sep 12 14:50:10 untappable pluto[5434]: "packetdefault"[1] 0.0.0.0/0=== ...193.110.157.17===? #1: responding to Main Mode from unknown peer 193.110.157.17
| Sep 12 14:50:10 untappable pluto[5434]: | unreference key: 0x80a7868 (none) cnt 2--
| Sep 12 14:50:11 untappable pluto[5434]: "packetdefault"[1] 0.0.0.0/0=== ...193.110.157.17===? #1: sent MR3, ISAKMP SA established
| Sep 12 14:50:11 untappable pluto[5434]: | unreference key: 0x80a7430 193.110.157.17 cnt 3--

This is very bad.  It means that a key is being reference counted
improperly.  Somehow, a reference is surviving past when it should.

Possible consequence: memory could have been reallocated and then
there are two objects stored in the same memory.  The bytes then
become mixed up in some unpredicable way.

Also note that you got a debugging message (one starting with "| ")
without having any debugging options.  This is wrong.

Version:
	Linux FreeS/WAN Ucvs2003May11_04:14:20/K2.00

I'm not sure whether we've changed/fixed anything in this area since
May 11.

BTW, thanks for the barf -- it really helps me figure this out.

I will investigate.

Hugh Redelmeier
[email protected]  voice: +1 416 482-8253

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBP2Ho8sFAuQPManGZAQGItQP/TcTz+hMrupf3iwHlFyP0qxRT2vnoW/f+
pWb4kBnJLBC6vvK0OmW1gXJrtRxRbUp7R2Fee0T0bKYn+/hg/dI0x4umyFDEA5sH
C+nZaxIJXm0Du2G0uomEP98XpWWcu2TOu2SAzPQhjWPvolThNeyFA2lMPlBVO4G4
mb+v2KkKhgQ=
=EULB
-----END PGP SIGNATURE-----