×

SparkFun Support and Front Desk will be closed on Thursday 11/14 from 1-2:30pm for a company event. Please plan to pick up your orders before or after this timeframe.

rdev5

Member Since: April 24, 2015

Country: United States

  • For some reason I never got a notification of your reply. Is this still available and do you take PayPal or have an address I can contact you at?

  • Argh! I had one in my cart too and now that I'm revisiting Arduino this month, it's run out of stock :/

    Is there no way to get these now?

  • Is this compatible for use with the Arduino Mega 2560?

    I pretty much put down Arduino the day my Uno got bricked so I'm either looking at buying a second Arduino (double as ISP) but then if I'm going to do that, I know from past experience that the Uno starts to run out of room quickly so I'm considering the Mega.

  • Sorry, little slow catching on to what you were referring to.

    I did find something these searching for ATAES132 and believe I could do what you're saying and just create my own breakout boards. Thanks for the tip!

  • One for ATAES132, one for ATECC108, a BOB for this, a BOB for that...yes, just like you guys have for the ATSHA204.

    Or even better, how about a grab bag? :)

  • Sounds like I'm not the only one getting into ECC these days :)

  • I find the cliche/canned "don't implement crypto yourself because you'll make mistakes" response to be exactly the opposite reason for not implementing crypto yourself. I would trust an implementor who after a thousand attempts finally gets it right (i.e. Edison), more than I would trust an implementor that just takes what he/she was given and runs with it without doing their homework. After all, if it's in NIST's recommendation, we should just go with it, right?

    There is great value in learning the inner workings of algorithms and technology, and the reward comes when we finally managed to do it ourselves. After all, isn't that what we're doing with prototyping, learning to do from scratch what's already been done for us at a higher level?

  • Spot on. And thanks for the like to uECC! I started implementing finite clock fields and clock crypto in C# but this is nice too :)

  • ...not to mention you can implement a lot of this stuff in software (you're going to be using a library anyways to interface the device).

    The concept of a dedicate hardware crypto device is novel, but not at this price point, and especially not for prototyping. After all, much crypto can be learned and done in code, which is free. I'd much rather see these components broken out into individual ICs that we cherry pick and wire into our own applications. I think I would definitely jump on something like that.

No public wish lists :(