Bitwarden manager (alpha)

Submitted by nemishkor on Sat, 2021/04/17 - 19:13

Rating:

Your rating: None Average: 5 (3 votes)

Alpha version of Bitwarden password manager. Please be aware that application has security issues because stores some credentials as plain text. So use it only with demo accounts. Sailfish-secrets package does not allowed by harbour validator. Master password used to generate key only and it clears instantly then. Encryption keys stores in RAM only.

Done:

login/logout (authentication, token refreshing)
encryption
ciphers list
most data of single cipher (login/card/identity types, notes, custom fields, password history)
copy to clipboard

Plans to do:

organizations related functions
output more data about ciphers to view
folders list
...

Be free to leave your propositions and issues here

Screenshots:

Keywords:

Application versions:

Attachment	Size	Date
harbour-bitwarden-manager-0.7.0-1.armv7hl.rpm	127.79 KB	17/04/2021 - 19:12
harbour-bitwarden-manager-0.6.0-1.armv7hl.rpm	122.05 KB	16/04/2021 - 01:39
harbour-bitwarden-manager-0.5.0-1.armv7hl.rpm	117.26 KB	16/04/2021 - 00:12
harbour-bitwarden-manager-0.4.0-1.armv7hl.rpm	116.43 KB	11/04/2021 - 23:43

Changelog:

- Add Swedish translation (thanks to eson57)
- Add cipher's revision date field to view
- Add password history
- Add "copy to clipboard" function

Comments

explit

Tue, 2021/04/20 - 04:13

Permalink

Sync with real bitwarden account doesnt work (the app close immediately after sync). Will look what happens in the terminal during closing of the app an sync

ninepine

Sat, 2021/04/10 - 21:03

Permalink

Thanks for the work so far. I can unlock my Bitwarden vault and the app then says that a sync is required. When I attempt to sync I am thrown out to Home screen and my vault is locked. Is sync still to be implemented please? (on the Lock/unlock screen the circular "timer" turns but does nothing.

nemishkor

Sat, 2021/04/10 - 22:56

Permalink

Thanks for comment =)
Unlocking/locking vault and data syncing are implemented. But these functions was tested on new and almost empty account that was created on bitwarden.com.
Try version 0.1-1. Maybe I broke something in v.0.3.0-1.
App could works wrong if:
- different encryption is used
- you use self-hosted bitwarden server that has older version
- your account is premium
- something required organizations related or SSO functions or 2FA

ninepine

Sun, 2021/04/11 - 10:30

Permalink

Hi nemishkor and thanks for the suggestions.

I do have a premium account but only use the default encryption as far as I am aware. I don't self host or use 2FA or organisations etc.

I have therefore set up a "test" account with a different email.

With a single entry and using v0.3.0-1 sync works (although the App kicks me out when I then try and view the single record). I still get the circling "timer" on the lock/unlock screen. I therefore don't think the upgrade to 0.3 broke anything.

When I import my full set of records into the "test" non-premium account sync crashes as before. The problem may therefore not be premium or version related but due to file size or number of records. I have 11 folders and 250 records in my vault.

Over the next few days I'll try reducing the "test" records and see if and when, with fewer records, sync works. :)

Interestingly I don't get a warning email from Bitwarden to say a new device has accessed my account when I log in using the Sailfish version. With any other Android or PC device that I connect. I do.

nemishkor

Sun, 2021/04/11 - 23:12

Permalink

> With a single entry and using v0.3.0-1 sync works
Just to be clear. Sync page should contains text "done" if sync successfully finished.

> Over the next few days I'll try reducing the "test" records and see if and when, with fewer records, sync works. :)
It would be nice. I'll wait for responce

> Interestingly I don't get a warning email from Bitwarden to say a new device has accessed my account when I log in using the Sailfish version. With any other Android or PC device that I connect. I do.
I had deauthorized sessions and then tried to login via official CLI client. And email was not sent. Maybe server sends notifications if specific clients are used. https://i.imgur.com/QV0GDFA.png
In this SFOS app client_id, deviceType, deviceName fields have the same values as in official CLI client