Cyberduck Mountain Duck CLI

#10448 closed defect (fixed)

Certificate verification failed / Error in certificate verification when trying to install Cyberduck CLI using Debian package

Reported by: patakijv Owned by:
Priority: normal Milestone:
Component: cli Version: 6.7.1
Severity: normal Keywords:
Cc: Architecture: Intel
Platform:

Description (last modified by patakijv)

The following steps were performed and results received in a fresh Ubuntu 18.04.1 LTS (Bionic Beaver) server Docker Container. Is this expected?

echo -e "deb https://s3.amazonaws.com/repo.deb.cyberduck.io nightly main" > /etc/apt/sources.list.d/cyberduck.list
echo -e "deb https://s3.amazonaws.com/repo.deb.cyberduck.io stable main" >> /etc/apt/sources.list.d/cyberduck.list
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys FE7097963FEFBE72
apt-get update

Results:

Ign:1 https://s3.amazonaws.com/repo.deb.cyberduck.io nightly InRelease
Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease                             
Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease                                            
Ign:4 https://s3.amazonaws.com/repo.deb.cyberduck.io stable InRelease                            
Hit:5 http://archive.ubuntu.com/ubuntu bionic-updates InRelease                                  
Err:6 https://s3.amazonaws.com/repo.deb.cyberduck.io nightly Release                              
  Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error in the certificate verification. [IP: 52.216.32.43 443]
Hit:7 http://archive.ubuntu.com/ubuntu bionic-backports InRelease                                 
Err:8 https://s3.amazonaws.com/repo.deb.cyberduck.io stable Release         
  Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error in the certificate verification. [IP: 52.216.32.43 443]
Reading package lists... Done                                               
W: https://s3.amazonaws.com/repo.deb.cyberduck.io/dists/nightly/InRelease: No system certificates available. Try installing ca-certificates.
W: https://s3.amazonaws.com/repo.deb.cyberduck.io/dists/stable/InRelease: No system certificates available. Try installing ca-certificates.
W: https://s3.amazonaws.com/repo.deb.cyberduck.io/dists/nightly/Release: No system certificates available. Try installing ca-certificates.
E: The repository 'https://s3.amazonaws.com/repo.deb.cyberduck.io nightly Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: https://s3.amazonaws.com/repo.deb.cyberduck.io/dists/stable/Release: No system certificates available. Try installing ca-certificates.
E: The repository 'https://s3.amazonaws.com/repo.deb.cyberduck.io stable Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Change History (6)

comment:1 Changed on Aug 30, 2018 at 5:35:21 PM by patakijv

  • Description modified (diff)

comment:2 Changed on Aug 30, 2018 at 5:39:13 PM by patakijv

  • Description modified (diff)

comment:3 Changed on Aug 30, 2018 at 6:40:04 PM by dkocher

I cannot reproduce this on Linux ubuntu 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux.

comment:4 follow-up: Changed on Aug 30, 2018 at 8:14:14 PM by patakijv

  • Description modified (diff)

Apparently since this was a bare bones server setup it needed that ca-certificate setup first.

Adding the following to my setup resolved the issue:

apt-get install -y ca-certificates

FWIW,

There were also some other dependencies required that are not already installed in a fresh install. (sudo, gnupg)

So my full commands from a fresh install of Ubuntu 18.04 are now:

export DEBIAN_FRONTEND=noninteractive 
apt-get -y update && apt-get install -y sudo apt-utils gnupg ca-certificates
echo deb https://s3.amazonaws.com/repo.deb.cyberduck.io stable main >> /etc/apt/sources.list.d/cyberduck.list
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys FE7097963FEFBE72
apt-get -y update
apt-get -y install duck

In case it is useful, I also found that if ca-certificates was already installed and this problem existed, you can do a clear and reinstall of ca-certificates: https://stackoverflow.com/a/29319873

comment:5 Changed on Aug 30, 2018 at 8:24:46 PM by patakijv

  • Resolution set to fixed
  • Status changed from new to closed

comment:6 in reply to: ↑ 4 Changed on Aug 31, 2018 at 6:28:39 AM by dkocher

Replying to patakijv:

Apparently since this was a bare bones server setup it needed that ca-certificate setup first.

Thank you for providing the exact steps to resolve this.

Note: See TracTickets for help on using tickets.
swiss made software