Saturday, 2018-04-07

*** tpb has joined #tomu00:00
*** ccase- has quit IRC01:03
*** ccase has joined #tomu01:04
*** eightdot_ has joined #tomu02:29
*** eightdot has quit IRC02:32
*** theshaun111 has joined #tomu02:33
*** theshaun has quit IRC02:34
*** theshaun111 is now known as theshaun02:34
m2049r[m]is it possible to flash the new u2f firmware without destroying the keys already in flash?09:23
auscompgeekthe keys are generated when building, not on the device09:23
m2049r[m]AFAICT that used to be so. current code generates them on device, no?09:24
tpbTitle: chopstx/u2f-apdu.c at efm32 · im-tomu/chopstx · GitHub (at
kyaputenm2049r[m] wouldn't it be a security problem if you could reflash ?12:30
m2049r[m]well, you could upgrade the software and keep your keys intact- that would be good. security problem: IMHO no, as if someone has physical access to the device they can use it to do whatever anyway. and read out the keys if they wanted to (since we don't have a secure element).13:59
*** CRImier is now known as JDat_16:06
*** NoGodDamnIdea has joined #tomu16:16
*** JDat_ is now known as not_JDats16:18
*** not_JDats is now known as not_JDat16:20
*** not_JDat is now known as CRImier16:26
SergeiGm2049r[m], will this feature resolve your issue?
tpbTitle: chopstx/ at tobootv2 · im-tomu/chopstx · GitHub (at
*** NoGodDamnIdea has quit IRC21:41
m2049r[m]SergeiG: that looks like what i'm looking for - thanks! but ... i can't seem to find inject_key.py22:22
SergeiGm2049r[m], it is in tobootv2 branch, it is not merged yet.22:25
m2049r[m]Oh :)22:26

Generated by 2.13.1 by Marius Gedminas - find it at!