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
|
@api
Feature: API mapping/info tests using volume test1.tc
Scenario: Map outer volume
Given I map volume test1.tc as tcplay_test with the API using the following settings:
| passphrase | test |
And I request information about mapped volume tcplay_test with the API
Then I expect dmsetup to have the following tables:
| name | begin | end | algo | offset | iv_offset | key |
| tcplay_test | 0 | 40448 | aes-xts-plain64 | 256 | 256 | b736aebe0ba9e67f58f110769955a19d1351b07f99cbda9f59249e0aaed72f9e672365dee6d2bf00a34bdd1b8aafa31b274103b9e925ac568e60562ce0c6ff0e |
And I expect tcplay to report the following:
| Cipher | AES-256-XTS |
| Key Length | 512 bits |
| Volume size | 20709376 bytes |
| IV offset | 131072 bytes |
| Block offset | 131072 bytes |
Scenario: Map hidden volume
Given I map volume test1.tc as tcplay_test with the API using the following settings:
| passphrase | hidden |
And I request information about mapped volume tcplay_test with the API
Then I expect dmsetup to have the following tables:
| name | begin | end | algo | offset | iv_offset | key |
| tcplay_test | 0 | 10240 | aes-xts-plain64 | 30464 | 30464 | 7dd9086e92b756f55465723a9b4594bf61040a6bea8b2291a45821ff80d0676dd86caf6595d57beb7902e952706fbb7bad8b69048c47cced1aba08ebac847dd9 |
And I expect tcplay to report the following:
| Cipher | AES-256-XTS |
| Key Length | 512 bits |
| Volume size | 5242880 bytes |
| IV offset | 15597568 bytes |
| Block offset | 15597568 bytes |
Scenario: Map outer volume protecting hidden volume
Given I map volume test1.tc as tcplay_test with the API using the following settings:
| passphrase | test |
| passphrase_hidden | hidden |
| protect_hidden | yes |
And I request information about mapped volume tcplay_test with the API
Then I expect dmsetup to have the following tables:
| name | begin | end | algo | offset | iv_offset | key |
| tcplay_test | 0 | 30208 | aes-xts-plain64 | 256 | 256 | b736aebe0ba9e67f58f110769955a19d1351b07f99cbda9f59249e0aaed72f9e672365dee6d2bf00a34bdd1b8aafa31b274103b9e925ac568e60562ce0c6ff0e |
And I expect tcplay to report the following:
| Cipher | AES-256-XTS |
| Key Length | 512 bits |
| Volume size | 15466496 bytes |
| IV offset | 131072 bytes |
| Block offset | 131072 bytes |
Scenario: Info on outer volume
Given I request information about volume test1.tc with the API using the following settings:
| passphrase | test |
Then I expect tcplay to report the following:
| PBKDF2 PRF | whirlpool |
| Cipher | AES-256-XTS |
| Key Length | 512 bits |
| Volume size | 20709376 bytes |
| IV offset | 131072 bytes |
| Block offset | 131072 bytes |
Scenario: Info on hidden volume
Given I request information about volume test1.tc with the API using the following settings:
| passphrase | hidden |
Then I expect tcplay to report the following:
| PBKDF2 PRF | whirlpool |
| Cipher | AES-256-XTS |
| Key Length | 512 bits |
| Volume size | 5242880 bytes |
| IV offset | 15597568 bytes |
| Block offset | 15597568 bytes |
Scenario: Info on outer volume protecting hidden volume
Given I request information about volume test1.tc with the API using the following settings:
| passphrase | test |
| passphrase_hidden | hidden |
| protect_hidden | yes |
Then I expect tcplay to report the following:
| PBKDF2 PRF | whirlpool |
| Cipher | AES-256-XTS |
| Key Length | 512 bits |
| Volume size | 15466496 bytes |
| IV offset | 131072 bytes |
| Block offset | 131072 bytes |
|
