We’re planning to decommission the old apt package server at apt.opscode.com on Wednesday this week between 3-4 p.m. Eastern.
This server contains really, really old versions of Chef that are no
longer maintained (10.18 and older). The recommended mechanism to
install Chef these days is via the self-contained full-stack
installer:
We're planning to decommission the old apt package server at apt.opscode.com on Wednesday this week between 3-4 p.m. Eastern.
This server contains really, really old versions of Chef that are no
longer maintained (10.18 and older). The recommended mechanism to
install Chef these days is via the self-contained full-stack
installer:
We are hosting chef-client and chef-server RPMs internally in our
repositories and we would like to download the RPM GPG key used to
sign the packages. It used to be available at http://apt.opscode.com/packages@opscode.com.gpg.key
We're planning to decommission the old apt package server at apt.opscode.com on Wednesday this week between 3-4 p.m. Eastern.
This server contains really, really old versions of Chef that are no
longer maintained (10.18 and older). The recommended mechanism to
install Chef these days is via the self-contained full-stack
installer:
We are hosting chef-client and chef-server RPMs internally in our
repositories and we would like to download the RPM GPG key used to
sign the packages. It used to be available at http://apt.opscode.com/packages@opscode.com.gpg.key
We are hosting chef-client and chef-server RPMs internally in our
repositories and we would like to download the RPM GPG key used to
sign the packages. It used to be available at http://apt.opscode.com/packages@opscode.com.gpg.key
We are hosting chef-client and chef-server RPMs internally in our
repositories and we would like to download the RPM GPG key used to
sign the packages. It used to be available at http://apt.opscode.com/packages@opscode.com.gpg.key
Just wanted to drop a note mentioning that I'm looking into this.
There is a key available here: https://downloads.chef.io/packages-chef-io-public.key but it is
different from the previous chef.gpg.key. I will follow up with our
release engineering team once they get online and get some
clarification on the situation.
We are hosting chef-client and chef-server RPMs internally in our
repositories and we would like to download the RPM GPG key used to
sign the packages. It used to be available at http://apt.opscode.com/packages@opscode.com.gpg.key
A quick follow up. It looks like https://downloads.chef.io/packages-chef-io-public.key is the same as
the old key (same gpg fingerprint) but the file is just in a slightly
different format and has a different uid. I also confirmed that this
key can be used to validate the most recent chef packages as well as
older chef packages. I'll still follow up with the Release Eng. team
to see if we can restore the old URL for those of you who might be
depending on it.
Cheers,
Steven
On Wed, Dec 10, 2014 at 9:55 AM, Steven Danna steve@chef.io wrote:
Hi Jeremy,
Just wanted to drop a note mentioning that I'm looking into this.
There is a key available here: https://downloads.chef.io/packages-chef-io-public.key but it is
different from the previous chef.gpg.key. I will follow up with our
release engineering team once they get online and get some
clarification on the situation.
We are hosting chef-client and chef-server RPMs internally in our
repositories and we would like to download the RPM GPG key used to
sign the packages. It used to be available at http://apt.opscode.com/packages@opscode.com.gpg.key
A redirect is now in place for the old url. Thanks for bringing this
to our attention!
Cheers,
Steven
On Wed, Dec 10, 2014 at 10:22 AM, Steven Danna steve@chef.io wrote:
Hi,
A quick follow up. It looks like https://downloads.chef.io/packages-chef-io-public.key is the same as
the old key (same gpg fingerprint) but the file is just in a slightly
different format and has a different uid. I also confirmed that this
key can be used to validate the most recent chef packages as well as
older chef packages. I'll still follow up with the Release Eng. team
to see if we can restore the old URL for those of you who might be
depending on it.
Cheers,
Steven
On Wed, Dec 10, 2014 at 9:55 AM, Steven Danna steve@chef.io wrote:
Hi Jeremy,
Just wanted to drop a note mentioning that I'm looking into this.
There is a key available here: https://downloads.chef.io/packages-chef-io-public.key but it is
different from the previous chef.gpg.key. I will follow up with our
release engineering team once they get online and get some
clarification on the situation.
We are hosting chef-client and chef-server RPMs internally in our
repositories and we would like to download the RPM GPG key used to
sign the packages. It used to be available at http://apt.opscode.com/packages@opscode.com.gpg.key