rancher/kcrypt
1
0
Fork 0
mirror of https://github.com/kairos-io/kcrypt.git synced 2025-04-27 11:21:45 +00:00
Code Issues Packages Projects Releases Wiki Activity
930d7433ae
kcrypt/go.sum

574 lines
54 KiB
Plaintext
Raw Normal View History

Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
atomicgo.dev/assert v0.0.2 h1:FiKeMiZSgRrZsPo9qn/7vmr7mCsh5SZyXY4YGYiYwrg=
atomicgo.dev/cursor v0.1.1 h1:0t9sxQomCTRh5ug+hAMCs59x/UmC9QL6Ci5uosINKD4=
atomicgo.dev/cursor v0.1.1/go.mod h1:Lr4ZJB3U7DfPPOkbH7/6TOtJ4vFGHlgj1nc+n900IpU=
atomicgo.dev/keyboard v0.2.8 h1:Di09BitwZgdTV1hPyX/b9Cqxi8HVuJQwWivnZUEqlj4=
atomicgo.dev/keyboard v0.2.8/go.mod h1:BC4w9g00XkxH/f1HXhW2sXmJFOCWbKn9xrOunSFtExQ=
cloud.google.com/go v0.26.0/go.mod h1:aQUYkXzVsufM+DwF1aE+0xfcU+56JwCaLick0ClmMTw=
Initial import
2022-10-03 09:03:48 +00:00
github.com/BurntSushi/toml v0.3.1/go.mod h1:xHWCNGjB5oqiDr8zfno3MHue2Ht5sIBksp03qcyfWMU=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/MarvinJWendt/testza v0.1.0/go.mod h1:7AxNvlfeHP7Z/hDQ5JtE3OKYT3XFUeLCDE2DQninSqs=
github.com/MarvinJWendt/testza v0.2.1/go.mod h1:God7bhG8n6uQxwdScay+gjm9/LnO4D3kkcZX4hv9Rp8=
github.com/MarvinJWendt/testza v0.2.8/go.mod h1:nwIcjmr0Zz+Rcwfh3/4UhBp7ePKVhuBExvZqnKYWlII=
github.com/MarvinJWendt/testza v0.2.10/go.mod h1:pd+VWsoGUiFtq+hRKSU1Bktnn+DMCSrDrXDpX2bG66k=
github.com/MarvinJWendt/testza v0.2.12/go.mod h1:JOIegYyV7rX+7VZ9r77L/eH6CfJHHzXjB69adAhzZkI=
github.com/MarvinJWendt/testza v0.3.0/go.mod h1:eFcL4I0idjtIx8P9C6KkAuLgATNKpX4/2oUqKc6bF2c=
github.com/MarvinJWendt/testza v0.4.2/go.mod h1:mSdhXiKH8sg/gQehJ63bINcCKp7RtYewEjXsvsVUPbE=
github.com/MarvinJWendt/testza v0.5.1 h1:a9Fqx6vQrHQ4CyiaLhktfTTelwGotmFWy8MNhyaohw8=
github.com/Masterminds/goutils v1.1.1/go.mod h1:8cTjp+g8YejhMuvIA5y2vz3BpJxksy863GQaJW2MFNU=
github.com/Masterminds/semver/v3 v3.1.1/go.mod h1:VPu/7SZ7ePZ3QOrcuXROw5FAcLl4a0cBrbBpGY/8hQs=
github.com/Masterminds/sprig/v3 v3.2.2/go.mod h1:UoaO7Yp8KlPnJIYWTFkMaqPUYKTfGFPhxNuwnnxkKlk=
github.com/Microsoft/go-winio v0.4.14/go.mod h1:qXqCSQ3Xa7+6tgxaGTIe4Kpcdsi+P8jBhyzoq1bpyYA=
github.com/Microsoft/go-winio v0.4.16/go.mod h1:XB6nPKklQyQ7GC9LdcBEcBl8PF76WugXOPRXwdLnMv0=
github.com/Microsoft/go-winio v0.5.0/go.mod h1:JPGBdM1cNvN/6ISo+n8V5iA4v8pBzdOpzfwIujj1a84=
github.com/Microsoft/go-winio v0.5.2/go.mod h1:WpS1mjBmmwHBEWmogvA2mj8546UReBk4v8QkMxJ6pZY=
github.com/OneOfOne/xxhash v1.2.2/go.mod h1:HSdplMjZKSmBqAxg5vPj2TmRDmfkzw+cTzAElWljhcU=
github.com/ProtonMail/go-crypto v0.0.0-20210428141323-04723f9f07d7/go.mod h1:z4/9nQmJSSwwds7ejkxaJwO37dru3geImFUdJlaLzQo=
github.com/ProtonMail/go-crypto v0.0.0-20220623141421-5afb4c282135/go.mod h1:z4/9nQmJSSwwds7ejkxaJwO37dru3geImFUdJlaLzQo=
Initial import
2022-10-03 09:03:48 +00:00
github.com/StackExchange/wmi v1.2.1 h1:VIkavFPXSjcnS+O8yTq7NI32k0R5Aj+v39y29VYDOSA=
github.com/StackExchange/wmi v1.2.1/go.mod h1:rcmrprowKIVzvc+NUiLncP2uuArMWLCbu9SBzvHz7e8=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/acomagu/bufpipe v1.0.3/go.mod h1:mxdxdup/WdsKVreO5GpW4+M/1CE2sMG4jeGJ2sYmHc4=
github.com/alecthomas/template v0.0.0-20160405071501-a0175ee3bccc/go.mod h1:LOuyumcjzFXgccqObfd/Ljyb9UuFJ6TxHnclSeseNhc=
github.com/alecthomas/units v0.0.0-20151022065526-2efee857e7cf/go.mod h1:ybxpYRFXyAe+OPACYpWeL0wqObRcbAqCMya13uyzqw0=
Initial import
2022-10-03 09:03:48 +00:00
github.com/anatol/devmapper.go v0.0.0-20220716012224-693a1447fc15 h1:741Z9HQjbLXe4SnZ6liQTYINeD559oFl/vOtzA21KM0=
github.com/anatol/devmapper.go v0.0.0-20220716012224-693a1447fc15/go.mod h1:Ow7/kdG1m4K6UDTOwJeYJv9bkSLoL44qSu7S/Bxxi4Y=
github.com/anatol/luks.go v0.0.0-20220803222236-155595903818 h1:IyYgXFMhnSIbkDnDrTnMrPDYlc/uYhG5UcGX6NVkO58=
github.com/anatol/luks.go v0.0.0-20220803222236-155595903818/go.mod h1:1lE8PgTi0cS+3YsxbWcpfvGfjiPrRdcKJZc9j70OOTs=
github.com/anatol/vmtest v0.0.0-20220413190228-7a42f1f6d7b8 h1:t4JGeY9oaF5LB4Rdx9e2wARRRPAYt8Ow4eCf5SwO3fA=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/anmitsu/go-shlex v0.0.0-20161002113705-648efa622239/go.mod h1:2FmKhYUyUczH0OGQWaF5ceTx0UBShxjsH6f8oGKYe2c=
github.com/apex/log v1.9.0/go.mod h1:m82fZlWIuiWzWP04XCTXmnX0xRkYYbCdYn8jbJeLBEA=
github.com/apex/logs v1.0.0/go.mod h1:XzxuLZ5myVHDy9SAmYpamKKRNApGj54PfYLcFrXqDwo=
github.com/aphistic/golf v0.0.0-20180712155816-02c07f170c5a/go.mod h1:3NqKYiepwy8kCu4PNA+aP7WUV72eXWJeP9/r3/K9aLE=
github.com/aphistic/sweet v0.2.0/go.mod h1:fWDlIh/isSE9n6EPsRmC0det+whmX6dJid3stzu0Xys=
github.com/armon/consul-api v0.0.0-20180202201655-eb2c6b5be1b6/go.mod h1:grANhF5doyWs3UAsr3K4I6qtAmlQcZDesFNEHPZAzj8=
github.com/armon/go-socks5 v0.0.0-20160902184237-e75332964ef5/go.mod h1:wHh0iHkYZB8zMSxRWpUBQtwG5a7fFgvEO+odwuTv2gs=
github.com/atomicgo/cursor v0.0.1/go.mod h1:cBON2QmmrysudxNBFthvMtN32r3jxVRIvzkUiF/RuIk=
github.com/avast/retry-go v3.0.0+incompatible h1:4SOWQ7Qs+oroOTQOYnAHqelpCO0biHSxpiH9JdtuBj0=
github.com/avast/retry-go v3.0.0+incompatible/go.mod h1:XtSnn+n/sHqQIpZ10K1qAevBhOOCWBLXXy3hyiqqBrY=
github.com/aws/aws-sdk-go v1.20.6/go.mod h1:KmX6BPdI08NWTb3/sm4ZGu5ShLoqVDhKgpiN924inxo=
github.com/aybabtme/rgbterm v0.0.0-20170906152045-cc83f3b3ce59 h1:WWB576BN5zNSZc/M9d/10pqEx5VHNhaQ/yOVAkmj5Yo=
github.com/aybabtme/rgbterm v0.0.0-20170906152045-cc83f3b3ce59/go.mod h1:q/89r3U2H7sSsE2t6Kca0lfwTK8JdoNGS/yzM/4iH5I=
github.com/beorn7/perks v0.0.0-20180321164747-3a771d992973/go.mod h1:Dwedo/Wpr24TaqPxmxbtue+5NUziq4I4S80YR8gNf3Q=
github.com/beorn7/perks v1.0.0/go.mod h1:KWe93zE9D1o94FZ5RNwFwVgaQK1VOXiVxmqh+CedLV8=
github.com/cavaliergopher/grab v2.0.0+incompatible/go.mod h1:6ICNRTQPwkMP0m2sKIDv/9XkhFJJwiEOQyZ+8E4H7Yg=
github.com/cespare/xxhash v1.1.0/go.mod h1:XrSqR1VqqWfGrhpAt58auRo0WTKS1nRRg3ghfAqPWnc=
Initial import
2022-10-03 09:03:48 +00:00
github.com/chuckpreslar/emission v0.0.0-20170206194824-a7ddd980baf9 h1:xz6Nv3zcwO2Lila35hcb0QloCQsc38Al13RNEzWRpX4=
github.com/chuckpreslar/emission v0.0.0-20170206194824-a7ddd980baf9/go.mod h1:2wSM9zJkl1UQEFZgSd68NfCgRz1VL1jzy/RjCg+ULrs=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/chzyer/logex v1.1.10/go.mod h1:+Ywpsq7O8HXn0nuIou7OrIPyXbp3wmkHB+jjWRnGsAI=
github.com/chzyer/readline v0.0.0-20180603132655-2972be24d48e/go.mod h1:nSuG5e5PlCu98SY8svDHJxuZscDgtXS6KTTbou5AhLI=
github.com/chzyer/test v0.0.0-20180213035817-a1ea475d72b1/go.mod h1:Q3SI9o4m/ZMnBNeIyt5eFwwo7qiLfzFZmjNmxjkiQlU=
github.com/client9/misspell v0.3.4/go.mod h1:qj6jICC3Q7zFZvVWo7KLAzC3yx5G7kyvSDkc90ppPyw=
github.com/containerd/console v1.0.3 h1:lIr7SlA5PxZyMV30bDW0MGbiOPXwc63yRuCP0ARubLw=
github.com/containerd/console v1.0.3/go.mod h1:7LqA/THxQ86k76b8c/EMSiaJ3h1eZkMkXar0TQ1gf3U=
github.com/coreos/bbolt v1.3.2/go.mod h1:iRUV2dpdMOn7Bo10OQBFzIJO9kkE559Wcmn+qkEiiKk=
github.com/coreos/etcd v3.3.10+incompatible/go.mod h1:uF7uidLiAD3TWHmW31ZFd/JWoc32PjwdhPthX9715RE=
github.com/coreos/go-semver v0.2.0/go.mod h1:nnelYz7RCh+5ahJtPPxZlU+153eP4D4r3EedlOD2RNk=
github.com/coreos/go-systemd v0.0.0-20190321100706-95778dfbb74e/go.mod h1:F5haX7vjVVG0kc13fIWeqUViNPyEJxv/OmvnBo0Yme4=
github.com/coreos/pkg v0.0.0-20180928190104-399ea9e2e55f/go.mod h1:E3G3o1h8I7cfcXa63jLwjI0eiQQMgzzUDFVpN/nH/eA=
Initial import
2022-10-03 09:03:48 +00:00
github.com/cpuguy83/go-md2man/v2 v2.0.0-20190314233015-f79a8a8ca69d/go.mod h1:maD7wRr/U5Z6m/iR4s+kqSMx2CaBsrgA7czyZG/E6dU=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/cpuguy83/go-md2man/v2 v2.0.0/go.mod h1:maD7wRr/U5Z6m/iR4s+kqSMx2CaBsrgA7czyZG/E6dU=
github.com/cpuguy83/go-md2man/v2 v2.0.2 h1:p1EgwI/C7NhT0JmVkwCD2ZBK8j4aeHQX2pMHHBfMQ6w=
github.com/cpuguy83/go-md2man/v2 v2.0.2/go.mod h1:tgQtvFlXSQOSOSIRvRPT7W67SCa46tRHOmNcaadrF8o=
github.com/creack/pty v1.1.9/go.mod h1:oKZEueFk5CKHvIhNR5MUki03XCEU+Q6VDXinZuGJ33E=
github.com/davecgh/go-spew v1.1.0/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38=
Initial import
2022-10-03 09:03:48 +00:00
github.com/davecgh/go-spew v1.1.1 h1:vj9j/u1bqnvCEfJOwUhtlOARqs3+rkHYY13jYWTU97c=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/davecgh/go-spew v1.1.1/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38=
github.com/davidcassany/linuxkit/pkg/metadata v0.0.0-20220725140037-b49d0fec13b3/go.mod h1:GIS28BxE1G2YB+dCf+O2Ow/bVP7hqioSWLsvr9YQg3o=
github.com/denisbrodbeck/machineid v1.0.1 h1:geKr9qtkB876mXguW2X6TU4ZynleN6ezuMSRhl4D7AQ=
github.com/denisbrodbeck/machineid v1.0.1/go.mod h1:dJUwb7PTidGDeYyUBmXZ2GphQBbjJCrnectwCyxcUSI=
github.com/dgrijalva/jwt-go v3.2.0+incompatible/go.mod h1:E3ru+11k8xSBh+hMPgOLZmtrrCbhqsmaPHjLKYnJCaQ=
github.com/dgryski/go-sip13 v0.0.0-20181026042036-e10d5fee7954/go.mod h1:vAd38F8PWV+bWy6jNmig1y/TA+kYO4g3RSRF0IAv0no=
github.com/diskfs/go-diskfs v1.1.1/go.mod h1:afUPxxu+x1snp4aCY2bKR0CoZ/YFJewV3X2UEr2nPZE=
github.com/diskfs/go-diskfs v1.2.1-0.20211109185859-9509735ba7a4/go.mod h1:IoDpuEbpS+D+yCGdoOm6GNfyTeEws77ALvcMQFxmenw=
github.com/dnaeon/go-vcr v1.0.1/go.mod h1:aBB1+wY4s93YsC3HHjMBMrwTj2R9FHDzUr9KyGc8n1E=
github.com/docker/docker v20.10.17+incompatible/go.mod h1:eEKB0N0r5NX/I1kEveEz05bcu8tLC/8azJZsviup8Sk=
github.com/docker/libnetwork v0.8.0-dev.2.0.20200612180813-9e99af28df21/go.mod h1:93m0aTqz6z+g32wla4l4WxTrdtvBRmVzYRkYvasA5Z8=
github.com/emirpasic/gods v1.12.0/go.mod h1:YfzfFFoVP/catgzJb4IKIqXjX78Ha8FMSDh3ymbK86o=
github.com/emirpasic/gods v1.18.1/go.mod h1:8tpGGwCnJ5H4r6BWwaV6OrWmMoPhUl5jm/FMNAnJvWQ=
github.com/fatih/color v1.7.0/go.mod h1:Zm6kSWBoL9eyXnKyktHP6abPY2pDugNf5KwzbycvMj4=
github.com/flynn/go-shlex v0.0.0-20150515145356-3f9db97f8568/go.mod h1:xEzjJPgXI435gkrCt3MPfRiAkVrwSbHsst4LCFVfpJc=
github.com/frankban/quicktest v1.13.0/go.mod h1:qLE0fzW0VuyUAJgPU19zByoIr0HtCHN/r/VLSOOIySU=
github.com/frankban/quicktest v1.14.3/go.mod h1:mgiwOwqx65TmIk1wJ6Q7wvnVMocbUorkibMOrVTHZps=
Initial import
2022-10-03 09:03:48 +00:00
github.com/fsnotify/fsnotify v1.4.7/go.mod h1:jwhsz4b93w/PPRr/qN1Yymfu8t87LnFCMoQvtojpjFo=
github.com/fsnotify/fsnotify v1.4.9/go.mod h1:znqG4EE+3YCdAaPaxE2ZRY/06pZUdp0tY4IgpuI1SZQ=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/fsnotify/fsnotify v1.5.4 h1:jRbGcIw6P2Meqdwuo0H1p6JVLbL5DHKAKlYndzMwVZI=
Initial import
2022-10-03 09:03:48 +00:00
github.com/ghodss/yaml v1.0.0 h1:wQHKEahhL6wmXdzwWG11gIVCkOv05bNOh+Rxn0yngAk=
github.com/ghodss/yaml v1.0.0/go.mod h1:4dBDuWmgqj2HViK6kFavaiC9ZROes6MMH2rRYeMEF04=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/gliderlabs/ssh v0.2.2/go.mod h1:U7qILu1NlMHj9FlMhZLlkCdDnU1DBEAqr0aevW3Awn0=
github.com/go-git/gcfg v1.5.0/go.mod h1:5m20vg6GwYabIxaOonVkTdrILxQMpEShl1xiMF4ua+E=
github.com/go-git/go-billy/v5 v5.2.0/go.mod h1:pmpqyWchKfYfrkb/UVH4otLvyi/5gJlGI4Hb3ZqZ3W0=
github.com/go-git/go-billy/v5 v5.3.1/go.mod h1:pmpqyWchKfYfrkb/UVH4otLvyi/5gJlGI4Hb3ZqZ3W0=
github.com/go-git/go-git-fixtures/v4 v4.2.1/go.mod h1:K8zd3kDUAykwTdDCr+I0per6Y6vMiRR/nnVTBtavnB0=
github.com/go-git/go-git/v5 v5.4.2/go.mod h1:gQ1kArt6d+n+BGd+/B/I74HwRTLhth2+zti4ihgckDc=
github.com/go-kit/kit v0.8.0/go.mod h1:xBxKIO96dXMWWy0MnWVtmwkA9/13aqxPnvrjFYMA2as=
github.com/go-logfmt/logfmt v0.3.0/go.mod h1:Qt1PoO58o5twSAckw1HlFXLmHsOX5/0LbT9GBnD5lWE=
github.com/go-logfmt/logfmt v0.4.0/go.mod h1:3RMwSq7FuexP4Kalkev3ejPJsZTpXXBr9+V4qmtdjCk=
Create parition info parsing library to be used both here (when trying to find the partition UUID using a label) and on the kairos side when updating the file after calling kcrypt to encrypt a partition (which causes the UUID to change). Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2022-11-11 08:54:33 +00:00
github.com/go-logr/logr v1.2.3 h1:2DntVwHkVopvECVRSlL5PSo9eG+cAkDCuckLubN+rq0=
github.com/go-logr/logr v1.2.3/go.mod h1:jdQByPbusPIv2/zmleS9BjJVeZ6kBagPoEUsqbVz/1A=
Initial import
2022-10-03 09:03:48 +00:00
github.com/go-ole/go-ole v1.2.5/go.mod h1:pprOEPIfldk/42T2oK7lQ4v4JSDwmV0As9GaiUsvbm0=
github.com/go-ole/go-ole v1.2.6 h1:/Fpf6oFPoeFik9ty7siob0G6Ke8QvQEuVcuChpwXzpY=
github.com/go-ole/go-ole v1.2.6/go.mod h1:pprOEPIfldk/42T2oK7lQ4v4JSDwmV0As9GaiUsvbm0=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/go-stack/stack v1.8.0/go.mod h1:v0f6uXyyMGvRgIKkXu+yp6POWl0qKG85gN/melR3HDY=
github.com/go-task/slim-sprig v0.0.0-20210107165309-348f09dbbbc0/go.mod h1:fyg7847qk6SyHyPtNmDHnmrv/HOrqktSC+C9fM+CJOE=
github.com/gogo/protobuf v1.1.1/go.mod h1:r8qH/GZQm5c6nD/R0oafs1akxWv10x8SbQlK7atdtwQ=
github.com/gogo/protobuf v1.2.1/go.mod h1:hp+jE20tsWTFYpLwKvXlhS1hjn+gTNwPg2I6zVXpSg4=
github.com/golang/glog v0.0.0-20160126235308-23def4e6c14b/go.mod h1:SBH7ygxi8pfUlaOkMMuAQtPIUF8ecWP5IEl/CR7VP2Q=
github.com/golang/groupcache v0.0.0-20190129154638-5b532d6fd5ef/go.mod h1:cIg4eruTrX1D+g88fzRXU5OdNfaM+9IcxsU14FzY7Hc=
github.com/golang/mock v1.1.1/go.mod h1:oTYuIxOrZwtPieC+H1uAHpcLFnEyAGVDL/k47Jfbm0A=
Initial import
2022-10-03 09:03:48 +00:00
github.com/golang/protobuf v1.2.0/go.mod h1:6lQm79b+lXiMfvg/cZm0SGofjICqVBUtrP5yJMmIC1U=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/golang/protobuf v1.3.1/go.mod h1:6lQm79b+lXiMfvg/cZm0SGofjICqVBUtrP5yJMmIC1U=
github.com/golang/protobuf v1.3.2/go.mod h1:6lQm79b+lXiMfvg/cZm0SGofjICqVBUtrP5yJMmIC1U=
Initial import
2022-10-03 09:03:48 +00:00
github.com/golang/protobuf v1.4.0-rc.1/go.mod h1:ceaxUfeHdC40wWswd/P6IGgMaK3YpKi5j83Wpe3EHw8=
github.com/golang/protobuf v1.4.0-rc.1.0.20200221234624-67d41d38c208/go.mod h1:xKAWHe0F5eneWXFV3EuXVDTCmh+JuBKY0li0aMyXATA=
github.com/golang/protobuf v1.4.0-rc.2/go.mod h1:LlEzMj4AhA7rCAGe4KMBDvJI+AwstrUpVNzEA03Pprs=
github.com/golang/protobuf v1.4.0-rc.4.0.20200313231945-b860323f09d0/go.mod h1:WU3c8KckQ9AFe+yFwt9sWVRKCVIyN9cPHBJSNnbL67w=
github.com/golang/protobuf v1.4.0/go.mod h1:jodUvKwWbYaEsadDk5Fwe5c77LiNKVO9IDvqG2KuDX0=
github.com/golang/protobuf v1.4.2/go.mod h1:oDoupMAO8OvCJWAcko0GGGIgR6R6ocIYbsSw735rRwI=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/golang/protobuf v1.4.3/go.mod h1:oDoupMAO8OvCJWAcko0GGGIgR6R6ocIYbsSw735rRwI=
github.com/golang/protobuf v1.5.0/go.mod h1:FsONVRAS9T7sI+LIUmWTfcYkHO4aIWwzhcaSAoJOfIk=
Create parition info parsing library to be used both here (when trying to find the partition UUID using a label) and on the kairos side when updating the file after calling kcrypt to encrypt a partition (which causes the UUID to change). Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2022-11-11 08:54:33 +00:00
github.com/golang/protobuf v1.5.2 h1:ROPKBNFfQgOUMifHyP+KYbvpjbdoFNs+aK7DXlji0Tw=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/golang/protobuf v1.5.2/go.mod h1:XVQd3VNwM+JqD3oG2Ue2ip4fOMUkwXdXDdiuN0vRsmY=
github.com/google/btree v1.0.0/go.mod h1:lNA+9X1NB3Zf8V7Ke586lFgjr2dZNuvo3lPJSGZ5JPQ=
github.com/google/go-cmp v0.2.0/go.mod h1:oXzfMopK8JAjlY9xF4vHSVASa0yLyX7SntLO5aqRK0M=
Initial import
2022-10-03 09:03:48 +00:00
github.com/google/go-cmp v0.3.0/go.mod h1:8QqcDgzrUqlUb/G2PQTWiueGozuR1884gddMywk6iLU=
github.com/google/go-cmp v0.3.1/go.mod h1:8QqcDgzrUqlUb/G2PQTWiueGozuR1884gddMywk6iLU=
github.com/google/go-cmp v0.4.0/go.mod h1:v8dTdLbMG2kIc/vJvl+f65V22dbkXbowE6jgT/gNBxE=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/google/go-cmp v0.5.4/go.mod h1:v8dTdLbMG2kIc/vJvl+f65V22dbkXbowE6jgT/gNBxE=
github.com/google/go-cmp v0.5.5/go.mod h1:v8dTdLbMG2kIc/vJvl+f65V22dbkXbowE6jgT/gNBxE=
github.com/google/go-cmp v0.5.6/go.mod h1:v8dTdLbMG2kIc/vJvl+f65V22dbkXbowE6jgT/gNBxE=
github.com/google/go-cmp v0.5.7/go.mod h1:n+brtR0CgQNWTVd5ZUFpTBC8YFBDLK/h/bpaJ8/DtOE=
Create parition info parsing library to be used both here (when trying to find the partition UUID using a label) and on the kairos side when updating the file after calling kcrypt to encrypt a partition (which causes the UUID to change). Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2022-11-11 08:54:33 +00:00
github.com/google/go-cmp v0.5.9 h1:O2Tfq5qg4qc4AmwVlvv0oLiVAGB7enBSJ2x2DqQFi38=
github.com/google/go-cmp v0.5.9/go.mod h1:17dUlkBOakJ0+DkrSSNjCkIjxS6bF9zb3elmeNGIjoY=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/google/pprof v0.0.0-20210407192527-94a9f03dee38/go.mod h1:kpwsk12EmLew5upagYY7GY0pfYCcupk39gWOCRROcvE=
github.com/google/shlex v0.0.0-20191202100458-e7afc7fbc510 h1:El6M4kTTCOh6aBiKaUGG7oYTSPP8MxqL4YI3kZKwcP4=
github.com/google/shlex v0.0.0-20191202100458-e7afc7fbc510/go.mod h1:pupxD2MaaD3pAXIBCelhxNneeOaAeabZDe5s4K6zSpQ=
github.com/google/uuid v1.1.1/go.mod h1:TIyPZe4MgqvfeYDBFedMoGGpEw/LqOeaOT+nhxU+yHo=
github.com/google/uuid v1.3.0/go.mod h1:TIyPZe4MgqvfeYDBFedMoGGpEw/LqOeaOT+nhxU+yHo=
github.com/gookit/color v1.4.2/go.mod h1:fqRyamkC1W8uxl+lxCQxOT09l/vYfZ+QeiX3rKQHCoQ=
github.com/gookit/color v1.5.0/go.mod h1:43aQb+Zerm/BWh2GnrgOQm7ffz7tvQXEKV6BFMl7wAo=
github.com/gookit/color v1.5.2 h1:uLnfXcaFjlrDnQDT+NCBcfhrXqYTx/rcCa6xn01Y8yI=
github.com/gookit/color v1.5.2/go.mod h1:w8h4bGiHeeBpvQVePTutdbERIUf3oJE5lZ8HM0UgXyg=
github.com/gopherjs/gopherjs v0.0.0-20181017120253-0766667cb4d1/go.mod h1:wJfORRmW1u3UXTncJ5qlYoELFm8eSnnEO6hX4iZ3EWY=
github.com/gorilla/websocket v1.4.0/go.mod h1:E7qHFY5m1UJ88s3WnNqhKjPHQ0heANvMoAMk2YaljkQ=
github.com/grpc-ecosystem/go-grpc-middleware v1.0.0/go.mod h1:FiyG127CGDf3tlThmgyCl78X/SZQqEOJBCDaAfeWzPs=
github.com/grpc-ecosystem/go-grpc-prometheus v1.2.0/go.mod h1:8NvIoxWQoOIhqOTXgfV/d3M/q6VIi02HzZEHgUlZvzk=
github.com/grpc-ecosystem/grpc-gateway v1.9.0/go.mod h1:vNeuVxBJEsws4ogUvrchl83t/GYV9WGTSLVdBhOQFDY=
Initial import
2022-10-03 09:03:48 +00:00
github.com/hashicorp/errwrap v1.0.0/go.mod h1:YH+1FKiLXxHSkmPseP+kNlulaMuP3n2brvKWEqk/Jc4=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/hashicorp/errwrap v1.1.0 h1:OxrOeh75EUXMY8TBjag2fzXGZ40LB6IKw45YeGUDY2I=
github.com/hashicorp/errwrap v1.1.0/go.mod h1:YH+1FKiLXxHSkmPseP+kNlulaMuP3n2brvKWEqk/Jc4=
Initial import
2022-10-03 09:03:48 +00:00
github.com/hashicorp/go-multierror v1.1.1 h1:H5DkEtf6CXdFp0N0Em5UCwQpXMWke8IA0+lD48awMYo=
github.com/hashicorp/go-multierror v1.1.1/go.mod h1:iw975J/qwKPdAO1clOe2L8331t/9/fmwbPZ6JB6eMoM=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/hashicorp/hcl v1.0.0/go.mod h1:E5yfLk+7swimpb2L/Alb/PJmXilQ/rhwaUYs4T20WEQ=
Initial import
2022-10-03 09:03:48 +00:00
github.com/hpcloud/tail v1.0.0/go.mod h1:ab1qPbhIpdTxEkNHXyeSf5vhxWSCs/tWer42PpOxQnU=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/huandu/xstrings v1.3.1/go.mod h1:y5/lhBue+AyNmUVz9RLU9xbLR0o4KIIExikq4ovT0aE=
github.com/huandu/xstrings v1.3.2/go.mod h1:y5/lhBue+AyNmUVz9RLU9xbLR0o4KIIExikq4ovT0aE=
github.com/ianlancetaylor/demangle v0.0.0-20200824232613-28f6c0f3b639/go.mod h1:aSSvb/t6k1mPoxDqO4vJh6VOCGPwU4O0C2/Eqndh1Sc=
github.com/imdario/mergo v0.3.11/go.mod h1:jmQim1M+e3UYxmgPu/WyfjB3N3VflVyUjjjwH0dnCYA=
github.com/imdario/mergo v0.3.12/go.mod h1:jmQim1M+e3UYxmgPu/WyfjB3N3VflVyUjjjwH0dnCYA=
github.com/imdario/mergo v0.3.13 h1:lFzP57bqS/wsqKssCGmtLAb8A0wKjLGrve2q3PPVcBk=
github.com/imdario/mergo v0.3.13/go.mod h1:4lJ1jqUDcsbIECGy0RUJAXNIhg+6ocWgb1ALK2O4oXg=
Initial import
2022-10-03 09:03:48 +00:00
github.com/inconshreveable/mousetrap v1.0.0/go.mod h1:PxqpIevigyE2G7u3NXJIT2ANytuPF1OarO4DADm73n8=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/ishidawataru/sctp v0.0.0-20210707070123-9a39160e9062/go.mod h1:co9pwDoBCm1kGxawmb4sPq0cSIOOWNPT4KnHotMP1Zg=
github.com/itchyny/gojq v0.12.8/go.mod h1:gE2kZ9fVRU0+JAksaTzjIlgnCa2akU+a1V0WXgJQN5c=
github.com/itchyny/gojq v0.12.11 h1:YhLueoHhHiN4mkfM+3AyJV6EPcCxKZsOnYf+aVSwaQw=
github.com/itchyny/gojq v0.12.11/go.mod h1:o3FT8Gkbg/geT4pLI0tF3hvip5F3Y/uskjRz9OYa38g=
github.com/itchyny/timefmt-go v0.1.3/go.mod h1:0osSSCQSASBJMsIZnhAaF1C2fCBTJZXrnj37mG8/c+A=
github.com/itchyny/timefmt-go v0.1.5 h1:G0INE2la8S6ru/ZI5JecgyzbbJNs5lG1RcBqa7Jm6GE=
github.com/itchyny/timefmt-go v0.1.5/go.mod h1:nEP7L+2YmAbT2kZ2HfSs1d8Xtw9LY8D2stDBckWakZ8=
Initial import
2022-10-03 09:03:48 +00:00
github.com/jaypipes/ghw v0.9.0 h1:TWF4wNIGtZcgDJaiNcFgby5BR8s2ixcUe0ydxNO2McY=
github.com/jaypipes/ghw v0.9.0/go.mod h1:dXMo19735vXOjpIBDyDYSp31sB2u4hrtRCMxInqQ64k=
github.com/jaypipes/pcidb v1.0.0 h1:vtZIfkiCUE42oYbJS0TAq9XSfSmcsgo9IdxSm9qzYU8=
github.com/jaypipes/pcidb v1.0.0/go.mod h1:TnYUvqhPBzCKnH34KrIX22kAeEbDCSRJ9cqLRCuNDfk=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/jbenet/go-context v0.0.0-20150711004518-d14ea06fba99/go.mod h1:1lJo3i6rXxKeerYnT8Nvf0QmHCRC1n8sfWVwXF2Frvo=
Initial import
2022-10-03 09:03:48 +00:00
github.com/jessevdk/go-flags v1.4.0/go.mod h1:4FA24M0QyGHXBuZZK/XkWh8h0e1EYbRYJSGM75WSRxI=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/jessevdk/go-flags v1.5.0/go.mod h1:Fw0T6WPc1dYxT4mKEZRfG5kJhaTDP9pj1c2EWnYs/m4=
github.com/jmespath/go-jmespath v0.0.0-20180206201540-c2b33e8439af/go.mod h1:Nht3zPeWKUH0NzdCt2Blrr5ys8VGpn0CEB0cQHVjt7k=
github.com/joho/godotenv v1.4.0 h1:3l4+N6zfMWnkbPEXKng2o2/MR5mSwTrBih4ZEkkz1lg=
github.com/joho/godotenv v1.4.0/go.mod h1:f4LDr5Voq0i2e/R5DDNOoa2zzDfwtkZa6DnEwAbqwq4=
github.com/jonboulle/clockwork v0.1.0/go.mod h1:Ii8DK3G1RaLaWxj9trq07+26W01tbo22gdxWY5EU2bo=
github.com/jpillora/backoff v0.0.0-20180909062703-3050d21c67d7/go.mod h1:2iMrUgbbvHEiQClaW2NsSzMyGHqN+rDFqY705q49KG0=
github.com/jtolds/gls v4.20.0+incompatible/go.mod h1:QJZ7F/aHp+rZTRtaJ1ow/lLfFfVYBRgL+9YlvaHOwJU=
github.com/julienschmidt/httprouter v1.2.0/go.mod h1:SYymIcj16QtmaHHD7aYtjjsJG7VTCxuUUipMqKk8s4w=
github.com/kairos-io/kairos v1.24.3-56.0.20230118103822-e3dbd41dddd1 h1:CRLvgZ5/iJAVZwbQvDJLPKNM3yWIlFsArlYhOVVrm8g=
github.com/kairos-io/kairos v1.24.3-56.0.20230118103822-e3dbd41dddd1/go.mod h1:YAqNNHoJyWknQQtWFmYDgvchClhhuMCrsdZdSVhIegc=
Initial import
2022-10-03 09:03:48 +00:00
github.com/kballard/go-shellquote v0.0.0-20180428030007-95032a82bc51 h1:Z9n2FFNUXsshfwJMBgNA0RU6/i7WVaAegv3PtuIHPMs=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/kevinburke/ssh_config v0.0.0-20201106050909-4977a11b4351/go.mod h1:CT57kijsi8u/K/BOFA39wgDQJ9CxiF4nAY/ojJ6r6mM=
github.com/kevinburke/ssh_config v1.2.0/go.mod h1:CT57kijsi8u/K/BOFA39wgDQJ9CxiF4nAY/ojJ6r6mM=
github.com/kisielk/errcheck v1.1.0/go.mod h1:EZBBE59ingxPouuu3KfxchcWSUPOHkagtvWXihfKN4Q=
github.com/kisielk/gotool v1.0.0/go.mod h1:XhKaO+MFFWcvkIS/tQcRk01m1F5IRFswLeQ+oQHNcck=
github.com/klauspost/cpuid/v2 v2.0.9/go.mod h1:FInQzS24/EEf25PyTYn52gqo7WaD8xa0213Md/qVLRg=
github.com/klauspost/cpuid/v2 v2.0.10/go.mod h1:g2LTdtYhdyuGPqyWyv7qRAmj1WBqxuObKfj5c0PQa7c=
github.com/klauspost/cpuid/v2 v2.0.12/go.mod h1:g2LTdtYhdyuGPqyWyv7qRAmj1WBqxuObKfj5c0PQa7c=
github.com/klauspost/cpuid/v2 v2.2.0 h1:4ZexSFt8agMNzNisrsilL6RClWDC5YJnLHNIfTy4iuc=
github.com/konsorten/go-windows-terminal-sequences v1.0.1/go.mod h1:T0+1ngSBFLxvqU3pZ+m/2kptfBszLMUkC4ZK/EgS/cQ=
github.com/kr/logfmt v0.0.0-20140226030751-b84e30acd515/go.mod h1:+0opPa2QZZtGFBFZlji/RkVcI2GknAs/DXo4wKdlNEc=
Initial import
2022-10-03 09:03:48 +00:00
github.com/kr/pretty v0.1.0/go.mod h1:dAy3ld7l9f0ibDNOQOHHMYYIIbhfbHSm3C4ZsoJORNo=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/kr/pretty v0.2.0/go.mod h1:ipq/a2n7PKx3OHsz4KJII5eveXtPO4qwEXGdVfWzfnI=
github.com/kr/pretty v0.2.1/go.mod h1:ipq/a2n7PKx3OHsz4KJII5eveXtPO4qwEXGdVfWzfnI=
github.com/kr/pretty v0.3.0 h1:WgNl7dwNpEZ6jJ9k1snq4pZsg7DOEN8hP9Xw0Tsjwk0=
github.com/kr/pretty v0.3.0/go.mod h1:640gp4NfQd8pI5XOwp5fnNeVWj67G7CFk/SaSQn7NBk=
Initial import
2022-10-03 09:03:48 +00:00
github.com/kr/pty v1.1.1/go.mod h1:pFQYn66WHrOpPYNljwOMqo10TkYh1fy3cYio2l3bCsQ=
github.com/kr/text v0.1.0/go.mod h1:4Jbv+DJW3UT/LiOwJeYQe1efqtUx/iVham/4vfdArNI=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/kr/text v0.2.0 h1:5Nx0Ya0ZqY2ygV366QzturHI13Jq95ApcVaJBhpS+AY=
github.com/kr/text v0.2.0/go.mod h1:eLer722TekiGuMkidMxC/pM04lWEeraHUUmBw8l2grE=
github.com/lithammer/fuzzysearch v1.1.5 h1:Ag7aKU08wp0R9QCfF4GoGST9HbmAIeLP7xwMrOBEp1c=
github.com/lithammer/fuzzysearch v1.1.5/go.mod h1:1R1LRNk7yKid1BaQkmuLQaHruxcC4HmAH30Dh61Ih1Q=
github.com/magiconair/properties v1.8.0/go.mod h1:PppfXfuXeibc/6YijjN8zIbojt8czPbwD3XqdrwzmxQ=
github.com/matryer/is v1.2.0/go.mod h1:2fLPjFQM9rhQ15aVEtbuwhJinnOqrmgXPNdZsdwlWXA=
github.com/mattn/go-colorable v0.1.1/go.mod h1:FuOcm+DKB9mbwrcAfNl7/TZVBZ6rcnceauSikq3lYCQ=
github.com/mattn/go-colorable v0.1.2/go.mod h1:U0ppj6V5qS13XJ6of8GYAs25YV2eR4EVcfRqFIhoBtE=
github.com/mattn/go-isatty v0.0.5/go.mod h1:Iq45c/XA43vh69/j3iqttzPXn0bhXyGjM0Hdxcsrc5s=
github.com/mattn/go-isatty v0.0.8/go.mod h1:Iq45c/XA43vh69/j3iqttzPXn0bhXyGjM0Hdxcsrc5s=
github.com/mattn/go-isatty v0.0.14/go.mod h1:7GGIvUiUoEMVVmxf/4nioHXj79iQHKdU27kJ6hsGG94=
github.com/mattn/go-isatty v0.0.16 h1:bq3VjFmv/sOjHtdEhmkEV4x1AJtvUvOJ2PFAZ5+peKQ=
github.com/mattn/go-isatty v0.0.16/go.mod h1:kYGgaQfpe5nmfYZH+SKPsOc2e4SrIfOl2e/yFXSvRLM=
github.com/mattn/go-runewidth v0.0.9/go.mod h1:H031xJmbD/WCDINGzjvQ9THkh0rPKHF+m2gUSrubnMI=
github.com/mattn/go-runewidth v0.0.13/go.mod h1:Jdepj2loyihRzMpdS35Xk/zdY8IAYHsh153qUoGf23w=
github.com/mattn/go-runewidth v0.0.14 h1:+xnbZSEeDbOIg5/mE6JF0w6n9duR1l3/WmbinWVwUuU=
github.com/mattn/go-runewidth v0.0.14/go.mod h1:Jdepj2loyihRzMpdS35Xk/zdY8IAYHsh153qUoGf23w=
github.com/matttproud/golang_protobuf_extensions v1.0.1/go.mod h1:D8He9yQNgCq6Z5Ld7szi9bcBfOoFv/3dc6xSMkL2PC0=
github.com/mgutz/ansi v0.0.0-20170206155736-9520e82c474b/go.mod h1:01TrycV0kFyexm33Z7vhZRXopbI8J3TDReVlkTgMUxE=
github.com/mitchellh/copystructure v1.0.0/go.mod h1:SNtv71yrdKgLRyLFxmLdkAbkKEFWgYaq1OVrnRcwhnw=
github.com/mitchellh/copystructure v1.2.0/go.mod h1:qLl+cE2AmVv+CoeAwDPye/v+N2HKCj9FbZEVFJRxO9s=
Initial import
2022-10-03 09:03:48 +00:00
github.com/mitchellh/go-homedir v1.0.0/go.mod h1:SfyaCUpYCn1Vlf4IUYiD9fPX4A5wJrkLzIz1N1q0pr0=
github.com/mitchellh/go-homedir v1.1.0 h1:lukF9ziXFxDFPkA1vsr5zpc1XuPDn/wFntq5mG+4E0Y=
github.com/mitchellh/go-homedir v1.1.0/go.mod h1:SfyaCUpYCn1Vlf4IUYiD9fPX4A5wJrkLzIz1N1q0pr0=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/mitchellh/mapstructure v1.1.2/go.mod h1:FVVH3fgwuzCH5S8UJGiWEs2h04kUh9fWfEaFds41c1Y=
github.com/mitchellh/reflectwalk v1.0.0/go.mod h1:mSTlrgnPZtwu0c4WaC2kGObEpuNDbx0jmZXqmk4esnw=
github.com/mitchellh/reflectwalk v1.0.2/go.mod h1:mSTlrgnPZtwu0c4WaC2kGObEpuNDbx0jmZXqmk4esnw=
github.com/moby/libnetwork v0.8.0-dev.2.0.20200612180813-9e99af28df21/go.mod h1:RQTqDxGZChsPHosY8R3ZL2THYWUuW8X5SRhiBNoTY5I=
github.com/mudler/entities v0.0.0-20211108084227-d1414478861b/go.mod h1:qquFT9tYp+/NO7tTotto4BT9zSRYSMDxo2PGZwujpFA=
Initial import
2022-10-03 09:03:48 +00:00
github.com/mudler/go-pluggable v0.0.0-20220716112424-189d463e3ff3 h1:t4X6t8WisUy5mExfS58RBOkzaEGmuor5kOUMQS8lT2g=
github.com/mudler/go-pluggable v0.0.0-20220716112424-189d463e3ff3/go.mod h1:WmKcT8ONmhDQIqQ+HxU+tkGWjzBEyY/KFO8LTGCu4AI=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/mudler/yip v0.11.4 h1:xTeSOtK2JUCCbtpkdQsZsJyIbTRwxWWBj1B/Np7bI/4=
github.com/mudler/yip v0.11.4/go.mod h1:hdQfJzbhjSclVGhTzWKhCLdonoFUM0fZGwibNE5Rtr8=
github.com/mwitkow/go-conntrack v0.0.0-20161129095857-cc309e4a2223/go.mod h1:qRWi+5nqEBWmkhHvq77mSJWrCKwh8bxhgT7d/eI7P4U=
github.com/nfnt/resize v0.0.0-20180221191011-83c6a9932646 h1:zYyBkD/k9seD2A7fsi6Oo2LfFZAehjjQMERAvZLEDnQ=
github.com/nfnt/resize v0.0.0-20180221191011-83c6a9932646/go.mod h1:jpp1/29i3P1S/RLdc7JQKbRpFeM1dOBd8T9ki5s+AY8=
github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e/go.mod h1:zD1mROLANZcx1PVRCS0qkT7pwLkGfwJo4zjcN/Tysno=
Initial import
2022-10-03 09:03:48 +00:00
github.com/nxadm/tail v1.4.4/go.mod h1:kenIhsEOeOJmVchQTgglprH7qJGnHDVpk1VPCcaMI8A=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/nxadm/tail v1.4.8 h1:nPr65rt6Y5JFSKQO7qToXr7pePgD6Gwiw05lkbyAQTE=
github.com/nxadm/tail v1.4.8/go.mod h1:+ncqLTQzXmGhMZNUePPaPqPvBxHAIsmXswZKocGu+AU=
github.com/oklog/ulid v1.3.1/go.mod h1:CirwcVhetQ6Lv90oh/F+FBtV6XMibvdAFo93nm5qn4U=
github.com/olekukonko/tablewriter v0.0.5/go.mod h1:hPp6KlRPjbx+hW8ykQs1w3UBbZlj6HuIJcUGPhkA7kY=
Initial import
2022-10-03 09:03:48 +00:00
github.com/onsi/ginkgo v1.6.0/go.mod h1:lLunBs/Ym6LB5Z9jYTR76FiuTmxDTDusOGeTQH+WWjE=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/onsi/ginkgo v1.12.0/go.mod h1:oUhWkIvk5aDxtKvDDuw8gItl8pKl42LzjC9KZE0HfGg=
Initial import
2022-10-03 09:03:48 +00:00
github.com/onsi/ginkgo v1.12.1/go.mod h1:zj2OWP4+oCPe1qIXoGWkgMRwljMUYCdkwsT2108oapk=
github.com/onsi/ginkgo v1.14.2/go.mod h1:iSB4RoI2tjJc9BBv4NKIKWKya62Rps+oPG/Lv9klQyY=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/onsi/ginkgo v1.16.1/go.mod h1:CObGmKUOKaSC0RjmoAK7tKyn4Azo5P2IWuoMnvwxz1E=
github.com/onsi/ginkgo v1.16.4 h1:29JGrr5oVBm5ulCWet69zQkzWipVXIol6ygQUe/EzNc=
github.com/onsi/ginkgo v1.16.4/go.mod h1:dX+/inL/fNMqNlz0e9LfyB9TswhZpCVdJM/Z6Vvnwo0=
github.com/onsi/ginkgo/v2 v2.0.0/go.mod h1:vw5CSIxN1JObi/U8gcbwft7ZxR2dgaR70JSE3/PpL4c=
github.com/onsi/ginkgo/v2 v2.1.0/go.mod h1:vw5CSIxN1JObi/U8gcbwft7ZxR2dgaR70JSE3/PpL4c=
github.com/onsi/ginkgo/v2 v2.7.0 h1:/XxtEV3I3Eif/HobnVx9YmJgk8ENdRsuUmM+fLCFNow=
github.com/onsi/ginkgo/v2 v2.7.0/go.mod h1:yjiuMwPokqY1XauOgju45q3sJt6VzQ/Fict1LFVcsAo=
github.com/onsi/gomega v1.5.0/go.mod h1:ex+gbHU/CVuBBDIJjb2X0qEXbFg53c61hWP/1CpauHY=
Initial import
2022-10-03 09:03:48 +00:00
github.com/onsi/gomega v1.7.1/go.mod h1:XdKZgCCFLUoM/7CFJVPcG8C1xQ1AJ0vpAezJrB7JYyY=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/onsi/gomega v1.9.0/go.mod h1:Ho0h+IUsWyvy1OpqCwxlQ/21gkhVunqlU8fDGcoTdcA=
Initial import
2022-10-03 09:03:48 +00:00
github.com/onsi/gomega v1.10.1/go.mod h1:iN09h71vgCQne3DLsj+A5owkum+a2tYe+TOCB1ybHNo=
github.com/onsi/gomega v1.10.3/go.mod h1:V9xEwhxec5O8UDM77eCW8vLymOMltsqPVYWrpDsH8xc=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/onsi/gomega v1.11.0/go.mod h1:azGKhqFUon9Vuj0YmTfLSmx0FUwqXYSTl5re8lQLTUg=
github.com/onsi/gomega v1.17.0/go.mod h1:HnhC7FXeEQY45zxNK3PPoIUhzk/80Xly9PcubAlGdZY=
github.com/onsi/gomega v1.18.0/go.mod h1:0q+aL8jAiMXy9hbwj2mr5GziHiwhAIQpFmmtT5hitRs=
github.com/onsi/gomega v1.25.0 h1:Vw7br2PCDYijJHSfBOWhov+8cAnUf8MfMaIOV323l6Y=
github.com/onsi/gomega v1.25.0/go.mod h1:r+zV744Re+DiYCIPRlYOTxn0YkOLcAnW8k1xXdMPGhM=
github.com/otiai10/copy v1.9.0 h1:7KFNiCgZ91Ru4qW4CWPf/7jqtxLagGRmIxWldPP9VY4=
github.com/otiai10/copy v1.9.0/go.mod h1:hsfX19wcn0UWIHUQ3/4fHuehhk2UyArQ9dVFAn3FczI=
Initial import
2022-10-03 09:03:48 +00:00
github.com/otiai10/curr v0.0.0-20150429015615-9b4961190c95/go.mod h1:9qAhocn7zKJG+0mI8eUu6xqkFDYS2kb2saOteoSB3cE=
github.com/otiai10/curr v1.0.0/go.mod h1:LskTG5wDwr8Rs+nNQ+1LlxRjAtTZZjtJW4rMXl6j4vs=
github.com/otiai10/mint v1.3.0/go.mod h1:F5AjcsTsWUqX+Na9fpHb52P8pcRX2CI6A3ctIT91xUo=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/otiai10/mint v1.4.0 h1:umwcf7gbpEwf7WFzqmWwSv0CzbeMsae2u9ZvpP8j2q4=
github.com/otiai10/mint v1.4.0/go.mod h1:gifjb2MYOoULtKLqUAEILUG/9KONW6f7YsJ6vQLTlFI=
github.com/packethost/packngo v0.1.0/go.mod h1:otzZQXgoO96RTzDB/Hycg0qZcXZsWJGJRSXbmEIJ+4M=
github.com/packethost/packngo v0.25.0/go.mod h1:/UHguFdPs6Lf6FOkkSEPnRY5tgS0fsVM+Zv/bvBrmt0=
github.com/pelletier/go-toml v1.2.0/go.mod h1:5z9KED0ma1S8pY6P1sdut58dfprrGBbd/94hg7ilaic=
github.com/phayes/permbits v0.0.0-20190612203442-39d7c581d2ee/go.mod h1:3uODdxMgOaPYeWU7RzZLxVtJHZ/x1f/iHkBZuKJDzuY=
github.com/pierrec/lz4 v2.3.0+incompatible/go.mod h1:pdkljMzZIN41W+lC3N2tnIh5sFi+IEE17M5jbnwPHcY=
github.com/pierrec/lz4 v2.6.1+incompatible/go.mod h1:pdkljMzZIN41W+lC3N2tnIh5sFi+IEE17M5jbnwPHcY=
github.com/pkg/errors v0.8.0/go.mod h1:bwawxfHBFNV+L2hUp1rHADufV3IMtnDRdf1r5NINEl0=
github.com/pkg/errors v0.8.1/go.mod h1:bwawxfHBFNV+L2hUp1rHADufV3IMtnDRdf1r5NINEl0=
Initial import
2022-10-03 09:03:48 +00:00
github.com/pkg/errors v0.9.1 h1:FEBLx1zS214owpjy7qsBeixbURkuhQAwrK5UwLGTwt4=
github.com/pkg/errors v0.9.1/go.mod h1:bwawxfHBFNV+L2hUp1rHADufV3IMtnDRdf1r5NINEl0=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/pkg/xattr v0.4.1/go.mod h1:W2cGD0TBEus7MkUgv0tNZ9JutLtVO3cXu+IBRuHqnFs=
github.com/pkg/xattr v0.4.7/go.mod h1:di8WF84zAKk8jzR1UBTEWh9AUlIZZ7M/JNt8e9B6ktU=
Initial import
2022-10-03 09:03:48 +00:00
github.com/pmezard/go-difflib v1.0.0 h1:4DBwDE0NGyQoBHbLQYPwSUPoCMWR5BEzIk/f1lZbAQM=
github.com/pmezard/go-difflib v1.0.0/go.mod h1:iKH77koFhYxTK1pcRnkKkqfTogsbg7gZNVY4sRDYZ/4=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/prometheus/client_golang v0.9.1/go.mod h1:7SWBe2y4D6OKWSNQJUaRYU/AaXPKyh/dDVn+NZz0KFw=
github.com/prometheus/client_golang v0.9.3/go.mod h1:/TN21ttK/J9q6uSwhBd54HahCDft0ttaMvbicHlPoso=
github.com/prometheus/client_model v0.0.0-20180712105110-5c3871d89910/go.mod h1:MbSGuTsp3dbXC40dX6PRTWyKYBIrTGTE9sqQNg2J8bo=
github.com/prometheus/client_model v0.0.0-20190129233127-fd36f4220a90/go.mod h1:xMI15A0UPsDsEKsMN9yxemIoYk6Tm2C1GtYGdfGttqA=
github.com/prometheus/common v0.0.0-20181113130724-41aa239b4cce/go.mod h1:daVV7qP5qjZbuso7PdcryaAu0sAZbrN9i7WWcTMWvro=
github.com/prometheus/common v0.4.0/go.mod h1:TNfzLD0ON7rHzMJeJkieUDPYmFC7Snx/y86RQel1bk4=
github.com/prometheus/procfs v0.0.0-20181005140218-185b4288413d/go.mod h1:c3At6R/oaqEKCNdg8wHV1ftS6bRYblBhIjjI8uT2IGk=
github.com/prometheus/procfs v0.0.0-20190507164030-5867b95ac084/go.mod h1:TjEm7ze935MbeOT/UhFTIMYKhuLP4wbCsTZCD3I8kEA=
github.com/prometheus/tsdb v0.7.1/go.mod h1:qhTCs0VvXwvX/y3TZrWD7rabWM+ijKTux40TwIPHuXU=
github.com/pterm/pterm v0.12.27/go.mod h1:PhQ89w4i95rhgE+xedAoqous6K9X+r6aSOI2eFF7DZI=
github.com/pterm/pterm v0.12.29/go.mod h1:WI3qxgvoQFFGKGjGnJR849gU0TsEOvKn5Q8LlY1U7lg=
github.com/pterm/pterm v0.12.30/go.mod h1:MOqLIyMOgmTDz9yorcYbcw+HsgoZo3BQfg2wtl3HEFE=
github.com/pterm/pterm v0.12.31/go.mod h1:32ZAWZVXD7ZfG0s8qqHXePte42kdz8ECtRyEejaWgXU=
github.com/pterm/pterm v0.12.33/go.mod h1:x+h2uL+n7CP/rel9+bImHD5lF3nM9vJj80k9ybiiTTE=
github.com/pterm/pterm v0.12.36/go.mod h1:NjiL09hFhT/vWjQHSj1athJpx6H8cjpHXNAK5bUw8T8=
github.com/pterm/pterm v0.12.40/go.mod h1:ffwPLwlbXxP+rxT0GsgDTzS3y3rmpAO1NMjUkGTYf8s=
github.com/pterm/pterm v0.12.53 h1:8ERV5eXyvXlAIY8LRrhapPS34j7IKKDAnb7o1Ih3T0w=
github.com/pterm/pterm v0.12.53/go.mod h1:BY2H3GtX2BX0ULqLY11C2CusIqnxsYerbkil3XvXIBg=
github.com/qeesung/image2ascii v1.0.1 h1:Fe5zTnX/v/qNC3OC4P/cfASOXS501Xyw2UUcgrLgtp4=
github.com/qeesung/image2ascii v1.0.1/go.mod h1:kZKhyX0h2g/YXa/zdJR3JnLnJ8avHjZ3LrvEKSYyAyU=
github.com/rivo/uniseg v0.2.0 h1:S1pD9weZBuJdFmowNwbpi7BJ8TNftyUImj/0WQi72jY=
github.com/rivo/uniseg v0.2.0/go.mod h1:J6wj4VEh+S6ZtnVlnTBMWIodfgj8LQOQFoIToxlJtxc=
github.com/rogpeppe/fastuuid v0.0.0-20150106093220-6724a57986af/go.mod h1:XWv6SoW27p1b0cqNHllgS5HIMJraePCO15w5zCzIWYg=
github.com/rogpeppe/fastuuid v1.1.0/go.mod h1:jVj6XXZzXRy/MSR5jhDC/2q6DgLz+nrA6LYCDYWNEvQ=
github.com/rogpeppe/go-internal v1.6.1 h1:/FiVV8dS/e+YqF2JvO3yXRFbBLTIuSDkuC7aBOAvL+k=
github.com/rogpeppe/go-internal v1.6.1/go.mod h1:xXDCJY+GAPziupqXw64V24skbSoqbTEfhy4qGm1nDQc=
Initial import
2022-10-03 09:03:48 +00:00
github.com/russross/blackfriday/v2 v2.0.1/go.mod h1:+Rmxgy9KzJVeS9/2gXHxylqXiyQDYRxCVz55jmeOWTM=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/russross/blackfriday/v2 v2.1.0 h1:JIOH55/0cWyOuilr9/qlrm0BSXldqnqwMsf35Ld67mk=
github.com/russross/blackfriday/v2 v2.1.0/go.mod h1:+Rmxgy9KzJVeS9/2gXHxylqXiyQDYRxCVz55jmeOWTM=
github.com/satori/go.uuid v1.2.1-0.20180404165556-75cca531ea76/go.mod h1:dA0hQrYB0VpLJoorglMZABFdXlWrHn1NEOzdhQKdks0=
github.com/sergi/go-diff v1.0.0/go.mod h1:0CfEIISq7TuYL3j771MWULgwwjU+GofnZX9QAmXWZgo=
github.com/sergi/go-diff v1.1.0/go.mod h1:STckp+ISIX8hZLjrqAeVduY0gWCT9IjLuqbuNXdaHfM=
github.com/sergi/go-diff v1.2.0 h1:XU+rvMAioB0UC3q1MFrIQy4Vo5/4VsRDQQXHsEya6xQ=
github.com/sergi/go-diff v1.2.0/go.mod h1:STckp+ISIX8hZLjrqAeVduY0gWCT9IjLuqbuNXdaHfM=
github.com/shopspring/decimal v1.2.0/go.mod h1:DKyhrW/HYNuLGql+MJL6WCR6knT2jwCFRcu2hWCYk4o=
github.com/shopspring/decimal v1.3.1/go.mod h1:DKyhrW/HYNuLGql+MJL6WCR6knT2jwCFRcu2hWCYk4o=
Initial import
2022-10-03 09:03:48 +00:00
github.com/shurcooL/sanitized_anchor_name v1.0.0/go.mod h1:1NzhyTcUVG4SuEtjjoZeVRXNmyL/1OwPU0+IJeTBvfc=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/sirupsen/logrus v1.0.3/go.mod h1:pMByvHTf9Beacp5x1UXfOR9xyW/9antXMhjMPG0dEzc=
github.com/sirupsen/logrus v1.2.0/go.mod h1:LxeOpSwHxABJmUn/MG1IvRgCAasNZTLOkJPxbbu5VWo=
github.com/sirupsen/logrus v1.4.1/go.mod h1:ni0Sbl8bgC9z8RoU9G6nDWqqs/fq4eDPysMBDgk/93Q=
github.com/sirupsen/logrus v1.7.0/go.mod h1:yWOB1SBYBC5VeMP7gHvWumXLIWorT60ONWic61uBYv0=
github.com/sirupsen/logrus v1.8.1/go.mod h1:yWOB1SBYBC5VeMP7gHvWumXLIWorT60ONWic61uBYv0=
github.com/smartystreets/assertions v0.0.0-20180927180507-b2de0cb4f26d/go.mod h1:OnSkiWE9lh6wB0YB77sQom3nweQdgAjqCqsofrRNTgc=
github.com/smartystreets/assertions v1.0.0/go.mod h1:kHHU4qYBaI3q23Pp3VPrmWhuIUrLW/7eUrw0BU5VaoM=
github.com/smartystreets/go-aws-auth v0.0.0-20180515143844-0c1422d1fdb9/go.mod h1:SnhjPscd9TpLiy1LpzGSKh3bXCfxxXuqd9xmQJy3slM=
github.com/smartystreets/goconvey v1.6.4/go.mod h1:syvi0/a8iFYH4r/RixwvyeAJjdLS9QV7WQ/tjFTllLA=
github.com/smartystreets/gunit v1.0.0/go.mod h1:qwPWnhz6pn0NnRBP++URONOVyNkPyr4SauJk4cUOwJs=
github.com/soheilhy/cmux v0.1.4/go.mod h1:IM3LyeVVIOuxMH7sFAkER9+bJ4dT7Ms6E4xg4kGIyLM=
github.com/spaolacci/murmur3 v0.0.0-20180118202830-f09979ecbc72/go.mod h1:JwIasOWyU6f++ZhiEuf87xNszmSA2myDM2Kzu9HwQUA=
github.com/spf13/afero v1.1.2/go.mod h1:j4pytiNVoe2o6bmDsKpLACNPDBIoEAkihy7loJ1B0CQ=
github.com/spf13/cast v1.3.0/go.mod h1:Qx5cxh0v+4UWYiBimWS+eyWzqEqokIECu5etghLkUJE=
github.com/spf13/cast v1.3.1/go.mod h1:Qx5cxh0v+4UWYiBimWS+eyWzqEqokIECu5etghLkUJE=
github.com/spf13/cast v1.5.0/go.mod h1:SpXXQ5YoyJw6s3/6cMTQuxvgRl3PCJiyaX9p6b155UU=
Initial import
2022-10-03 09:03:48 +00:00
github.com/spf13/cobra v0.0.3/go.mod h1:1l0Ry5zgKvJasoi3XT1TypsSe7PqH0Sj9dhYf7v3XqQ=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/spf13/cobra v0.0.6/go.mod h1:/6GTrnGXV9HjY+aR4k0oJ5tcvakLuG6EuKReYlHNrgE=
github.com/spf13/cobra v1.5.0/go.mod h1:dWXEIy2H428czQCjInthrTRUg7yKbok+2Qi/yBIJoUM=
github.com/spf13/jwalterweatherman v1.0.0/go.mod h1:cQK4TGJAtQXfYWX+Ddv3mKDzgVb68N+wFjFa4jdeBTo=
Initial import
2022-10-03 09:03:48 +00:00
github.com/spf13/pflag v1.0.2/go.mod h1:DYY7MBk1bdzusC3SYhjObp+wFpr4gzcvqqNjLnInEg4=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/spf13/pflag v1.0.3/go.mod h1:DYY7MBk1bdzusC3SYhjObp+wFpr4gzcvqqNjLnInEg4=
github.com/spf13/pflag v1.0.5/go.mod h1:McXfInJRrz4CZXVZOBLb0bTZqETkiAhM9Iw0y3An2Bg=
github.com/spf13/viper v1.4.0/go.mod h1:PTJ7Z/lr49W6bUbkmS1V3by4uWynFiR9p7+dSq/yZzE=
github.com/stretchr/objx v0.1.0/go.mod h1:HFkY916IF+rwdDfMAkV7OtwuqBVzrE8GR6GFx+wExME=
github.com/stretchr/objx v0.1.1/go.mod h1:HFkY916IF+rwdDfMAkV7OtwuqBVzrE8GR6GFx+wExME=
github.com/stretchr/objx v0.4.0 h1:M2gUjqZET1qApGOWNSnZ49BAIMX4F/1plDv3+l31EJ4=
github.com/stretchr/objx v0.4.0/go.mod h1:YvHI0jy2hoMjB+UWwv71VJQ9isScKT/TqJzVSSt89Yw=
github.com/stretchr/testify v1.2.2/go.mod h1:a8OnRcib4nhh0OaRAV+Yts87kKdq0PP7pXfy6kDkUVs=
github.com/stretchr/testify v1.3.0/go.mod h1:M5WIy9Dh21IEIfnGCwXGc5bZfKNJtfHm1UVUgZn+9EI=
github.com/stretchr/testify v1.4.0/go.mod h1:j7eGeouHqKxXV5pUuKE4zz7dFj8WfuZ+81PSLYec5m4=
github.com/stretchr/testify v1.5.1/go.mod h1:5W2xD1RspED5o8YsWQXVCued0rvSQ+mT+I5cxcmMvtA=
github.com/stretchr/testify v1.6.1/go.mod h1:6Fq8oRcR53rry900zMqJjRRixrwX3KX962/h/Wwjteg=
github.com/stretchr/testify v1.7.0/go.mod h1:6Fq8oRcR53rry900zMqJjRRixrwX3KX962/h/Wwjteg=
github.com/stretchr/testify v1.7.1/go.mod h1:6Fq8oRcR53rry900zMqJjRRixrwX3KX962/h/Wwjteg=
github.com/stretchr/testify v1.8.0/go.mod h1:yNjHg4UonilssWZ8iaSj1OCr/vHnekPRkoO+kdMU+MU=
github.com/stretchr/testify v1.8.1 h1:w7B6lhMri9wdJUVmEZPGGhZzrYTPvgJArz7wNPgYKsk=
github.com/tj/assert v0.0.0-20171129193455-018094318fb0/go.mod h1:mZ9/Rh9oLWpLLDRpvE+3b7gP/C2YyLFYxNmcLnPTMe0=
github.com/tj/assert v0.0.3/go.mod h1:Ne6X72Q+TB1AteidzQncjw9PabbMp4PBMZ1k+vd1Pvk=
github.com/tj/go-buffer v1.1.0/go.mod h1:iyiJpfFcR2B9sXu7KvjbT9fpM4mOelRSDTbntVj52Uc=
github.com/tj/go-elastic v0.0.0-20171221160941-36157cbbebc2/go.mod h1:WjeM0Oo1eNAjXGDx2yma7uG2XoyRZTq1uv3M/o7imD0=
github.com/tj/go-kinesis v0.0.0-20171128231115-08b17f58cb1b/go.mod h1:/yhzCV0xPfx6jb1bBgRFjl5lytqVqZXEaeqWP8lTEao=
github.com/tj/go-spin v1.1.0/go.mod h1:Mg1mzmePZm4dva8Qz60H2lHwmJ2loum4VIrLgVnKwh4=
github.com/tmc/grpc-websocket-proxy v0.0.0-20190109142713-0ad062ec5ee5/go.mod h1:ncp9v5uamzpCO7NfCPTXjqaC+bZgJeR0sMTm6dMHP7U=
Initial import
2022-10-03 09:03:48 +00:00
github.com/tmc/scp v0.0.0-20170824174625-f7b48647feef h1:7D6Nm4D6f0ci9yttWaKjM1TMAXrH5Su72dojqYGntFY=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
github.com/tredoe/osutil/v2 v2.0.0-rc.16/go.mod h1:uLRVx/3pb7Y4RQhG8cQFbPE9ha5r81e6MXpBsxbTAYc=
github.com/twpayne/go-vfs v1.7.2 h1:ZNYMAXcu2Av8c109USrSGYm8dIIIV0xPlG19I2088Kw=
github.com/twpayne/go-vfs v1.7.2/go.mod h1:1eni2ntkiiAHZG27xfLOO4CYvMR4Kw8V7rYiLeeolsQ=
github.com/ugorji/go v1.1.4/go.mod h1:uQMGLiO92mf5W77hV/PUCpI3pbzQx3CRekS0kk+RGrc=
github.com/ulikunitz/xz v0.5.10/go.mod h1:nbz6k7qbPmH4IRqmfOplQw/tblSgqTqBwxkY0oWt/14=
github.com/urfave/cli v1.22.11 h1:3wLoofQeDAA/zDjLA4uvtzIv73+qdxJ3QkxfAqk4UVI=
github.com/urfave/cli v1.22.11/go.mod h1:Gos4lmkARVdJ6EkW0WaNv/tZAAMe9V7XWyB60NtXRu0=
github.com/vishvananda/netlink v0.0.0-20170808154308-f5a6f697a596/go.mod h1:+SR5DhBJrl6ZM7CoCKvpw5BKroDKQ+PJqOg65H/2ktk=
github.com/vishvananda/netlink v1.1.0/go.mod h1:cTgwzPIzzgDAYoQrMm0EdrjRUBkTqKYppBueQtXaqoE=
github.com/vishvananda/netns v0.0.0-20170707011535-86bef332bfc3/go.mod h1:ZjcWmFBXmLKZu9Nxj3WKYEafiSqer2rnvPr0en9UNpI=
github.com/vishvananda/netns v0.0.0-20191106174202-0a2b9b5464df/go.mod h1:JP3t17pCcGlemwknint6hfoeCVQrEMVwxRLRjXpq+BU=
github.com/vishvananda/netns v0.0.0-20211101163701-50045581ed74/go.mod h1:DD4vA1DwXk04H54A1oHXtwZmA0grkVMdPxx/VGLCah0=
github.com/wayneashleyberry/terminal-dimensions v1.1.0 h1:EB7cIzBdsOzAgmhTUtTTQXBByuPheP/Zv1zL2BRPY6g=
github.com/wayneashleyberry/terminal-dimensions v1.1.0/go.mod h1:2lc/0eWCObmhRczn2SdGSQtgBooLUzIotkkEGXqghyg=
github.com/willdonnelly/passwd v0.0.0-20141013001024-7935dab3074c/go.mod h1:xcvfY9pOw6s4wyrhilFSbMthL6KzgrfCIETHHUOQ/fQ=
github.com/xanzy/ssh-agent v0.3.0/go.mod h1:3s9xbODqPuuhK9JV1R321M/FlMZSBvE5aY6eAcqrDh0=
github.com/xanzy/ssh-agent v0.3.1/go.mod h1:QIE4lCeL7nkC25x+yA3LBIYfwCc1TFziCtG7cBAac6w=
github.com/xiang90/probing v0.0.0-20190116061207-43a291ad63a2/go.mod h1:UETIi67q53MR2AWcXfiuqkDkRtnGDLqkBTpCHuJHxtU=
github.com/xo/terminfo v0.0.0-20210125001918-ca9a967f8778 h1:QldyIu/L63oPpyvQmHgvgickp1Yw510KJOqX7H24mg8=
github.com/xo/terminfo v0.0.0-20210125001918-ca9a967f8778/go.mod h1:2MuV+tbUrU1zIOPMxZ5EncGwgmMJsa+9ucAQZXxsObs=
github.com/xordataexchange/crypt v0.0.3-0.20170626215501-b2862e3d0a77/go.mod h1:aYKd//L2LvnjZzWKhF00oedf4jCCReLcmhLdhm1A27Q=
github.com/yuin/goldmark v1.2.1/go.mod h1:3hX8gzYuyVAZsxl0MRgGTJEmQBFcNTphYh9decYSb74=
github.com/zcalusic/sysinfo v0.9.5/go.mod h1:Z/gPVufBrFc8X5sef3m6kkw3r3nlNFp+I6bvASfvBZQ=
go.etcd.io/bbolt v1.3.2/go.mod h1:IbVyRI1SCnLcuJnV2u8VeU0CEYM7e686BmAb1XKL+uU=
go.uber.org/atomic v1.4.0/go.mod h1:gD2HeocX3+yG+ygLZcrzQJaqmWj9AIm7n08wl/qW/PE=
go.uber.org/multierr v1.1.0/go.mod h1:wR5kodmAFQ0UK8QlbwjlSNy0Z68gJhDJUG5sjR94q/0=
go.uber.org/zap v1.10.0/go.mod h1:vwi/ZaCAaUcBkycHslxD9B2zi4UTXhF60s6SWpuDF0Q=
golang.org/x/crypto v0.0.0-20180904163835-0709b304e793/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
golang.org/x/crypto v0.0.0-20190219172222-a4c6cb3142f2/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/crypto v0.0.0-20190426145343-a29dc8fdc734/go.mod h1:yigFU9vqHzYiE8UmvKecakEJjdnWj3jj499lnFckfCI=
golang.org/x/crypto v0.0.0-20191011191535-87dc89f01550/go.mod h1:yigFU9vqHzYiE8UmvKecakEJjdnWj3jj499lnFckfCI=
golang.org/x/crypto v0.0.0-20200414173820-0848c9571904/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
golang.org/x/crypto v0.0.0-20200420201142-3c4aac89819a/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/crypto v0.0.0-20210322153248-0c34fe9e7dc2/go.mod h1:T9bdIzuCu7OtxOm1hfPfRQxPLYneinmdGuTeoZ9dtd4=
golang.org/x/crypto v0.0.0-20210421170649-83a5a9bb288b/go.mod h1:T9bdIzuCu7OtxOm1hfPfRQxPLYneinmdGuTeoZ9dtd4=
golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97/go.mod h1:GvvjBRRGRdwPK5ydBHafDWAxML/pGHZbMvKqRZ5+Abc=
golang.org/x/crypto v0.0.0-20220622213112-05595931fe9d/go.mod h1:IxCIyHEi3zRg3s0A5j5BB6A9Jmi73HwBIUl50j+osU4=
golang.org/x/crypto v0.2.0 h1:BRXPfhNivWL5Yq0BGQ39a2sW6t44aODpfxkWjYdzewE=
golang.org/x/crypto v0.2.0/go.mod h1:hebNnKkNXi2UzZN1eVRvBB7co0a+JxK6XbPiWVs/3J4=
golang.org/x/lint v0.0.0-20181026193005-c67002cb31c3/go.mod h1:UVdnD1Gm6xHRNCYTkRU2/jEulfH38KcIWyp/GAMgvoE=
golang.org/x/lint v0.0.0-20190313153728-d0100b6bd8b3/go.mod h1:6SW0HCj/g11FgYtHlgUYUwCkIfeOF89ocIRzGO/8vkc=
golang.org/x/mod v0.3.0/go.mod h1:s0Qsj1ACt9ePp/hMypM3fl4fZqREWJwdYDEqhRiZZUA=
golang.org/x/net v0.0.0-20180826012351-8a410e7b638d/go.mod h1:mL1N/T3taQHkDXs73rZJwtUhF3w3ftmwwsq0BUmARs4=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/net v0.0.0-20180906233101-161cd47e91fd/go.mod h1:mL1N/T3taQHkDXs73rZJwtUhF3w3ftmwwsq0BUmARs4=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/net v0.0.0-20181114220301-adae6a3d119a/go.mod h1:mL1N/T3taQHkDXs73rZJwtUhF3w3ftmwwsq0BUmARs4=
golang.org/x/net v0.0.0-20181220203305-927f97764cc3/go.mod h1:mL1N/T3taQHkDXs73rZJwtUhF3w3ftmwwsq0BUmARs4=
golang.org/x/net v0.0.0-20190311183353-d8887717615a/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/net v0.0.0-20190522155817-f3200d17e092/go.mod h1:HSz+uSET+XFnRR8LxR5pz3Of3rY3CfYBVs4xY44aLks=
golang.org/x/net v0.0.0-20190620200207-3b0461eec859/go.mod h1:z5CRVTTTmAJ677TzLLGU+0bjPO0LkuOLi4/5GtJWs/s=
golang.org/x/net v0.0.0-20191209160850-c0dbc17a3553/go.mod h1:z5CRVTTTmAJ677TzLLGU+0bjPO0LkuOLi4/5GtJWs/s=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/net v0.0.0-20200520004742-59133d7f0dd7/go.mod h1:qpuaurCH72eLCgpAm/N6yyVIVM9cpaDIP3A8BGJEC5A=
golang.org/x/net v0.0.0-20201006153459-a7d1128ccaa0/go.mod h1:sp8m0HH+o8qH0wwXwYZr8TS3Oi6o0r6Gce1SSxlDquU=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/net v0.0.0-20201021035429-f5854403a974/go.mod h1:sp8m0HH+o8qH0wwXwYZr8TS3Oi6o0r6Gce1SSxlDquU=
golang.org/x/net v0.0.0-20201202161906-c7110b5ffcbb/go.mod h1:sp8m0HH+o8qH0wwXwYZr8TS3Oi6o0r6Gce1SSxlDquU=
golang.org/x/net v0.0.0-20210226172049-e18ecbb05110/go.mod h1:m0MpNAwzfU5UDzcl9v0D8zg8gWTRqZa9RBIspLL5mdg=
golang.org/x/net v0.0.0-20210326060303-6b1517762897/go.mod h1:uSPa2vr4CLtc/ILN5odXGNXS6mhrKVzTaCXzk9m6W3k=
golang.org/x/net v0.0.0-20210428140749-89ef3d95e781/go.mod h1:OJAsFXCWl8Ukc7SiCT/9KSuxbyM7479/AVlXFRxuMCk=
golang.org/x/net v0.0.0-20211112202133-69e39bad7dc2/go.mod h1:9nx3DQGgdP8bBQD5qxJ1jj9UTztislL4KSBs9R2vV5Y=
golang.org/x/net v0.0.0-20220630215102-69896b714898/go.mod h1:XRhObCWvk6IyKnWLug+ECip1KBveYUHfp+8e9klMJ9c=
golang.org/x/net v0.5.0 h1:GyT4nK/YDHSqa1c4753ouYCDajOYKTja9Xb/OHtgvSw=
golang.org/x/net v0.5.0/go.mod h1:DivGGAXEgPSlEBzxGzZI+ZLohi+xUj054jfeKui00ws=
golang.org/x/oauth2 v0.0.0-20180821212333-d2e6202438be/go.mod h1:N/0e6XlmueqKjAGxoOufVs8QHGRruUQn6yWY3a++T0U=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/sync v0.0.0-20180314180146-1d60e4601c6f/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/sync v0.0.0-20181108010431-42b317875d0f/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
golang.org/x/sync v0.0.0-20181221193216-37e7f081c4d4/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
golang.org/x/sync v0.0.0-20190423024810-112230192c58/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
golang.org/x/sync v0.0.0-20201020160332-67f06af15bc9/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
golang.org/x/sys v0.0.0-20180830151530-49385e6e1522/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
golang.org/x/sys v0.0.0-20180905080454-ebe1bf3edb33/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/sys v0.0.0-20180909124046-d0be0721c37e/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/sys v0.0.0-20181021155630-eda9bb28ed51/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
golang.org/x/sys v0.0.0-20181107165924-66b7b1311ac8/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
golang.org/x/sys v0.0.0-20181116152217-5ac8a444bdc5/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/sys v0.0.0-20190222072716-a9d3bda3a223/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/sys v0.0.0-20190507160741-ecd444e8653b/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20190606203320-7fc4e5ec1444/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/sys v0.0.0-20190904154756-749cb33beabd/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20190916202348-b4ddaad3f8a3/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20191005200804-aed5e4c7ecf9/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/sys v0.0.0-20191026070338-33540a1f6037/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/sys v0.0.0-20191120155948-bd437916bb0e/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/sys v0.0.0-20191204072324-ce4227a45e2e/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20200102141924-c96a22e43c9c/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20200217220822-9197077df867/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20200302150141-5c8b2ff67527/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/sys v0.0.0-20200323222414-85ca7c5b95cd/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/sys v0.0.0-20200420163511-1957bb5e6d1f/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/sys v0.0.0-20200519105757-fe76b779f299/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20200930185726-fdedc70b468f/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/sys v0.0.0-20201119102817-f84b799fce68/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20201223074533-0d417f636930/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20210112080510-489259a85091/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20210124154548-22da62e12c0c/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20210309074719-68d13333faf2/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20210320140829-1e4c9ba3b0c4/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20210324051608-47abb6519492/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20210330210617-4fbd30eecc44/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20210423082822-04245dca01da/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20210502180810-71e4cd670f79/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
golang.org/x/sys v0.0.0-20210615035016-665e8c7367d1/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
golang.org/x/sys v0.0.0-20210630005230-0f9fa26af87c/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
golang.org/x/sys v0.0.0-20211013075003-97ac67df715c/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
golang.org/x/sys v0.0.0-20211216021012-1d35b9e2eb4e/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/sys v0.0.0-20220319134239-a9b59b0215f8/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/sys v0.0.0-20220408201424-a24fb2fb8a0f/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
golang.org/x/sys v0.0.0-20220520151302-bc2c85ada10a/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
golang.org/x/sys v0.0.0-20220704084225-05e143d24a9e/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
golang.org/x/sys v0.0.0-20220715151400-c0bba94af5f8/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
golang.org/x/sys v0.0.0-20220811171246-fbc7d0a398ab/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
golang.org/x/sys v0.4.0 h1:Zr2JFtRQNX3BCZ8YtxRE9hNJYC8J6I1MVbMg6owUp18=
golang.org/x/sys v0.4.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
golang.org/x/term v0.0.0-20201126162022-7de9c90e9dd1/go.mod h1:bj7SfCRtBDWHUb9snDiAeCFNEtKQo2Wmx5Cou7ajbmo=
golang.org/x/term v0.0.0-20210220032956-6a3ed077a48d/go.mod h1:bj7SfCRtBDWHUb9snDiAeCFNEtKQo2Wmx5Cou7ajbmo=
golang.org/x/term v0.0.0-20210615171337-6886f2dfbf5b/go.mod h1:jbD1KX2456YbFQfuXm/mYQcufACuNUgVhRMnK/tPxf8=
golang.org/x/term v0.0.0-20210927222741-03fcf44c2211/go.mod h1:jbD1KX2456YbFQfuXm/mYQcufACuNUgVhRMnK/tPxf8=
golang.org/x/term v0.4.0 h1:O7UWfv5+A2qiuulQk30kVinPoMtoIPeVaKLEgLpVkvg=
golang.org/x/term v0.4.0/go.mod h1:9P2UbLfCdcvo3p/nzKvsmas4TnlujnuoV9hGgYzW1lQ=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/text v0.3.0/go.mod h1:NqM8EUOU14njkJ3fqMW+pc6Ldnwhi/IjpwHt7yyuwOQ=
golang.org/x/text v0.3.2/go.mod h1:bEr9sfX3Q8Zfm5fL9x+3itogRgK3+ptLWKqgva+5dAk=
golang.org/x/text v0.3.3/go.mod h1:5Zoc/QRtKVWzQhOtBMvqHzDpF6irO9z98xDceosuGiQ=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/text v0.3.6/go.mod h1:5Zoc/QRtKVWzQhOtBMvqHzDpF6irO9z98xDceosuGiQ=
golang.org/x/text v0.3.7/go.mod h1:u+2+/6zg+i71rQMx5EYifcz6MCKuco9NR6JIITiCfzQ=
golang.org/x/text v0.6.0 h1:3XmdazWV+ubf7QgHSTWeykHOci5oeekaGJBLkrkaw4k=
golang.org/x/text v0.6.0/go.mod h1:mrYo+phRRbMaCq/xk9113O4dZlRixOauAjOtrjsXDZ8=
golang.org/x/time v0.0.0-20190308202827-9d24e82272b4/go.mod h1:tRJNPiyCQ0inRvYxbN9jk5I+vvW/OXSQhTDSoE431IQ=
golang.org/x/tools v0.0.0-20180221164845-07fd8470d635/go.mod h1:n7NCudcB/nEzxVGmLbDWY5pfWTLqBcC2KZ6jyYvM4mQ=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/tools v0.0.0-20180917221912-90fa682c2a6e/go.mod h1:n7NCudcB/nEzxVGmLbDWY5pfWTLqBcC2KZ6jyYvM4mQ=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/tools v0.0.0-20190114222345-bf090417da8b/go.mod h1:n7NCudcB/nEzxVGmLbDWY5pfWTLqBcC2KZ6jyYvM4mQ=
golang.org/x/tools v0.0.0-20190311212946-11955173bddd/go.mod h1:LCzVGOaR6xXOjkQ3onu1FJEFr0SW1gC7cKk1uF8kGRs=
golang.org/x/tools v0.0.0-20190328211700-ab21143f2384/go.mod h1:LCzVGOaR6xXOjkQ3onu1FJEFr0SW1gC7cKk1uF8kGRs=
golang.org/x/tools v0.0.0-20190624222133-a101b041ded4/go.mod h1:/rFqwRUd4F7ZHNgwSSTFct+R/Kf4OFW1sUzUTQQTgfc=
golang.org/x/tools v0.0.0-20191119224855-298f0cb1881e/go.mod h1:b+2E5dAYhXwXZwtnZ6UAqBI28+e2cm9otk0dWdXHAEo=
golang.org/x/tools v0.0.0-20201224043029-2b0845dc783e/go.mod h1:emZCQorbCU4vsT4fOWvOPXz4eW1wZW4PmDk9uLelYpA=
golang.org/x/xerrors v0.0.0-20190717185122-a985d3407aa7/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
golang.org/x/xerrors v0.0.0-20191011141410-1b5146add898/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
Initial import
2022-10-03 09:03:48 +00:00
golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
golang.org/x/xerrors v0.0.0-20200804184101-5ec99f83aff1/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
google.golang.org/appengine v1.1.0/go.mod h1:EbEs0AVv82hx2wNQdGPgUI5lhzA/G0D9YwlJXL52JkM=
google.golang.org/genproto v0.0.0-20180817151627-c66870c02cf8/go.mod h1:JiN7NxoALGmiZfu7CAH4rXhgtRTLTxftemlI0sWmxmc=
google.golang.org/grpc v1.19.0/go.mod h1:mqu4LbDTu4XGKhr4mRzUsmM4RtVoemTSY81AxZiDr8c=
google.golang.org/grpc v1.21.0/go.mod h1:oYelfM1adQP15Ek0mdvEgi9Df8B9CZIaU1084ijfRaM=
Initial import
2022-10-03 09:03:48 +00:00
google.golang.org/protobuf v0.0.0-20200109180630-ec00e32a8dfd/go.mod h1:DFci5gLYBciE7Vtevhsrf46CRTquxDuWsQurQQe4oz8=
google.golang.org/protobuf v0.0.0-20200221191635-4d8936d0db64/go.mod h1:kwYJMbMJ01Woi6D6+Kah6886xMZcty6N08ah7+eCXa0=
google.golang.org/protobuf v0.0.0-20200228230310-ab0ca4ff8a60/go.mod h1:cfTl7dwQJ+fmap5saPgwCLgHXTUD7jkjRqWcaiX5VyM=
google.golang.org/protobuf v1.20.1-0.20200309200217-e05f789c0967/go.mod h1:A+miEFZTKqfCUM6K7xSMQL9OKL/b6hQv+e19PK+JZNE=
google.golang.org/protobuf v1.21.0/go.mod h1:47Nbq4nVaFHyn7ilMalzfO3qCViNmqZ2kzikPIcrTAo=
google.golang.org/protobuf v1.23.0/go.mod h1:EGpADcykh3NcUnDUJcl1+ZksZNG86OlYog2l/sGQquU=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
google.golang.org/protobuf v1.26.0-rc.1/go.mod h1:jlhhOSvTdKEhbULTjvd4ARK9grFBp09yW+WbY/TyQbw=
google.golang.org/protobuf v1.26.0/go.mod h1:9q0QmTI4eRPtz6boOQmLYwt+qCgq0jsYwAQnmE0givc=
google.golang.org/protobuf v1.28.1 h1:d0NfwRgPtno5B1Wa6L2DAG+KivqkdutMf1UhdNx175w=
gopkg.in/airbrake/gobrake.v2 v2.0.9/go.mod h1:/h5ZAUhDkGaJfjzjKLSjv6zCL6O0LLBxU4K+aSYdM/U=
gopkg.in/alecthomas/kingpin.v2 v2.2.6/go.mod h1:FMv+mEhP44yOT+4EoQTLFTRgOQ1FBLkstjWtayDeSgw=
Initial import
2022-10-03 09:03:48 +00:00
gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
gopkg.in/check.v1 v1.0.0-20180628173108-788fd7840127/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
gopkg.in/check.v1 v1.0.0-20200227125254-8fa46927fb4f/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c h1:Hei/4ADfdWqJk1ZMxUNpqntNwaWcugrBjAiHlqqRiVk=
gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c/go.mod h1:JHkPIbrfpd72SG/EVd6muEfDQjcINNoR0C8j2r3qZ4Q=
gopkg.in/djherbis/times.v1 v1.2.0/go.mod h1:AQlg6unIsrsCEdQYhTzERy542dz6SFdQFZFv6mUY0P8=
gopkg.in/djherbis/times.v1 v1.3.0/go.mod h1:AQlg6unIsrsCEdQYhTzERy542dz6SFdQFZFv6mUY0P8=
gopkg.in/errgo.v2 v2.1.0/go.mod h1:hNsd1EY+bozCKY1Ytp96fpM3vjJbqLJn88ws8XvfDNI=
Initial import
2022-10-03 09:03:48 +00:00
gopkg.in/fsnotify.v1 v1.4.7/go.mod h1:Tz8NjZHkW78fSQdbUxIjBTcgA1z1m8ZHf0WmKUhAMys=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
gopkg.in/gemnasium/logrus-airbrake-hook.v2 v2.1.2/go.mod h1:Xk6kEKp8OKb+X14hQBKWaSkCsqBpgog8nAV2xsGOxlo=
gopkg.in/ini.v1 v1.62.0/go.mod h1:pNLf8WUiyNEtQjuu5G5vTm06TEv9tsIgeAvK8hOrP4k=
gopkg.in/ini.v1 v1.66.6/go.mod h1:pNLf8WUiyNEtQjuu5G5vTm06TEv9tsIgeAvK8hOrP4k=
gopkg.in/resty.v1 v1.12.0/go.mod h1:mDo4pnntr5jdWRML875a/NmxYqAlA73dVijT2AXvQQo=
Initial import
2022-10-03 09:03:48 +00:00
gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7 h1:uRGJdciOHaEIrze2W8Q3AKkepLTh2hOroT7a+7czfdQ=
gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7/go.mod h1:dt/ZhP58zS4L8KSrWDmTeBkI65Dw0HsyUHuEVlX15mw=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
gopkg.in/warnings.v0 v0.1.2/go.mod h1:jksf8JmL6Qr/oQM2OXTHunEvvTAsrWBLb6OOjuVWRNI=
gopkg.in/yaml.v1 v1.0.0-20140924161607-9f9df34309c0 h1:POO/ycCATvegFmVuPpQzZFJ+pGZeX22Ufu6fibxDVjU=
Initial import
2022-10-03 09:03:48 +00:00
gopkg.in/yaml.v1 v1.0.0-20140924161607-9f9df34309c0/go.mod h1:WDnlLJ4WF5VGsH/HVa3CI79GS0ol3YnhVnKP89i0kNg=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
gopkg.in/yaml.v2 v2.0.0-20170812160011-eb3733d160e7/go.mod h1:JAlM8MvJe8wmxCU4Bli9HhUf9+ttbYbLASfIpnQbh74=
gopkg.in/yaml.v2 v2.2.1/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
Initial import
2022-10-03 09:03:48 +00:00
gopkg.in/yaml.v2 v2.2.2/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
gopkg.in/yaml.v2 v2.2.4/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
gopkg.in/yaml.v2 v2.2.8/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
Initial import
2022-10-03 09:03:48 +00:00
gopkg.in/yaml.v2 v2.3.0/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
gopkg.in/yaml.v2 v2.4.0 h1:D8xgwECY7CYvx+Y2n4sBz93Jn9JRvxdiyyo8CTfuKaY=
gopkg.in/yaml.v2 v2.4.0/go.mod h1:RDklbk79AGWmwhnvt/jBztapEOGDOx6ZbXqjP6csGnQ=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM=
gopkg.in/yaml.v3 v3.0.0-20200605160147-a5ece683394c/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM=
gopkg.in/yaml.v3 v3.0.0-20210107192922-496545a6307b/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM=
gopkg.in/yaml.v3 v3.0.0/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM=
Initial import
2022-10-03 09:03:48 +00:00
gopkg.in/yaml.v3 v3.0.1 h1:fxVm/GzAzEWqLHuvctI91KS9hhNmmWOoWu0XTYJS7CA=
Create parition info parsing library to be used both here (when trying to find the partition UUID using a label) and on the kairos side when updating the file after calling kcrypt to encrypt a partition (which causes the UUID to change). Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2022-11-11 08:54:33 +00:00
gopkg.in/yaml.v3 v3.0.1/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
gotest.tools v2.2.0+incompatible/go.mod h1:DsYFclhRJ6vuDpmuTbkuFWG+y2sxOXAzmJt81HFBacw=
gotest.tools/v3 v3.0.2/go.mod h1:3SzNCllyD9/Y+b5r9JIKQ474KzkZyqLqEfYqMsX94Bk=
honnef.co/go/tools v0.0.0-20190102054323-c2f93a96b099/go.mod h1:rf3lG4BRIbNafJWhAfAdb/ePZxsR/4RtNHQocxwk9r4=
Initial import
2022-10-03 09:03:48 +00:00
howett.net/plist v1.0.0 h1:7CrbWYbPPO/PyNy38b2EB/+gYbjCe2DXBxgtOOZbSQM=
howett.net/plist v1.0.0/go.mod h1:lqaXoTrLY4hg8tnEzNru53gicrbv7rrk+2xJA/7hw9g=
Move from partition_info to config package Now the kcrypt configuration will be just a block (`kcrypt`) in the regular kairos configuration files. We will use the config mechanism of looking up in multiple directories becase the old code was only looking at `/oem` but at boot time (initramfs) the configuration was present in `/sysroot/oem`. The reason it "worked" was that we had a bug and a sealedvolume was matching our request simply because we sent an empty UUID/Label/Name and the sealedvolume had and empty UUID (empty matches empty, right?) With that fixed on the challenger server side, it became obvious that we never actually read the partition_info file because we were looking for it at the wrong place. Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
2023-01-13 15:41:39 +00:00
pault.ag/go/modprobe v0.1.2/go.mod h1:afr2STC/2Maz/qi4+Bma1s0dszZgO/PcM8AKar9DWhM=
pault.ag/go/topsort v0.0.0-20160530003732-f98d2ad46e1a/go.mod h1:INqx0ClF7kmPAMk2zVTX8DRnhZ/yaA/Mg52g8KFKE7k=
pault.ag/go/topsort v0.1.1/go.mod h1:r1kc/L0/FZ3HhjezBIPaNVhkqv8L0UJ9bxRuHRVZ0q4=
Reference in New Issue Copy Permalink