Availability through f-droid? about keepass2android HOT 50 OPEN

I have created an fdroid branch which should resolve the licensing issues. For updates, please refer to https://gitlab.com/fdroid/rfp/issues/5

from keepass2android.

Any news on pushing this app to F-Droid eventually? I'd rather install it from F-Droid than from Google Play.

from keepass2android.

🙈

After almost 3 years, the switch to KeePassDX seems a good advice 😉

from keepass2android.

@nazar-pc it's currently available in my repo – but I agree it should be in the official one. The reason why it isn't can be found here: it's a Xamarin app, and would need an F-Droid team member with Xamarin experience to build…

from keepass2android.

@alexanderadam @natrius @DJCrashdummy @CryptOwl finally it's available in my repo (since July 9th).

from keepass2android.

There's even a badge available for that 😉

from keepass2android.

@x-jokay I tried out KeePassDX but unfortunately it seems I cannot set up a WebDAV database for easy synchronisation with my Nextcloud instance.

I tried TinyKeepass also but it doesn't allow editing. So I'll stick to Keepass2android through Google…

And we can't blame KP2A developers for F-Droid not being able to handle the code so I'm inclined to keep supporting/using the best app I know of.

from keepass2android.

It's somehow a pity. There are a some really good KeePass clients like keepass2android and keepshare that are open source bot not on F-Droid yet.
Currently I'm using KeePassDX because it looks more modern than keepassdroid.

Is there any client I could have missed?

from keepass2android.

I think that's the policy for submitting to f-droid: https://f-droid.org/wiki/page/Inclusion_Policy

It links to the gnu.org list of licenses: https://www.gnu.org/licenses/license-list.html . As far as I understand all GPLCompatibleLicenses and GPLIncompatibleLicenses are fine.

from keepass2android.

Hello,
Could you add some kind of tl;dr about current f-droid status to readme, please?
I see that issue got duplicated multiple times and people asking for updates, so it will be easier for all to find that information in readme.

BTW, link to @IzzySoft repo in readme is good idea, too

from keepass2android.

Nextcloud app is really bad on Android, I wouldn't recommend it on a phone for anything, it is simply not reliable (DavX5 mount works fine though).
But in the end it is just WebDav, which I use for years with great success and Keepass2Android does suggest merging if remote was changed in the meantime when using WebDav.

from keepass2android.

Presumably proprietary file syncing features are removed, and that should be the only difference.

from keepass2android.

Hm, if you don't want to hassle much around it would be possible to set up your own repo for f-droid:
https://f-droid.org/docs/Setup_an_F-Droid_App_Repo/
You may consider it, you don't have to change anything at the app itself. And everybody gets updates if you update it.
But via the f-droid repo would still be wonderful : D

from keepass2android.

Is there an update? Or is there even the possibility to download the .apk ?

from keepass2android.

@natrius the apks are still on the releases page and the app is still not on F-Droid.

You could save other people's time, simply by reading and clicking.

from keepass2android.

Ouch, I missed 3 letters in that link: "not" 😱 Apologies!

from keepass2android.

@IzzySoft thank you very much! definitely an improvement.
do you think is it somehow possible to get the add-ons into a repo - at least into yours, as long as they are also not in the main one?

from keepass2android.

Not sure how WebDAV would (meaningfully) merge encrypted files, but OK :) . It could hold different versions, but any merge conflicts is going to be manual (though possibly mediated through a smart enough client, but that wouldn't care about WebDAV versus local filesystem either).

from keepass2android.

@IzzySoft Thank you, I totally agree. The nonet variant is so old that it looked like not being maintained any more. If it were a current release it will be absolutely fine for me.

from keepass2android.

There were build issues with the nonet variant. And yes, it just needs @PhilippC to replace the APK by a signed one and give me a ping, then it would be updated in my repo on the very next day.

from keepass2android.

There has been a packaging request on F-Droid's Gitlab site. Maybe someone can help out @PhilippC with the licensing questions?

from keepass2android.

@PhilippC: I think the best option is to disable all proprietary things through a F-Droid build flavor. It should be the de-facto standard, and one example is riot-android.

Just by the way, Syncthing is comfortable.

from keepass2android.

Looking forward to the F-Droid release! :)

from keepass2android.

@PhilippC will the fdroid-build have entirely the same features as the master?

if not - or as a quick workaround, since it isn't completely done for now - please release an apk at github/gitlab. i'm sure @IzzySoft will be so kind to pick it up and add to his F-Droid Repository.

from keepass2android.

If it's a build different from F-Droid, it should preferably have a different package name then to avoid confusion. But yes, feel free to ping me then.

from keepass2android.

@ishitatsuyuki for sure all proprietary parts won't be included in an fdroid-version, but what specific features will be affected...?

from keepass2android.

Most file syncing platforms.

from keepass2android.

...so the nonet-version may be identical and easier to publish via f-droid?

from keepass2android.

@natrius that's why i asked in #38 (comment) to publish an apk-file which can be included into an own repo.

from keepass2android.

