Skip to content

fix: Formatting

fix: Formatting #62

Triggered via push September 5, 2025 20:20
Status Failure
Total duration 2m 46s
Artifacts

ci.yml

on: push
Templ Generate
14s
Templ Generate
Docker Release
0s
Docker Release
Build Development
0s
Build Development
Build Pull Request
0s
Build Pull Request
Nix Build
0s
Nix Build
Simulation
0s
Simulation
Docker Development
0s
Docker Development
Release
0s
Release
Fit to window
Zoom out
Zoom in

Annotations

5 errors
Lint
issues found
Lint: msgtausch-srv/proxy/https_interceptor_test.go#L826
SA1019: x509.EncryptPEMBlock has been deprecated since Go 1.16 because it shouldn't be used: Legacy PEM encryption as specified in RFC 1423 is insecure by design. Since it does not authenticate the ciphertext, it is vulnerable to padding oracle attacks that can let an attacker recover the plaintext. (staticcheck)
Lint: msgtausch-srv/proxy/https_interceptor_test.go#L745
SA1019: x509.EncryptPEMBlock has been deprecated since Go 1.16 because it shouldn't be used: Legacy PEM encryption as specified in RFC 1423 is insecure by design. Since it does not authenticate the ciphertext, it is vulnerable to padding oracle attacks that can let an attacker recover the plaintext. (staticcheck)
Lint: msgtausch-srv/proxy/proxy.go#L54
SA1019: x509.DecryptPEMBlock has been deprecated since Go 1.16 because it shouldn't be used: Legacy PEM encryption as specified in RFC 1423 is insecure by design. Since it does not authenticate the ciphertext, it is vulnerable to padding oracle attacks that can let an attacker recover the plaintext. (staticcheck)
Lint: msgtausch-srv/proxy/proxy.go#L48
SA1019: x509.IsEncryptedPEMBlock has been deprecated since Go 1.16 because it shouldn't be used: Legacy PEM encryption as specified in RFC 1423 is insecure by design. Since it does not authenticate the ciphertext, it is vulnerable to padding oracle attacks that can let an attacker recover the plaintext. (staticcheck)