-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathaes.feature
105 lines (92 loc) · 4.84 KB
/
aes.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
Feature: aes
@aes
Scenario: Send and receive an unencrypted message
Given a default access class
And a requester, set to default access class
And a responder, listening for foreground packets on the default access class
And an interface configuration using the default scan access class and using no encryption
And a command, direct forward using this interface configuration
When the requester starts a session for this command
Then the requester s session should complete successfully
And the responder should receive an unsolicited response
@aes
Scenario: Send and receive an encrypted message using aes ctr with same keys
Given a default access class
And a requester, set to default access class
And a responder, listening for foreground packets on the default access class
And a key, randomly generated
And the generated key written to the requester
And the generated key also written to the responder
And an interface configuration using the default scan access class and using AES CTR
And a command, direct forward using this interface configuration
When the requester starts a session for this command
Then the requester s session should complete successfully
And the responder should receive an unsolicited response
@aes
Scenario: Send and not receive an encrypted message using aes ctr with different keys
Given a default access class
And a requester, set to default access class
And a responder, listening for foreground packets on the default access class
And a key, randomly generated
And the generated key written to the requester
And a key, different from the other one
And the different key written to the responder
And an interface configuration using the default scan access class and using AES CTR
And a command, direct forward using this interface configuration
When the requester starts a session for this command
Then the requester s session should not complete successfully
And the responder should not receive an unsolicited response
@aes
Scenario: Send and receive an encrypted message using aes cbc with same keys
Given a default access class
And a requester, set to default access class
And a responder, listening for foreground packets on the default access class
And a key, randomly generated
And the generated key written to the requester
And the generated key also written to the responder
And an interface configuration using the default scan access class and using AES CBC
And a command, direct forward using this interface configuration
When the requester starts a session for this command
Then the requester s session should complete successfully
And the responder should receive an unsolicited response
@aes
Scenario: Send and not receive an encrypted message using aes cbc with different keys
Given a default access class
And a requester, set to default access class
And a responder, listening for foreground packets on the default access class
And a key, randomly generated
And the generated key written to the requester
And a key, different from the other one
And the different key written to the responder
And an interface configuration using the default scan access class and using AES CBC
And a command, direct forward using this interface configuration
When the requester starts a session for this command
Then the requester s session should not complete successfully
And the responder should not receive an unsolicited response
@aes
Scenario: Send and receive an encrypted message using aes ccm with same keys
Given a default access class
And a requester, set to default access class
And a responder, listening for foreground packets on the default access class
And a key, randomly generated
And the generated key written to the requester
And the generated key also written to the responder
And an interface configuration using the default scan access class and using AES CCM
And a command, direct forward using this interface configuration
When the requester starts a session for this command
Then the requester s session should complete successfully
And the responder should receive an unsolicited response
@aes
Scenario: Send and not receive an encrypted message using aes ccm with different keys
Given a default access class
And a requester, set to default access class
And a responder, listening for foreground packets on the default access class
And a key, randomly generated
And the generated key written to the requester
And a key, different from the other one
And the different key written to the responder
And an interface configuration using the default scan access class and using AES CCM
And a command, direct forward using this interface configuration
When the requester starts a session for this command
Then the requester s session should not complete successfully
And the responder should not receive an unsolicited response