Starting with Version 7.7 the downloadable Package is still named *.deb, in fact it is a tar.gz containing the following:
Which means, you cannot just install the so-called "deb package", but you have to create a directory, copy a file and then you are able to install the deb file...
Was working properly before.
PLEASE FIX THIS!
Hi @RonaldWeiss I checked internally - please note that this is a desired behavior.
To better secure your Cortex XDR agent installations on Linux machines, installation packages are now signed by Palo Alto Networks. The installation package contains a new configuration file which includes the tenant ID and registration key. When installing the agent installation package, if signature-checking is configured, you will need to install a Cortex XDR public key.
Yeah, i have read that, too. BUT:
In that guide it says:
Ubuntu or Debian apt-get install ./filename.deb or dpkg -i ./filename.deb
But that doesn't work because the package provided is NOT a deb package, but a tar.gz with the wrong file extension!
2022_05_30_Cortex_XDR_Linux_7_7_1_62043.deb: gzip compressed data, was "traps_linux-184.108.40.206152_deb.tar", last modified: Mon May 30 08:29:27 2022, max compression, original size 55715840
Why not just include the tennant ID and reg-key into the deb package?
btw: i could do that myself, but thats not my job...
this might work. But if there is a deb package provided, it should work as expected, and not unveil as a renamed tar.gz.
When you follow the part "To deploy using package manager" on your screenshot, this simply doesnt work.
AND: the deb was working since 7.6!
i AM able to install a tar.gz, but there is the fact that the deb installer is not working as expected.
So i think someone messed something up. The Intention of the post is to inform about the failing installer.
PA should either change the manual below "To deploy using package manager" (add "unpack the *.deb using tar -xfz, and copy the config file"), and get the laughts of every linux-admin,
or just fix the creation of the deb file.
Hi @RonaldWeiss I was able to follow the steps in sequence to extract the contents of the tarball. The tarball contained a .deb file, which I installed with dpkg -i ./cortex-220.127.116.11152.deb.
What you're referring to in your last post is a recommendation, and not a break-fix. I will let the documentation team know about your recommendation.
Have a good day ahead!
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 LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!