@alexanderadam that RFP is still stalled, so the app itself is not on F-Droid yet.

from keepass2android.

@IzzySoft I know. That's the reason why I wrote that it is still not available and linked to that rfp. 😉

from keepass2android.

@alexanderadam keepshare hasn't been updated for more than a year now (last commit was in 6/2017, last release in 2016). TinyKeePass is at F-Droid as well.

If you follow the RFP for Keepass2Android you will find that @PhilippC and I are working to get it into my repo at least, but that might take a little (Philipp might be able to give an ETA).

from keepass2android.

But still not in the official repos. 😢

from keepass2android.

@DJCrashdummy hard to say, as most of the linked ones don't have APKs in their repos. And the other 2 (K2AUSBKeyboard and AutoFill Plug-in) are already in my repo 😉

from keepass2android.

@IzzySoft i knew about the K2AUSBKeyboard but somehow missed the AutoFill Plug-in... 😕
i'll take this as an ok from your side as soon as we get some APKs. 😉

from keepass2android.

@DJCrashdummy you didn't mention the first (but had me check! evil, evil 🤣) – and couldn't have seen the second as I adopted that only after your previous comment was posted. And you can take that as a "not OK as long as there are no APKs" – though I'll probably take them in when they're there; but wouldn't it be better to file an RFP with the official repo first? If they accept and build it, there'd be no reason for Philipp to provide APKs in his repos.

from keepass2android.

Still no progress?

from keepass2android.

KeePassDX but unfortunately it seems I cannot set up a WebDAV database for easy synchronisation with my Nextcloud instance.

FYI: If you have Nextcloud installed on your phone you can select the database like a normal file. Nextcloud will handle the synchronization for you then.

from keepass2android.

FYI: If you have Nextcloud installed on your phone you can select the database like a normal file. Nextcloud will handle the synchronization for you then.

True, but it wouldn't be able to handle conflicts and gracefully merge the two versions of the database. Also I don't need to send back and forth the whole database file when I correct a simple typo. Using WebDAV has its advantages :)

from keepass2android.

The root cause appears to be Xamarin, more specifically how to build it one a buildserver. That problem with F-Droid is tracked here: https://gitlab.com/fdroid/fdroiddata/-/issues/1529

from keepass2android.

I recently started using this app. Works like a charm.
I just wanted to ping this thread to remind how wonderful it would be if it was available on F-droid. Can we give it a push?

from keepass2android.

@mottech20 the problem is rather that F-Droid cannot build Xamarin apps yet (see the comment right on top of yours). It's being worked on, but with the entire team being volunteers and not enough hands for all tasks waiting to be tackled, that might take time.

from keepass2android.

Hopefully, it will be available soon on F-droid or at least by Izzys repo. I could not find it there

from keepass2android.

@IzzySoft Would you mind adding this full and maintained app to your repo? Thanks.

from keepass2android.

@bege10 it is in my repo (the "nonet" variant). Just not the latest release, as the APK there is unsigned (I've already pinged Philip on that from a different issue). The "full" variant is beyond the per-app size limit of my repo. Should "per-ABI builds" be provided (one APK per architecture, like armeabi, arm64, x86, x86_64) the APK size for each would fall below 20 MB and I could consider that, too. But a non-free dependency (here: Google Services) with an app dealing with sensitive details (passwords) AND network permissions (no offense meant, but with Google's stuff you can never be sure what it's doing behind the curtains, and you cannot check if its proprietary without the full code base open) rather not.

from keepass2android.

@PhilippC I wish there were a WebDAV-only version, instead of a NoNet version. WebDAV is widely available and inclusion wouldn't require any proprietary libraries. Inclusion on Izzy wouldn't be an issue either.

from keepass2android.

@ltguillaume when it comes to password safes, I prefer them to not have network permissions. That way the app dealing with the plain-text passwords and doing the encryption cannot send them out – and the app dealing with the sync of the database cannot peek in. Keepass2Android already has some proprietary components in, which is what ruled it out for my personal use but is kind of gray area for my repo. Add network, and the gray becomes pretty dark. I fully trust @PhilippC here, but he cannot vouch for what those proprietary parts (which after all come from Google, the big data collector) might be up to.

So with the non-free components gone, having WebDav in (and thus requiring network permission) would be OK for my repo, yes. But as I don't know why those are needed I cannot tell if they can be removed easily (or what might have dragged them in).

from keepass2android.

I'm thinking there may be merge issues when using the Nextcloud app for syncing, as opposed to letting Keepass2Android handle it via WebDAV. But I might be wrong about that, and it could be that Keepass2Android just overwrites the local database with a newer from the remote location, without merging the two (as Keepass2 does). Perhaps @PhilippC can shed some light on this?

from keepass2android.

There will probably never be an app on F-Droid / F-Droid custom repo, right? A custom repo like NewPipe's would be really cool.

from keepass2android.

There will probably never be an app on F-Droid / F-Droid custom repo, right? A custom repo like NewPipe's would be really cool.

The Offline version is available in Izzy's custom repo.

from keepass2android.