CharlesO
I have been battling with some code:
I have 2 variants I have been testing:
def ds4 do
try do
private_key_pem = File.read!("priv/flows/private_unencrypted.pem")
# Decode PEM key explicitly
private_key_entry = :public_key.pem_decode(private_key_pem) |> hd()
IO.inspect(private_key_entry, label: "Private Key Entry")
# Correctly decode the private key
case private_key_entry do
{:RSAPrivateKey, rsa_key} ->
IO.inspect(rsa_key, label: "RSA Private Key Structure")
# Decrypt AES key
encrypted_aes_key =
Base.decode64!(
"i/j13zUEy37M00eFJYchyIyk+HIlmLs8X6gmJLO9UfiljUmQCX1kYVPYfVRbS+5moWKtkIc0K/KG59CObmT8sMbhSXFEbnCKL7bbLka80NC5lqoill4LKrAtOaWJ/Zxbw7YjWS1+zinkIZZCbJ0OGZjH24XVgx3pVx5PYK53JDSYt6kUo1Kt15uc5M7zne1/T46c5YCw2BnSGDvXX+74W7T8xo+dTl6krOzFGuxNXFOYtG3coFK3Ad4eteMIhlsxpoRjFggfIWv9VuA7TT9AOQ9mdF2juN98Hu0hm3kSi5IHHGagTq+UwrspnMl76kw+GZXinjQNSI2ZV8yYYHxQ=="
)
decrypted_aes_key =
:crypto.private_decrypt(:rsa, encrypted_aes_key, rsa_key,
rsa_padding: :rsa_pkcs1_oaep_padding,
oaep_hash: :sha256
)
IO.inspect(decrypted_aes_key, label: "Decrypted AES Key")
decrypted_aes_key
other ->
IO.inspect(other, label: "Unexpected Private Key Structure")
{:error, :unexpected_private_key_structure}
end
rescue
e ->
IO.inspect("Failed to decrypt: #{inspect({e, __STACKTRACE__})}",
label: "Decryption Error"
)
{:error, e}
end
end
def ds5 do
try do
private_key_pem = File.read!("priv/flows/private_unencrypted.pem")
# Remove PEM headers and decode base64
private_key_der =
private_key_pem
|> String.replace(~r/-----BEGIN RSA PRIVATE KEY-----/, "")
|> String.replace(~r/-----END RSA PRIVATE KEY-----/, "")
|> Base.decode64!()
# Decode DER-encoded private key
{:Ok, private_key, _} = :public_key.der_decode(private_key_der, :RSAPrivateKey)
IO.inspect(private_key, label: "RSA Private Key Structure")
m = %{
encrypted_aes_key:
"i/j13zUEy37M00eFJYchyIyk+HIlmLs8X6gmJLO9UfiljUmQCX1kYVPYfVRbS+5moWKtkIc0K/KG59CObmT8sMbhSXFEbnCKL7bbLka80NC5lqoill4LKrAtOaWJ/Zxbw7YjWS1+zinkIZZCbJ0OGZjH24XVgx3pVx5PYK53JDSYt6T6kUo1Kt15uc5M7zne1/T46c5YCw2BnSGDvXX+74W7T8xo+dTl6krOzFGuxNXFOYtG3coFK3Ad4eteMIhlsxpoRjFggfIWv9VuA7TT9AOQ9mdF2juN98Hu0hm3kSi5IHHGagTq+UwrspnMl76kw+GZXinjQNSI2ZV8yYYHxQ==",
encrypted_flow_data:
"esYLI3l/ZREnkg3EDoipH/TeF8fL6goV1GELcV/Jv+WWVkB/5JcJ5NRoFzfnDZrTKA==",
initial_vector: "65SPDGDmgHlG4MiRzy5abQ=="
}
# Decrypt AES key
encrypted_aes_key = Base.decode64!(m.encrypted_aes_key)
decrypted_aes_key =
:crypto.private_decrypt(:rsa, encrypted_aes_key, private_key,
rsa_padding: :rsa_pkcs1_oaep_padding,
oaep_hash: :sha256
)
IO.inspect(decrypted_aes_key, label: "Decrypted AES Key")
decrypted_aes_key
rescue
e ->
IO.inspect("Failed to decrypt: #{inspect({e, __STACKTRACE__})}",
label: "Decryption Error"
)
{:error, e}
end
end
I’m at a loss for the errors I keep getting:
FL.ds4
Private Key Entry: {:PrivateKeyInfo,
<<48, 130, 4, 190, 2, 1, 0, 48, 13, 6, 9, 42, 134, 72, 134, 247, 13, 1, 1, 1,
5, 0, 4, 130, 4, 168, 48, 130, 4, 164, 2, 1, 0, 2, 130, 1, 1, 0, 162, 144,
53, 31, 174, 226, 155, 127, 205, 227, ...>>, :not_encrypted}
Unexpected Private Key Structure: {:PrivateKeyInfo,
<<48, 130, 4, 190, 2, 1, 0, 48, 13, 6, 9, 42, 134, 72, 134, 247, 13, 1, 1, 1,
5, 0, 4, 130, 4, 168, 48, 130, 4, 164, 2, 1, 0, 2, 130, 1, 1, 0, 162, 144,
53, 31, 174, 226, 155, 127, 205, 227, ...>>, :not_encrypted}
{:error, :unexpected_private_key_structure}
15:36:33.174 DB "get_inactive_agents"
15:36:33.193 DB "summarize_1"
15:36:33.227 DB "summarize_2"
15:36:33.423 {:sse, "stats-refresh"}
FL.ds5
Decryption Error: "Failed to decrypt: {%ArgumentError{message: \"non-alphabet character found: \\\"-\\\" (byte 45)\"}, [{Base, :bad_character!, 1, [file: ~c\"lib/base.ex\", line: 137]}, {Base, :\"-decode64base!/2-lbc$^0/2-0-\", 2, [file: ~c\"lib/base.ex\", line: 642]}, {Base, :decode64base!, 2, [file: ~c\"lib/base.ex\", line: 640]}, {FL, :ds5, 0, [file: ~c\"lib/chatflow/fl.ex\", line: 222]}, {:elixir, :eval_external_handler, 3, [file: ~c\"src/elixir.erl\", line: 386]}, {:erl_eval, :do_apply, 7, [file: ~c\"erl_eval.erl\", line: 750]}, {:elixir, :eval_forms, 4, [file: ~c\"src/elixir.erl\", line: 364]}, {Module.ParallelChecker, :verify, 1, [file: ~c\"lib/module/parallel_checker.ex\", line: 112]}]}"
{:error, %ArgumentError{message: "non-alphabet character found: \"-\" (byte 45)"}}
Any help and insight would be appreciated ![]()
Also, i have updated the question to include the requirements from META:
Implementing Endpoints for Flows - WhatsApp Flows (facebook.com)
Request Decryption and Encryption
The incoming request body is encrypted, you need to decrypt it first, then you need to encrypt the server response before returning it to the client.You can find code examples of decryption/encryption in various programming languages in the Code Examples section.
For data_api_version “3.0” you should follow below instructions to decrypt request payload:
extract payload encryption key from encrypted_aes_key field:
decode base64-encoded field content to byte array;
decrypt resulting byte array with the private key corresponding to the uploaded public key using RSA/ECB/OAEPWithSHA-256AndMGF1Padding algorithm with SHA256 as a hash function for MGF1;
as a result, you’ll get a 128-bit payload encryption key.
decrypt request payload from encrypted_flow_data field:
decode base64-encoded field content to get encrypted byte array;
decrypt encrypted byte array using AES-GCM algorithm, payload encryption key and initialization vector passed in initial_vector field (which is base64-encoded as well and should be decoded first). Note that the 128-bit authentication tag for the AES-GCM algorithm is appended to the end of the encrypted array.
result of above step is UTF-8 encoded clear request payload.
For data_api_version “3.0” you should follow below instructions to encrypt the response:encode response payload string to response byte array using UTF-8;
prepare initialization vector for response encryption by inverting all bits of the initialization vector used for request payload encryption;
encrypt response byte array using AES-GCM algorithm with the following parameters:
secret key - payload encryption key from request decryption stage;
initialization vector for response encryption from above step;
empty AAD (additional authentication data) - many libraries assume this by default, check the documentation of the library in use;
128-bit (16 byte) length for authentication tag - many libraries assume this by default, check the documentation of the library in use;
append authentication tag generated during encryption to the end of the encryption result;
encode the whole output as base64 string and send it in the HTTP response body as plain text.
Trending in Questions
Other Trending Topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










