Unable to update Expedition "expedition-updates/ Release' does not have a Release file"

Announcements

ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.

Reply
Highlighted
L1 Bithead

Unable to update Expedition "expedition-updates/ Release' does not have a Release file"

Currently have expedition 1.1.46.1 installed and running.

on "sudo apt-get update" I receive the message below.

 

W: The repository 'https://conversionupdates.paloaltonetworks.com expedition-updates/ Release' does not have a Release file.

N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.

 

I was unable to find any previous threads concerning this issue.


Accepted Solutions
Highlighted
L1 Bithead

Editing the repo list at /etc/apt/sources.list.d/ex-repo.list to include

deb [trusted=yes] https://conversionupdates.paloaltonetworks.com/ expedition-updates/

 

Prevents the warnings from appearing in the future.

 

View solution in original post


All Replies
Highlighted
L5 Sessionator

This is a normal message due to the settings of our repository.

 

Continue ahead installing the updates.

Highlighted
L1 Bithead

This is not a solution. I have concerns on running Palo Alto software in my network considering the "push ahead" attitude when confronted with security concerns. Why has this software not been signed? Is it current PA policy to produce applications for enterprise use with such lenient security?

Highlighted
L5 Sessionator

Hi,

 

We understand your concerns. This is not a product, but a tool offered for free to use and download, and not strictly required to run Palo Alto Networks products.

While we do not have the repository signed, the deb packages themselves are actually signed.

We have plans to provide certified repository listing as well, but it is not yet deployed and we have certain points with higher priority we want to get covered first.

Highlighted
L1 Bithead

Editing the repo list at /etc/apt/sources.list.d/ex-repo.list to include

deb [trusted=yes] https://conversionupdates.paloaltonetworks.com/ expedition-updates/

 

Prevents the warnings from appearing in the future.

 

View solution in original post

Highlighted
L0 Member

Still an issue nine months (really years) later, though the work-around (not a solution) let's it continue, this violates most corporate policies of using signed repositories for updates. This has been requested for years, any chance we'll ever get the repo signed?

Tags (1)
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!