Debian Codegraph @

src/luks/tests/bind-already-used-luksmeta-slot

raw
1 #!/bin/bash -ex
2 # vim: set tabstop=8 shiftwidth=4 softtabstop=4 expandtab smarttab colorcolumn=80:
3 #
4 # Copyright (c) 2019 Red Hat, Inc.
5 # Author: Sergio Correia <[email protected]>
6 #
7 # This program is free software: you can redistribute it and/or modify
8 # it under the terms of the GNU General Public License as published by
9 # the Free Software Foundation, either version 3 of the License, or
10 # (at your option) any later version.
11 #
12 # This program is distributed in the hope that it will be useful,
13 # but WITHOUT ANY WARRANTY; without even the implied warranty of
14 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
15 # GNU General Public License for more details.
16 #
17 # You should have received a copy of the GNU General Public License
18 # along with this program. If not, see <http://www.gnu.org/licenses/>.
19 #
20
21 TEST="${0}"
22 . luks-common-test-functions
23
24 on_exit() {
25 [ -d "${TMP}" ] && rm -rf "${TMP}"
26 }
27
28 trap 'on_exit' EXIT
29 trap 'exit' ERR
30
31 TMP="$(mktemp -d)"
32
33 ADV="${TMP}/adv.jws"
34 tang_create_adv "${TMP}" "${ADV}"
35 CFG="$(printf '{"url":"foobar","adv":"%s"}' "$ADV")"
36
37 # LUKS1.
38 DEV="${TMP}/luks1-device"
39 UUID="cb6e8904-81ff-40da-a84a-07ab9ab5715e"
40
41 # We can have a "partially" used if it is an inactive slot that has an UUID
42 # already:
43 # 1 inactive cb6e8904-81ff-40da-a84a-07ab9ab5715e
44 # We end up in this situation if the cryptsetup step adding the key failed,
45 # for instance because we provided a wrong pass phrase, and luksmeta saved
46 # data anyway. We used to have an issue with clevis luks bind script, in which
47 # we would still run luksmeta save even if the cryptsetup step failed.
48
49 bind_and_verify() {
50 local DEV="${1}"
51 local PASS="${2}"
52 local SLT="${3}"
53
54 if ! clevis luks bind -f -d "${DEV}" tang "${CFG}" <<< "${PASS}"; then
55 error "${TEST}: Binding is expected to succeed when given a correct (${PASS}) password." >&2
56 fi
57
58 if ! read -r _ state uuid < <(luksmeta show -d "${DEV}" | grep "^${SLT} *"); then
59 error "${TEST}: Error reading LUKSmeta info for slot ${SLT} of ${DEV}." >&2
60 fi
61
62 if [ "${state}" != "active" ]; then
63 error "${TEST}: state (${state}) is expected to be 'active'." >&2
64 fi
65
66 if [ "${uuid}" != "${UUID}" ]; then
67 error "${TEST}: UUID ($uuid) is expected to be '${UUID}'." >&2
68 fi
69 }
70
71 SLT=1
72 NEW_PASS="new-pass"
73 PASS="${DEFAULT_PASS}"
74 WRONG_PASS="wrong-password-here"
75
76 new_device "luks1" "${DEV}"
77 luksmeta init -f -d "${DEV}"
78 if cryptsetup luksAddKey "${DEV}" < <(echo "${WRONG_PASS}"; echo -n "${NEW_PASS}"); then
79 error "${TEST}: cryptsetup should not succeed in adding key when given a wrong passphrase." >&2
80 fi
81
82 # Ok, the cryptsetup step failed, since we gave a wrong password. That means
83 # that right now the luksmeta slot is inactive. Let's simulate the bad
84 # condition by saving the UUID there anyway.
85 echo "foo" | luksmeta save -d "${DEV}" -u "${UUID}"
86
87 # Verify we have slot 1 like this:
88 # # 1 inactive cb6e8904-81ff-40da-a84a-07ab9ab5715e
89 if ! read -r _ state uuid < <(luksmeta show -d "${DEV}" | grep "^${SLT} *"); then
90 error "${TEST}: Error reading LUKSmeta info for slot ${SLT} of ${DEV}." >&2
91 fi
92
93 if [ "${state}" != "inactive" ]; then
94 error "${TEST}: state (${state}) is expected to be 'inactive', in case #1." >&2
95 fi
96
97 if [ "${uuid}" != "${UUID}" ]; then
98 error "${TEST}: UUID ($uuid) is expected to be '${UUID}', in case #1." >&2
99 fi
100
101 # Verify if can bind correctly in this situation.
102 bind_and_verify "${DEV}" "${PASS}" "1"