warning: :crypto.block_decrypt/4 defined in application :crypto is used by the current application but the current application does not depend on :crypto. To fix this, you must do one of:
1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: [:crypto]]] to your "def project" in mix.exs
Found at 2 locations:
lib/kryptonite/aes.ex:236: Kryptonite.AES.decrypt_cbc/3
lib/kryptonite/aes.ex:253: Kryptonite.AES.decrypt_gcm/5
warning: :crypto.block_encrypt/4 defined in application :crypto is used by the current application but the current application does not depend on :crypto. To fix this, you must do one of:
1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: [:crypto]]] to your "def project" in mix.exs
Found at 2 locations:
lib/kryptonite/aes.ex:100: Kryptonite.AES.encrypt_cbc/3
lib/kryptonite/aes.ex:123: Kryptonite.AES.encrypt_gcm/4
warning: :crypto.hash/2 defined in application :crypto is used by the current application but the current application does not depend on :crypto. To fix this, you must do one of:
1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: [:crypto]]] to your "def project" in mix.exs
Found at 2 locations:
lib/kryptonite/bip39.ex:154: Kryptonite.Bip39.compute_checksum/1
lib/kryptonite/random.ex:56: Kryptonite.Random.hash_round/2
warning: :crypto.hmac_final/1 defined in application :crypto is used by the current application but the current application does not depend on :crypto. To fix this, you must do one of:
1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: [:crypto]]] to your "def project" in mix.exs
lib/kryptonite/aes.ex:298: Kryptonite.AES.stream_tag/2
warning: :crypto.hmac_init/2 defined in application :crypto is used by the current application but the current application does not depend on :crypto. To fix this, you must do one of:
1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: [:crypto]]] to your "def project" in mix.exs
lib/kryptonite/aes.ex:295: Kryptonite.AES.stream_tag/2
warning: :crypto.hmac_update/2 defined in application :crypto is used by the current application but the current application does not depend on :crypto. To fix this, you must do one of:
1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: [:crypto]]] to your "def project" in mix.exs
lib/kryptonite/aes.ex:296: Kryptonite.AES.stream_tag/2
warning: :crypto.stream_decrypt/2 defined in application :crypto is used by the current application but the current application does not depend on :crypto. To fix this, you must do one of:
1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: [:crypto]]] to your "def project" in mix.exs
lib/kryptonite/aes.ex:282: Kryptonite.AES.stream_decrypt/3
warning: :crypto.stream_encrypt/2 defined in application :crypto is used by the current application but the current application does not depend on :crypto. To fix this, you must do one of:
1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: [:crypto]]] to your "def project" in mix.exs
Found at 2 locations:
lib/kryptonite/aes.ex:146: Kryptonite.AES.stream_encrypt/3
lib/kryptonite/aes.ex:322: Kryptonite.AES.do_stream_encrypt/2
warning: :crypto.stream_init/3 defined in application :crypto is used by the current application but the current application does not depend on :crypto. To fix this, you must do one of:
1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: [:crypto]]] to your "def project" in mix.exs
Found at 3 locations:
lib/kryptonite/aes.ex:143: Kryptonite.AES.stream_encrypt/3
lib/kryptonite/aes.ex:171: Kryptonite.AES.stream_encrypt/5
lib/kryptonite/aes.ex:279: Kryptonite.AES.stream_decrypt/3
warning: :crypto.strong_rand_bytes/1 defined in application :crypto is used by the current application but the current application does not depend on :crypto. To fix this, you must do one of:
1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: [:crypto]]] to your "def project" in mix.exs
Found at 2 locations:
lib/kryptonite/bip39.ex:39: Kryptonite.Bip39.generate/1
lib/kryptonite/random.ex:19: Kryptonite.Random.bytes!/1
warning: :public_key.decrypt_private/2 defined in application :public_key is used by the current application but the current application does not depend on :public_key. To fix this, you must do one of:
1. If :public_key is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :public_key is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :public_key, you may optionally skip this warning by adding [xref: [exclude: [:public_key]]] to your "def project" in mix.exs
lib/kryptonite/rsa/private_key.ex:164: Kryptonite.RSA.PrivateKey.decrypt/2
warning: :public_key.decrypt_public/2 defined in application :public_key is used by the current application but the current application does not depend on :public_key. To fix this, you must do one of:
1. If :public_key is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :public_key is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :public_key, you may optionally skip this warning by adding [xref: [exclude: [:public_key]]] to your "def project" in mix.exs
lib/kryptonite/rsa/public_key.ex:80: Kryptonite.RSA.PublicKey.decrypt/2
warning: :public_key.encrypt_private/2 defined in application :public_key is used by the current application but the current application does not depend on :public_key. To fix this, you must do one of:
1. If :public_key is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :public_key is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :public_key, you may optionally skip this warning by adding [xref: [exclude: [:public_key]]] to your "def project" in mix.exs
lib/kryptonite/rsa/private_key.ex:146: Kryptonite.RSA.PrivateKey.encrypt/2
warning: :public_key.encrypt_public/2 defined in application :public_key is used by the current application but the current application does not depend on :public_key. To fix this, you must do one of:
1. If :public_key is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :public_key is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :public_key, you may optionally skip this warning by adding [xref: [exclude: [:public_key]]] to your "def project" in mix.exs
lib/kryptonite/rsa/public_key.ex:62: Kryptonite.RSA.PublicKey.encrypt/2
warning: :public_key.generate_key/1 defined in application :public_key is used by the current application but the current application does not depend on :public_key. To fix this, you must do one of:
1. If :public_key is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :public_key is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :public_key, you may optionally skip this warning by adding [xref: [exclude: [:public_key]]] to your "def project" in mix.exs
lib/kryptonite/rsa/private_key.ex:63: Kryptonite.RSA.PrivateKey.new/2
warning: :public_key.sign/3 defined in application :public_key is used by the current application but the current application does not depend on :public_key. To fix this, you must do one of:
1. If :public_key is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :public_key is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :public_key, you may optionally skip this warning by adding [xref: [exclude: [:public_key]]] to your "def project" in mix.exs
lib/kryptonite/rsa/private_key.ex:127: Kryptonite.RSA.PrivateKey.sign/2
warning: :public_key.verify/4 defined in application :public_key is used by the current application but the current application does not depend on :public_key. To fix this, you must do one of:
1. If :public_key is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :public_key is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :public_key, you may optionally skip this warning by adding [xref: [exclude: [:public_key]]] to your "def project" in mix.exs
lib/kryptonite/rsa/public_key.ex:44: Kryptonite.RSA.PublicKey.verify/3```
