Seth Archer Brown

less info
113 reputation
5
bio website twitter.com/learc83
location Atlanta, GA
age 30
visits member for 8 months
seen yesterday

I'm Co-Founder of Toasty LLC. I build retail automation sytems.

I'm good with Go, Java, Ruby, C, JavaScript, Full stack web development, and embedded programming/hardware hacking.

Github

@learc83

google

facebook


Aug
11
awarded  Scholar
Aug
11
awarded  Supporter
Aug
11
comment Verify Messages to Embedded Device
You're probably right that using one key pair is probably worth the trade off. To your first point, I had thought about the vulnerability of the server, and I've been thinking about keeping the private key on a local machine, then signing any updates/messages before I push them to the server (this should be fairly infrequent).
Aug
11
accepted Verify Messages to Embedded Device
Aug
11
awarded  Student
Aug
11
revised Verify Messages to Embedded Device
edited body
Aug
11
comment Verify Messages to Embedded Device
@Maeher I was thinking along the lines of if an attacker were able to reconstruct/steal one, or a few, private keys, he wouldn't be able to spoof messages to all of the devices. I also edited my question to make it clear I'm talking about the RNG on the server that's signing messages , not on the devices.
Aug
11
revised Verify Messages to Embedded Device
added 45 characters in body
Aug
11
awarded  Editor
Aug
11
revised Verify Messages to Embedded Device
edited title
Aug
11
asked Verify Messages to Embedded Device
Aug
11
awarded  Autobiographer