109 lines
5.3 KiB
HTML
109 lines
5.3 KiB
HTML
<table class="table colsep rowsep table-striped">
|
|
<colgroup><col style="width: 33.003300330033%"><col style="width: 66.996699669967%"></colgroup>
|
|
<thead class="thead" data-sticky-top="62" style="top: 62px;">
|
|
<tr class="row"><th class="entry">Issue ID</th><th class="entry">Description</th></tr>
|
|
</thead>
|
|
<tbody class="tbody">
|
|
<tr class="row">
|
|
<td class="entry">
|
|
<div class="p">PANG-11201</div>
|
|
<div class="p"><b class="ph b">Resolved in Prisma Access Agent 26.1.1</b></div>
|
|
</td>
|
|
<td class="entry relcol">
|
|
<div class="p">On Prisma Access Agents for Linux, when NetworkManager is
|
|
configured not to manage the tunnel interface, the Prisma Access
|
|
Agent connection profile becomes stuck in an "activating" state,
|
|
resulting in a tunnel connect and disconnect loop that prevents
|
|
successful establishment of the tunnel.</div>
|
|
</td>
|
|
</tr>
|
|
<tr class="row">
|
|
<td class="entry">
|
|
<div class="p">PANG-11153</div>
|
|
<div class="p"><b class="ph b">Resolved in Prisma Access Agent 26.1.1</b></div>
|
|
</td>
|
|
<td class="entry relcol">
|
|
<div class="p">On Linux, the Prisma Access Agent may experience recurring PASrv
|
|
process crashes approximately every 20 seconds due to abnormal
|
|
termination, causing the agent to become unresponsive and
|
|
preventing log collection. This issue occurs primarily during
|
|
agent upgrade operations.</div>
|
|
</td>
|
|
</tr>
|
|
<tr class="row">
|
|
<td class="entry">
|
|
<div class="p">PANG-10947</div>
|
|
</td>
|
|
<td class="entry relcol">
|
|
<div class="p">When Prisma Access Agent is configured in on-demand mode on Arch
|
|
Linux and the network connection is interrupted and then
|
|
restored, the agent fails to automatically reconnect to the
|
|
gateway. As a result, the agent remains in a disconnected
|
|
state.</div>
|
|
</td>
|
|
</tr>
|
|
<tr class="row">
|
|
<td class="entry">
|
|
<div class="p">PANG-10865</div>
|
|
</td>
|
|
<td class="entry relcol">
|
|
<div class="p">On Prisma Access Agent for Linux systems, the Prisma Access Agent
|
|
user interface exhibits minor cosmetic and usability
|
|
inconsistencies. The Location list lacks a line separator
|
|
between entries and is not sorted alphabetically, with the
|
|
exception of the "Best Location" option.</div>
|
|
</td>
|
|
</tr>
|
|
<tr class="row">
|
|
<td class="entry">
|
|
<div class="p">PANG-10801</div>
|
|
</td>
|
|
<td class="entry relcol">
|
|
<div class="p">During a Host Information Profile (HIP) check on Prisma Access
|
|
Agent for Linux, the system incorrectly validates certificates
|
|
based solely on the issuer's Common Name (CN). This results in
|
|
expired or revoked certificates being considered valid if their
|
|
issuer's CN matches the configured criteria, potentially
|
|
allowing non-compliant endpoints to pass HIP checks.</div>
|
|
</td>
|
|
</tr>
|
|
<tr class="row">
|
|
<td class="entry">
|
|
<div class="p">PANG-10668</div>
|
|
</td>
|
|
<td class="entry relcol">
|
|
<div class="p">After upgrading to Prisma Access Agent version 26.1.0.25 on Arch
|
|
Linux with KDE Plasma desktop environments, the settings page in
|
|
the Prisma Access Agent app might appear partially blank when
|
|
the operating system's dark theme is enabled. This prevents the
|
|
display of relevant information on the settings page.</div>
|
|
</td>
|
|
</tr>
|
|
<tr class="row">
|
|
<td class="entry">
|
|
<div class="p">PANG-9501</div>
|
|
</td>
|
|
<td class="entry relcol">
|
|
<div class="p">When using Prisma Access Agent on a system running Fedora 42
|
|
(GNOME), running the <span class="ph userinput">pacli traffic log
|
|
<n></span> command does not show the log
|
|
details.</div>
|
|
</td>
|
|
</tr>
|
|
<tr class="row">
|
|
<td class="entry">
|
|
<div class="p">PANG-9196</div>
|
|
</td>
|
|
<td class="entry relcol">
|
|
<div class="p">When Prisma Access Agent is installed on a Linux virtual machine
|
|
(VM) running on an ESXi host, and the VM undergoes network
|
|
changes (such as connecting or disconnecting from gateways) or
|
|
experiences a sleep/wake cycle, the entire VM and the ESXi host
|
|
might become unresponsive. Access to the ESXi host is lost, and
|
|
the system hangs for approximately 5 minutes before access is
|
|
regained.</div>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|