[Bitwarden] Manage passwords and other sensitive informations

Announcements Apps
21

Ok merci de ton retour. J’essaie depuis une save de 1password et de bitwarden aussi mais fonctionne pas …

22

Édit :
Bon j’ai réinstallé et testé sur deux machines différente et toujours les même soucis …
Je ne comprends pas.

Ca me dit soit :
Une erreur est survenue.
Une erreur inattendue est survenue.

Ou

Une erreur est survenue.
Rien à importer

23

Juste pour voir, essaie d’importer autre chose ? (c’est peut être le format 1password qui pose soucis ? )

24

J’ai essayé format csv aussi et via un export du site bitwarden aussi :s
Peut etre une limite de taille d’ envoie de fichier ?

Existe t’il peut être un endroit ou on peut voir les erreurs ?

26

I can’t install bitwarden.

Using VPS with SSH access and 2 domains.
CPU:1 vCore
RAM:1024 MB
Storage:32 GB NVMe

I have wordpress and SOGo on my first domain and want to install Bitwarden on my second domain but it’s giving me an error.

2019-12-17 19:39:09,592: WARNING - e[91me[1m[ERR]e[0m !!
2019-12-17 19:39:09,592: DEBUG - + local legacy_args=m
2019-12-17 19:39:09,592: WARNING -   bitwarden's script has encountered an error. Its execution was cancelled.
2019-12-17 19:39:09,592: DEBUG - + args_array=([m]=message=)
2019-12-17 19:39:09,592: WARNING - !!
2019-12-17 19:39:09,593: DEBUG - + declare -Ar args_array
2019-12-17 19:39:09,593: WARNING - 
2019-12-17 19:39:09,593: DEBUG - + local message
2019-12-17 19:39:09,593: DEBUG - + ynh_handle_getopts_args '--message=!!\n  bitwarden'\''s script has encountered an error. Its execution was cancelled.\n!!'
2019-12-17 19:39:09,593: DEBUG - + set +x
2019-12-17 19:39:09,593: DEBUG - + ynh_print_log '\e[91m\e[1m[ERR]\e[0m !!\n  bitwarden'\''s script has encountered an error. Its execution was cancelled.\n!!'
2019-12-17 19:39:09,593: DEBUG - + echo -e '\e[91m\e[1m[ERR]\e[0m !!\n  bitwarden'\''s script has encountered an error. Its execution was cancelled.\n!!'
2019-12-17 19:39:09,593: DEBUG - + '[' api == cli ']'
2019-12-17 19:39:09,593: DEBUG - + type -t ynh_clean_setup
2019-12-17 19:39:09,593: DEBUG - + ynh_clean_setup
2019-12-17 19:39:09,593: DEBUG - + ynh_clean_check_starting
2019-12-17 19:39:09,593: DEBUG - + kill -s 15
2019-12-17 19:39:09,593: DEBUG - kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
2019-12-17 19:39:09,593: DEBUG - + ynh_secure_remove ''
2019-12-17 19:39:09,594: DEBUG - + local legacy_args=f
2019-12-17 19:39:09,594: DEBUG - + args_array=([f]=file=)
2019-12-17 19:39:09,594: DEBUG - + declare -Ar args_array
2019-12-17 19:39:09,594: DEBUG - + local file
2019-12-17 19:39:09,594: DEBUG - + ynh_handle_getopts_args ''
2019-12-17 19:39:09,594: DEBUG - + set +x
2019-12-17 19:39:09,594: DEBUG - + echo '! Helper used in legacy mode !'
2019-12-17 19:39:09,594: DEBUG - + set +x
2019-12-17 19:39:09,594: DEBUG - + local 'forbidden_path=     /var/www     /home/yunohost.app'
2019-12-17 19:39:09,594: DEBUG - + '[' 1 -ge 2 ']'
2019-12-17 19:39:09,594: DEBUG - + [[      /var/www     /home/yunohost.app =~ '' ]]
2019-12-17 19:39:09,594: DEBUG - + ynh_print_warn '--message=Avoid deleting .'
2019-12-17 19:39:09,594: DEBUG - + local legacy_args=m
2019-12-17 19:39:09,594: DEBUG - + args_array=([m]=message=)
2019-12-17 19:39:09,594: DEBUG - + declare -Ar args_array
2019-12-17 19:39:09,595: DEBUG - + local message
2019-12-17 19:39:09,595: DEBUG - + ynh_handle_getopts_args '--message=Avoid deleting .'
2019-12-17 19:39:09,595: DEBUG - + set +x
2019-12-17 19:39:09,595: DEBUG - + ynh_print_log '\e[93m\e[1m[WARN]\e[0m Avoid deleting .'
2019-12-17 19:39:09,595: DEBUG - + echo -e '\e[93m\e[1m[WARN]\e[0m Avoid deleting .'
2019-12-17 19:39:09,595: DEBUG - e[93me[1m[WARN]e[0m Avoid deleting .
2019-12-17 19:39:09,595: DEBUG - + ynh_die
2019-12-17 19:39:09,595: DEBUG - + local legacy_args=mc
2019-12-17 19:39:09,595: DEBUG - + args_array=([m]=message= [c]=ret_code=)
2019-12-17 19:39:09,595: DEBUG - + declare -Ar args_array
2019-12-17 19:39:09,595: DEBUG - + local message
2019-12-17 19:39:09,595: DEBUG - + local ret_code
2019-12-17 19:39:09,595: DEBUG - + ynh_handle_getopts_args
2019-12-17 19:39:09,596: DEBUG - + set +x
2019-12-17 19:39:09,596: DEBUG - + echo ''
2019-12-17 19:39:09,596: DEBUG - + exit 1

Can anyone assist?

Thanks

27

This is an old topic, but since the package is still there and kicking, and I just figured it out myself, I thought it ought to be documented somewhere so that the next one won’t spend too much time on it:

The BW Android client does not yet support TLS v1.3:

If you set nginx security to “modern” on your Yuno instance, since version 4+ (?), nginx will only support TLS v1.3.

You will get an error at login:
handshake failed

You need to reset the variable security.nginx.compatibility in order to downgrade your security level to intermediate:
yunohost settings reset security.nginx.compatibility
yunohost tools regen-conf nginx

and… you can login again in your bitwarden’s instance!

–

Je déterre ce vieux topic pour documenter et partager avec les autres utilisateurs la solution à un problème que je viens de résoudre pour moi, en espérant que ce post se retrouve facilement pour ceux qui cherchent:

Le client Android de BW ne supporte pas encore TLSv1.3

Depuis la version 4 de Yunohost (je pense), si vous avez réglé la securité de nginx à “modern”, nginx ne supporte plus que la TSLv1.3.

Vous aurez alors un message d’erreur à la connexion:
Handshake failed

Pour résoudre ça, vous devez faire un reset sur le réglage de Yunohost:

yunohost settings reset security.nginx.compatibility
yunohost tools regen-conf nginx

et vous pouvez maintenant vous connecter à nouveau depuis le client Android.

En attendant le support du TLS v1.3 dans ce client…

28

This is strange, I use the last BitWarden build from F-Droid (no Play Store on my phone) and I can sync with the server, even with the “modern” security.

I even had to re-connect a few days ago, after a re-install of the BitWarden Android app.

29

This strange indeed because… I can’t find Bitwarden in F-droid, or at least not in the main repository. I installed it using Aurora.
The ticket for TLS 1.3 support is still open.

Can you double check which client (version) you’re using ? Mine is “2.6.1 (3178)”

30

2.6.1(3178) here too.
Bitwarden is not in the default F-Droid repo, they have their own (same build as Play Store, without Google libs)

Here is the repo link :
https://mobileapp.bitwarden.com/fdroid/repo?fingerprint=BC54EA6FD1CD5175BCCCC47C561C5726E1C3ED7E686B6DB4B18BAC843A3EFE6C

There is also a build in Izzy’s repo (maybe the same one, I don’t know)

31

Got an error while trying to upgrade Bitwarden… Luckily this time my app was not removed! Below the log:

https://paste.yunohost.org/raw/aqecevefen

32

J’ai fait la MaJ hier sans soucis, est ce que tu peux en dire plus sur ton serveur, au cas où ça puisse aider à trouver la source du problème ?

33

I think that the problems lies here:

2021-04-01 20:19:46,918: DEBUG - + sudo -u bitwarden RUSTUP_HOME=/var/www/bitwarden/.rustup CARGO_HOME=/var/www/bitwarden/.cargo bash -c ‘curl -sSf -L https://static.rust-lang.org/rustup.sh | sh -s – -y --default-toolchain nightly’
2021-04-01 20:19:47,521: WARNING - info: downloading installer
2021-04-01 20:19:50,427: WARNING - warning: it looks like you have an existing installation of Rust at:
2021-04-01 20:19:50,427: WARNING - warning: /usr/bin
2021-04-01 20:19:50,428: WARNING - warning: rustup should not be installed alongside Rust. Please uninstall your existing Rust first.
2021-04-01 20:19:50,428: WARNING - warning: Otherwise you may have confusion unless you are careful with your PATH
2021-04-01 20:19:50,428: WARNING - warning: If you are sure that you want both rustup and your already installed Rust
2021-04-01 20:19:50,429: WARNING - warning: then please reply y' or yes’ or set RUSTUP_INIT_SKIP_PATH_CHECK to yes
2021-04-01 20:19:50,429: WARNING - warning: or pass `-y’ to ignore all ignorable checks.
2021-04-01 20:19:50,430: WARNING - error: cannot install while Rust is installed

I’ve installed cargo rustc in order to get Synapse server back online after the wrong package update (see https://forum.yunohost.org/t/problem-during-the-synapse-update/6776/22 )

@Mamie You think I need to uninstall it?

34

Yeap that was it. I purged cargo rustc and the app upgraded correctly.

35

Hey all.

I have migrated yesterday from Btiwarden to Vault warder using this : sudo yunohost app upgrade bitwarden -u https://github.com/YunoHost-Apps/vaultwarden_ynh --debug

All went ok apart from the time to compile everything, which was mentioned in the guidelines.

In this morning’s diagnosis, I got this error :

[ERROR] An issue was found for app Vaultwarden
  - This application is not in YunoHost's application catalog. If it was in the past and got removed, you should consider uninstalling this app as it won't receive upgrade, and may compromise the integrity and security of your system.

I got this also the day before I migrated from Bitwarden and the text was the same apart from the different name of the app.

Anyone knows if there is anything else to do to resolve this error?

EDIT:

I also get this error in system update log (web admin): Failed to get label for app bitwarden ?