Arch Linux User Repository

Hi,

I'm interested in packaging onlykey-agent and onlykey-cli. Does anybody have a work-in-progress or something to work on or should I start from scratch?

Hi @slackline,

This packages the official OnlyKey App released here: https://github.com/trustcrypto/OnlyKey-App/

It is compatible with OnlyKey DUO (note that the download links in "Install OnlyKey Desktop App" point to the same GitHub repository).

The onlykey-udev package will be used as a dependency of this one as soon as the package owner fixes it. Until then this package provides the same udev rules.

Hi,

Got an OnlyKey Duo and was wondering what the state of play is with this and other related packages is? I've seen there is a separate package for udev rules but its still included in this package.

@thurstylark sure, let's go for it. I will remove 49-onlykey.rules and will require your package as soon as you create it.

One suggestion about the package, though: either add the whole file in the AUR repo (like this package does) or fetch from stable URL by commit hash, instead of branch name. That is instead of master you should use b530e0e0a1d638a64c64376f36d0b7b0e80a8e38. Otherwise any future commit of this file will break your package due to mismatching checksum.

P.S.: Feel free to contact me directly via email (visible on my AUR profile). It might speed up the whole communication.

I think that shipping the same file in both packages will cause more problems than its worth down the line. I also intend to package onlykey-agent ( https://github.com/trustcrypto/onlykey-agent ) which also depends on these udev rules to be in place, but onlykey, onlykey-cli, and onlykey-agent aren't dependent on each other, and can be run separately if the user desires.

On top of that, there is an alternative udev rules file provided by upstream ( https://github.com/trustcrypto/trustcrypto.github.io/blob/master/49-onlykey-blink.rules ) which would be even harder for someone to use if multiple packages were shipping the same rules file.

My first reflex was to suggest adding the udev rules as a split package to one of the onlykey utilities, but that would cause the user to need to build the entirety of that utility just for the udev rules, even though they may not need/want that utility.

With these considerations, I think creating another package for these udev rules is the best way out of this chicken/egg problem. We can create it as a split package which covers both versions of the udev rules to minimize effort for both us on the maintainer side, and for the user when building/using these utilities.

The new package should be extremely simple to manually parse if the user desires. I have created a prototype onlykey-udev package if you'd like to review it: https://git.thurstylark.com/aur/onlykey-udev As of writing, I have yet to make this into a split package which ships 49-onlykey-blink.rules, but there are other requirements that need to be considered before that's ready to be packaged.

TL;DR: I think a separate package for the udev rules is unavoidable, and I've got a package ready to go if we decide to go ahead with it.

I also have other changes to propose for onlykey before this is ready to package, but we should definitely come to a decision on how things are going to be set up before getting into those.

@thurstylark, sure let's work together. The only way I can think of is creating a third package like onlykey-udev or something. Said that, making a whole package for one single file seems like a bit of an overkill to me. Especially when it comes to packages that are supposed to be manually sanitized by end users one by one.

Wouldn't it be easier to just use a different name for the .rules file? 50-onlykey.rules, for instance?

I'm looking at packaging onlykey-cli ( https://github.com/trustcrypto/python-onlykey ), which will need to ship the same udev rules that this package does.

Instead of shipping the rules in one package and making it a dep of the other package, would you be willing to work together to ship these udev rules in a way that both packages will be able to use them without the other package being installed?

a dependency (for those not using X11) is having libxss.

This is the actual "OnlyKey Desktop App" , not the Chrome application. Which is exactly what I was looking for. An added bonus is that it installs the necessary uDev rules for the key to work. https://docs.crp.to/linux#install-app Thanks!