First 10 of 25 Posts
al2o3cr
The first one is because the PEM file you’re supplying has a PKCS #8
PrivateKeyInfoin it (see also RFC5208) which can contain anRSAPrivateKey, rather than the bareRSAPrivateKeythe code expects.The second one is harder to guess, but I suspect there’s some other
-----BEGINheader that’s tripping up the base64 decoder. Based on not printingRSA Private Key Structure, I don’t thinkds5is even making it to any cryptographic calls.voltone
If you want to use
:public_keyto decode PEM-encoded keys you need to use:public_key.pem_entry_decode/1on the data returned by:public_key.pem_decode/1.If you want to extract the DER entry from the PEM yourself you’re going to have to do a bit more work to remove extra whitespace (e.g. newlines).
P.S. you can save yourself a lot of trouble by using x509…
CharlesO
thanks for the reference, i was not aware of x509 library
CharlesO
Thanks for the reply.
these were the steps META provided for key creation:
al2o3cr
Using those steps, I was able to recreate your observations and make some additional ones:
private_unencrypted.pemfile has a-----BEGIN PRIVATE KEY-----header, not the one that the code inds5was expecting to trim offRSAPrivateKeydetails are available by also usingpem_entry_decodeas @voltone suggested:CharlesO
Thanks for this, ill review.
But it begs the question,
Take meta’s requiremets, for interfacing with WhatsApp flows, it’s well spelt out and we see how its done in 3 other mainstream languages.
Ive been at this for 2 days in elixir and erlang with no success.
Not good.
LostKobrakai
I’ve felt the same in the past. Crypto seems to sit at a different level of abstraction, which makes adapting code examples not really enjoyable.
CharlesO
But we we should have standard reference implementations for these pretty common use-cases.
Everyone says dont do your own cryptography…, okay, but give us copy- paste code to use then…
AI at this point is just generating broken code that doesn’t help either.
These things have complete implementations in other languages.
Not a good look that we can’t get this done easily and, more importantly - correctly in Elixir or Erlang
D4no0
For this to be the case, someone has to do it first. @voltone’s x509 library and his contributions to OTP really moved the needle, but in the short time I’ve dealt with decoding certificates too, this is absolutely not an easy job, as there is a lot of edge-cases.
Speaking generally, you can always call
opensslfunctionality usingSystem.cmd/1orPortfrom your app, this has always saved me in the cases where I couldn’t figure out how to do it myself in elixir/erlang.CharlesO
Calling shell commands Might not be ideal for many use-caes.
WhatsApp is high traffic solution. Wouldn’t want this to become an avoidable bottleneck.
The steps, and specifications are clearly spelt out by Meta.
@voltone has pointed out x509, I’ll look at that now.
Its funny how this is a breeze in JavaScript, and nodejs.
There is a python reference done by meta themselves.
Calling that implementing via a port would be one sad way to do it…