[Openswan dev] 2.3.1: regression from 2.2.0 to 2.3 still exists
rene.mayrhofer at gibraltar.at
Thu Apr 14 17:16:10 CEST 2005
Am Sonntag, 10. April 2005 20:57 schrieb Paul Wouters:
> On Sun, 10 Apr 2005, Rene Mayrhofer wrote:
> > Apr 10 12:44:40 whisper pluto: "wlanIpsecOnly" #3: ASSERTION
> > FAILED at crypto.c:219: st->st_new_iv_len >= e->enc_blocksize
> this seems to be the essence of your crasher. If I understood you
> correctly, this (crashing) end is openswan 2.3.1, and the remote
> is a 2.2.0 right?
> Looking at the lines I see:
> crypto_cbc_encrypt(const struct encrypt_desc *e, bool enc
> , u_int8_t *buf, size_t size, struct state *st)
> passert(st->st_new_iv_len >= e->enc_blocksize);
> st->st_new_iv_len = e->enc_blocksize; /* truncate */
> I am not sure why we would passert fail and then still truncate.
Any news on that? The next few days are probably the last chance of getting
openswan into the next Debian stable release....
with best regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.openswan.org/pipermail/dev/attachments/20050414/51105676/attachment.bin
More information about the Dev