Difference between revisions of "Truxton message get dont route"

From truxwiki.com
Jump to navigation Jump to search
 
Line 2: Line 2:
  
 
=Syntax=
 
=Syntax=
<syntaxhighlight lang="C">
+
<source lang="C">
 
uint32_t truxton_message_get_dont_route( uint64_t message_handle );
 
uint32_t truxton_message_get_dont_route( uint64_t message_handle );
</syntaxhighlight>
+
</source>
  
 
=Parameters=
 
=Parameters=
Line 15: Line 15:
  
 
=Sample=
 
=Sample=
<syntaxhighlight lang="C" highlight="3">
+
<source lang="C" highlight="3">
void check_message(uint64_t message)
+
void check_message( uint64_t message )
 
{
 
{
 
   if ( truxton_message_get_dont_route( message ) == 0 )
 
   if ( truxton_message_get_dont_route( message ) == 0 )
Line 27: Line 27:
 
   }
 
   }
 
}
 
}
</syntaxhighlight>
+
</source>

Latest revision as of 12:39, 9 February 2021

Tells you if your message should be forwarded to any other exploitation processes in the ETL layer.

Syntax

uint32_t truxton_message_get_dont_route( uint64_t message_handle );

Parameters

message_handle

The handle to a message created by the truxton_message_create call.

Return value

If the message should be allowed to flow to other exploitation processes, this value will be zero. If the value is non-zero, the message will not be forward to any process down the line.

Sample

void check_message( uint64_t message )
{
   if ( truxton_message_get_dont_route( message ) == 0 )
   {
      printf( "Message can be forwarded.\n" );
   }
   else
   {
      printf( "Message will not be routed\n" );
   }
}