Skip to content
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.

[FEATURE] Integrate hwsecurity to leverage PIV (for Solo v2 keys) #1486

Closed
colemickens opened this issue Aug 14, 2021 · 7 comments
Closed

[FEATURE] Integrate hwsecurity to leverage PIV (for Solo v2 keys) #1486

colemickens opened this issue Aug 14, 2021 · 7 comments
Labels
A-auth Area: Connection and authentication C-feature Category: This is a feature request E-hard Effort: This will require a lot of work P-low Priority: low S-help-wanted Status: This issue could use external help with implementation S-unactionable Status: There is not enough information to act on this problem
Milestone

Comments

@colemickens
Copy link

Is your feature request related to a problem? Please describe.

Not really.

Solo Keys is having a v2 with Rust-based firmware. It seems, at launch, they expect to only provide a PIV-based application, and not an OpenPGP-based application.

I understand that on Windows and Linux, I have options, such as using gnupg-pkcs11-scd.

Describe the solution you'd like

Using this GPLv3 library to perform encrypt/decrypt operations via PIV/smartcard : https://github.com/cotechde/hwsecurity/tree/master/hwsecurity/piv/src/main

  1. encrypt/decrypt store entries
  2. used for the SSH auth to sync the store entries as wells (this is less important to me, I suppose, I could start syncing my password store with Syncthing).

Describe alternatives you've considered

The only alternative seems more expensive: write an OpenPGP app for the Trussed firmware.

Additional context
n/a

Thank you very much for Password Store. I understand if this is out-of-scope, but I thought I'd ask, I'd really like to switch to open-(firmware-)source keys.

@colemickens colemickens added C-feature Category: This is a feature request S-awaiting-triage Status: New issues that have not been assessed yet labels Aug 14, 2021
@msfjarvis
Copy link
Member

I don't have the time yet to actually look through the code but the simple fact that none of the maintainers own a SoloKeys product (to my knowledge) makes it a non-starter for us to work on it.

If someone can volunteer time to contribute this I'd be happy to assist them. Alternatively, sponsoring one of the maintainers for their time and whatever the cost ends up being for procuring one of Solo's security keys can also be an option if anyone from @android-password-store/devs is up for it.

@msfjarvis msfjarvis added A-auth Area: Connection and authentication E-hard Effort: This will require a lot of work P-low Priority: low S-unactionable Status: There is not enough information to act on this problem and removed S-awaiting-triage Status: New issues that have not been assessed yet labels Aug 14, 2021
@nickray
Copy link

nickray commented Aug 23, 2021

We'd be happy to send over a few keys for contributors, just drop an email to [email protected] if there is developer interest.

Thinking experimentally, there are a few projects named "passage", i.e. pass backed by age instead of pgp, including some with PIV backend. Also FYI, Nitrokey has plans to develop a PGP app, that would then run on both vendors' keys as they reuse our Trussed framework.

@msfjarvis
Copy link
Member

msfjarvis commented Aug 23, 2021

We'd be happy to send over a few keys for contributors, just drop an email to [email protected] if there is developer interest.

Great, I'll have a chat with the maintainers and see who all are willing to take this feature up.

Thinking experimentally, there are a few projects named "passage", i.e. pass backed by age instead of pgp, including some with PIV backend. Also FYI, Nitrokey has plans to develop a PGP app, that would then run on both vendors' keys as they reuse our Trussed framework.

I've already been burned by OpenKeychain's poorly designed app locking us into its ecosystem then going into maintenance mode, so I'm very unlikely to switch to a different external app for PGP anytime soon. We're in the process of introducing a new PGP backend powered by Gopenpgp which we intend to fully switch over to in APS v2.

Re: passage and PIV, we've refactored a fair chunk of the crypto code to allow multiple backends and there is maintainer interest in age, so we will likely be supporting it once Filippo's official version of passage is out.

@fmeum
Copy link
Member

fmeum commented Aug 23, 2021

I'm very much looking forward to replacing my usage of GPG with hardware tokens for SSH authentication and pass encryption with PIV/age. I don't think the age ecosystem is quite there yet though, but it also doesn't make sense to implement PIV support now if not backed by age. Based on my understanding of the ecosystem, the following parts are still missing:

  • an age port of desktop pass
  • stable age plugin support for PIV tokens
  • an age plugin for yubikey-agent to match gpg-agent in using PIV for decryption and SSH auth simultaneously

Once these exist, I would happily work on the following ingredients on getting age support into APS:

  1. a Java/Kotlin library implementation of enough of age to support both PIV and standard age key file recipients
  2. an APS backend for PIV decryption that defers to the Cotech SDK
  3. (maybe) an additional backend that uses an age key stored in the Android Keystore

@msfjarvis msfjarvis added the S-help-wanted Status: This issue could use external help with implementation label Nov 20, 2021
@msfjarvis
Copy link
Member

msfjarvis commented Dec 26, 2021

Status update on the required components

  • an age port of desktop pass

Filippo has an alpha release available for his port of pass, passage.

  • stable age plugin support for PIV tokens

This has yet to happen in the reference Go implementation, but the rage implementation written in Rust offers a first-party Yubikey plugin: age-plugin-yubikey.

  • an age plugin for yubikey-agent to match gpg-agent in using PIV for decryption and SSH auth simultaneously

This does not exist yet. It's briefly discussed in the age-plugin-yubikey README noting why this is currently unimplemented.

@FiloSottile
Copy link

I'm working through the list on my side and making progress! :)

https://twitter.com/FiloSottile/status/1469041023196221444

Feel free to @ me if I can help with roadmap planning, design decisions, or fixing things on our side to make this possible!

@msfjarvis
Copy link
Member

I have made the decision to archive the project for reasons outlined here.

This issue is being closed to ensure everyone subscribed to it is made aware of this change in the app's maintenance status.

@msfjarvis msfjarvis closed this as not planned Won't fix, can't repro, duplicate, stale Oct 12, 2024
@android-password-store android-password-store locked as resolved and limited conversation to collaborators Oct 12, 2024
@github-project-automation github-project-automation bot moved this from 🆕 Unexplored to ✅ Done in APS v2 Backlog Oct 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-auth Area: Connection and authentication C-feature Category: This is a feature request E-hard Effort: This will require a lot of work P-low Priority: low S-help-wanted Status: This issue could use external help with implementation S-unactionable Status: There is not enough information to act on this problem
Projects
Archived in project
Development

No branches or pull requests

5 participants