Distribution of binary
jeremydrake+gnuk at eacceleration.com
Thu Jan 3 02:29:32 CET 2019
On Thu, 20 Dec 2018, Peter Lebbing wrote:
> On 20/12/2018 12:58, Werner Koch wrote:
>> May I suggest to use 1209:2440 for such uses?
> Oh, that's a good solution, thanks! That way there's no way the FSIJ
> will get sullied by people not observing their conditions.
Also, with as long as this discussion of how to properly exercise freedom
2 of the essential freedoms  has gone on, I was beginning to wonder if
this truly qualified as "free software" ;)
> So what should be the strings for vendor and product?
> Suggestions for vendor string:
> GnuPG e.V.
> (I mean the literal string "None")
I would suggest something generic here, like "Open Source Developer"
> Suggestions for product string:
> GnuK Token
> An OpenPGP Token
> With the first product string, Niibe's udev match on product string
> will catch this device.
I would vote for the more specific option here, namely "GnuK Token", given
that the string is stored in the device itself.
If we were talking about adding to usb.ids, I would swap which should be
generic and which should be specific, and vote for "GnuPG e.V."/"An
OpenPGP Token" as these strings are given to any device with that VID:PID.
> Note that the current code of GnuK will choose these strings based on a
> user-supplied VID:PID. So the strings will always be the same for the
> supplied VID:PID. It would require code changes to implement "If the
> GnuPG e.V. is spreading them, choose that as vendor, otherwise choose
Anyone who wants to distribute binaries (or by extension hardware) with
different strings need only modify GNUK_USB_DEVICE_ID text file at the
root of the source tree, IIRC.
I believe that some software "knows" the 234b:0001 VID:PID, and should be
taught that 1209:2440 should be treated the same. Off the top of my head,
the udev rules which have already been mentioned, plus libccid  and
More information about the Gnuk-users