31–40 of 65 posts
Earlier quoted context omitted.
Thank you, I’ll fix it later tonight. Can you confirm your resolution? I mostly tested it on small screens, I wasn’t expecting the front page.
Overlaps on widths >1500px. (My recommendation would be to not make this a background image, but simply an image in the markup after the headline.)
(followed the recommendation -- only for large screens though, it's late and I don't want to make mistakes ehehe)
Absent some very serious issue with the crypto implementation, that would be my greatest concern -- how easy would it be for a state-level actor to introduce some sort of backdoor or other vulnerability (even a subtle one, e.g. modification to EM radiation pattern) to either all or just a select subset of devices, either into components "upstream" in the supply chain, in manufacturing itself, or downstream in transit to the retailer/customer.
I wonder where are they going to manufacture it, and what control and visibility will they have into their supply chains, both upstream and downstream? Absent some very serious issue with the crypto implementation, that would be my greatest concern -- how easy would it be for a state-level actor to introduce some sort of backdoor or other vulnerability (even a subtle one, e.g. modification to EM radiation pattern) to…
Any chance someone might make this work with Nextcloud?
Earlier quoted context omitted.
As cool as that would be its probably not doable because gpg doesn't support curve 25519, which is what signal uses for its authentication keys. So either needs gpg decides to support the curve or hardware keys need to explicitly support either signal or the 25519.
GnuPG supports Curve 25519: https://gist.github.com/jmgrosen/5e646d6a6624c0d0e45f241be21... However, perhaps you're referring to the OpenPGP Smart Card spec, which does indeed lack support for Curve 25519 and EdDSA.
I wish the spec would be updated to include them...
Earlier quoted context omitted.
First version will be fido2 only, thought the firmware is open, so easy to extend. We'll just have to verify which features are copiable vs proprietary for yubikeys. To be honest I don't know at this point, I mostly use my keys for auth, rarely otp, but no gpg/ssh/etc. Do you have any primary use case that you're interested in?
I use mine everyday for signing Git commits and tags. Also as my SSH keys. If it did that then it would potentially replace my YubiKey(s).
Earlier quoted context omitted.
First version will be fido2 only, thought the firmware is open, so easy to extend. We'll just have to verify which features are copiable vs proprietary for yubikeys. To be honest I don't know at this point, I mostly use my keys for auth, rarely otp, but no gpg/ssh/etc. Do you have any primary use case that you're interested in?
Secure storage of GPG/SSH keys preferably 4096bit, so I can have offline "cold signing"/emergency keys that are valid for a long time.
I think I like my tomu.im gadget better. Just sayin'.