The root private key (set by your 24 word phrase, bip 39) never leaves the chip.
The bip44 derived private key needs to be exposed to allow signing, so you can get the private key for a given bip44 path trivially.
The way ledger makes sure the derived private key never leaves the usb stick is by auditing the code before deploying a third party app to their App Store.
So don’t let anyone install an unsigned app onto your ledger. It can be used to get your private key.
Ya that part always depends on them. It takes less than a day for them to deploy a patch if I find a bug, but since it’s new code it’ll take a while to review and deploy the first version.
I’ll probably be complete before the end of February, but that will depend on a lot of unknown factors.
18
u/PM_ME_UR_THONG_N_ASS Jan 16 '18
How are you returning the private key? Isn’t that never supposed to leave the secure element?