| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-fix-libvirt-connection-plugin-warning.patch | Fix libvirt connection plugin warning | not-needed | upstream, https://github.com/ansible-collections/community.libvirt/pull/147 | 2023-07-22 | ||
| 0002-fix-libvirt-encoding-errors-on-windows-guests.patch | [PATCH 1/2] Fix encoding errors on Windows guests (fixes: #156) On Windows guests the default encoding will be set to whatever default legacy encoding, not utf-8. This issue isn't apparent on English locale Windows guests, as there the encodings (ISO-8859-1, utf-8) happen to coincide. However, on e.g. German Windows guests this will cause an encoding error when reading any output from there. This patch ensures that the proper encoding is set on every command. |
Lee Garrett <lgarrett@rocketjump.eu> | no | 2023-09-01 | ||
| 0003-fix-libvirt-path-resolution.patch | Fix issue with ansible.builtin.copy when using libvirt connection plugin The libvirt connection plugin is unable to resolve "~", leading to files copied to literal /~/ansible-tmp/, and thus many modules failing. |
antonc42 | yes | upstream | upstream, https://github.com/ansible-collections/community.libvirt/pull/162 | 2023-10-20 |
| 0004-fix-CVE-2023-4237.patch | [PATCH] Update document to use no_log and register when creating a new keypair. (#1716) Update document to use no_log and register when creating a new keypair SUMMARY "When creating a new keypair the ec2_key module prints out the private key directly to the standard output. This makes it unusable in any kind of public workflow." To fix this security vulnerability no_log and register should be used while using this module to create a keypair. ISSUE TYPE Docs Pull Request COMPONENT NAME ADDITIONAL INFORMATION (cherry picked from commit 39b19d83db072f1854adaac92e05f06abb63dd3e) |
GomathiselviS <gomathiselvi@gmail.com> | no | 2023-08-30 |