Pull request #10974 introduces the @bitwarden/sdk-internal dependency which is needed to build the desktop client. The dependency contains a licence statement which contains the following clause:

You may not use this SDK to develop applications for use with software other than Bitwarden (including non-compatible implementations of Bitwarden) or to develop another SDK.

This violates freedom 0.

It is not possible to build desktop-v2024.10.0 (or, likely, current master) without removing this dependency.

You are viewing a single thread.
View all comments View context
1 point

How does this play with mobile?

permalink
report
parent
reply
5 points
*

as another option this KeePassXC(PC)+radicale+DAVx5 The same for KeepassDX

permalink
report
parent
reply
2 points

Radicale+DavX5 is for calendars and contacts, no? How does this work for passwords

permalink
report
parent
reply
2 points

for passwords no way, as you noted it is for calendars and contacts

permalink
report
parent
reply
3 points

There’s an Android app, but it’s not being developed any more https://github.com/android-password-store/Android-Password-Store

There’s an iOS app as well https://mssun.github.io/passforios/

They have a list with all the clients and other tools on their website
https://www.passwordstore.org/#other

permalink
report
parent
reply
3 points

besides everything else, the end of support for syncthing-android, yes, that’s a real blow to the gut.

permalink
report
parent
reply
2 points
*

Integration with Android

The GnuPG implementation for Android is called OpenKeychain. To configure it, just go to the “key management” menu and import the previously created secret key. The only drawback of OpenKeychain for me personally is that there is no fingerprint unlocking.

The pass implementation for Android is called android-password-store, or simply APS.

Install and launch APS. Before synchronizing the password store, go to the “Settings” menu. There we will need the following items:

  1. Git server settings. The resulting URL should be the same as that specified on the repository page on github. Authorization type - OpenKeychain.

  2. Git utils. In this section, specify the username and email from the gpg key.

  3. OpenPGP provider. Select OpenKeychain.

  4. Autofill.

Now you can clone. Select “clone from server” on the main screen, specify the desired location of the repository, check the git settings.

Of course, pass is not that easy to set up. However, this price buys confidence that the tools we use will not one day be declared obsolete, will not change their data format, and will not be left without support.

permalink
report
parent
reply

Open Source

!opensource@lemmy.ml

Create post

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

  • Posts must be relevant to the open source ideology
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

Community stats

  • 3.3K

    Monthly active users

  • 1.2K

    Posts

  • 10K

    Comments