Arch Linux User Repository

@system7 Thank you for reporting that error. I've added libfido2 to the runtime dependencies.

I have an error. I cannot figure out what is the problem with it

==> Starting build()...
fatal: No names found, cannot describe anything.
cd ./utils/ && ./credits.sh bridge
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
CGO_LDFLAGS="-lfido2 -lcbor -lssl -lcrypto" go build -tags='' -ldflags '-X github.com/ProtonMail/proton-bridge/v3/internal/constants.Version=3.22.0+git -X github.com/ProtonMail/proton-bridge/v3/internal/constants.Revision=0e96ddd3f7 -X github.com/ProtonMail/proton-bridge/v3/internal/constants.Tag=NOTAG -X github.com/ProtonMail/proton-bridge/v3/internal/constants.BuildTime=2026-02-12T07:14:26+0100 -X "github.com/ProtonMail/proton-bridge/v3/internal/constants.FullAppName=Proton Mail Bridge" -X github.com/ProtonMail/proton-bridge/v3/internal/constants.BuildEnv=dev' -o "proton-bridge" "./cmd/Desktop-Bridge/"
# github.com/mattn/go-sqlite3
sqlite3-binding.c: In function ‘sqlite3ShadowTableName’:
sqlite3-binding.c:123133:9: warning: assignment discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
123133 |   zTail = strrchr(zName, '_');
       |         ^
# github.com/keys-pub/go-libfido2
# [pkg-config --cflags  -- libfido2]
Package libfido2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libfido2.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libfido2' not found
make: *** [Makefile:143: proton-bridge] Error 1
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: protonmail-bridge-nokeychain-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
protonmail-bridge-nokeychain - exit status 4

EDIT: Lol, after I wrote this, I saw the error: missing libfido2 package. So, $ yay -S libfido2 and after that, it worked seamlessly.

According to the wiki, https://wiki.archlinux.org/title/PKGBUILD#makedepends, base-devel is assumed to be already installed and its dependencies should not be listed in makedepends. patch and make are both dependencies of base-devel.

This has an unstated make dependency on patch and make. It should probably be included in the dependencies.

@cyclic3 Updated the package metadata, thanks for the heads up.

Just a heads up: this package also conflicts with protonmail-bridge-core, could that be added to the PKGBUILD?

@andrei.dubovik Great, thanks!

@DrosteEffect Yes, I'll try to allocate some time to update the package this week. Sorry for a long delay.

In general, maybe my two cents on security and why I bothered in the first place to make this package, and why I think it is perfectly reasonable to store "secrets" in a cleartext file. Adding additional security layers on top of what an OS already provides adds extra complexity and possibly extra vulnerabilities while not actually giving any extra security under the scenario that the OS itself is compromised. SSH stores its secrets in plain text, for instance. Then again, if your keychain requires a yubikey to open or a similar authorization solution, then I would agree that using the keychain provides better security. I just don't think it's correct to say the official package is strictly more secure under all typical usage scenarios.

@DrosteEffect, it seems at this point it is best if you migrated to the up-to-date protonmail-bridge-core.

It serves the same use case, but in a secure way (unlike this package that stores "secrets" in a cleartext file.)

Edit: changed the link to protonmail-bridge-core, because that is the successor of protonmail-bridge-nogui (and the latter is pending deletion as of now).

Will this package be updated soon? It's been out of date since July 2023.