Dominik Schürmann

You can use ICSDroid for it, see https://forums.bitfire.at/topic/771/feature-request-sync-local-ics-files-e-g-them-synced-via-dropbox-teamdrive-etc/9 But don't expect bi-directional sync.

@tasn Could you look into this?

I released 2.6. Let's try this fix.

We should use ACTION_CREATE_DOCUMENT from https://developer.android.com/guide/topics/providers/document-provider.html for this on Android 4.4.

I received my Solo Tap (+USB-C) and it works in Chrome with Pixel 2XL on https://u2f.hwsecurity.dev and https://webauthn.hwsecurity.dev . We implemented workarounds for https://github.com/solokeys/solo/issues/214 and https://github.com/solokeys/solo/issues/213 and now it also...

So, some information how Android does FIDO: Chrome is using Google's proprietary FIDO implementation that is shipped in their Google Play Services. I think, we can do a lot better...

@Mincka thanks for your testing, very interesting. I tested the SoloKey Tap successfully on Pixel 2 XL over NFC. I will do a more detailed testing with our different devices...

PR to integrate OpenKeychain with ConnectBot is here: https://github.com/connectbot/connectbot/pull/567

Our newest TermBot release is now using our Hardware Security SDK: https://hwsecurity.dev/ So OpenKeychain is no longer a requirement to get support for Security Keys and smart cards. We think...

Are you following step 3 in https://github.com/PrivacyApps/donations#how-to-use ?