Hello,
Due to some API and/or infrastructure changes to Bitwarden's official
servers, rbw would not accept the password on new machines, and
re-prompt for it, via pinentry, constantly[0].
It would still work on existing machines but would stop working after
the config has been purged and the client reconfigured.
Fortunately, PR #151 on GitHub[1] resolves the issue.
Given that it might take upstream a while to make a new release, it
would be good to have rbw working again.
Either way, patch inlined below.
[0] https://github.com/doy/rbw/issues/145
[1] https://github.com/doy/rbw/pull/151
Regards,
Raf
P.S. I'm not subscribed to ports@ mailing list so please CC me if need be.
Index: security/rbw/Makefile
===================================================================
RCS file: /cvs/ports/security/rbw/Makefile,v
retrieving revision 1.19
diff -u -p -r1.19 Makefile
--- security/rbw/Makefile 27 Sep 2023 16:34:36 -0000 1.19
+++ security/rbw/Makefile 21 Dec 2023 10:12:31 -0000
@@ -4,7 +4,7 @@ NOT_FOR_ARCHS = powerpc64 riscv64 sparc6
COMMENT = command line BitWarden client
DISTNAME = rbw-1.8.3
-REVISION = 0
+REVISION = 1
CATEGORIES = security
Index: security/rbw/patches/patch-src_api_rs
===================================================================
RCS file: security/rbw/patches/patch-src_api_rs
diff -N security/rbw/patches/patch-src_api_rs
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ security/rbw/patches/patch-src_api_rs 21 Dec 2023 10:12:31 -0000
@@ -0,0 +1,14 @@
+Index: src/api.rs
+--- src/api.rs.orig
++++ src/api.rs
+@@ -831,6 +831,10 @@ impl Client {
+ "auth-email",
+ crate::base64::encode_url_safe_no_pad(email),
+ )
++ .header(
++ "user-agent",
++ format!("rbw/{}", env!("CARGO_PKG_VERSION")),
++ )
+ .send()
+ .await
+ .map_err(|source| Error::Reqwest { source })?;
No comments:
Post a Comment