starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Fails to build with OpenSSL 1.1.1 #96

New Issue
Closed
opened 2026-02-04 16:55:09 +03:00 by OVERLORD · 10 comments
OVERLORD commented 2026-02-04 16:55:09 +03:00
Owner
Copy Link

Originally created by @luusl on GitHub (Sep 19, 2018).

On my machine I have OpenSSL 1.1.1 installed and building fails according to this error:

error: failed to run custom build command for `openssl v0.9.24`
process didn't exit successfully: `/home/build/bitwarden_rs-1.1.0/target/release/build/openssl-70a8875277726cb3/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'Unable to detect OpenSSL version', /home/build/.cargo/registry/src/github.com-1ecc6299db9ec823/openssl-0.9.24/build.rs:16:14
Originally created by @luusl on GitHub (Sep 19, 2018). On my machine I have OpenSSL 1.1.1 installed and building fails according to this error: ``` error: failed to run custom build command for `openssl v0.9.24` process didn't exit successfully: `/home/build/bitwarden_rs-1.1.0/target/release/build/openssl-70a8875277726cb3/build-script-build` (exit code: 101) --- stderr thread 'main' panicked at 'Unable to detect OpenSSL version', /home/build/.cargo/registry/src/github.com-1ecc6299db9ec823/openssl-0.9.24/build.rs:16:14 ```
OVERLORD added the enhancementquestion labels 2026-02-04 16:55:09 +03:00
OVERLORD commented 2026-02-04 16:55:24 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (Sep 19, 2018):

This is a problem with the old openssl crate, which doesn't support OpenSSL 1.1.1. (See https://github.com/sfackler/rust-openssl/issues/994).

We have two dependencies that require that openssl version: reqwest, which works fine in its version 0.9 and lettre, which needs a change (See open PR: https://github.com/lettre/lettre/pull/303)

The solutions for now are to:

  • Revert to openssl 1.0.2
  • Fork lettre with that PR and change the Cargo.toml to use that instead, also updating the reqwest dependency
@dani-garcia commented on GitHub (Sep 19, 2018): This is a problem with the old `openssl` crate, which doesn't support OpenSSL 1.1.1. (See https://github.com/sfackler/rust-openssl/issues/994). We have two dependencies that require that `openssl` version: `reqwest`, which works fine in its version 0.9 and `lettre`, which needs a change (See open PR: https://github.com/lettre/lettre/pull/303) The solutions for now are to: - Revert to openssl 1.0.2 - Fork lettre with that PR and change the Cargo.toml to use that instead, also updating the reqwest dependency
OVERLORD commented 2026-02-04 16:55:32 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (Sep 19, 2018):

I pushed a fix with the second solution I mentioned here: https://github.com/dani-garcia/bitwarden_rs/tree/openssl-fix

Hopefully the PR is merged soon and we can continue using the upstream version directly.

@dani-garcia commented on GitHub (Sep 19, 2018): I pushed a fix with the second solution I mentioned here: https://github.com/dani-garcia/bitwarden_rs/tree/openssl-fix Hopefully the PR is merged soon and we can continue using the upstream version directly.
OVERLORD commented 2026-02-04 16:55:33 +03:00
Author
Owner
Copy Link

@luusl commented on GitHub (Sep 20, 2018):

Thank you, I tried that branch and it works.

@luusl commented on GitHub (Sep 20, 2018): Thank you, I tried that branch and it works.
OVERLORD commented 2026-02-04 16:55:37 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (Sep 20, 2018):

Okay, that PR was merged, so the OpenSSL fix is now in master. With that, we can mark this issue as fixed.

@dani-garcia commented on GitHub (Sep 20, 2018): Okay, that PR was merged, so the OpenSSL fix is now in master. With that, we can mark this issue as fixed.
OVERLORD commented 2026-02-04 16:55:40 +03:00
Author
Owner
Copy Link

@chris-morgan commented on GitHub (Sep 23, 2018):

Any chance of a bitwarden_rs 1.1.1 release to go with the openssl 1.1.1?

@chris-morgan commented on GitHub (Sep 23, 2018): Any chance of a bitwarden_rs 1.1.1 release to go with the openssl 1.1.1?
OVERLORD commented 2026-02-04 16:55:51 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (Sep 23, 2018):

You are right, we need a release.
As the changes since the last version are significant, I decided to release a 1.2.0 version. I hope that works for you.

https://github.com/dani-garcia/bitwarden_rs/releases/tag/1.2.0

@mprasil Can you trigger a docker build of the new version, please?

@dani-garcia commented on GitHub (Sep 23, 2018): You are right, we need a release. As the changes since the last version are significant, I decided to release a 1.2.0 version. I hope that works for you. https://github.com/dani-garcia/bitwarden_rs/releases/tag/1.2.0 @mprasil Can you trigger a docker build of the new version, please?
OVERLORD commented 2026-02-04 16:55:58 +03:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Sep 24, 2018):

