container-tools:4.0 security and bug fix update
エラータID: AXSA:2023-7317:01
リリース日:
2023/12/27 Wednesday - 07:23
題名:
container-tools:4.0 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)
- 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: 4.0
解決策:
パッケージをアップデートしてください。
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-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
- buildah-1.24.6-7.module+el8+1690+f8a32f44.src.rpm
MD5: 0893af27456f04795cad1a6d75f48e97
SHA-256: 26f8ae41e72392b03cfe5c1c9d7212ae23b037f426abff1313e16f78e37f1577
Size: 13.27 MB - cockpit-podman-46-1.module+el8+1690+f8a32f44.src.rpm
MD5: ce9673d804cde41630a3b8213a636de5
SHA-256: f6ff4dfc30545ae22d2dd225202537054fbab7feded8c8cf52ccedde8835e555
Size: 738.04 kB - conmon-2.1.4-2.module+el8+1690+f8a32f44.src.rpm
MD5: f81b9214a05a7510f2cde40964d45b19
SHA-256: 9794287f56d1d67b73b73116d9f4c2558d40a678cadde162d88b333fef807290
Size: 171.22 kB - containernetworking-plugins-1.1.1-5.module+el8+1690+f8a32f44.src.rpm
MD5: c75c27ff3974fded412af935cc5bb095
SHA-256: 059d599df3cf2a776ee23721b56a103e4579a3b896057df3544f9386efff0089
Size: 2.80 MB - containers-common-1-38.module+el8+1690+f8a32f44.src.rpm
MD5: 0f02bc5ec0bb6f513f14e4762db0afda
SHA-256: 72f9d3f5dea95e46dbaf8a66bfc2b5e934317d7150e72519f750a83e54bf0a5e
Size: 42.42 MB - container-selinux-2.205.0-3.module+el8+1690+f8a32f44.src.rpm
MD5: 8a182972c6953eadfb59d70b7acab6e6
SHA-256: 919975c0a33c3a371d054dc455c20c885f4dcc08bd83f6f8ccd5732ab286e516
Size: 59.75 kB - criu-3.15-3.module+el8+1690+f8a32f44.src.rpm
MD5: e1d0d77f84dbd7b9eac95ae7e8bffaed
SHA-256: e32c21fb2b912c2ee088a54ad2318eb8906b47f34957dc0186cf2cf81735e2e8
Size: 914.17 kB - crun-1.8.3-1.module+el8+1690+f8a32f44.src.rpm
MD5: e854a651d72fad5fed67724869d73ace
SHA-256: 67eb1ae5e764217eb523763a53ee09cfc021488e6bb6f4fca9c87bef42fd4715
Size: 1.62 MB - fuse-overlayfs-1.9-2.module+el8+1690+f8a32f44.src.rpm
MD5: ac151d6378db5448ea7a256389fbcf75
SHA-256: df78b247bc355c9f9fd5149a8d34e6e6bc310a6de2138355ec994b167336b19c
Size: 115.67 kB - libslirp-4.4.0-1.module+el8+1690+f8a32f44.src.rpm
MD5: a353c3289a2c34ee903b805972c9117c
SHA-256: 8428643b733150f25b3327f37cd936b996d4172560e20859f0b9e46fe1ff8b5b
Size: 114.78 kB - oci-seccomp-bpf-hook-1.2.5-2.module+el8+1690+f8a32f44.src.rpm
MD5: ad668456318664b142841efd8d71a8b2
SHA-256: f43915dd69db03014fbbe895333e6554e5dd9e0ed77f44c753c860b42e25b4a4
Size: 1.20 MB - podman-4.0.2-24.module+el8+1690+f8a32f44.src.rpm
MD5: ac4358309cd77e5966caa3c836201750
SHA-256: c1ad2872535a3a5527ccf7f424743543eb7e9958bc79201c2620b2e19cf645d3
Size: 16.83 MB - python-podman-4.0.0-2.module+el8+1690+f8a32f44.src.rpm
MD5: de288cfd994c506752a612422895b378
SHA-256: ff73f78bcb442ed640e5e16c17cbb8c892dc38b91ee0e6954e6c700896d4d19d
Size: 79.45 kB - runc-1.1.5-2.module+el8+1690+f8a32f44.src.rpm
MD5: f2622734c2de8a4d6e0514219bbaf763
SHA-256: 3275ca5be3ac9d00167e8c4f2a62db8d6913b97e544b2c968974a1db2520b2b2
Size: 2.22 MB - skopeo-1.6.2-8.module+el8+1690+f8a32f44.src.rpm
MD5: a8ce8360d1bb4fdb78789788b630f970
SHA-256: 367a41f53bcca18e4550969def6b416d62d8d97f6a865547c1d51334bfacd54c
Size: 6.18 MB - slirp4netns-1.1.8-3.module+el8+1690+f8a32f44.src.rpm
MD5: 11069458c2342d2e09294415cfd19357
SHA-256: 791981496c789c0c152dc352a7235b90ecd5856f6af53bda13a8ab883ff48fd5
Size: 69.55 kB - toolbox-0.0.99.4-5.module+el8+1690+f8a32f44.src.rpm
MD5: 7f384957305d2018663ce95c218cc775
SHA-256: 705b7ccaad0890b69d815c78b8e98696db676c0b2082872b03888e7ddbc0bb6e
Size: 2.25 MB - udica-0.2.6-4.module+el8+1690+f8a32f44.src.rpm
MD5: 056eb17f0fd9c4498b81f58b295469dd
SHA-256: 2aebd05b5d763d03407a341ff0dd59ad2951aaf6db9fbb86a8dbf98a66c2187b
Size: 134.00 kB
Asianux Server 8 for x86_64
- aardvark-dns-1.0.1-38.module+el8+1690+f8a32f44.x86_64.rpm
MD5: e29c448358c07f82b0e41dd611af9dc9
SHA-256: f93eac3b345c49b3a63c90d1e14c89436572c8b0b2412a3ad764b9c82066ab36
Size: 1.01 MB - buildah-1.24.6-7.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 298587c41612b7adc7cc75cfdfd8b7a7
SHA-256: 5102d7a8b5c5f698fc5275b6b1e86223829184015bd42aa3a6ea82cd5999cc2c
Size: 8.00 MB - buildah-debugsource-1.24.6-7.module+el8+1690+f8a32f44.x86_64.rpm
MD5: ca3276a7884ef6b0287468cfa64aa607
SHA-256: b15290db388b0cc29c9b78487bca98eed3b16029ec30ce3b2713c695d7d5fa9e
Size: 3.29 MB - buildah-tests-1.24.6-7.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 9c26128a5ed7ff95f30b4276714af22f
SHA-256: 9e82b1ddc71d0f22c75a1bfc464b81bb914683de99595d18215c795afb2c345a
Size: 18.06 MB - cockpit-podman-46-1.module+el8+1690+f8a32f44.noarch.rpm
MD5: a9ef4924d199bebfb7b7641cdce67db1
SHA-256: ae9b10047735d6c93df779970bbd120dc768f714f6206f9f9e7a6f4f56ee6879
Size: 499.61 kB - conmon-2.1.4-2.module+el8+1690+f8a32f44.x86_64.rpm
MD5: d6c04c78a44e3fdedc5ee9194c358e18
SHA-256: 9228b6c6e97a5fe5bdc411f79395d7dcb7bd18e1264a398d5df3e867cf922dcc
Size: 55.12 kB - conmon-debugsource-2.1.4-2.module+el8+1690+f8a32f44.x86_64.rpm
MD5: ec045fa3eb0a61bb9804a7e256fcdec8
SHA-256: 0a2bd3207edf6b93727d540629dfcdbc5ce19424f282b459ebe7e145fe357d9e
Size: 48.45 kB - containernetworking-plugins-1.1.1-5.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 1c06dc497104ddc2915da5d4cec47df5
SHA-256: 766bff339e8b86244cef230236dc939e2c4d171d76073391ba419ed6222c638b
Size: 19.08 MB - containernetworking-plugins-debugsource-1.1.1-5.module+el8+1690+f8a32f44.x86_64.rpm
MD5: c52e376c86d38b9de771c1329a34a198
SHA-256: e3a2bf8edff3414c18505df8df21e98a6718fde1b8738cec1246b0a6dcb85aa6
Size: 376.11 kB - containers-common-1-38.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 8316cf2517f5c1ff408eceb03386cff2
SHA-256: 8c4b7b65d6848865c85697baa8cc4c39d8efccfe8ea54e090873693b5893c4fe
Size: 105.56 kB - container-selinux-2.205.0-3.module+el8+1690+f8a32f44.noarch.rpm
MD5: a7b4a4448f919c5216256542980cf9e4
SHA-256: 518160411f77bfe2f97ad9976cda11564172c59025ad31da9de816e701e3e7e4
Size: 62.17 kB - crit-3.15-3.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 36318c74079852d3cc4b454fa00fefc8
SHA-256: 3090500663d80a5ff15b58523741124438c10c4606dccd013e727972f64f1b42
Size: 18.59 kB - criu-3.15-3.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 92cea1ab4f8d9995a7bf04e7f4f2f0b2
SHA-256: 49058fb5ad0e885b941fcb4a54e2ec72ac328a1eef31b4163e37db6363511a23
Size: 516.61 kB - criu-debugsource-3.15-3.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 39035f88422e51f3492a373783dfe36a
SHA-256: bb8da1335088b31259f6f2ab372d3b1f668143587c51edd35c451f3defac431e
Size: 675.30 kB - criu-devel-3.15-3.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 495dee54b9e13465d9d53c08a14c9a39
SHA-256: d5fa6973ff3b36592c5b97ea901bffc7b5760f1d86f8b658c92cc8761a09a802
Size: 23.81 kB - criu-libs-3.15-3.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 92e565d72da8ecbc62ab0a2d0a0aefc0
SHA-256: 519973978410fb37b2d012b4a1ce53e9936aebd0529d89ea994e7a17517acf78
Size: 36.65 kB - crun-1.8.3-1.module+el8+1690+f8a32f44.x86_64.rpm
MD5: cf5827611420d2125895cf77c122ed5b
SHA-256: 62b5b407968a267dc279bb860fb1942b1644639aff5382dbdb563a680ee5cb23
Size: 232.10 kB - crun-debugsource-1.8.3-1.module+el8+1690+f8a32f44.x86_64.rpm
MD5: fe107ad355a6f912694cb8d536958cbf
SHA-256: cc781a50042f2381cca917590b25e90fcc1f899b5b90292537db03d3765339f0
Size: 177.91 kB - fuse-overlayfs-1.9-2.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 26ec37487b3ba97f2e52848ada2c2287
SHA-256: 1694cb65ebb561b55632cc50cb70afcf02f8d5b3353f8210ae2674e23f9bcef7
Size: 72.27 kB - fuse-overlayfs-debugsource-1.9-2.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 31488358ed10adbf0012974a883add4e
SHA-256: e842a6c1a804c53d3fe4923628cf5d063dfba73bd541774b5bda296f0a8d1ad2
Size: 54.22 kB - libslirp-4.4.0-1.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 59b558469894a45ab529aa3fd09bc892
SHA-256: 26043effcbac2392af74216999577ec4871da38abbd0c4296bc61aac8f39001a
Size: 69.16 kB - libslirp-debugsource-4.4.0-1.module+el8+1690+f8a32f44.x86_64.rpm
MD5: ca6abed1a5d7b2a1dedc15e5bee1f815
SHA-256: ae6d979e1c6e155671fa564fb68c3e66019d2c1528ba3a01a403ca3140afce32
Size: 114.43 kB - libslirp-devel-4.4.0-1.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 9edfa9324a50d417b3f3932b0edc758d
SHA-256: 62c8f8435dfa5beef5b515e969428000004773651839490778279a4c0fa5be93
Size: 11.29 kB - netavark-1.0.1-38.module+el8+1690+f8a32f44.x86_64.rpm
MD5: c395a11ca020ef7d639a15fee2587a74
SHA-256: e6e75136a2e63978dabd01306b0c0b072dbaf82d5b483d8ffdb422126fe88390
Size: 2.06 MB - oci-seccomp-bpf-hook-1.2.5-2.module+el8+1690+f8a32f44.x86_64.rpm
MD5: f66393ce59003d23865d59747a538f4f
SHA-256: 92a705c49f80723fd2c412a86f5dd824765ceee944cc450908feceadd5789ee8
Size: 1.06 MB - oci-seccomp-bpf-hook-debugsource-1.2.5-2.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 48c06a33e19493ce112b2a4b81c52979
SHA-256: 1a311f1c88c541d028fd850af85fa5843c3a3dea3ff9517de2e4a53392c39cb6
Size: 174.59 kB - podman-4.0.2-24.module+el8+1690+f8a32f44.x86_64.rpm
MD5: c26ace45d6b4138a18d995385244d2a1
SHA-256: f729abb9e6c0f7494956badd42aa6aabe350bf11e484eef544cba5c9a36d5b0b
Size: 13.10 MB - podman-catatonit-4.0.2-24.module+el8+1690+f8a32f44.x86_64.rpm
MD5: e1c60af034f615bc1d1176349e29d6cb
SHA-256: 266c36fc43a6bbc357f0dd1e46ad91afcb35fdfd3cd5a8357eab33301a492a5f
Size: 354.97 kB - podman-debugsource-4.0.2-24.module+el8+1690+f8a32f44.x86_64.rpm
MD5: d078f371f9aa6b0c699ec19b3e0c9a5c
SHA-256: 9b5a2fa12aa44dc229c743d223ffe9aa23e65538c7d26e64974504e51c0ae98f
Size: 6.06 MB - podman-docker-4.0.2-24.module+el8+1690+f8a32f44.noarch.rpm
MD5: e1f2a63de3a84e565c1faf826124219d
SHA-256: cf695baaa8e91644377e9cb0ca5d2dfe54d3f256839f8e6a60665c08000367b3
Size: 68.72 kB - podman-gvproxy-4.0.2-24.module+el8+1690+f8a32f44.x86_64.rpm
MD5: a8a75203cb0ee38f4fc24251e6ae5a38
SHA-256: 9240bb6bda698db67082e9e079fe946cd01df1a84ccd18646ea491b0dc1aa6f6
Size: 3.73 MB - podman-plugins-4.0.2-24.module+el8+1690+f8a32f44.x86_64.rpm
MD5: a4d158bb15a1bcbc2afad5132bbd80e2
SHA-256: bb8046df7e864df2a6085fbd4e4390ad4aeb8c2fafa57310126e599069b81758
Size: 3.28 MB - podman-remote-4.0.2-24.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 61946e1e8592b6faf844be098f3d6f34
SHA-256: fa2d568798311394e1d0c33af297d7db314120877f6e8711102460e78b93216f
Size: 8.10 MB - podman-tests-4.0.2-24.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 1312a390277db68e441444385feae970
SHA-256: 9f1c1a55fbe74926cba2230cc9d466e3c205530fc8107ebccd1743f647e10e27
Size: 176.15 kB - python3-criu-3.15-3.module+el8+1690+f8a32f44.x86_64.rpm
MD5: c68f7b8ca94e67f004e154260f375544
SHA-256: d18c5722ddac8aa67e8df755279d7beaad922c308bc15a168c39e2e3945e43ee
Size: 168.78 kB - python3-podman-4.0.0-2.module+el8+1690+f8a32f44.noarch.rpm
MD5: b5d23d151bfacef511c82a0793354aab
SHA-256: 87f5d15237ba4817bab130cd43f9f77eb24180a4a10d0292d86e3a7f7ed620db
Size: 148.11 kB - runc-1.1.5-2.module+el8+1690+f8a32f44.x86_64.rpm
MD5: b63834a8151030f4d8a5591d402eb6db
SHA-256: 0271cfbcbf5283e9da3b1cd0b70bc83786e2f20f0c0b6c9a718c71fd53f102ed
Size: 3.08 MB - runc-debugsource-1.1.5-2.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 11d1ab6214b61ff33bc4c05fc3607630
SHA-256: 1e1df8b15aa9a820306c549e6c7db30fd633a92ad0d0ee77aef50d25f33d47db
Size: 868.28 kB - skopeo-1.6.2-8.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 4ed32328fdb711f6fd8f8c8b2737c9c9
SHA-256: 9967ff29006b7a46eed2c1c9debab0fa965dd50cdbe8c0d6196dac5644d5a342
Size: 6.64 MB - skopeo-debugsource-1.6.2-8.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 7c59b3962777b8431f35d039bfbc86fe
SHA-256: 32e71ee177877a7d936a5f4ceb69ff7def9680ae75f38a1c7ee745ea5615b36f
Size: 2.48 MB - skopeo-tests-1.6.2-8.module+el8+1690+f8a32f44.x86_64.rpm
MD5: de9596df9147f1cc12b4696d0cef2e64
SHA-256: 0eeb479dd7e074d0b4a1442f84279b2c815baf5891c7f0a08b9805a6b82882f3
Size: 780.08 kB - slirp4netns-1.1.8-3.module+el8+1690+f8a32f44.x86_64.rpm
MD5: d52a9366cca113781a3d5e823b4eda13
SHA-256: c6c21897410530f84ee5c717aba09ffafccf451388d1b052f5707b5dd15e44a5
Size: 50.31 kB - slirp4netns-debugsource-1.1.8-3.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 3517b4f21bc8a7c5d9380c9ae210203a
SHA-256: b5401ded8369d0f11b1d55eea666faddbf5394f1329056ea96dac5c406ee3b3b
Size: 38.88 kB - toolbox-0.0.99.4-5.module+el8+1690+f8a32f44.x86_64.rpm
MD5: b44f9dd7a1631ef74620cb3e91d76e4a
SHA-256: 3598192d189959066b351bdf41a18e47a3d397954375838f79fae1dca835f90c
Size: 2.53 MB - toolbox-debugsource-0.0.99.4-5.module+el8+1690+f8a32f44.x86_64.rpm
MD5: cd864a7c8a37bd51f0de9e7ea0bfaab8
SHA-256: 173cae22350a2c7489e6f003f07ebe8f104c707e4620a62c881c8cfcafbce2bb
Size: 559.42 kB - toolbox-tests-0.0.99.4-5.module+el8+1690+f8a32f44.x86_64.rpm
MD5: 70f95f32c5c2763e795165d1283e4455
SHA-256: 49836ade181b9e4596c153dec6362d043e9f8a57b3a85949ef301735f1c5b4c6
Size: 37.48 kB - udica-0.2.6-4.module+el8+1690+f8a32f44.noarch.rpm
MD5: ea43795e972720c3286e54d45f47c666
SHA-256: 6be5e45be8ad0c5bc207636f7e468c75ac8faa3894371cc5cd5315a756ef2053
Size: 48.04 kB
English