Skip to content

Conversation

@dd9jn
Copy link
Contributor

@dd9jn dd9jn commented Dec 12, 2018

We like to hand out tokens as well as giving everyone an opportunity to use this hardware and software for their own idea on how to implement an OpenPGP compliant token. For interoperability it would be good to have a dedicated VID/PID for such small series of tokens. After all the different implementations can apply for a free manufacturer ID (according to the OpenPGP card specs) and use this to distinguish their implementations. Due to the usual problems the VID of the FSIJ can't be used for own experiments or tokens and thus the missing VID/PID is major hurdle to deploy such tokens.

FWIW, 2440 is the original RFC number for OpenPGP. 4880 being the current one but I hesitate to ask for two PIDs just to reserve it.

@Arachnid
Copy link
Contributor

Thanks for your pull request! Is the project at the point where you need a dedicated PID? If it's still in the prototyping phase, you're welcome to use our test PID.

@dd9jn
Copy link
Contributor Author

dd9jn commented Dec 14, 2018

Well, the hardware is in actual use but several people asked how to build or modify the hardware on their own without running into problems with the VID:PID. The VID:PID in use when you buy ready tokens from the author, the FSF, or Seeed Studio can't be used if you want to distribute the tokens yourself.

Having a dedicated VID:PID for these types of tokens would be very useful so that they can be made part of the Linux distros USB VID:PID registries. The need for the VID:PID is merely so that it is possible for GnuPG to access those tokes without requireing the user to fiddle with the USB setup or worse use arbitrary or even 0000:0000 ids.

For our own project we need to decide on a case and can then start to flash and distribute the tokens.

@Arachnid Arachnid merged commit 8e1de48 into pidcodes:master Dec 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants