[strongSwan-dev] imv_attestation crash

Andreas Steffen andreas.steffen at strongswan.org
Wed Jun 18 12:38:00 CEST 2014

Hi Avesh,

I had a look into your crash. Line 692 in imv_attestation_agent.c
(referring to the current master) is

691	enumerator = session->create_workitem_enumerator(session);
692	while (enumerator->enumerate(enumerator, &workitem))

Thus first I checked if the enumerator returned by


could be a NULL pointer so that enumerator->enumerate() in line 692
would crash. Having a look at the create_workitem_enumerator() method:

METHOD(imv_session_t, create_workitem_enumerator, enumerator_t*,
	private_imv_session_t *this)
	if (!this->policy_started)
		return enumerator_create_empty();
	return this->workitems->create_enumerator(this->workitems);

I see that the enumerator is always well defined so that there must
be another reason for the crash.

Which strongSwan version were you using when this crash occurred?
It might be that the line numbers have changed in the master.

Best regards


On 06/16/2014 06:55 PM, Avesh Agarwal wrote:
> Hi,
> While testing IMA measurements over TLS between imc-attestation and
> imv-attestation, I see imv-attestation crashing at attestation server. I
> have pretty much used the standard configurations as specified in the
> pt-tls test case. The back trace is as follows:
> (gdb) bt
> #0  0x00007fc24e689989 in raise () from /lib64/libc.so.6
> #1  0x00007fc24e68b098 in abort () from /lib64/libc.so.6
> #2  0x00007fc24fa35138 in segv_handler (signal=11) at charon.c:197
> #3  <signal handler called>
> #4  0x00007fc246ffefcc in batch_ending (this=0x7fc250097360,
> id=<optimized out>) at imv_attestation_agent.c:692
> #5  0x00007fc247ad1197 in batch_ending (this=0x7fc2500924d0, id=1) at
> tnc_imv_manager.c:401
> #6  0x00007fc2476c0c0b in process (this=0x7fc220000a10, buf=<optimized
> out>, buflen=<optimized out>) at tnccs_20.c:644
> #7  0x00007fc2480f3772 in assess (this=0x7fc220000d50,
> this=0x7fc220000d50, tnccs=0x7fc220000a10) at pt_tls_server.c:433
> #8  handle (this=0x7fc220000d50) at pt_tls_server.c:489
> #9  0x00007fc24850086d in pt_tls_receive_more (this=0x7fc220000d50,
> fd=19, event=<optimized out>) at tnc_pdp.c:592
> #10 0x00007fc24f5e4364 in notify_async (data=0x7fc230000970) at
> processing/watcher.c:143
> #11 0x00007fc24f5e2bfe in execute (this=<optimized out>) at
> processing/jobs/callback_job.c:77
> #12 0x00007fc24f5e34c2 in process_job (worker=0x7fc250098920,
> this=0x7fc25005a490) at processing/processor.c:235
> #13 process_jobs (worker=0x7fc250098920) at processing/processor.c:321
> #14 0x00007fc24f5ec0d9 in thread_main (this=0x7fc2500ad110) at
> threading/thread.c:309
> #15 0x00007fc24ec20df3 in start_thread () from /lib64/libpthread.so.0
> #16 0x00007fc24e74a3dd in clone () from /lib64/libc.so.6
> Not sure if it is known or not or I am missing something. Any help is
> appreciated.
> Thanks and Regards
> Avesh
Andreas Steffen                         andreas.steffen at strongswan.org
strongSwan - the Open Source VPN Solution!          www.strongswan.org
Institute for Internet Technologies and Applications
University of Applied Sciences Rapperswil
CH-8640 Rapperswil (Switzerland)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4255 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.strongswan.org/pipermail/dev/attachments/20140618/8957c551/attachment.bin>

More information about the Dev mailing list