On 2024/10/16 16:50, Rubén Llorente wrote:
> Ping,
>
> tested against a recent current. It still works as expected.
>
> Rubén Llorente wrote:
> > Hello,
> >
> > interest in getting Nitrokey hardware supported has been shown on @misc,
> > so I think it is a good idea to post this port. If we are lucky we might
> > get Nitrokeys supported by the time of the next -release. Woo-whooo!
>
pkg-readme has some issues,
- (minor) ==== underlines don't match up with the lines above
- I worry that people won't read the wall of text and just try
to paste the chgrp/chmod directly. Better show something of a
worked example of how to find the device nodes. I don't have a
nitrokey but this is how it could be done for yubikey so this
could be adapted.
$ usbdevs | grep -e /dev/usb -e Yubi
Controller /dev/usb0:
Controller /dev/usb1:
addr 05: 1050:0406 Yubico, YubiKey FIDO+CCID
$ usbdevs -v -d /dev/usb1 -a 05
addr 05: 1050:0406 Yubico, YubiKey FIDO+CCID
full speed, power 30 mA, config 1, rev 5.43
driver: uhidev0
driver: ugen2
I think there were some other concerns voiced about
"Beware this may allow the user unintended access to other hardware
associated to the same usb(4) controller, so do this with extreme
caution."
... what is the user supposed to do?
- modules.inc is for ports with go modules. this should use crates.inc.
- what's up with this MY_REPLACE_CMD, MY_HEADER stuff? just put the
command in post-patch.
No comments:
Post a Comment