Klopklopi
08f71e93c5
Encryption improve error messages ( #2595 )
...
Signed-off-by: Hugo JOUBERT <hugo.joubert@ippon.fr >
Signed-off-by: Klopklopi <76015884+Klopklopi@users.noreply.github.com >
Signed-off-by: Hugo JOUBERT <hugo.joubert4@gmail.com >
Signed-off-by: Hugo JOUBERT <hugojklop52@gmail.com >
Co-authored-by: Hugo JOUBERT <hugo.joubert@ippon.fr >
Co-authored-by: Hugo JOUBERT <hugo.joubert4@gmail.com >
Co-authored-by: Andrei Ciobanu <andreic9203@gmail.com >
2025-05-07 10:28:28 -04:00
Christian Mesh
b2bf39802a
Implement the first part of RFC 20250303-linter-policy ( #2577 )
...
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
2025-03-10 13:16:27 -04:00
Christian Mesh
ce7279c39f
Improve encryption internals and fix a few bugs therein ( #2551 )
...
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
Signed-off-by: yottta <andrei.ciobanu@opentofu.org >
Co-authored-by: yottta <andrei.ciobanu@opentofu.org >
Co-authored-by: Martin Atkins <mart@degeneration.co.uk >
2025-03-06 12:51:09 -05:00
Martin Atkins
ad32bde2ae
Temporarily disable the complexity-related lint rules
...
We're intending to gradually improve all of the existing functions that
fail these checks as a separate project from other work, because fixing
for these particular lint rules tends to be too invasive to be safe or
sensible to combine with other work.
Therefore we'll temporarily disable these lints from the main lint run
and add a separate .golangci-complexity.yml that we can use to track our
progress towards eliminating those lint failures without continuing to
litter the code with nolint comments in the meantime.
This also removes all of the existing nolint comments for these linters so
that we can start fresh and review each one as part of our improvement
project.
We'll re-enable these linters (and remove .golangci-complexity.yml) once
each example has either been rewritten to pass the checks or we've
concluded that further decomposition would hurt readability and so added
"nolint" comments back in so we can review whether our lint rules are too
strict once we've got a bunch of examples to consider together.
Signed-off-by: Martin Atkins <mart@degeneration.co.uk >
2025-01-03 10:41:05 -05:00
Christian Mesh
c7aaa5ed50
Force state change if encryption used fallback ( #2232 )
...
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
2024-12-03 17:44:30 -05:00
AbstractionFactory
9d842aa920
Fixes #1605 : Customizable metadata key on encryption key providers ( #2080 )
...
Signed-off-by: AbstractionFactory <179820029+abstractionfactory@users.noreply.github.com >
2024-10-30 19:52:23 +01:00
Nathan Baulch
ea558d9d4b
Fix typos ( #1905 )
...
Signed-off-by: Nathan Baulch <nathan.baulch@gmail.com >
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
Co-authored-by: Christian Mesh <christianmesh1@gmail.com >
2024-08-29 13:20:33 -04:00
Oleksandr Levchenkov
19b5287b8f
allow static evaluations in encryption configuration ( #1728 )
...
Signed-off-by: ollevche <ollevche@gmail.com >
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
Signed-off-by: Oleksandr Levchenkov <ollevche@gmail.com >
Co-authored-by: Christian Mesh <christianmesh1@gmail.com >
2024-06-24 10:18:16 -04:00
Oleksandr Levchenkov
568ff66bef
add early validation for enforced encryption methods ( #1711 )
...
Signed-off-by: ollevche <ollevche@gmail.com >
2024-06-12 21:06:06 +03:00
Christian Mesh
d7e96665f6
Add unencrypted Method for migrations ( #1458 )
...
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
2024-04-12 09:38:21 -04:00
Christian Mesh
979bf5ce3f
Fix #1407 : Pass through metadata fields in state encryption ( #1417 )
...
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
2024-03-28 11:14:08 -04:00
Christian Mesh
f02bb11812
Generate all encryption keys during encryption setup ( #1421 )
...
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
Co-authored-by: James Humphries <jamesh@spacelift.io >
2024-03-26 07:43:34 -04:00
Christian Mesh
b052880246
Encryption should require an explicit fallback ( #1364 )
...
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
2024-03-11 09:24:59 -04:00
Christian Mesh
cef62ea738
Update to encryption key provider interface ( #1351 )
...
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
2024-03-08 07:55:08 -05:00
Christian Mesh
5ab6167bbf
Initial wiring of encryption through the command package ( #1316 )
...
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
2024-03-07 08:55:57 -05:00
Janos
fa638907f1
Fixes #1169 : AES-GCM implementation ( #1291 )
...
Signed-off-by: Janos <86970079+janosdebugs@users.noreply.github.com >
Signed-off-by: Mikel Olasagasti Uranga <mikel@olasagasti.info >
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
Signed-off-by: James Humphries <James@james-humphries.co.uk >
Co-authored-by: James Humphries <jamesh@spacelift.io >
Co-authored-by: Serdar Dalgıç <serdardalgic@users.noreply.github.com >
Co-authored-by: Mikel Olasagasti Uranga <mikel@olasagasti.info >
Co-authored-by: Christian Mesh <christianmesh1@gmail.com >
2024-03-07 10:24:37 +00:00
Christian Mesh
997e5fa46e
State Encryption Error Handling / Diagnostics ( #1294 )
...
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
2024-03-04 08:30:30 -05:00
James Humphries
cbab4bee83
State Encryption Documentation and Partial Implementation ( #1227 )
...
Signed-off-by: StephanHCB <sbs_github_u43a@packetloss.de >
Signed-off-by: Christian Mesh <christianmesh1@gmail.com >
Signed-off-by: Janos <86970079+janosdebugs@users.noreply.github.com >
Signed-off-by: James Humphries <james@james-humphries.co.uk >
Co-authored-by: StephanHCB <sbs_github_u43a@packetloss.de >
Co-authored-by: Janos <86970079+janosdebugs@users.noreply.github.com >
Co-authored-by: Christian Mesh <christianmesh1@gmail.com >
2024-02-16 14:59:19 +00:00