Port SERVICEACCESS - TLS 🛈¶
Port for opening TLS-protected connections that can be used by other ports
Stimulation¶
This port has no stimulus capabilities.
Properties 🛈¶
Name |
Available if |
Default value |
Valid values |
Type |
Description |
|---|---|---|---|---|---|
TLS version |
TLSv1_3 |
[SSLv3, TLSv1, TLSv1_1, TLSv1_2, TLSv1_3] |
string |
The TLS version provided by ecu.test |
|
Client certificate chain |
string |
Absolute path to the file in PEM format containig the certificate as well as any number of CA certificates needed for the authentication of ecu.test. |
|||
Private key |
string |
Absolute path to the private key used by ecu.test. |
|||
Root certificate |
string |
Absolute path to the root or CA certificate that is trusted to authenticate the remote peer. |
|||
Generate keylog file |
☐ |
bool |
Generate a keylog file to be able to decrypt a corresponding, recorded TLS communication. The keylog file will be stored in the report directory afterwards. It contains TLS traffic secrets that can only be used for the corresponding TLS session in which they were calculated. |
||
Automatically decrypt PCAP |
Generate keylog file |
☑ |
bool |
Inject the TLS traffic secrets in the recorded PCAP files automatically. Then analysis tools such as wireshark can decrypt the recorded TLS communication automatically without needing to specify a keylog file. These traffic secrets are exactly as the ones that are contained in the keylog file. TLS traffic secrets can only be used for the corresponding TLS session in which they were calculated. For now, only PCAPNGs are supported. |
|
Global keylog file |
Generate keylog file |
string |
The specified file is extended by the keylog file generated in the test case. This might be useful if a static keylog file shall be configured in an analysis tool such as wireshark. The file can be absolute or relative to the workspace. |