Repository: cloudfoundry/cli

Issue #3194: Certificate has expired
Created: 2024-09-11T07:36:55Z
Please fill out the issue checklist below and provide ALL the requested information.

  I reviewed open and closed github issues that may be related to my problem.
  I tried updating to the latest version of the CF CLI to see if it fixed my problem.
  I attempted to run the command with CF_TRACE=1 to help debug the issue.
  I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
Like every year, the certificate has expired.
Also see:
#2046
#2571
What happened
While installing the CLI from debian repo this  issue occurs.
W: GPG error:
https://cf-cli-debian-repo.s3.amazonaws.com/
stable InRelease: The following signatures were invalid: EXPKEYSIG 172B5989FCD21EF8 CF CLI Team
[cf-cli-eng@pivotal.io](mailto:cf-cli-eng@pivotal.io)
E: The repository '
https://cf-cli-debian-repo.s3.amazonaws.com/
stable InRelease' is not signed.
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.

Expected behavior

make a note in your calender and refresh the certificate BEFORE it has expired
alternative: use a certificate which lasts longer but still set a reminder in your calender

Exact Steps To Reproduce
See above.
Provide more context
CF cli 8.X
Debian Version 12.6

Duplicate issue #3198: The repository 'https://packages.cloudfoundry.org/debian stable InRelease' is not signed.
Created: 2024-09-11T12:50:43Z
Please fill out the issue checklist below and provide ALL the requested information.

 I reviewed open and closed github issues that may be related to my problem.
 I tried updating to the latest version of the CF CLI to see if it fixed my problem.
 I attempted to run the command with CF_TRACE=1 to help debug the issue.
 I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
Provide details on what you were trying to do (and why).
What happened
cf install-plugin multiapps -f -> failed due to package error
Expected behavior
cf command used to run until last week using same commands.
Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:

Run get -v -O- https://packages.cloudfoundry.org/debian/cli.cloudfoundry.org.key | gpg --dearmor | sudo tee /etc/apt/keyrings/cloudfoundry.gpg > /dev/null ls /dev/null echo "deb [signed-by=/etc/apt/keyrings/cloudfoundry.gpg] https://packages.cloudfoundry.org/debian stable main" | sudo tee /etc/apt/sources.list.d/cloudfoundry.list cat /etc/apt/sources.list.d/cloudfoundry.list sudo apt-get update sudo apt-get install cf-cli cf install-plugin multiapps -f
See error below:
Err:12 https://cf-cli-debian-repo.s3.amazonaws.com stable InRelease
The following signatures were invalid: EXPKEYSIG 172B5989FCD21EF8 CF CLI Team cf-cli-eng@pivotal.io
Reading package lists...
W: GPG error: https://cf-cli-debian-repo.s3.amazonaws.com stable InRelease: The following signatures were invalid: EXPKEYSIG 172B5989FCD21EF8 CF CLI Team cf-cli-eng@pivotal.io
E: The repository 'https://packages.cloudfoundry.org/debian stable InRelease' is not signed.

Provide more context

platform and shell details : ubuntu-latest
version of the CLI you are running: latest
version of the CC API Release you are on

Notes regarding V6 and V7 CLI support:

V6:

Minimum supported version of CF Deployment: v7.0.0 (CAPI Release: 1.74.0 (APIs 2.128.0 and 3.63.0))
Maximum supported version of CF Deployment: v13.4.0 (CAPI Release: 1.94.0 (APIs 2.149.0 and 3.84.0))


V7:

Minimum supported version of CF Deployment: v13.5.0 (CAPI Release: 1.95.0 (APIs 2.150.0 and 3.85.0))

Closing comment (2024-09-11T18:54:22Z): This is a duplicate of #3194 which was fixed a short time ago