One Hat Cyber Team
Your IP :
216.73.216.115
Server IP :
194.44.31.54
Server :
Linux zen.imath.kiev.ua 4.18.0-553.77.1.el8_10.x86_64 #1 SMP Fri Oct 3 14:30:23 UTC 2025 x86_64
Server Software :
Apache/2.4.37 (Rocky Linux) OpenSSL/1.1.1k
PHP Version :
5.6.40
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
usr
/
share
/
doc
/
qemu-kvm
/
system
/
View File Name :
authz.html
<!DOCTYPE html> <!--[if IE 8]><html class="no-js lt-ie9" lang="en" > <![endif]--> <!--[if gt IE 8]><!--> <html class="no-js" lang="en" > <!--<![endif]--> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>Client authorization — QEMU qemu-kvm-6.2.0-53.module+el8.10.0+2055+8eb7870b.4 documentation</title> <link rel="shortcut icon" href="../_static/qemu_32x32.png"/> <link rel="stylesheet" href="../_static/css/theme.css" type="text/css" /> <link rel="stylesheet" href="../_static/pygments.css" type="text/css" /> <link rel="index" title="Index" href="../genindex.html" /> <link rel="search" title="Search" href="../search.html" /> <link rel="next" title="GDB usage" href="gdb.html" /> <link rel="prev" title="Providing secret data to QEMU" href="secrets.html" /> <script src="../_static/js/modernizr.min.js"></script> </head> <body class="wy-body-for-nav"> <div class="wy-grid-for-nav"> <nav data-toggle="wy-nav-shift" class="wy-nav-side"> <div class="wy-side-scroll"> <div class="wy-side-nav-search"> <a href="../index.html" class="icon icon-home"> QEMU <img src="../_static/qemu_128x128.png" class="logo" alt="Logo"/> </a> <div class="version"> 6.2.0 </div> <div role="search"> <form id="rtd-search-form" class="wy-form" action="../search.html" method="get"> <input type="text" name="q" placeholder="Search docs" /> <input type="hidden" name="check_keywords" value="yes" /> <input type="hidden" name="area" value="default" /> </form> </div> </div> <div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation"> <p class="caption"><span class="caption-text">Contents:</span></p> <ul class="current"> <li class="toctree-l1"><a class="reference internal" href="../about/index.html">About QEMU</a></li> <li class="toctree-l1 current"><a class="reference internal" href="index.html">System Emulation</a><ul class="current"> <li class="toctree-l2"><a class="reference internal" href="quickstart.html">Quick Start</a></li> <li class="toctree-l2"><a class="reference internal" href="invocation.html">Invocation</a></li> <li class="toctree-l2"><a class="reference internal" href="device-emulation.html">Device Emulation</a></li> <li class="toctree-l2"><a class="reference internal" href="keys.html">Keys in the graphical frontends</a></li> <li class="toctree-l2"><a class="reference internal" href="mux-chardev.html">Keys in the character backend multiplexer</a></li> <li class="toctree-l2"><a class="reference internal" href="monitor.html">QEMU Monitor</a></li> <li class="toctree-l2"><a class="reference internal" href="images.html">Disk Images</a></li> <li class="toctree-l2"><a class="reference internal" href="virtio-net-failover.html">QEMU virtio-net standby (net_failover)</a></li> <li class="toctree-l2"><a class="reference internal" href="linuxboot.html">Direct Linux Boot</a></li> <li class="toctree-l2"><a class="reference internal" href="generic-loader.html">Generic Loader</a></li> <li class="toctree-l2"><a class="reference internal" href="guest-loader.html">Guest Loader</a></li> <li class="toctree-l2"><a class="reference internal" href="barrier.html">QEMU Barrier Client</a></li> <li class="toctree-l2"><a class="reference internal" href="vnc-security.html">VNC security</a></li> <li class="toctree-l2"><a class="reference internal" href="tls.html">TLS setup for network services</a></li> <li class="toctree-l2"><a class="reference internal" href="secrets.html">Providing secret data to QEMU</a></li> <li class="toctree-l2 current"><a class="current reference internal" href="#">Client authorization</a><ul> <li class="toctree-l3"><a class="reference internal" href="#identity-providers">Identity providers</a></li> <li class="toctree-l3"><a class="reference internal" href="#authorization-drivers">Authorization drivers</a><ul> <li class="toctree-l4"><a class="reference internal" href="#simple">Simple</a></li> <li class="toctree-l4"><a class="reference internal" href="#list">List</a></li> <li class="toctree-l4"><a class="reference internal" href="#list-file">List file</a></li> <li class="toctree-l4"><a class="reference internal" href="#pam">PAM</a></li> </ul> </li> <li class="toctree-l3"><a class="reference internal" href="#connecting-backends">Connecting backends</a></li> </ul> </li> <li class="toctree-l2"><a class="reference internal" href="gdb.html">GDB usage</a></li> <li class="toctree-l2"><a class="reference internal" href="managed-startup.html">Managed start up options</a></li> <li class="toctree-l2"><a class="reference internal" href="bootindex.html">Managing device boot order with bootindex properties</a></li> <li class="toctree-l2"><a class="reference internal" href="cpu-hotplug.html">Virtual CPU hotplug</a></li> <li class="toctree-l2"><a class="reference internal" href="pr-manager.html">Persistent reservation managers</a></li> <li class="toctree-l2"><a class="reference internal" href="targets.html">QEMU System Emulator Targets</a></li> <li class="toctree-l2"><a class="reference internal" href="security.html">Security</a></li> <li class="toctree-l2"><a class="reference internal" href="multi-process.html">Multi-process QEMU</a></li> </ul> </li> <li class="toctree-l1"><a class="reference internal" href="../user/index.html">User Mode Emulation</a></li> <li class="toctree-l1"><a class="reference internal" href="../tools/index.html">Tools</a></li> <li class="toctree-l1"><a class="reference internal" href="../interop/index.html">System Emulation Management and Interoperability</a></li> <li class="toctree-l1"><a class="reference internal" href="../specs/index.html">System Emulation Guest Hardware Specifications</a></li> <li class="toctree-l1"><a class="reference internal" href="../devel/index.html">Developer Information</a></li> </ul> </div> </div> </nav> <section data-toggle="wy-nav-shift" class="wy-nav-content-wrap"> <nav class="wy-nav-top" aria-label="top navigation"> <i data-toggle="wy-nav-top" class="fa fa-bars"></i> <a href="../index.html">QEMU</a> </nav> <div class="wy-nav-content"> <div class="rst-content"> <div role="navigation" aria-label="breadcrumbs navigation"> <ul class="wy-breadcrumbs"> <li><a href="../index.html">Docs</a> »</li> <li><a href="index.html">System Emulation</a> »</li> <li>Client authorization</li> <li class="wy-breadcrumbs-aside"> <a href="https://gitlab.com/qemu-project/qemu/blob/master/docs/system/authz.rst" class="fa fa-gitlab"> Edit on GitLab</a> </li> </ul> <hr/> </div> <div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article"> <div itemprop="articleBody"> <div class="section" id="client-authorization"> <span id="id1"></span><h1>Client authorization<a class="headerlink" href="#client-authorization" title="Permalink to this headline">¶</a></h1> <p>When configuring a QEMU network backend with either TLS certificates or SASL authentication, access will be granted if the client successfully proves their identity. If the authorization identity database is scoped to the QEMU client this may be sufficient. It is common, however, for the identity database to be much broader and thus authentication alone does not enable sufficient access control. In this case QEMU provides a flexible system for enforcing finer grained authorization on clients post-authentication.</p> <div class="section" id="identity-providers"> <h2>Identity providers<a class="headerlink" href="#identity-providers" title="Permalink to this headline">¶</a></h2> <p>At the time of writing there are two authentication frameworks used by QEMU that emit an identity upon completion.</p> <blockquote> <div><ul> <li><p class="first">TLS x509 certificate distinguished name.</p> <p>When configuring the QEMU backend as a network server with TLS, there are a choice of credentials to use. The most common scenario is to utilize x509 certificates. The simplest configuration only involves issuing certificates to the servers, allowing the client to avoid a MITM attack against their intended server.</p> <p>It is possible, however, to enable mutual verification by requiring that the client provide a certificate to the server to prove its own identity. This is done by setting the property <code class="docutils literal notranslate"><span class="pre">verify-peer=yes</span></code> on the <code class="docutils literal notranslate"><span class="pre">tls-creds-x509</span></code> object, which is in fact the default.</p> <p>When peer verification is enabled, client will need to be issued with a certificate by the same certificate authority as the server. If this is still not sufficiently strong access control the Distinguished Name of the certificate can be used as an identity in the QEMU authorization framework.</p> </li> <li><p class="first">SASL username.</p> <p>When configuring the QEMU backend as a network server with SASL, upon completion of the SASL authentication mechanism, a username will be provided. The format of this username will vary depending on the choice of mechanism configured for SASL. It might be a simple UNIX style user <code class="docutils literal notranslate"><span class="pre">joebloggs</span></code>, while if using Kerberos/GSSAPI it can have a realm attached <code class="docutils literal notranslate"><span class="pre">joebloggs@QEMU.ORG</span></code>. Whatever format the username is presented in, it can be used with the QEMU authorization framework.</p> </li> </ul> </div></blockquote> </div> <div class="section" id="authorization-drivers"> <h2>Authorization drivers<a class="headerlink" href="#authorization-drivers" title="Permalink to this headline">¶</a></h2> <p>The QEMU authorization framework is a general purpose design with choice of user customizable drivers. These are provided as objects that can be created at startup using the <code class="docutils literal notranslate"><span class="pre">-object</span></code> argument, or at runtime using the <code class="docutils literal notranslate"><span class="pre">object_add</span></code> monitor command.</p> <div class="section" id="simple"> <h3>Simple<a class="headerlink" href="#simple" title="Permalink to this headline">¶</a></h3> <p>This authorization driver provides a simple mechanism for granting access based on an exact match against a single identity. This is useful when it is known that only a single client is to be allowed access.</p> <p>A possible use case would be when configuring QEMU for an incoming live migration. It is known exactly which source QEMU the migration is expected to arrive from. The x509 certificate associated with this source QEMU would thus be used as the identity to match against. Alternatively if the virtual machine is dedicated to a specific tenant, then the VNC server would be configured with SASL and the username of only that tenant listed.</p> <p>To create an instance of this driver via QMP:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">{</span> <span class="s2">"execute"</span><span class="p">:</span> <span class="s2">"object-add"</span><span class="p">,</span> <span class="s2">"arguments"</span><span class="p">:</span> <span class="p">{</span> <span class="s2">"qom-type"</span><span class="p">:</span> <span class="s2">"authz-simple"</span><span class="p">,</span> <span class="s2">"id"</span><span class="p">:</span> <span class="s2">"authz0"</span><span class="p">,</span> <span class="s2">"identity"</span><span class="p">:</span> <span class="s2">"fred"</span> <span class="p">}</span> <span class="p">}</span> </pre></div> </div> <p>Or via the command line</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="o">-</span><span class="nb">object</span> <span class="n">authz</span><span class="o">-</span><span class="n">simple</span><span class="p">,</span><span class="nb">id</span><span class="o">=</span><span class="n">authz0</span><span class="p">,</span><span class="n">identity</span><span class="o">=</span><span class="n">fred</span> </pre></div> </div> </div> <div class="section" id="list"> <h3>List<a class="headerlink" href="#list" title="Permalink to this headline">¶</a></h3> <p>In some network backends it will be desirable to grant access to a range of clients. This authorization driver provides a list mechanism for granting access by matching identities against a list of permitted one. Each match rule has an associated policy and a catch all policy applies if no rule matches. The match can either be done as an exact string comparison, or can use the shell-like glob syntax, which allows for use of wildcards.</p> <p>To create an instance of this class via QMP:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">{</span> <span class="s2">"execute"</span><span class="p">:</span> <span class="s2">"object-add"</span><span class="p">,</span> <span class="s2">"arguments"</span><span class="p">:</span> <span class="p">{</span> <span class="s2">"qom-type"</span><span class="p">:</span> <span class="s2">"authz-list"</span><span class="p">,</span> <span class="s2">"id"</span><span class="p">:</span> <span class="s2">"authz0"</span><span class="p">,</span> <span class="s2">"rules"</span><span class="p">:</span> <span class="p">[</span> <span class="p">{</span> <span class="s2">"match"</span><span class="p">:</span> <span class="s2">"fred"</span><span class="p">,</span> <span class="s2">"policy"</span><span class="p">:</span> <span class="s2">"allow"</span><span class="p">,</span> <span class="s2">"format"</span><span class="p">:</span> <span class="s2">"exact"</span> <span class="p">},</span> <span class="p">{</span> <span class="s2">"match"</span><span class="p">:</span> <span class="s2">"bob"</span><span class="p">,</span> <span class="s2">"policy"</span><span class="p">:</span> <span class="s2">"allow"</span><span class="p">,</span> <span class="s2">"format"</span><span class="p">:</span> <span class="s2">"exact"</span> <span class="p">},</span> <span class="p">{</span> <span class="s2">"match"</span><span class="p">:</span> <span class="s2">"danb"</span><span class="p">,</span> <span class="s2">"policy"</span><span class="p">:</span> <span class="s2">"deny"</span><span class="p">,</span> <span class="s2">"format"</span><span class="p">:</span> <span class="s2">"exact"</span> <span class="p">},</span> <span class="p">{</span> <span class="s2">"match"</span><span class="p">:</span> <span class="s2">"dan*"</span><span class="p">,</span> <span class="s2">"policy"</span><span class="p">:</span> <span class="s2">"allow"</span><span class="p">,</span> <span class="s2">"format"</span><span class="p">:</span> <span class="s2">"glob"</span> <span class="p">}</span> <span class="p">],</span> <span class="s2">"policy"</span><span class="p">:</span> <span class="s2">"deny"</span> <span class="p">}</span> <span class="p">}</span> </pre></div> </div> <p>Due to the way this driver requires setting nested properties, creating it on the command line will require use of the JSON syntax for <code class="docutils literal notranslate"><span class="pre">-object</span></code>. In most cases, however, the next driver will be more suitable.</p> </div> <div class="section" id="list-file"> <h3>List file<a class="headerlink" href="#list-file" title="Permalink to this headline">¶</a></h3> <p>This is a variant on the previous driver that allows for a more dynamic access control policy by storing the match rules in a standalone file that can be reloaded automatically upon change.</p> <p>To create an instance of this class via QMP:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">{</span> <span class="s2">"execute"</span><span class="p">:</span> <span class="s2">"object-add"</span><span class="p">,</span> <span class="s2">"arguments"</span><span class="p">:</span> <span class="p">{</span> <span class="s2">"qom-type"</span><span class="p">:</span> <span class="s2">"authz-list-file"</span><span class="p">,</span> <span class="s2">"id"</span><span class="p">:</span> <span class="s2">"authz0"</span><span class="p">,</span> <span class="s2">"filename"</span><span class="p">:</span> <span class="s2">"/etc/qemu/myvm-vnc.acl"</span><span class="p">,</span> <span class="s2">"refresh"</span><span class="p">:</span> <span class="n">true</span> <span class="p">}</span> <span class="p">}</span> </pre></div> </div> <p>If <code class="docutils literal notranslate"><span class="pre">refresh</span></code> is <code class="docutils literal notranslate"><span class="pre">yes</span></code>, inotify is used to monitor for changes to the file and auto-reload the rules.</p> <p>The <code class="docutils literal notranslate"><span class="pre">myvm-vnc.acl</span></code> file should contain the match rules in a format that closely matches the previous driver:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">{</span> <span class="s2">"rules"</span><span class="p">:</span> <span class="p">[</span> <span class="p">{</span> <span class="s2">"match"</span><span class="p">:</span> <span class="s2">"fred"</span><span class="p">,</span> <span class="s2">"policy"</span><span class="p">:</span> <span class="s2">"allow"</span><span class="p">,</span> <span class="s2">"format"</span><span class="p">:</span> <span class="s2">"exact"</span> <span class="p">},</span> <span class="p">{</span> <span class="s2">"match"</span><span class="p">:</span> <span class="s2">"bob"</span><span class="p">,</span> <span class="s2">"policy"</span><span class="p">:</span> <span class="s2">"allow"</span><span class="p">,</span> <span class="s2">"format"</span><span class="p">:</span> <span class="s2">"exact"</span> <span class="p">},</span> <span class="p">{</span> <span class="s2">"match"</span><span class="p">:</span> <span class="s2">"danb"</span><span class="p">,</span> <span class="s2">"policy"</span><span class="p">:</span> <span class="s2">"deny"</span><span class="p">,</span> <span class="s2">"format"</span><span class="p">:</span> <span class="s2">"exact"</span> <span class="p">},</span> <span class="p">{</span> <span class="s2">"match"</span><span class="p">:</span> <span class="s2">"dan*"</span><span class="p">,</span> <span class="s2">"policy"</span><span class="p">:</span> <span class="s2">"allow"</span><span class="p">,</span> <span class="s2">"format"</span><span class="p">:</span> <span class="s2">"glob"</span> <span class="p">}</span> <span class="p">],</span> <span class="s2">"policy"</span><span class="p">:</span> <span class="s2">"deny"</span> <span class="p">}</span> </pre></div> </div> <p>The object can be created on the command line using</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="o">-</span><span class="nb">object</span> <span class="n">authz</span><span class="o">-</span><span class="nb">list</span><span class="o">-</span><span class="n">file</span><span class="p">,</span><span class="nb">id</span><span class="o">=</span><span class="n">authz0</span><span class="p">,</span>\ <span class="n">filename</span><span class="o">=/</span><span class="n">etc</span><span class="o">/</span><span class="n">qemu</span><span class="o">/</span><span class="n">myvm</span><span class="o">-</span><span class="n">vnc</span><span class="o">.</span><span class="n">acl</span><span class="p">,</span><span class="n">refresh</span><span class="o">=</span><span class="n">on</span> </pre></div> </div> </div> <div class="section" id="pam"> <h3>PAM<a class="headerlink" href="#pam" title="Permalink to this headline">¶</a></h3> <p>In some scenarios it might be desirable to integrate with authorization mechanisms that are implemented outside of QEMU. In order to allow maximum flexibility, QEMU provides a driver that uses the <code class="docutils literal notranslate"><span class="pre">PAM</span></code> framework.</p> <p>To create an instance of this class via QMP:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">{</span> <span class="s2">"execute"</span><span class="p">:</span> <span class="s2">"object-add"</span><span class="p">,</span> <span class="s2">"arguments"</span><span class="p">:</span> <span class="p">{</span> <span class="s2">"qom-type"</span><span class="p">:</span> <span class="s2">"authz-pam"</span><span class="p">,</span> <span class="s2">"id"</span><span class="p">:</span> <span class="s2">"authz0"</span><span class="p">,</span> <span class="s2">"parameters"</span><span class="p">:</span> <span class="p">{</span> <span class="s2">"service"</span><span class="p">:</span> <span class="s2">"qemu-vnc-tls"</span> <span class="p">}</span> <span class="p">}</span> <span class="p">}</span> </pre></div> </div> <p>The driver only uses the PAM “account” verification subsystem. The above config would require a config file /etc/pam.d/qemu-vnc-tls. For a simple file lookup it would contain</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">account</span> <span class="n">requisite</span> <span class="n">pam_listfile</span><span class="o">.</span><span class="n">so</span> <span class="n">item</span><span class="o">=</span><span class="n">user</span> <span class="n">sense</span><span class="o">=</span><span class="n">allow</span> \ <span class="n">file</span><span class="o">=/</span><span class="n">etc</span><span class="o">/</span><span class="n">qemu</span><span class="o">/</span><span class="n">vnc</span><span class="o">.</span><span class="n">allow</span> </pre></div> </div> <p>The external file would then contain a list of usernames. If x509 cert was being used as the username, a suitable entry would match the distinguished name:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">CN</span><span class="o">=</span><span class="n">laptop</span><span class="o">.</span><span class="n">berrange</span><span class="o">.</span><span class="n">com</span><span class="p">,</span><span class="n">O</span><span class="o">=</span><span class="n">Berrange</span> <span class="n">Home</span><span class="p">,</span><span class="n">L</span><span class="o">=</span><span class="n">London</span><span class="p">,</span><span class="n">ST</span><span class="o">=</span><span class="n">London</span><span class="p">,</span><span class="n">C</span><span class="o">=</span><span class="n">GB</span> </pre></div> </div> <p>On the command line it can be created using</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="o">-</span><span class="nb">object</span> <span class="n">authz</span><span class="o">-</span><span class="n">pam</span><span class="p">,</span><span class="nb">id</span><span class="o">=</span><span class="n">authz0</span><span class="p">,</span><span class="n">service</span><span class="o">=</span><span class="n">qemu</span><span class="o">-</span><span class="n">vnc</span><span class="o">-</span><span class="n">tls</span> </pre></div> </div> <p>There are a variety of PAM plugins that can be used which are not illustrated here, and it is possible to implement brand new plugins using the PAM API.</p> </div> </div> <div class="section" id="connecting-backends"> <h2>Connecting backends<a class="headerlink" href="#connecting-backends" title="Permalink to this headline">¶</a></h2> <p>The authorization driver is created using the <code class="docutils literal notranslate"><span class="pre">-object</span></code> argument and then needs to be associated with a network service. The authorization driver object will be given a unique ID that needs to be referenced.</p> <p>The property to set in the network service will vary depending on the type of identity to verify. By convention, any network server backend that uses TLS will provide <code class="docutils literal notranslate"><span class="pre">tls-authz</span></code> property, while any server using SASL will provide a <code class="docutils literal notranslate"><span class="pre">sasl-authz</span></code> property.</p> <p>Thus an example using SASL and authorization for the VNC server would look like:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$QEMU --object authz-simple,id=authz0,identity=fred \ --vnc 0.0.0.0:1,sasl,sasl-authz=authz0 </pre></div> </div> <p>While to validate both the x509 certificate and SASL username:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span>echo "CN=laptop.qemu.org,O=QEMU Project,L=London,ST=London,C=GB" >> tls.acl $QEMU --object authz-simple,id=authz0,identity=fred \ --object authz-list-file,id=authz1,filename=tls.acl \ --object tls-creds-x509,id=tls0,dir=/etc/qemu/tls,verify-peer=yes \ --vnc 0.0.0.0:1,sasl,sasl-authz=auth0,tls-creds=tls0,tls-authz=authz1 </pre></div> </div> </div> </div> </div> </div> <footer> <div class="rst-footer-buttons" role="navigation" aria-label="footer navigation"> <a href="gdb.html" class="btn btn-neutral float-right" title="GDB usage" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right"></span></a> <a href="secrets.html" class="btn btn-neutral" title="Providing secret data to QEMU" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left"></span> Previous</a> </div> <hr/> <div role="contentinfo"> <p> © Copyright 2021, The QEMU Project Developers. </p> </div> Built with <a href="http://sphinx-doc.org/">Sphinx</a> using a <a href="https://github.com/rtfd/sphinx_rtd_theme">theme</a> provided by <a href="https://readthedocs.org">Read the Docs</a>. <!-- Empty para to force a blank line after "Built with Sphinx ..." --> <p></p> <p>This documentation is for QEMU version 6.2.0.</p> <p><a href="../about/license.html">QEMU and this manual are released under the GNU General Public License, version 2.</a></p> </footer> </div> </div> </section> </div> <script type="text/javascript"> var DOCUMENTATION_OPTIONS = { URL_ROOT:'../', VERSION:'qemu-kvm-6.2.0-53.module+el8.10.0+2055+8eb7870b.4', LANGUAGE:'None', COLLAPSE_INDEX:false, FILE_SUFFIX:'.html', HAS_SOURCE: false, SOURCELINK_SUFFIX: '.txt' }; </script> <script type="text/javascript" src="../_static/jquery.js"></script> <script type="text/javascript" src="../_static/underscore.js"></script> <script type="text/javascript" src="../_static/doctools.js"></script> <script type="text/javascript" src="../_static/js/theme.js"></script> <script type="text/javascript"> jQuery(function () { SphinxRtdTheme.Navigation.enable(true); }); </script> </body> </html>