Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Epic] Port Core codebase to Trezor One hardware #24

Closed
12 of 14 tasks
prusnak opened this issue Oct 2, 2018 · 4 comments
Closed
12 of 14 tasks

[Epic] Port Core codebase to Trezor One hardware #24

prusnak opened this issue Oct 2, 2018 · 4 comments
Labels
core Trezor Core firmware. Runs on Trezor Model T and T2B1. epic Issue that aggregates a larger area of tasks.

Comments

@prusnak
Copy link
Member

prusnak commented Oct 2, 2018

@prusnak prusnak transferred this issue from trezor/trezor-core Apr 16, 2019
@prusnak prusnak added core Trezor Core firmware. Runs on Trezor Model T and T2B1. firmware labels Apr 16, 2019
@prusnak prusnak added this to the backlog milestone Apr 16, 2019
@prusnak prusnak added core Trezor Core firmware. Runs on Trezor Model T and T2B1. and removed core Trezor Core firmware. Runs on Trezor Model T and T2B1. labels Apr 17, 2019
@ZdenekSL ZdenekSL modified the milestones: backlog, 2019-Q4 Jun 25, 2019
@tsusanka
Copy link
Contributor

Doing #435 beforehand would help us a lot.

@tsusanka tsusanka modified the milestones: 2019-Q4, backlog Sep 20, 2019
@ZdenekSL ZdenekSL added the epic Issue that aggregates a larger area of tasks. label Oct 24, 2019
@tsusanka tsusanka added the port label May 26, 2020
@tsusanka tsusanka changed the title [meta] port codebase to Trezor One hardware [Epic] Port codebase to Trezor One hardware Jun 5, 2020
@tsusanka tsusanka changed the title [Epic] Port codebase to Trezor One hardware [Epic] Port Core codebase to Trezor One hardware Jun 5, 2020
@tsusanka
Copy link
Contributor

tsusanka commented Jul 2, 2020

We have agreed on with Product that we would like to keep the PIN entry on T1 as it is, that means using the pin matrix. Yes this has a drawback that the USB needs to be turned on beforehand, however we do not want introduce a new feature into the Port process.

@prusnak
Copy link
Member Author

prusnak commented Jul 2, 2020

We have agreed on with Product that we would like to keep the PIN entry on T1 as it is, that means using the pin matrix. Yes this has a drawback that the USB needs to be turned on beforehand, however we do not want introduce a new feature into the Port process.

This makes FIDO2 PIN entry on the device impossible. We could theoretically allow entering the FIDO PIN on host (FIDO allows us to specify this) - but this is a bad idea when the FIDO PIN will be the same as a device PIN (current situation) - introducing different PIN for FIDO also seems like a UX hell.

However, I guess we can live with FIDO being PIN-less on T1.

@tsusanka tsusanka removed this from the backlog milestone Oct 6, 2021
@hynek-jina hynek-jina removed the LOW label May 6, 2022
@Hannsek
Copy link
Contributor

Hannsek commented Sep 24, 2024

After 6 years we can close this issue as we do not have any intention to do such thing anymore.
Moreover, recent split of the core firmware made it impossible to port core to model One.

@Hannsek Hannsek closed this as not planned Won't fix, can't repro, duplicate, stale Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Trezor Core firmware. Runs on Trezor Model T and T2B1. epic Issue that aggregates a larger area of tasks.
Projects
Archived in project
Development

No branches or pull requests

5 participants