container-tools:rhel8 security and bug fix update
エラータID: AXSA:2023-7318:02
リリース日:
2023/12/27 Wednesday - 08:05
題名:
container-tools:rhel8 security and bug fix update
影響のあるチャネル:
Asianux Server 8 for x86_64
Severity:
Moderate
Description:
以下項目について対処しました。
[Security Fix]
- Go の yaml モジュールには、大量の CPU リソースおよび
メモリを消費してしまう問題があるため、リモートの攻撃者に
より、巧妙に細工された YAML ドキュメント、または大きな
YAML ドキュメントの解析処理を介して、サービス拒否攻撃
(CPU リソースおよびメモリ枯渇) を可能とする脆弱性が存在
します。(CVE-2022-3064)
- container-tools の HPACK デコーダには、CPU リソース
を消費してしまう問題があるため、リモートの攻撃者により、
細工された HTTP/2 プロトコルによる要求を介して、サービス
拒否攻撃を可能とする脆弱性が存在します。(CVE-2022-41723)
- Go には、TLS ハンドシェイクレコードが大きい場合に応答
を構築しようとするとサーバーとクライアントでそれぞれ
パニックを引き起こす問題があるため、リモートの攻撃者に
より、大きな TLS ハンドシェイクレコードの送信を介して、
サービス拒否 (システムクラッシュ) 状態を引き起こすこと
を可能とする脆弱性が存在します。(CVE-2022-41724)
- Go には、net/http および mime/multipart での過剰な
リソース消費の問題があるため、リモートの攻撃者により、
巧妙なリクエストの送信を介して、サービス拒否攻撃を可能
とする脆弱性が存在します。(CVE-2022-41725)
- Go の HTTP および MIME ヘッダーの解析処理には、必要以上
の大量のメモリを割り当ててしまう問題があるため、リモート
の攻撃者により、細工された HTTP もしくは MIME ヘッダーの
入力を介して、サービス拒否攻撃 (メモリ枯渇) を可能とする
脆弱性が存在します。(CVE-2023-24534)
- Go の mime/multipart モジュールの Reader.ReadForm()
関数には、大量の CPU リソースおよびメモリ量を消費して
しまう問題があるため、リモートの攻撃者により、非常に多く
のパートを含むように細工された Web フォームの処理を介して、
サービス拒否攻撃 (CPU リソースおよびメモリ枯渇) を可能
とする脆弱性が存在します。(CVE-2023-24536)
- Go の Parse() 関数には、整数オーバーフローに起因する
無限ループの問題があるため、リモートの攻撃者により、非常
に大きい行番号が設定された //line ディレクティブの指定を
介して、サービス拒否攻撃を可能とする脆弱性が存在します。
(CVE-2023-24537)
- Go には、HTML テンプレート内のバッククォート文字 "`"
をJavaScript の区切り文字として適切にエスケープしない
問題があるため、リモートの攻撃者により、巧妙に細工された
リクエストの送信を介して、任意のコードの実行を可能とする
脆弱性が存在します。(CVE-2023-24538)
- Go には、"/" 文字で区切られた複数の埋め込み文字を含む
テンプレートの解析時に CSS コンテキストが予期せず閉じられて
しまう問題があるため、リモートの攻撃者により、信頼できない
入力を介して、予期しない HTML タグなどの挿入を可能とする
脆弱性が存在します。(CVE-2023-24539)
- Go には、JavaScript で利用できる空白文字の一部を空白
としてサニタイズ処理しない問題があるため、リモートの攻撃者
により、特定の空白文字を含むように細工されたテンプレートを
介して、意図しない動作を可能とする脆弱性が存在します。
(CVE-2023-24540)
- containerd には、サプリメンタルグループの設定がコンテナ
内に適切に反映されず、プライマリグループによるアクセス制限
を迂回できてしまう問題があるため、ローカルの攻撃者により、
コンテナ内でのサプリメンタルグループの操作を介して、任意
のコードの実行、および情報の漏洩を可能とする脆弱性が存在
します。(CVE-2023-25173)
- runc には、ローカルの攻撃者により、特定の条件下において
コンテナを実行した利用者が所有する /sys/fs/cgroup/user.slice
ディレクトリ配下への書き込みを可能とする脆弱性が存在します。
(CVE-2023-25809)
- runc には、競合状態によりアクセス制御が正しく機能しない
問題があるため、2 つのコンテナイメージの制御が可能なローカル
の攻撃者により、権限の昇格を可能とする脆弱性が存在します。
(CVE-2023-27561)
- runc には、ローカルの攻撃者により、コンテナ内の /proc
ディレクトリが特定の構成でシンボリックリンクされている信頼
できないコンテナイメージを介して、AppArmor によるセキュリティ
保護の迂回を可能とする脆弱性が存在します。(CVE-2023-28642)
- Go には、HTML テンプレートの解析処理時に予期しない結果
が出力されてしまう問題があるため、リモートの攻撃者により、
引用符で囲まれていない HTML 属性を含むテンプレートの解析
を介して、HTML タグへの任意の属性の埋め込みを可能とする
脆弱性が存在します。(CVE-2023-29400)
- Go の HTTP/1 クライアントには、Host ヘッダーの内容の検証
が不十分な問題があるため、リモートの攻撃者により、巧妙に
細工された Host ヘッダーを介して、リクエストの送信時に
ヘッダーやリクエストの追加を可能とする脆弱性が存在します。
(CVE-2023-29406)
- Go の html モジュールには、HTML 名前空間に存在しない
テキストノードをエスケープ処理を行わずに表示してしまう問題
があるため、リモートの攻撃者により、巧妙に細工された URL
を介して、クロスサイトスクリプティング攻撃、および Cookie
に記録された認証情報の漏洩を可能とする脆弱性が存在します。
(CVE-2023-3978)
Modularity name: container-tools
Stream name: rhel8
解決策:
パッケージをアップデートしてください。
CVE:
CVE-2022-3064
Parsing malicious or large YAML documents can consume excessive amounts of CPU or memory.
Parsing malicious or large YAML documents can consume excessive amounts of CPU or memory.
CVE-2022-41723
A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.
A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.
CVE-2022-41724
Large handshake records may cause panics in crypto/tls. Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses. This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).
Large handshake records may cause panics in crypto/tls. Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses. This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).
CVE-2022-41725
A denial of service is possible from excessive resource consumption in net/http and mime/multipart. Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files. With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous. In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct. Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.
A denial of service is possible from excessive resource consumption in net/http and mime/multipart. Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files. With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous. In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct. Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.
CVE-2023-24534
HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service. Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service. With fix, header parsing now correctly allocates only the memory required to hold parsed headers.
HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service. Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service. With fix, header parsing now correctly allocates only the memory required to hold parsed headers.
CVE-2023-24536
Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.
Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.
CVE-2023-24537
Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.
Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.
CVE-2023-24538
Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.
Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.
CVE-2023-24539
Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.
Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.
CVE-2023-24540
Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.
Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.
CVE-2023-25173
containerd is an open source container runtime. A bug was found in containerd prior to versions 1.6.18 and 1.5.18 where supplementary groups are not set up properly inside a container. If an attacker has direct access to a container and manipulates their supplementary group access, they may be able to use supplementary group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive information or gaining the ability to execute code in that container. Downstream applications that use the containerd client library may be affected as well. This bug has been fixed in containerd v1.6.18 and v.1.5.18. Users should update to these versions and recreate containers to resolve this issue. Users who rely on a downstream application that uses containerd's client library should check that application for a separate advisory and instructions. As a workaround, ensure that the `"USER $USERNAME"` Dockerfile instruction is not used. Instead, set the container entrypoint to a value similar to `ENTRYPOINT ["su", "-", "user"]` to allow `su` to properly set up supplementary groups.
containerd is an open source container runtime. A bug was found in containerd prior to versions 1.6.18 and 1.5.18 where supplementary groups are not set up properly inside a container. If an attacker has direct access to a container and manipulates their supplementary group access, they may be able to use supplementary group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive information or gaining the ability to execute code in that container. Downstream applications that use the containerd client library may be affected as well. This bug has been fixed in containerd v1.6.18 and v.1.5.18. Users should update to these versions and recreate containers to resolve this issue. Users who rely on a downstream application that uses containerd's client library should check that application for a separate advisory and instructions. As a workaround, ensure that the `"USER $USERNAME"` Dockerfile instruction is not used. Instead, set the container entrypoint to a value similar to `ENTRYPOINT ["su", "-", "user"]` to allow `su` to properly set up supplementary groups.
CVE-2023-25809
runc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`.
runc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`.
CVE-2023-27561
runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression.
runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression.
CVE-2023-28642
runc is a CLI tool for spawning and running containers according to the OCI specification. It was found that AppArmor can be bypassed when `/proc` inside the container is symlinked with a specific mount configuration. This issue has been fixed in runc version 1.1.5, by prohibiting symlinked `/proc`. See PR #3785 for details. users are advised to upgrade. Users unable to upgrade should avoid using an untrusted container image.
runc is a CLI tool for spawning and running containers according to the OCI specification. It was found that AppArmor can be bypassed when `/proc` inside the container is symlinked with a specific mount configuration. This issue has been fixed in runc version 1.1.5, by prohibiting symlinked `/proc`. See PR #3785 for details. users are advised to upgrade. Users unable to upgrade should avoid using an untrusted container image.
CVE-2023-29400
Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.
Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.
CVE-2023-29406
The HTTP/1 client does not fully validate the contents of the Host header. A maliciously crafted Host header can inject additional headers or entire requests. With fix, the HTTP/1 client now refuses to send requests containing an invalid Request.Host or Request.URL.Host value.
The HTTP/1 client does not fully validate the contents of the Host header. A maliciously crafted Host header can inject additional headers or entire requests. With fix, the HTTP/1 client now refuses to send requests containing an invalid Request.Host or Request.URL.Host value.
CVE-2023-3978
Text nodes not in the HTML namespace are incorrectly literally rendered, causing text which should be escaped to not be. This could lead to an XSS attack.
Text nodes not in the HTML namespace are incorrectly literally rendered, causing text which should be escaped to not be. This could lead to an XSS attack.
追加情報:
N/A
ダウンロード:
SRPMS
- aardvark-dns-1.7.0-1.module+el8+1694+e4eeeb35.src.rpm
MD5: c397260bccb88c286cbaf32efba9c63f
SHA-256: 1cafec4a5e6f6e8c803cf5c142d06d43dceba7eee48aef234872afbe80a8c280
Size: 7.56 MB - buildah-1.31.3-1.module+el8+1694+e4eeeb35.src.rpm
MD5: 6aad51ba7f5f2c3c7661a8faa4e3de60
SHA-256: d197aa63360542f27bd5d28faae5297e6ed64b82545eb5889624d4cbeaf8ba0a
Size: 14.76 MB - cockpit-podman-75-1.module+el8+1694+e4eeeb35.src.rpm
MD5: b4b69ca9d77efd6d63b71b93d4bf5a3d
SHA-256: 0847ac31f7516228df4792f20474774eb77aad864dc84774468b972b179a8718
Size: 1.30 MB - conmon-2.1.8-1.module+el8+1694+e4eeeb35.src.rpm
MD5: 45d9b7b018ae57e79d8a0dc43fc0a339
SHA-256: 03c5c596c86ff438e8a0cbca31f68ef1da48dadbf1073e429fead6eadb77f479
Size: 132.94 kB - containernetworking-plugins-1.3.0-4.module+el8+1694+e4eeeb35.src.rpm
MD5: 8eecfeeaadc7cce3583eae0b1deffca7
SHA-256: 283b06c9f0a12393365f0afeded2978fb2d9ac4614a8fb1384de6fca70292785
Size: 3.36 MB - containers-common-1-54.module+el8+1694+e4eeeb35.src.rpm
MD5: 76cc8f05a40058116307db8269c09ca8
SHA-256: 586715440599dd0d17b45c95c3428c1c2d8494595087ced56e10ee2c6beb5ce6
Size: 131.82 kB - container-selinux-2.221.0-1.module+el8+1694+e4eeeb35.src.rpm
MD5: a7c44c4c3688c65afc20f425d7674483
SHA-256: 9e77188a9c16b7236f49844249c881a2a0dfb2c9d6c52b5ca6a4050a4ae091b2
Size: 63.52 kB - criu-3.18-4.module+el8+1694+e4eeeb35.src.rpm
MD5: e6e9b3db8612d0d0e58028f1cdc8a98c
SHA-256: 285f1de3fc81c2c07370ee0104cd639a660eb6fc6b42619d6b973c72231627d6
Size: 1.32 MB - crun-1.8.7-1.module+el8+1694+e4eeeb35.src.rpm
MD5: f5c0c4712cf982d15e99eea7fd250190
SHA-256: cab3dd53df887b1a7a8566205c0893b73a16a62cf60e00f2407b1c35ffedbb31
Size: 1.66 MB - fuse-overlayfs-1.12-1.module+el8+1694+e4eeeb35.src.rpm
MD5: 22b4edacf62e8a743325e4948d7bd7eb
SHA-256: f06970d4cff96244bd6fd730bfbcf5b82ba88ba6ade64cb7e99495e2fb846382
Size: 112.01 kB - libslirp-4.4.0-1.module+el8+1694+e4eeeb35.src.rpm
MD5: 838954c38b276f1e5220692912cefbf0
SHA-256: b6d7de3d2cafec0499d8b11fc2c0b1dfcfb759dc3ac4789fb4372b7cb4ef6256
Size: 114.78 kB - netavark-1.7.0-1.module+el8+1694+e4eeeb35.src.rpm
MD5: edcba267980eede47e9c91742263c088
SHA-256: de71574f10c08bc9a7586a6badbc07bd8d7e38c644ceec154d7897cee7dfe097
Size: 12.25 MB - oci-seccomp-bpf-hook-1.2.9-1.module+el8+1694+e4eeeb35.src.rpm
MD5: 9efcaf1d69da53f45ad25159ada050a2
SHA-256: 8616c4c4aa23a084977f112688eaf2cb4b838e7c8fadc9c32ba83e0fbb63329d
Size: 1.45 MB - podman-4.6.1-4.module+el8+1694+e4eeeb35.src.rpm
MD5: d615025f2a8fb27d24138bfa5bed67e7
SHA-256: 55bd2197abeab3aade98e37d89c255e991f52e155252c0929b39ee71886b883b
Size: 22.73 MB - python-podman-4.6.0-1.module+el8+1694+e4eeeb35.src.rpm
MD5: e85f4ade13f004b716ca633762600cf2
SHA-256: d17727d29beeb386aa17e6b047542ca9a2fa2862060d6559316d684451cbd236
Size: 185.04 kB - runc-1.1.9-1.module+el8+1694+e4eeeb35.src.rpm
MD5: c677c788845e629468621caffdc91668
SHA-256: adbaf001e5f8bb47874cc8c82466b21c84896558b67f79e4dee05b27114ddcb9
Size: 2.36 MB - skopeo-1.13.3-1.module+el8+1694+e4eeeb35.src.rpm
MD5: bc67c9f9005f0c621c20ea51d973a3e9
SHA-256: b12a7c900da3d1fee2d6a539dcfcbe5acea0de66b00d1cd6a66c3bbd870e4ead
Size: 7.49 MB - slirp4netns-1.2.1-1.module+el8+1694+e4eeeb35.src.rpm
MD5: 6beac3219f4eeaa6132be34132d0cbe9
SHA-256: f07f2dbb33ec3d2f92d11fe0dd55f67325158b3afc35217aaaba98e2e9321583
Size: 74.93 kB - toolbox-0.0.99.4-5.module+el8+1694+e4eeeb35.src.rpm
MD5: 4855b79fbde8c22d5dceba5ef863e9b1
SHA-256: f58c2fd36f3cc941dc19b10bf33ddcb1e63743a5bbac3cee7bdfd91d5a096603
Size: 2.25 MB - udica-0.2.6-20.module+el8+1694+e4eeeb35.src.rpm
MD5: 3300c26101d2b9d15aeb3980a720ec16
SHA-256: 6d1374e33eedfe6a0a89d3490f4d6a975309c7dcdd1d28f3430da6acd541f90f
Size: 134.17 kB
Asianux Server 8 for x86_64
- aardvark-dns-1.7.0-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 6a5433b2c7b120ee87acf036f47b2db1
SHA-256: 3c42bbc816c85658b7533b2bf689b5f163ebe471c4f743ced995f7d65ea0e70c
Size: 1.01 MB - buildah-1.31.3-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: a4fd3a3cf3dc9ac441902f1f6e0db649
SHA-256: 77ddeb95ae4d20f168966137daeee3e02a9666b29ac975c4c714ed822c77a812
Size: 8.81 MB - buildah-debugsource-1.31.3-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: ba53aa1dd96039496b7bd31695346dcd
SHA-256: 1797c95fb53a5019956ad22e1299980c70e4d726b25870c62a55e032a2cfe3e3
Size: 3.87 MB - buildah-tests-1.31.3-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: da19fedcb2a4d88d808ee30ba4d42e97
SHA-256: 0ed5929e1325acaa879f26a6262950f1b01a06e24c8192981534c1787c6c8341
Size: 28.43 MB - cockpit-podman-75-1.module+el8+1694+e4eeeb35.noarch.rpm
MD5: 368b67bfa897f905e3a9f0e70b180861
SHA-256: ff2ff49cc6c9f6fc245699e6f79a013c0d577d8a970ffbfefd766f6c71a77b62
Size: 738.05 kB - conmon-2.1.8-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: ff9765fd8cbfd637dbd58efe1e38e808
SHA-256: 2718d7f1a8bdce38254d1874ba14e2ccdc353918d279ed28332d144402a7fddd
Size: 56.29 kB - conmon-debugsource-2.1.8-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 3f3d8532d94497ded5a94f01253586dd
SHA-256: ff25e72cebfa44e805edcb747520b032df7ed516929261f47fb9930f6d7156ee
Size: 49.91 kB - containernetworking-plugins-1.3.0-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: abd1282ed1cd414565a6f8683199de3c
SHA-256: 536f37045bd568d36e9f5fe59db39feb2c42a02f8ad6ea956587bc866f17be7c
Size: 21.42 MB - containernetworking-plugins-debugsource-1.3.0-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 98c608dcc0f525eab4cfe35728df793d
SHA-256: 27e5e2bc9881e46a3c6de32a9a332e39c0b78b647be7ce05b622fe288808a1fc
Size: 427.56 kB - containers-common-1-54.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 0f52d1d45ae9604d3471878c28724107
SHA-256: 0af0f361995509ac794074330aecdbe36295537aea26e075d83cc816768c7fd6
Size: 132.96 kB - container-selinux-2.221.0-1.module+el8+1694+e4eeeb35.noarch.rpm
MD5: c90831f9fc502af6aadcac0837004ae1
SHA-256: 0c38f586f33bc15638ceb30f5fa1ead3f21fd2fd40f875967a0547dddf06193c
Size: 67.85 kB - crit-3.18-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 8c2644bdede612aa91b8ac37e58557b8
SHA-256: f8fe31c8ac11880e83ad250a9b7d2adcf39822d56c819813bc4fba1cfac489f2
Size: 22.01 kB - criu-3.18-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: d532812d429bef2be300be15b67b4c8c
SHA-256: b2f999818362143314abcb75ede53c7a3a58abbdf8f68b38f54e96cea3316d7c
Size: 563.03 kB - criu-debugsource-3.18-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 5473abacfeb2f757ebf5cfccdce7d79b
SHA-256: f8efbecd23337105884e92d2303d1bc2165740f09eb989c55f30d6a53c051526
Size: 729.67 kB - criu-devel-3.18-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 2835892c6d6ff56069ce5646956611ac
SHA-256: 035f79257bf042dfa97fc5879b9e6a001bccdae5c76b638511b20e00bd3d407c
Size: 28.13 kB - criu-libs-3.18-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 7157e609671a9cc4f3d3701fc845d62c
SHA-256: adb2cc2491322c9322a4364b862c7a8d787e4be80a5a8cc8f436faba3c1796c6
Size: 38.05 kB - crun-1.8.7-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 8fe2881060ef82b4d3800f59a067d610
SHA-256: bd5e0f735f36e2491a983464495efe07c7f8095bf05cd8f4fcddeeecd7c9c00c
Size: 237.93 kB - crun-debugsource-1.8.7-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: c3c04e540fc58712524bfc2dc42db6ce
SHA-256: aa19b1e6d9a55f0734f5fa5b00ba6345ae96f7c72736c4725fce4f636e677d28
Size: 183.80 kB - fuse-overlayfs-1.12-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 0ad0c7f199a63b50a0d436346a7372cd
SHA-256: c6eeb44fb0a2217261c9591b41a68e0f2cbdb42e3dae872d387443d91c74f988
Size: 68.55 kB - fuse-overlayfs-debugsource-1.12-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 7ec6f87dfba74d5c4d826405b4f15496
SHA-256: f17eb8255767057ef0a5d49193b892dc85d9e796143e51da07049c80ac8ada0b
Size: 55.41 kB - libslirp-4.4.0-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 33e66a20f2a7909593b9d6d027b3ceca
SHA-256: f7a542ab1b4499ba144bb5c57e2cc778cfd5372ec71ec72054d31aa2650d72e3
Size: 69.16 kB - libslirp-debugsource-4.4.0-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 30cf11b5a82cc0f9852082193bfdbbef
SHA-256: 4be45075da76fb01f9d9b4189dcce4906c0884065fc5e8b6fb9837e95d325aad
Size: 114.43 kB - libslirp-devel-4.4.0-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 362189c8f7b5997e98b7c9a77fc0d695
SHA-256: fbea5cd0694a1aecec4ccb2a6a199e8da177a9863057ffdd42054340387e4053
Size: 11.29 kB - netavark-1.7.0-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: c48a41c7ce65f12e8a9ca9c77c03262a
SHA-256: f69156d827a221ab857de328e7a1ad3777ce78b0b54eabf75e6f0a0eb15ab7ed
Size: 3.71 MB - oci-seccomp-bpf-hook-1.2.9-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 90c284c651be87db0ac62a432d5c4528
SHA-256: 3651afb0be79b02c73a5fb02dbf9aa050f12e96bfa497e93167cf356b9b0877e
Size: 1.06 MB - oci-seccomp-bpf-hook-debugsource-1.2.9-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 60a8d79d4161a7d092a55c123ca75de7
SHA-256: f665cd8621e117b148b73e8373ff774a9c58cc238408c5a2ea3dde81d35174b3
Size: 190.06 kB - podman-4.6.1-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 0b7a8a027be3898dbae738df1e212e94
SHA-256: da7dff35b3160c15baa149281c23b1880d7577ae8e74a3aaf1b06ace1d2b4167
Size: 15.33 MB - podman-catatonit-4.6.1-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: ac7632141bfea47d393f17e030175e98
SHA-256: 9e971bc5259b9050f20d148db0b2e2e741e2da3c103b20276de3204b96cbd342
Size: 361.05 kB - podman-debugsource-4.6.1-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 9fd8e716cc724123e47f7bf96ddddbb5
SHA-256: e8ca5e0137fc3117ce99503e7c5645831630bbf542db585c2f235d196dd39718
Size: 8.77 MB - podman-docker-4.6.1-4.module+el8+1694+e4eeeb35.noarch.rpm
MD5: 1c9bc0d184ad301bb41baf8162e96596
SHA-256: ba398cbded1a0eed7db5bc41e5c2bd55edb9c5672aa57b39b06967edd6891131
Size: 108.71 kB - podman-gvproxy-4.6.1-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: b1d45c8ea314f27915ab377bb94816f4
SHA-256: 9b5f7af322c1d1c15aa38b3ff1bab646c2ca720f22d8fddc424c86655232a24c
Size: 3.74 MB - podman-plugins-4.6.1-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 23638acb1e9d4ac5b22d5404f0ee640f
SHA-256: f6f1484a430da6eb2c288eebb0556db086ab875f17b23922579cb61bc78e69d3
Size: 1.26 MB - podman-remote-4.6.1-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: bd5b07b4721178b0502d608d1a61b45e
SHA-256: ed2a6178daf5547a4b758897c6efd24dc1c7e6b6bf2a99fdde5ac132a79f842b
Size: 9.65 MB - podman-tests-4.6.1-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 64c77a835f8453a03f7db9227b3ce06e
SHA-256: cb88e86c74c2379f709d8b6786ded996e0bcde2c6c12cab1824d1b962062ccfd
Size: 237.60 kB - python3-criu-3.18-4.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: f8d7808e340efe2bc529daa1e34a2cf9
SHA-256: 4ecec401ea64a6f87835d0ba396fc5bf24b6247ad74f027bb3037de54f8f6ef2
Size: 177.14 kB - python3-podman-4.6.0-1.module+el8+1694+e4eeeb35.noarch.rpm
MD5: 7abf705b7edfcaefcc66b09c292c7a7b
SHA-256: 47498c703c47eeae05db537da8b424559fa203799762c0fc874c5f7baad56ec5
Size: 152.16 kB - runc-1.1.9-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 830814b354d27c32bd35393d953f4b78
SHA-256: ad7d9d2e05caafee9bbf41112f9e38cec2d60b4b8bef2d96d87be87dcf3e21b1
Size: 3.07 MB - runc-debugsource-1.1.9-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 8384b6f9d3c61504446c1bf56475e379
SHA-256: 0fa2530dac2c1da7c63059d6ed56978e78e5594682e3cb2a161e84e5be619ecd
Size: 887.78 kB - skopeo-1.13.3-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: cf44d956ef68f78462d5398536b55ad2
SHA-256: 0bbe3256bba5b702b82cff8fdf5f85674b85e71d079bf79c9e5bece8a3908f96
Size: 8.14 MB - skopeo-tests-1.13.3-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 9ae0a399aede108157293a0eae485515
SHA-256: 29abc3b67f4165edc8d2452fbc6fc50b972c22c07f353a6afbc50d70f79356d9
Size: 783.21 kB - slirp4netns-1.2.1-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: ff1145408cdb266fe969d9e08baa0fb0
SHA-256: bfbd3a44f8eca6a7ab543235bbc3a3d232741b79b44da0d42c5e57bf06873911
Size: 54.52 kB - slirp4netns-debugsource-1.2.1-1.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 97010b40c55306c37b0639d58928bece
SHA-256: cb7fc6676502875bd1f5aa451fe17da7cfb459f23094168d11f1131b0376cd90
Size: 43.31 kB - toolbox-0.0.99.4-5.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 672deeb295f19057739ee853ea46afb1
SHA-256: 281eecd963986e46875365b3adeeef65a24883dd554360599fdaa203acb573d1
Size: 2.53 MB - toolbox-debugsource-0.0.99.4-5.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: 3dd9f6d8e9bfa1de68fc206955d4b625
SHA-256: 3c31a8b86a3ea74942fa33fef8f723d4c3a3af9b2c8465721442ae8daf05a8a2
Size: 559.50 kB - toolbox-tests-0.0.99.4-5.module+el8+1694+e4eeeb35.x86_64.rpm
MD5: dad589395b0026d77385d85b144652ea
SHA-256: b5638807c86c7d5596017302bbb4576bed979e008d00d9357c45637ec0a6b833
Size: 37.56 kB - udica-0.2.6-20.module+el8+1694+e4eeeb35.noarch.rpm
MD5: 9bf5879ecc460cfef491cd62f320bced
SHA-256: b9462cabb8f480e24ba7c484c9dec028c8aa14d4b16112e20c908c4448429fc2
Size: 48.16 kB
English