Skip to content

Actions

ic0ns edited this page Sep 5, 2017 · 13 revisions

A WorkflowTrace as implemented in TLS-Attacker consists of multiple Actions. The following Actions are currently implemented in TLS-Attacker:

  • SendAction
  • ReceiveAction
  • GenericReceiveAction
  • RenegotiationAction
  • ResetConnectionAction
  • WaitingAction
  • ChangeCipherSuiteAction
  • ChangeClientRandomAction
  • ChangeCompressionAction
  • ChangeMasterSecretAction
  • ChangePreMasterSecretAction
  • ChangeProtocolVersionAction
  • ChangeServerRandomAction
  • DeactivateEncryptionAction

The Actions are described in more Detail below. Note: You can also define your own Actions and use them with TLS-Attacker ##SendAction The SendAction is one of the basic TLS-Attacker Actions. If it is executed it sends a List of predefined Messages/Records.

<SendAction>
    <messages>
        <ClientHello/>
    </messages>
    <records>
        <Record/>
    </records>
</SendAction>

With messages you can specify a list of Messages you want to send, and with records you can defined the records in which these messages should be send. By default, TLS-Attacker will add Records to your WorkflowTrace as needed and create them with the correct sizes. With the default Settings TLS-Attacker will add additional records as needed to your WorkflowTrace and ignore Records it did not need to send the defined Messages. You can edit this behavior in the Config.

Clone this wiki locally