Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

we cannot install the globaleaks package from the repository #4136

Open
ivanricolivares14 opened this issue Jul 17, 2024 · 1 comment
Open

Comments

@ivanricolivares14
Copy link

What version of GlobaLeaks are you using?

we are trying to install the latest

What browser(s) are you seeing the problem on?

No response

What operating system(s) are you seeing the problem on?

Linux

Describe the issue

We are trying to install globaleaks in a docker container with a debian 12 system, we have downloaded the script install-globaleaks.sh as it says in the official documentation, but when it comes to connecting to the repository it seems that it cannot connect because the repository does not trust of the key. the error is the following:
fail_globaleaks1
globaleaks2

when execute the script:
Running: "apt-get -y install gnupg net-tools software-properties-common wget"... SUCCESS
Adding GlobaLeaks PGP key to trusted APT keys
Updating GlobaLeaks apt source.list in /etc/apt/sources.list.d/globaleaks.list ...
Running: "apt-get update -y"... SUCCESS
Running: "apt-get install globaleaks -y"... FAIL
Ouch! The installation failed.

when execute the command "apt-get update":
Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verificat
Reading package lists... Done
W: Failed to fetch http://deb.globaleaks.org/bookworm/InRelease Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unicate verification. [IP: 10.15.119.106 8080]
W: Some index files failed to download. They have been ignored, or old ones used instead.

Proposed solution

No response

@Hexdigest123
Copy link

Hello, you could potentially use the following official Docker image from GlobaLeaks in the meantime, while the bug persists:
https://hub.docker.com/r/globaleaks/globaleaks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants