jans23

@szszszsz Is this issue solved? At least for 1.3 I can find a manually attached tarball.

I think that would be very good to have. You find our Contribution Agreements [here](https://github.com/Nitrokey/wiki/wiki/Contribution-Agreement).

Arch has version 1.3.1 already in [repository](https://aur.archlinux.org/packages/nitrokey-app/). Hence, no need to get AppImage running on Arch - at least not a priority.

Yes, it would be good to have a perfect AppImage. But we introduced AppImage for distributions where NK App isn't available yet. From this perspective fixing this issue is not...

I don't really get the idea. If users don't want their password to be kept in the clipboard, they shouldn't use a clipboard manager at the first place. I don't...

We at Nitrokey use the same code base as Solokeys and reducing the key handle length's was the first [issue](https://github.com/Nitrokey/nitrokey-3-firmware/issues/36) we fixed because it didn't work with several services. Definitely...

I agree that such process should not require a 2nd computer. For clarification: IMO "export to secure storage" in the first two paragraphs refer to two different things. In the...

> If I would go for a solution to create a backup I would go either in a similar way you did or I would propose configuring two smart cards...

> Questions of how to deal with old keys is here: #493 (comment) with returns if users really want this from both Purism (@kylerankin ) /Nitrokey? (@jans23) ? Loosing backward...

If OEM Factory Reset should be used by non-OEMs, I suggest to changing the name to Factory Reset.