> should try simple approaches That's all well and fine. My statement was conjunctive, "... and try to encourage others to use it." You README implies that oth

> should try simple approaches That's all well and fine. My statement was conjunctive, "... and try to encourage others to use it." You README implies that others should use it. I'm saying that you need big huge warnings that try to keep people away. You say the Arduino lacks computational power. DES ran on 1970s era hardware. I ran it on a 4.77 MHz 8088. Even that weak cryptosystem cannot be brute forced "in a timeframe near to a second" by a smartphone. Searching now, http://crypto.stackexchange.com/questions/12891/aes-algorithm-processing-time-in-arduino-vs-raspberry-pi http://crypto.stackexchange.com/questions/12891/aes-algorith... gives links to 6 different projects that have implemented AES-256. Including implementations "that run directly on the 16 MHz Arduino [and] can encrypt approximately 1 block per millisecond, roughly 32 000 bytes/sec".