[Openswan Users] alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_ar in duplicate_state

[Alex Ip]

G'day...

	I don't know whether this is due to a misconfiguration on my part, but I keep getting this message in my logs for an otherwise perfectly functional link. It doesn't seem to be causing any problems, but I thought it might be important to report it to the developers. Any ideas?

Regards,

Alex.

--------------------- FreeS/WAN Begin ------------------------ 

 UNKNOWN: Jan  1 00:23:49 mail pluto[9456]: "thom-moor" #112: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_ar in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 00:23:49 mail pluto[9456]: "thom-moor" #112: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_er in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 00:23:49 mail pluto[9456]: "thom-moor" #112: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_pi in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 00:23:49 mail pluto[9456]: "thom-moor" #112: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_pr in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 08:13:40 mail pluto[9456]: "thom-moor" #123: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_ar in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 08:13:40 mail pluto[9456]: "thom-moor" #123: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_er in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 08:13:40 mail pluto[9456]: "thom-moor" #123: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_pi in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 08:13:40 mail pluto[9456]: "thom-moor" #123: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_pr in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 15:56:31 mail pluto[9456]: "thom-moor" #134: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_ar in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 15:56:31 mail pluto[9456]: "thom-moor" #134: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_er in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 15:56:31 mail pluto[9456]: "thom-moor" #134: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_pi in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 15:56:31 mail pluto[9456]: "thom-moor" #134: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_pr in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 23:44:34 mail pluto[9456]: "thom-moor" #145: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_ar in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 23:44:34 mail pluto[9456]: "thom-moor" #145: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_er in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 23:44:34 mail pluto[9456]: "thom-moor" #145: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_pi in duplicate_state, please report to dev at openswan.org
 UNKNOWN: Jan  1 23:44:34 mail pluto[9456]: "thom-moor" #145: alloc_bytes1() was mistakenly asked to malloc 0 bytes for st_skey_pr in duplicate_state, please report to dev at openswan.org
 Overview summary of log files:
 	 Jan 1 had 544 entries of which 84 were relevant
 Summary by peer:
   Peer thom-moor caused 513 lines of output.
 	connected from: 
 	Keyed: 30 successes 0 failures (max retries: 0)
 	IPsec SAs: 4

---------------------- FreeS/WAN End ------------------------- 

The (censored) configuration file for the link is as follows:



# /etc/ipsec.conf - Openswan IPsec configuration file
#
# Manual:     ipsec.conf.5
#
# Please place your own config files in /etc/ipsec.d/ ending in .conf

version 2.0     # conforms to second version of ipsec.conf specification

# basic configuration
config setup
        # Debug-logging controls:  "none" for (almost) none, "all" for lots.
        # klipsdebug=none
        # plutodebug="control parsing"
        # For Red Hat Enterprise Linux and Fedora, leave protostack=netkey
        protostack=netkey
        nat_traversal=yes

conn thom-moor
        # moor
        left=XXX.XXX.XXX.XXX
        leftid=@somewhere.com
        leftsubnet=192.168.64.0/24
        leftnexthop=
        leftrsasigkey=<secret stuff>
        # thom
        right=YYY.YYY.YYY.YYY
        rightid=@somewhere.else.com
        rightsubnet=192.168.0.0/24
        rightnexthop=
        rightrsasigkey=<secret stuff>
        auto=start