Just triggered it now, it's gonna take about 6h before all the image versions are done.

@mprasil commented on GitHub (Sep 24, 2018): Just triggered it now, it's gonna take about 6h before all the image versions are done.
OVERLORD commented 2026-02-04 16:56:02 +03:00
Author
Owner
Copy Link

@dobunzli commented on GitHub (Sep 24, 2018):

Hello,

Thanks for the work. I want to update the READ ME but just to be sure:

  • people who wants to use bitwarden_rs on a "ARM7 plateform" (e.g. raspberry pi) have to use mprasil/bitwarden:raspberry instead of mprasil/bitwarden:latest in the different commands
  • people who want to use bitwarden_rs on a "musl plateform" (e.g. gentoo musl) have to us mprasil/bitwarden:musl instead of mprasil/bitwarden:latest in the different commands

Is that correct ?

Thanks

Dominique

Le 24 sept. 2018 à 13:08, mprasil <notifications@github.com mailto:notifications@github.com> a écrit :

Just triggered it now, it's gonna take about 6h before all the image versions are done.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/dani-garcia/bitwarden_rs/issues/193#issuecomment-423940183, or mute the thread https://github.com/notifications/unsubscribe-auth/AbTYwl6BNcFjun45iyW5XisFBId3owRCks5ueL0agaJpZM4Wv6LU.

@dobunzli commented on GitHub (Sep 24, 2018): Hello, Thanks for the work. I want to update the READ ME but just to be sure: - people who wants to use bitwarden_rs on a "ARM7 plateform" (e.g. raspberry pi) have to use mprasil/bitwarden:raspberry instead of mprasil/bitwarden:latest in the different commands - people who want to use bitwarden_rs on a "musl plateform" (e.g. gentoo musl) have to us mprasil/bitwarden:musl instead of mprasil/bitwarden:latest in the different commands Is that correct ? Thanks Dominique > Le 24 sept. 2018 à 13:08, mprasil <notifications@github.com <mailto:notifications@github.com>> a écrit : > > Just triggered it now, it's gonna take about 6h before all the image versions are done. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub <https://github.com/dani-garcia/bitwarden_rs/issues/193#issuecomment-423940183>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AbTYwl6BNcFjun45iyW5XisFBId3owRCks5ueL0agaJpZM4Wv6LU>. >
OVERLORD commented 2026-02-04 16:56:11 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (Sep 24, 2018):

I think it's mprasil/bitwarden:alpine instead of musl, but yeah.

@dani-garcia commented on GitHub (Sep 24, 2018): I think it's `mprasil/bitwarden:alpine` instead of `musl`, but yeah.
OVERLORD commented 2026-02-04 16:56:14 +03:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Sep 24, 2018):

Just a small correction. People on musl platform don't have to use mprasil/bitwarden:alpine, the required platform dependencies are shipped in the image. So as long as you are on AMD64 platform, you can use both images.

I'm thinking that maybe we should replace the default Debian based image and just use Alpine as default?

@mprasil commented on GitHub (Sep 24, 2018): Just a small correction. People on `musl` platform don't have to use `mprasil/bitwarden:alpine`, the required platform dependencies are shipped in the image. So as long as you are on `AMD64` platform, you can use both images. I'm thinking that maybe we should replace the default Debian based image and just use Alpine as default?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label enhancement question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#96
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?