secret/internal/vault
sneak 8ec3fc877d Fix GetValue methods to return LockedBuffer internally
- Changed Secret.GetValue and Version.GetValue to return *memguard.LockedBuffer
- Updated all internal callers to handle LockedBuffer properly
- For backward compatibility, vault.GetSecret still returns []byte but makes a copy
- This ensures secret values are protected in memory during decryption
- Updated tests to handle LockedBuffer returns
- Fixed CLI getSecretValue to use LockedBuffer throughout
2025-07-15 08:59:23 +02:00
..
integration_test.go uses protected memory buffers now for all secrets in ram 2025-07-15 08:32:33 +02:00
integration_version_test.go uses protected memory buffers now for all secrets in ram 2025-07-15 08:32:33 +02:00
management.go fix: resolve all remaining linter issues (staticcheck, tagliatelle, lll) 2025-07-15 06:33:25 +02:00
metadata_test.go fix: resolve exported type stuttering issues (revive) 2025-06-20 12:47:06 -07:00
metadata.go fix: resolve all revive linter issues 2025-07-15 06:06:48 +02:00
secrets_version_test.go uses protected memory buffers now for all secrets in ram 2025-07-15 08:32:33 +02:00
secrets.go Fix GetValue methods to return LockedBuffer internally 2025-07-15 08:59:23 +02:00
unlockers.go Fix EncryptWithPassphrase to accept LockedBuffer for data parameter 2025-07-15 08:42:46 +02:00
vault_test.go uses protected memory buffers now for all secrets in ram 2025-07-15 08:32:33 +02:00
vault.go fix: resolve all nlreturn linter errors 2025-07-15 06:00:32 +02:00