heyo
~if want skip straight question, go pink bit~
recently made tough move secure passwords , accounts after years of not bothering , using same "secure" password everything. in process of doing so, downloaded google authenticator app phone secure accounts 2 factor. if haven't heard of before, generates new random 6 or 8 digit code every 30 seconds, bank fobs.
so had thought of hey, why not implement on safe? having pass code changes every 30 seconds cool , secure keep cookies nice , safe. went out , bought $20 safe second hand gumtree , pulled apart. circuitry surprisingly simple, uses standard keypad 7 pins connected cheap circuit board connected solenoid moves pin, allowing safe opened, powered 4 aa batteries. circuit board can scrapped , replaced arduino board.
so, break project it's basic components, need cover:
the battery power not huge issue, as been done long term use, it's important factor.
the passcodes need totp (timed 1 time passwords) time int 1970 used security key make code. opposed otp generated on demand, requiring both devices (phone , safe) have passcodes sequenced if 1 gets out of sequence, cookies locked away forever.
thankfully, lucadentella has written library generating google auth totp passcodes lego house's security system. problem requires accurate time integer, luca unfortunately did hard coding compile time , calculating time passed since then. a. bad practice , b. reliant on arduino's internal clock can apparently inaccurate on long term.
so part stuck at. need method of getting 1970 time integer doesn't use wired external source (so not on ethernet or usb) , low powered on long term (not wifi?). know gps method, im not sure work inside metal box, inside building. there's more accurate clock modules, im clueless when comes those...
any advice appreciated.
~if want skip straight question, go pink bit~
recently made tough move secure passwords , accounts after years of not bothering , using same "secure" password everything. in process of doing so, downloaded google authenticator app phone secure accounts 2 factor. if haven't heard of before, generates new random 6 or 8 digit code every 30 seconds, bank fobs.
so had thought of hey, why not implement on safe? having pass code changes every 30 seconds cool , secure keep cookies nice , safe. went out , bought $20 safe second hand gumtree , pulled apart. circuitry surprisingly simple, uses standard keypad 7 pins connected cheap circuit board connected solenoid moves pin, allowing safe opened, powered 4 aa batteries. circuit board can scrapped , replaced arduino board.
so, break project it's basic components, need cover:
- powering solenoid - transistor, done
- receiving keypad input - keypad compatible keypad library
- checking entered code code thats generated - tricky bit
- no external wires or leading safe - i.e. battery powered, trickier
the battery power not huge issue, as been done long term use, it's important factor.
the passcodes need totp (timed 1 time passwords) time int 1970 used security key make code. opposed otp generated on demand, requiring both devices (phone , safe) have passcodes sequenced if 1 gets out of sequence, cookies locked away forever.
thankfully, lucadentella has written library generating google auth totp passcodes lego house's security system. problem requires accurate time integer, luca unfortunately did hard coding compile time , calculating time passed since then. a. bad practice , b. reliant on arduino's internal clock can apparently inaccurate on long term.
so part stuck at. need method of getting 1970 time integer doesn't use wired external source (so not on ethernet or usb) , low powered on long term (not wifi?). know gps method, im not sure work inside metal box, inside building. there's more accurate clock modules, im clueless when comes those...
any advice appreciated.
if fun, ok...
but, trust 'ol mechanical combination lock more electronic lock. a key or combination lock can last years-and-years, , doesn't need batteries or external power. parents had safe belonged grandparents , @ least 75 years old. i'm pretty sure setup relies on smart phone & internet won't work 10 or 20 years now. electronics can last long time, doesn't, , technology changes that's not stand-alone can stop working @ time no warning.
i don't see big advantage constantly-changing combination or password. if wants break safe, break in drills, hammers, , saws, etc.
but, trust 'ol mechanical combination lock more electronic lock. a key or combination lock can last years-and-years, , doesn't need batteries or external power. parents had safe belonged grandparents , @ least 75 years old. i'm pretty sure setup relies on smart phone & internet won't work 10 or 20 years now. electronics can last long time, doesn't, , technology changes that's not stand-alone can stop working @ time no warning.
i don't see big advantage constantly-changing combination or password. if wants break safe, break in drills, hammers, , saws, etc.
Arduino Forum > Using Arduino > Project Guidance > Google Auth Safe/Vault
arduino
Comments
Post a Comment