[Openswan Users] pluto memory leak?

[Dmitry Melekhov]

Paul Wouters пишет:
> On Tue, 16 Jan 2007, Dmitry Melekhov wrote:
>
>   
>>> There is a known memory leak when retrying conenctions with a bad
>>> configuration (eg wrong PSK or PSK vs RSA auth).
>>>
>>>
>>>       
>> Hmm. I think that I have no problems in configuration.
>> It is possible that some links are not stable, can this results in
>> memory leaks?
>>     
>
> Not that we are aware of. You could recompile with -DLEAK_DETECTIVE and
> restart openswan nicely (using the scripts) to get a log of memory leaks.
>
>
>   
I tried to compile pluto with this option.
It doesn't work :-(


# ipsec whack --status | grep u304
000 "u304":
0.0.0.0/0===192.168.200.237...192.168.200.238===192.168.26.0/24; erouted
HOLD; eroute owner: #0
000 "u304": srcip=unset; dstip=unset; srcup=ipsec _updown; dstup=ipsec
_updown;
000 "u304": ike_life: 3600s; ipsec_life: 3600s; rekey_margin: 1200s;
rekey_fuzz: 100%; keyingtries: 0
000 "u304": policy: PSK+ENCRYPT+COMPRESS+TUNNEL+PFS+UP; prio: 0,24;
interface: eth1; encap: esp;
000 "u304": newest ISAKMP SA: #0; newest IPsec SA: #0;
000 #8: "u304":500 STATE_MAIN_R1 (sent MR1, expecting MI2);
EVENT_CRYPTO_FAILED in 299s; lastdpd=-1s(seq in:0 out:0)
000 #1: "u304":500 STATE_MAIN_I1 (sent MI1, expecting MR1);
EVENT_CRYPTO_FAILED in 295s; lastdpd=-1s(seq in:0 out:0)
000 #1: pending Phase 2 for "u304" replacing #0
000 #1: pending Phase 2 for "u304" replacing #0