4 ms·

Title is misleading, delivery is done by SES which is not built by the author. Might be ignorant here, but to me the article reads like an excuse to use serverl

by a_imho 5y ago

Title is misleading, delivery is done by SES which is not built by the author. Might be ignorant here, but to me the article reads like an excuse to use serverless. What I really miss is the testing story though, in my admittedly limited experience with serverless (Lambda and Workers) this was always a pain point I never really managed to overcome.

suifbwish 5y ago
I think an interesting approach would be to send secure email via programmatically generating the public string sequence within a domains TXT DNS record (short time to live expiry) you could even establish a very slow Diffie Hellman key exchange with two paired domains where their TXT records alterations reflect the key exchange. There are multiple dimensions of communication possible here too since you can have a near infinite number of TXT records per domain. You can even in theory transmit TCP packets (albeit slowly) over back and forth DNS modifications. If the encoded info were spread across multiple unrelated domains, it would require any interceptor to know which domains are the carriers of the information. This is pretty similar to blockchain transactions except as long as you have icanns authority to use that domain you control your own private part of the blockchain that is able to interact with any other as long as it operates on the same protocols.
- jerf 5y ago
  "You can even in theory transmit TCP packets (albeit slowly) over back and forth DNS modifications." More than theory: https://www.google.com/search?hl=en&q=tcp%2Dover%2Ddns https://www.google.com/search?hl=en&q=tcp%2Dover%2Ddns Given as a Google search rather than a concrete link because it's really a rich field. It did take me a few tries to get the right search term.
  - throwthere 5y ago
    Since its primary use is… nefarious? You might find more with searching for dns exfiltration
    - suifbwish 5y ago
      By that logic wouldn’t the primary purpose of encryption also be nefarious?
joawan 5y ago
Agree, not intentionally misleading though. Just a lack of a better word I guess. Original title was "Building a serverless emailing service". About testing: It's not that different from any other runtime. I admit, I put a lot of code into the same file in the examples as it was easier displaying the code that way. I tend to keep the handler of the lambda very lightweight and then test the functions that the handler calls. That way it's just unit testing and mocking away dependencies. The functions are pretty small so naive dependency injection works fine. AWS docs covers testing of Lambdas a bit here: https://docs.aws.amazon.com/whitepapers/latest/serverless-architectures-lambda/unit-tests.html https://docs.aws.amazon.com/whitepapers/latest/serverless-ar...

by a_imho 5y ago

suifbwish 5y ago

I think an interesting approach would be to send secure email via programmatically generating the public string sequence within a domains TXT DNS record (short time to live expiry) you could even establish a very slow Diffie Hellman key exchange with two paired domains where their TXT records alterations reflect the key exchange. There are multiple dimensions of communication possible here too since you can have a near infinite number of TXT records per domain. You can even in theory transmit TCP packets (albeit slowly) over back and forth DNS modifications. If the encoded info were spread across multiple unrelated domains, it would require any interceptor to know which domains are the carriers of the information. This is pretty similar to blockchain transactions except as long as you have icanns authority to use that domain you control your own private part of the blockchain that is able to interact with any other as long as it operates on the same protocols.

jerf 5y ago
"You can even in theory transmit TCP packets (albeit slowly) over back and forth DNS modifications." More than theory: https://www.google.com/search?hl=en&q=tcp%2Dover%2Ddns https://www.google.com/search?hl=en&q=tcp%2Dover%2Ddns Given as a Google search rather than a concrete link because it's really a rich field. It did take me a few tries to get the right search term.
- throwthere 5y ago
  Since its primary use is… nefarious? You might find more with searching for dns exfiltration
  - suifbwish 5y ago
    By that logic wouldn’t the primary purpose of encryption also be nefarious?

joawan 5y ago

Agree, not intentionally misleading though. Just a lack of a better word I guess. Original title was "Building a serverless emailing service". About testing: It's not that different from any other runtime. I admit, I put a lot of code into the same file in the examples as it was easier displaying the code that way. I tend to keep the handler of the lambda very lightweight and then test the functions that the handler calls. That way it's just unit testing and mocking away dependencies. The functions are pretty small so naive dependency injection works fine. AWS docs covers testing of Lambdas a bit here: https://docs.aws.amazon.com/whitepapers/latest/serverless-architectures-lambda/unit-tests.html https://docs.aws.amazon.com/whitepapers/latest/serverless-ar...