-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: (ErlangError) Erlang error: {:badarg, {'aead.c', 90}, 'Unknown cipher'} #118
Comments
Sadly, this forum thread: https://elixirforum.com/t/unknown-cipher-when-encrypting-data/41076 aren't much use. |
The official docs for this: https://www.erlang.org/doc/man/crypto.html#crypto_one_time_aead-6 are basically useless ... |
Replacing even though: iex> :aes_256_gcm in :crypto.supports(:ciphers)
true |
Still getting the same error in ** (ErlangError) Erlang error: {:badarg, {'aead.c', 90}, 'Unknown cipher'}
(crypto 5.0.2) :crypto.aead_cipher_nif(:aes_gcm, "",
<<226, 122, 88, 155, 245, 35, 254, 89, 187, 55, 146, 130, 164, 206, 219, 44>>,
"admin@dwylauth.com", "AES256GCM", 16, true)
(fields 2.10.2) lib/aes.ex:38: Fields.AES.encrypt/1
(fields 2.10.2) lib/encrypted.ex:21: Fields.Encrypted.dump/1
(ecto 3.7.2) lib/ecto/type.ex:915: Ecto.Type.process_dumpers/3
(ecto 3.7.2) lib/ecto/repo/schema.ex:996: Ecto.Repo.Schema.dump_field!/6
(ecto 3.7.2) lib/ecto/repo/schema.ex:1009: anonymous fn/6 in Ecto.Repo.Schema.dump_fields!/5
(stdlib 3.15.1) maps.erl:410: :maps.fold_1/3
(ecto 3.7.2) lib/ecto/repo/schema.ex:1007: Ecto.Repo.Schema.dump_fields!/5
Error: Process completed with exit code 1. Going to add a regression test here in |
OK, I think this is fixed because we're no longer seeing any crypto/fields errors in Auth: dwyl/auth#231 |
All tests pass on the latest PR #117 and
main
:But when we
try
to use this inauth
we get the following error:https://github.com/dwyl/auth/actions/runs/3272492583/jobs/5383565807
Need to fix this ASAP as it's preventing the
auth -> groups
PR dwyl/auth#231 from progressing. 🤦♂️Todo
The text was updated successfully, but these errors were encountered: