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
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
|
@api
Feature: API volume modification
Scenario: Simple volume #1 (change passphrase, neg)
Given I create a volume tmpvol1 of size 10M using the API with the following parameters:
| passphrase | test |
| pbkdf_prf | SHA512 |
| cipher | AES-256-XTS |
And I modify volume tmpvol1 with the API using the following settings:
| passphrase | test |
| new_passphrase | new |
And I map volume tmpvol1 as tcplay_test with the API using the following settings:
| passphrase | test |
And I request information about volume tmpvol1 with the API using the following settings:
| passphrase | test |
Then I expect tcplay to fail
Scenario: Simple volume #1 (change passphrase, pos)
Given I create a volume tmpvol1 of size 10M using the API with the following parameters:
| passphrase | test |
| pbkdf_prf | SHA512 |
| cipher | AES-256-XTS |
And I modify volume tmpvol1 with the API using the following settings:
| passphrase | test |
| new_passphrase | new |
And I map volume tmpvol1 as tcplay_test with the API using the following settings:
| passphrase | new |
And I request information about volume tmpvol1 with the API using the following settings:
| passphrase | new |
Then I expect tcplay to succeed
And I expect dmsetup to have the following tables:
| name | begin | end | algo | offset | iv_offset |
| tcplay_test | 0 | 19968 | aes-xts-plain64 | 256 | 256 |
And I expect tcplay to report the following:
| PBKDF2 PRF | SHA512 |
| Cipher | AES-256-XTS |
| Key Length | 512 bits |
| Volume size | 10223616 bytes |
| IV offset | 131072 bytes |
| Block offset | 131072 bytes |
Scenario: Simple volume #1 (change PBKDF PRF)
Given I create a volume tmpvol1 of size 10M using the API with the following parameters:
| passphrase | test |
| pbkdf_prf | SHA512 |
| cipher | AES-256-XTS |
And I modify volume tmpvol1 with the API using the following settings:
| passphrase | test |
| new_passphrase | test |
| new_pbkdf_prf | whirlpool |
And I map volume tmpvol1 as tcplay_test with the API using the following settings:
| passphrase | test |
And I request information about volume tmpvol1 with the API using the following settings:
| passphrase | test |
Then I expect tcplay to succeed
And I expect dmsetup to have the following tables:
| name | begin | end | algo | offset | iv_offset |
| tcplay_test | 0 | 19968 | aes-xts-plain64 | 256 | 256 |
And I expect tcplay to report the following:
| PBKDF2 PRF | whirlpool |
| Cipher | AES-256-XTS |
| Key Length | 512 bits |
| Volume size | 10223616 bytes |
| IV offset | 131072 bytes |
| Block offset | 131072 bytes |
Scenario: Cascade volume #1 (change passphrase)
Given I create a volume tmpvol1 of size 10M using the API with the following parameters:
| passphrase | test |
| pbkdf_prf | whirlpool |
| cipher | AES-256-XTS,SERPENT-256-XTS |
And I modify volume tmpvol1 with the API using the following settings:
| passphrase | test |
| new_passphrase | new |
And I map volume tmpvol1 as tcplay_test with the API using the following settings:
| passphrase | new |
And I request information about volume tmpvol1 with the API using the following settings:
| passphrase | new |
Then I expect dmsetup to have the following tables:
| name | begin | end | algo | offset | iv_offset |
| tcplay_test.0 | 0 | 19968 | serpent-xts-plain64 | 256 | 256 |
| tcplay_test | 0 | 19968 | aes-xts-plain64 | 256 | 0 |
And I expect tcplay to report the following:
| PBKDF2 PRF | whirlpool |
| Cipher | AES-256-XTS,SERPENT-256-XTS |
| Key Length | 1024 bits |
| Volume size | 10223616 bytes |
| IV offset | 131072 bytes |
| Block offset | 131072 bytes |
Scenario: Hidden volume #1 (change passphrase)
Given I create a volume tmpvol1 of size 10M using the API with the following parameters:
| passphrase | test |
| pbkdf_prf | whirlpool |
| cipher | TWOFISH-256-XTS |
| create_hidden | yes |
| hidden_mb | 2 |
| keyfiles_hidden | key.2 |
| pbkdf_prf_hidden | RIPEMD160 |
| cipher_hidden | SERPENT-256-XTS |
And I modify volume tmpvol1 with the API using the following settings:
| keyfiles | key.2 |
| new_passphrase | new_hidden |
And I map volume tmpvol1 as tcplay_test with the API using the following settings:
| passphrase | test |
And I request information about volume tmpvol1 with the API using the following settings:
| passphrase | test |
Then I expect dmsetup to have the following tables:
| name | begin | end | algo | offset | iv_offset |
| tcplay_test | 0 | 19968 | twofish-xts-plain64 | 256 | 256 |
And I expect tcplay to report the following:
| PBKDF2 PRF | whirlpool |
| Cipher | TWOFISH-256-XTS |
| Key Length | 512 bits |
| Volume size | 10223616 bytes |
| IV offset | 131072 bytes |
| Block offset | 131072 bytes |
Scenario: Hidden volume #2 (change passphrase, keyfiles)
Given I create a volume tmpvol1 of size 10M using the API with the following parameters:
| passphrase | test |
| pbkdf_prf | whirlpool |
| cipher | TWOFISH-256-XTS |
| create_hidden | yes |
| hidden_mb | 2 |
| keyfiles_hidden | key.2 |
| pbkdf_prf_hidden | RIPEMD160 |
| cipher_hidden | SERPENT-256-XTS |
And I modify volume tmpvol1 with the API using the following settings:
| keyfiles | key.2 |
| new_passphrase | new_hidden |
| new_keyfiles | key.1, key.2 |
And I map volume tmpvol1 as tcplay_test with the API using the following settings:
| passphrase | new_hidden |
| keyfiles | key.1, key.2 |
And I request information about volume tmpvol1 with the API using the following settings:
| passphrase | new_hidden |
| keyfiles | key.1, key.2 |
Then I expect dmsetup to have the following tables:
| name | begin | end | algo | offset | iv_offset |
| tcplay_test | 0 | 4096 | serpent-xts-plain64 | 16128 | 16128 |
And I expect tcplay to report the following:
| PBKDF2 PRF | RIPEMD160 |
| Cipher | SERPENT-256-XTS |
| Key Length | 512 bits |
| Volume size | 2097152 bytes |
| IV offset | 8257536 bytes |
| Block offset | 8257536 bytes |
Scenario: Hidden volume #3 (change keyfiles, PBKDF PRF)
Given I create a volume tmpvol1 of size 10M using the API with the following parameters:
| passphrase | test |
| pbkdf_prf | whirlpool |
| cipher | TWOFISH-256-XTS |
| create_hidden | yes |
| hidden_mb | 2 |
| keyfiles_hidden | key.2 |
| pbkdf_prf_hidden | RIPEMD160 |
| cipher_hidden | SERPENT-256-XTS |
And I modify volume tmpvol1 with the API using the following settings:
| keyfiles | key.2 |
| new_keyfiles | key.1, key.2 |
| new_pbkdf_prf | SHA512 |
And I map volume tmpvol1 as tcplay_test with the API using the following settings:
| keyfiles | key.1, key.2 |
And I request information about volume tmpvol1 with the API using the following settings:
| keyfiles | key.1, key.2 |
Then I expect dmsetup to have the following tables:
| name | begin | end | algo | offset | iv_offset |
| tcplay_test | 0 | 4096 | serpent-xts-plain64 | 16128 | 16128 |
And I expect tcplay to report the following:
| PBKDF2 PRF | SHA512 |
| Cipher | SERPENT-256-XTS |
| Key Length | 512 bits |
| Volume size | 2097152 bytes |
| IV offset | 8257536 bytes |
| Block offset | 8257536 bytes |
|
