<?xml version="1.0" encoding="UTF-8"?>
<otherdata xmlns="http://linux.duke.edu/metadata/other" packages="75">
<package pkgid="c46b261d89c11385b89a8aba3bfede69390927e3b1ae4281e2c8340d75fd1668" name="ccrypt" arch="src">
  <version epoch="0" ver="1.11" rel="13.1"/>
  <changelog author="mpluskal@suse.com" date="1449662400">- Update to 1.10
  * see ChangeLog for details
- Cleanup spec file with spec-cleaner
- Use shared gcrypt instead of bundled one
- Enable emacs support
- Initial changelog - previous packaging done by:
  * Pascal Bleser &lt;pascal.bleser@opensuse.org&gt;
  * Leo Eraly &lt;leo@unstable.be&gt;</changelog>
  <changelog author="mpluskal@suse.com" date="1461844800">- Install COPYING</changelog>
  <changelog author="mpluskal@suse.com" date="1512648000">- Split lang and emacs support subpackages
- Run provided tests</changelog>
  <changelog author="mpluskal@suse.com" date="1544788800">- Update to version 1.11:
  * In cat and unixcrypt modes, "-" can now be specified as a
    filename to mean standard input.
  * The emacs mode has been updated for compatibility with Emacs 26.
  * Estonian translations were added.</changelog>
  <changelog author="mpluskal@suse.com" date="1642766400">- Workaround failing tests on Tumbleweed</changelog>
  <changelog author="meissner@suse.com" date="1651579200">- switch to https source url</changelog>
</package>
<package pkgid="dc9db84d4ca806ef46648fc57a04d57e02854c1302d83ba613d002dba57b04d0" name="ccrypt" arch="x86_64">
  <version epoch="0" ver="1.11" rel="13.1"/>
  <changelog author="mpluskal@suse.com" date="1449662400">- Update to 1.10
  * see ChangeLog for details
- Cleanup spec file with spec-cleaner
- Use shared gcrypt instead of bundled one
- Enable emacs support
- Initial changelog - previous packaging done by:
  * Pascal Bleser &lt;pascal.bleser@opensuse.org&gt;
  * Leo Eraly &lt;leo@unstable.be&gt;</changelog>
  <changelog author="mpluskal@suse.com" date="1461844800">- Install COPYING</changelog>
  <changelog author="mpluskal@suse.com" date="1512648000">- Split lang and emacs support subpackages
- Run provided tests</changelog>
  <changelog author="mpluskal@suse.com" date="1544788800">- Update to version 1.11:
  * In cat and unixcrypt modes, "-" can now be specified as a
    filename to mean standard input.
  * The emacs mode has been updated for compatibility with Emacs 26.
  * Estonian translations were added.</changelog>
  <changelog author="mpluskal@suse.com" date="1642766400">- Workaround failing tests on Tumbleweed</changelog>
  <changelog author="meissner@suse.com" date="1651579200">- switch to https source url</changelog>
</package>
<package pkgid="72abc988702af9822bc47dd41273d1b0d31cba0c38026db919320f32e45e5fd6" name="ccrypt-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.11" rel="13.1"/>
  <changelog author="mpluskal@suse.com" date="1449662400">- Update to 1.10
  * see ChangeLog for details
- Cleanup spec file with spec-cleaner
- Use shared gcrypt instead of bundled one
- Enable emacs support
- Initial changelog - previous packaging done by:
  * Pascal Bleser &lt;pascal.bleser@opensuse.org&gt;
  * Leo Eraly &lt;leo@unstable.be&gt;</changelog>
  <changelog author="mpluskal@suse.com" date="1461844800">- Install COPYING</changelog>
  <changelog author="mpluskal@suse.com" date="1512648000">- Split lang and emacs support subpackages
- Run provided tests</changelog>
  <changelog author="mpluskal@suse.com" date="1544788800">- Update to version 1.11:
  * In cat and unixcrypt modes, "-" can now be specified as a
    filename to mean standard input.
  * The emacs mode has been updated for compatibility with Emacs 26.
  * Estonian translations were added.</changelog>
  <changelog author="mpluskal@suse.com" date="1642766400">- Workaround failing tests on Tumbleweed</changelog>
  <changelog author="meissner@suse.com" date="1651579200">- switch to https source url</changelog>
</package>
<package pkgid="49969949f132cf355002ce8a5bb6bee68d6ecbc931f206159c8329d1a008449d" name="ccrypt-debugsource" arch="x86_64">
  <version epoch="0" ver="1.11" rel="13.1"/>
  <changelog author="mpluskal@suse.com" date="1449662400">- Update to 1.10
  * see ChangeLog for details
- Cleanup spec file with spec-cleaner
- Use shared gcrypt instead of bundled one
- Enable emacs support
- Initial changelog - previous packaging done by:
  * Pascal Bleser &lt;pascal.bleser@opensuse.org&gt;
  * Leo Eraly &lt;leo@unstable.be&gt;</changelog>
  <changelog author="mpluskal@suse.com" date="1461844800">- Install COPYING</changelog>
  <changelog author="mpluskal@suse.com" date="1512648000">- Split lang and emacs support subpackages
- Run provided tests</changelog>
  <changelog author="mpluskal@suse.com" date="1544788800">- Update to version 1.11:
  * In cat and unixcrypt modes, "-" can now be specified as a
    filename to mean standard input.
  * The emacs mode has been updated for compatibility with Emacs 26.
  * Estonian translations were added.</changelog>
  <changelog author="mpluskal@suse.com" date="1642766400">- Workaround failing tests on Tumbleweed</changelog>
  <changelog author="meissner@suse.com" date="1651579200">- switch to https source url</changelog>
</package>
<package pkgid="d4e6e67015a95550eb350ece7883cde8dcaf57b82c92d2bd3a92643477af5567" name="ccrypt-emacs" arch="x86_64">
  <version epoch="0" ver="1.11" rel="13.1"/>
  <changelog author="mpluskal@suse.com" date="1449662400">- Update to 1.10
  * see ChangeLog for details
- Cleanup spec file with spec-cleaner
- Use shared gcrypt instead of bundled one
- Enable emacs support
- Initial changelog - previous packaging done by:
  * Pascal Bleser &lt;pascal.bleser@opensuse.org&gt;
  * Leo Eraly &lt;leo@unstable.be&gt;</changelog>
  <changelog author="mpluskal@suse.com" date="1461844800">- Install COPYING</changelog>
  <changelog author="mpluskal@suse.com" date="1512648000">- Split lang and emacs support subpackages
- Run provided tests</changelog>
  <changelog author="mpluskal@suse.com" date="1544788800">- Update to version 1.11:
  * In cat and unixcrypt modes, "-" can now be specified as a
    filename to mean standard input.
  * The emacs mode has been updated for compatibility with Emacs 26.
  * Estonian translations were added.</changelog>
  <changelog author="mpluskal@suse.com" date="1642766400">- Workaround failing tests on Tumbleweed</changelog>
  <changelog author="meissner@suse.com" date="1651579200">- switch to https source url</changelog>
</package>
<package pkgid="df6f2b21cdeb40c949b8d5c1b6355a46293223e989d636745536778e626ad04d" name="ccrypt-lang" arch="noarch">
  <version epoch="0" ver="1.11" rel="13.1"/>
  <changelog author="mpluskal@suse.com" date="1449662400">- Update to 1.10
  * see ChangeLog for details
- Cleanup spec file with spec-cleaner
- Use shared gcrypt instead of bundled one
- Enable emacs support
- Initial changelog - previous packaging done by:
  * Pascal Bleser &lt;pascal.bleser@opensuse.org&gt;
  * Leo Eraly &lt;leo@unstable.be&gt;</changelog>
  <changelog author="mpluskal@suse.com" date="1461844800">- Install COPYING</changelog>
  <changelog author="mpluskal@suse.com" date="1512648000">- Split lang and emacs support subpackages
- Run provided tests</changelog>
  <changelog author="mpluskal@suse.com" date="1544788800">- Update to version 1.11:
  * In cat and unixcrypt modes, "-" can now be specified as a
    filename to mean standard input.
  * The emacs mode has been updated for compatibility with Emacs 26.
  * Estonian translations were added.</changelog>
  <changelog author="mpluskal@suse.com" date="1642766400">- Workaround failing tests on Tumbleweed</changelog>
  <changelog author="meissner@suse.com" date="1651579200">- switch to https source url</changelog>
</package>
<package pkgid="f7f58656c3b732ce2e55fb82efbe1cbbd43dd220966baff6849be67b1b05e784" name="clamav" arch="src">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="7790712cdf90a64e4e72e32b48fc4cb026ecc13df944e0db0cbe8484dac35b4b" name="clamav" arch="x86_64">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="656e1d2f23847a47ffcc8d7340135ec82e06f656f22a9913cd11b6cf17bca57a" name="clamav-debuginfo" arch="x86_64">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="b1ef734fe5e8c1cdd643e2a2c400b5d43e4c578dea61e340c2dfc0fc49c212be" name="clamav-debugsource" arch="x86_64">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="db8b7ef70ca77205c7e40e76594a8e15365bbe877875567858def044faee6355" name="clamav-devel" arch="x86_64">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="7ceb1da137a98cb462445e64609b9a75960a4df75efac4fea5a90a1ed64e8d74" name="clamav-docs-html" arch="noarch">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="2e93af6afeb59588d5f9e612eee188f9f5e5b8f0714cb5bb240cb38ef0d5ab94" name="clamav-milter" arch="x86_64">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="f9e3bc3e471c8ab3c7872892f5c5194dc0f709f78601ddb76084261720e2e8c1" name="clamav-milter-debuginfo" arch="x86_64">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="e2161be9f1c590a69202ba0a2c6bd913d3655e9850985525a86f9a393b437cf6" name="cmake-gui" arch="x86_64">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="d5a78a029e4a88db8be645dcca6d77f5abe6a4008a24c921f99c375d439d8726" name="cmake-gui-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="19c51c814d3d228592a5a60de83a9ef2b07da30f5706747d64b952ae0b11118c" name="cmake-man" arch="x86_64">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="16de490367fe1d6118d4f077c549d7d5b9d4456098624a3883f308248e6a13ee" name="cmake3" arch="src">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="514ac07acd7c0303b1e2523d2ff622c8c4f61867531642a4d65e0a046ab40a3e" name="cmake3" arch="x86_64">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="fa626bcaaf4a55afc6fd368778a1a674c7f0e527d06ffc47b6c240a11773dcea" name="cmake3-full" arch="src">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="5779affbfc641acc181ff2ee9972e96f326a21a56c02bb634910c3f6fe946b6c" name="cmake3-full" arch="x86_64">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="0a4d1931af78d255431600d13c17589635da7738f993615fcd2e267c1d298da5" name="cmake3-full-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="4af3a25fd3293d242c5e7d44739353d914215a4a79de5071920815f14556c452" name="cmake3-full-debugsource" arch="x86_64">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="505c32c67f1d84b705f5a90832599d224f54ae83cd87c199b185ceb458959806" name="cmake3-mini" arch="src">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="aa92154fe9073856b554e59a6d5d7d29423e6facc40e72efdaedc40ce2e1f005" name="cmake3-mini" arch="x86_64">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="24d3be28e973e290e824089c1661bfd9ce8444e4bed23b70fdab7e98fc1938d7" name="cmake3-mini-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="ba8c0cfb96df1d91f6d0c32b8b1b39fd6fe2d046ba24f58cb132a31cf362ba07" name="cmake3-mini-debugsource" arch="x86_64">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="b9d3c77da34e03b10aa5c32ec5e40d05d175fd1e4fe39ab21500d1452c9392d0" name="cmake3-ui" arch="src">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="c6e18e4de9de1b63e4fb8bf94ad3c42b1dc7140b3689f7a2dc5a969b90520aa3" name="cmake3-ui-debugsource" arch="x86_64">
  <version epoch="0" ver="3.17.0" rel="1.11.1"/>
  <changelog author="andreas.stieger@gmx.de" date="1567598400">- cmake 3.15.3:
  * CrayPrgEnv compiler wrapper support updated for 19.06
- includes changes from 3.15.2:
  * Fix CMAKE_FIND_PACKAGE_PREFER_CONFIG variable causing the
    find_package() command to fail on a missing package even
    without the REQUIRED option</changelog>
  <changelog author="sflees@suse.de" date="1572177600">- cmake 3.15.4
  * In CMake 3.15.0 through 3.15.3, the EXCLUDE_FROM_ALL directory
    property was regressed from pre-3.14 behavior and caused targets
    within the directory to be excluded even from its own “all”.
    This has been fixed. The bug also existed in 3.14.0 through
    3.14.6 and is fixed in 3.14.7.
- Use pkgconfig for dependencies where possible (required due to
  tumbleweed build changes)</changelog>
  <changelog author="tchvatal@suse.com" date="1572609600">- Update cmake conditionals to make sure the multibuild is
  nicely leveraged</changelog>
  <changelog author="simonf.lees@suse.com" date="1572955200">- Drop debug patch (never in factory) and update patch numbers</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1573387200">- cmake 3.15.5:
  * no changelog available</changelog>
  <changelog author="mpluskal@suse.com" date="1573646400">- Switch back to libcurl-mini-devel to avoid new build cycle</changelog>
  <changelog author="foss@grueninger.de" date="1574769600">- update to CMake 3.16
  Changelog see https://blog.kitware.com/cmake-3-16-0-available-for-download/
- drop patch form.patch, fixed upstream</changelog>
  <changelog author="sflees@suse.de" date="1574856000">- Fix numbering of patches.</changelog>
  <changelog author="foss@grueninger.de" date="1576843200">- update to CMAke 3.16.2
  * FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX
  * FindBoost: Add support for Boost 1.72
  * FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries
  Full changelog see https://blog.kitware.com/cmake-3-16-2-available-for-download/</changelog>
  <changelog author="asn@cryptomilk.org" date="1579003200">- Fix setting CMAKE_INSTALL_LIBDIR in cmake macro
  * This is a relative path, see `cmake --help-module GNUInstallDirs`
- Do NOT set -DCMAKE_SKIP_RPATH:BOOL=OFF
  * A lot of applications have private libraries in a subdirectory
    and require linking with RPATH which is totally valid.</changelog>
  <changelog author="junghans@votca.org" date="1579003201">- use cmake generics in marcos.cmake</changelog>
  <changelog author="tchvatal@suse.com" date="1580904000">- Add new -mini flavor in order to break up cycles
  * make sure the default cmake links now all system libraries
    and mini uses bundled stuff as needed
- Switch to python3 variant of Sphinx on the manpage/docu creation</changelog>
  <changelog author="sflees@suse.de" date="1581076800">- Revert "use cmake generics in marcos.cmake" it breaks many
  cases in stagings.</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1581336000">- Revert LIBDIR change in macros - it is inconsistent (all other
  INSTALL_&lt;dir&gt;s use absolute paths), unneeded (paths may be
  absolute or relative), and breaks a number of packages.
- Update minimum libarchive version, &gt;= 3.3.3.
- Do not flag macros as config file.
- Adjust constraints (7G disk space is required, independent
  of architecture).</changelog>
  <changelog author="dimstar@opensuse.org" date="1582113600">- Change cmake to be a meta-package that requires
  cmake-implementation. This new symbol is provided by the (newly
  named) cmake-full package as well as cmake-mini.
- This is needed as the original attempt of using Substitute in OBS
  actually rewrites the used spec files on disk, not only on the
  fly and we ended up with packages Requiring cmake-mini (which is
  not installable on end user systems).</changelog>
  <changelog author="foss@grueninger.de" date="1584878400">- update to 3.17.0
  * cmake(1) gained a “Ninja Multi-Config” generator, which
    can be used to build multiple configurations at once.
  * cmake(1) gained a “–debug-find” command-line option to
    enable additional human-readable output on where find
    commands search.
  * Target link properties are now transitive over
    private dependencies on static libraries. See policy “CMP0099”.
  * cmake(1) gained a “-E rm” command-line tool that can
    be used to remove directories and files.
  Full changelog see
  https://blog.kitware.com/cmake-3-17-0-available-for-download/</changelog>
  <changelog author="sflees@suse.de" date="1584964800">- Many Leap packages don't build without -DCMAKE_SKIP_RPATH:BOOL=ON
  so leave this change to the next major version of Leap / SLE</changelog>
  <changelog author="sflees@suse.de" date="1585224000">- Fix mistake in previous change.</changelog>
  <changelog author="martin.sirringhaus@suse.com" date="1628251200">- copypac from SLE-15, because of Firefox91 (bsc#1188891)
  (Dependency chain: cmake3 -&gt; Rust -&gt; Firefox)</changelog>
  <changelog author="sflees@suse.de" date="1755864000">- Assertion failure due to improper validation of iteration variable
  counts in the foreach command processing logic
  (bsc#1248461, CVE-2025-9301)</changelog>
</package>
<package pkgid="efdbacd81f04850fa9df4e3e104157bb50e0e0b511948821c7cbde4d8f1b0a82" name="cryptctl" arch="src">
  <version epoch="0" ver="2.4" rel="31.1"/>
  <changelog author="hguo@suse.com" date="1465387200">- First version, only to help with building ISOs.
  Implement fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1467374400">- A preview version with most of the desired functions implemented:
  * Key database
  * Key RPC server
  * Client encryption and decryption routines
  Bump version to 1.1
  fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1468238400">- Implement mandatory features:
  * List and edit key records
  * Unlock file system via key record file
  * Use custom options to mount unlocked file system
  Enhance usability:
  * Make encryption procedure's pre-check more thorough
  * Improve overall command prompts
- Bump version to 1.2 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1470052800">- Implement mandatory features:
  * Encrypt empty directory skips backup steps.
  * Explain key revocation and TLS mechanisms in manual page.
- Bump version to 1.2.1 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1470225600">- Upon request, generate a self-signed TLS certificate for
  experimental purposes.
- Bump version to 1.2.2 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1471521600">- Implement mandatory enhancements:
  * Remove necessity for a backup directory to be involved for
    encryption routine.
  * Optimise certificate generation prompts.
  * Remove unused error messages and fix several of their typos.
  * Remove unnecessary safety checks.
  * Make the encryption routine work with btrfs and LVM.
- Bump version to 1.2.3 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1472817600">- Implement mandatory enhancements:
  * Make workflow across all sub-commands consistent in invocation
    style.
  * Implement auto-unlocking of encrypted disks.
  * Show key record usage and details on demand.
- Bump version to 1.2.4 for fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1474027200">- Implement mandatory enhancements:
  * Do not allow encrypting a remote file system.
  * Implement command for erasing an encrypted file system.
- Bump version to 1.2.5 for fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1479297600">- Upgrade to 1.2.6 for accumulated bug fixes (bsc#1006219):
  * Prevent user from attempting to encrypt a disk with mounted
    partitions, or an existing encrypted+opened disk.
  * Ensure CA path input is an absolute path.
  * Fix two mistakes in handling of timeout input.
  * Fix minor formatting issue in manual page.
  * Suppress consecutive failure messages in the journal of
    ReportAlive and AutoOnlineUnlockFS routines.</changelog>
  <changelog author="hguo@suse.com" date="1493380800">- Upgrade to 1.99pre that introduces a library for decoding, encoding,
  and serialisation operations of KMIP v1.3 for fate#322979.</changelog>
  <changelog author="hguo@suse.com" date="1494504000">- Upgrade to upstream release 2.0 that brings a protocol evolution
  together with several new features:
  * Optionally utilise an external KMIP-v1.3 compatible service to
    store actual encryption key.
  * Optionally verify client identity before serving its key requests.
  * Password is hashed before transmitting over TLS-secured channel.
  * Fix an issue that previously allowed a malicious administrator
    to craft RPC request to overwrite files outside of key database.
  Implemented accordint to fate#322979 and fate#322293.</changelog>
  <changelog author="hguo@suse.com" date="1496318400">- Upgrade to upstream release 2.1 that brings important enhancements
  in effort of implementing fate#322979:
  * Improve KMIP compatibility with key prefix names and proper
    serialisation of authentication header.
  * Fail over KMIP connection using a server list.
  * Destroy key on KMIP after its tracking record is erased from DB.</changelog>
  <changelog author="hguo@suse.com" date="1496836800">- Upgrade to upstream release 2.2 that brings important enhancements
  in effort of implementing fate#322979:
  * System administrator may now optionally turn off TLS certificate
    verification on KMIP server. Note that, certificate verification
    is enforced by default.
  * Improve handling of boolean answers from interactive command line.
  * Improve error handling in KMIP client.</changelog>
  <changelog author="hguo@suse.com" date="1503921600">- Upgrade to upstream release 2.3 that brings a new feature to allow
  system administrators to issue mount/umount commands to client
  computers via key server. (bsc#1056082)</changelog>
  <changelog author="hguo@suse.com" date="1508760000">- Add previously missing systemd service cryptctl-client.service
  into RPM content, continue with bsc#1056082.</changelog>
  <changelog author="rbrown@suse.com" date="1511438400">- Replace references to /var/adm/fillup-templates with new
  %_fillupdir macro (boo#1069468)</changelog>
  <changelog author="dimstar@opensuse.org" date="1580731200">- BuildRequire pkgconfig(systemd|udev) instead of systemd and udev:
  Allow OBS to shortcut through -mini flavors.
- Name the rpmlintrc file according the policy: cryptctl-rpmlintrc.</changelog>
  <changelog author="dimstar@opensuse.org" date="1597838400">- Use %{_udevrulesdir} instead of abusing %{_libexecdir}.</changelog>
  <changelog author="paolo.perego@suse.com" date="1626868800">- Fixed build errors adding a "go mod init"
- Binaries are now compiled with PIE support
- Also client service is symlinked so to avoid warnings</changelog>
  <changelog author="varkoly@suse.com" date="1652097600">- Update to version 2.4:
  * (bsc#1186226) - (CVE-2019-18906) client side password hashing is equivalent to clear text password storage
  * Fix authentication on all places.
  * Fix sysconfig variable name.
  * First step to use plain text password instead of hashed password.
  * Move repository into the SUSE github organization
  * decorate readme with more usage instructions
  * in RPC server, if client comes from localhost, remember its ipv4 localhost address instead of ipv6 address
  * Test clear expired commands in TestDB_UpdateSeenFlag
  * tell a record to clear expired pending commands upon saving a command result; introduce pending commands RPC test case
  * avoid hard coding 127.0.0.1 in host ID of alive message test; let system administrator mount and unmount disks by issuing these two commands on key server.</changelog>
</package>
<package pkgid="099ded5e8477f9599daf616b60dcfa066590ae6a28216cbbad6a651d0259d2e5" name="cryptctl" arch="x86_64">
  <version epoch="0" ver="2.4" rel="31.1"/>
  <changelog author="hguo@suse.com" date="1465387200">- First version, only to help with building ISOs.
  Implement fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1467374400">- A preview version with most of the desired functions implemented:
  * Key database
  * Key RPC server
  * Client encryption and decryption routines
  Bump version to 1.1
  fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1468238400">- Implement mandatory features:
  * List and edit key records
  * Unlock file system via key record file
  * Use custom options to mount unlocked file system
  Enhance usability:
  * Make encryption procedure's pre-check more thorough
  * Improve overall command prompts
- Bump version to 1.2 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1470052800">- Implement mandatory features:
  * Encrypt empty directory skips backup steps.
  * Explain key revocation and TLS mechanisms in manual page.
- Bump version to 1.2.1 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1470225600">- Upon request, generate a self-signed TLS certificate for
  experimental purposes.
- Bump version to 1.2.2 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1471521600">- Implement mandatory enhancements:
  * Remove necessity for a backup directory to be involved for
    encryption routine.
  * Optimise certificate generation prompts.
  * Remove unused error messages and fix several of their typos.
  * Remove unnecessary safety checks.
  * Make the encryption routine work with btrfs and LVM.
- Bump version to 1.2.3 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1472817600">- Implement mandatory enhancements:
  * Make workflow across all sub-commands consistent in invocation
    style.
  * Implement auto-unlocking of encrypted disks.
  * Show key record usage and details on demand.
- Bump version to 1.2.4 for fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1474027200">- Implement mandatory enhancements:
  * Do not allow encrypting a remote file system.
  * Implement command for erasing an encrypted file system.
- Bump version to 1.2.5 for fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1479297600">- Upgrade to 1.2.6 for accumulated bug fixes (bsc#1006219):
  * Prevent user from attempting to encrypt a disk with mounted
    partitions, or an existing encrypted+opened disk.
  * Ensure CA path input is an absolute path.
  * Fix two mistakes in handling of timeout input.
  * Fix minor formatting issue in manual page.
  * Suppress consecutive failure messages in the journal of
    ReportAlive and AutoOnlineUnlockFS routines.</changelog>
  <changelog author="hguo@suse.com" date="1493380800">- Upgrade to 1.99pre that introduces a library for decoding, encoding,
  and serialisation operations of KMIP v1.3 for fate#322979.</changelog>
  <changelog author="hguo@suse.com" date="1494504000">- Upgrade to upstream release 2.0 that brings a protocol evolution
  together with several new features:
  * Optionally utilise an external KMIP-v1.3 compatible service to
    store actual encryption key.
  * Optionally verify client identity before serving its key requests.
  * Password is hashed before transmitting over TLS-secured channel.
  * Fix an issue that previously allowed a malicious administrator
    to craft RPC request to overwrite files outside of key database.
  Implemented accordint to fate#322979 and fate#322293.</changelog>
  <changelog author="hguo@suse.com" date="1496318400">- Upgrade to upstream release 2.1 that brings important enhancements
  in effort of implementing fate#322979:
  * Improve KMIP compatibility with key prefix names and proper
    serialisation of authentication header.
  * Fail over KMIP connection using a server list.
  * Destroy key on KMIP after its tracking record is erased from DB.</changelog>
  <changelog author="hguo@suse.com" date="1496836800">- Upgrade to upstream release 2.2 that brings important enhancements
  in effort of implementing fate#322979:
  * System administrator may now optionally turn off TLS certificate
    verification on KMIP server. Note that, certificate verification
    is enforced by default.
  * Improve handling of boolean answers from interactive command line.
  * Improve error handling in KMIP client.</changelog>
  <changelog author="hguo@suse.com" date="1503921600">- Upgrade to upstream release 2.3 that brings a new feature to allow
  system administrators to issue mount/umount commands to client
  computers via key server. (bsc#1056082)</changelog>
  <changelog author="hguo@suse.com" date="1508760000">- Add previously missing systemd service cryptctl-client.service
  into RPM content, continue with bsc#1056082.</changelog>
  <changelog author="rbrown@suse.com" date="1511438400">- Replace references to /var/adm/fillup-templates with new
  %_fillupdir macro (boo#1069468)</changelog>
  <changelog author="dimstar@opensuse.org" date="1580731200">- BuildRequire pkgconfig(systemd|udev) instead of systemd and udev:
  Allow OBS to shortcut through -mini flavors.
- Name the rpmlintrc file according the policy: cryptctl-rpmlintrc.</changelog>
  <changelog author="dimstar@opensuse.org" date="1597838400">- Use %{_udevrulesdir} instead of abusing %{_libexecdir}.</changelog>
  <changelog author="paolo.perego@suse.com" date="1626868800">- Fixed build errors adding a "go mod init"
- Binaries are now compiled with PIE support
- Also client service is symlinked so to avoid warnings</changelog>
  <changelog author="varkoly@suse.com" date="1652097600">- Update to version 2.4:
  * (bsc#1186226) - (CVE-2019-18906) client side password hashing is equivalent to clear text password storage
  * Fix authentication on all places.
  * Fix sysconfig variable name.
  * First step to use plain text password instead of hashed password.
  * Move repository into the SUSE github organization
  * decorate readme with more usage instructions
  * in RPC server, if client comes from localhost, remember its ipv4 localhost address instead of ipv6 address
  * Test clear expired commands in TestDB_UpdateSeenFlag
  * tell a record to clear expired pending commands upon saving a command result; introduce pending commands RPC test case
  * avoid hard coding 127.0.0.1 in host ID of alive message test; let system administrator mount and unmount disks by issuing these two commands on key server.</changelog>
</package>
<package pkgid="d77745231bebe099f8ce05e7e18931b3740de5700b6266593c8f418dc52ad049" name="cryptctl-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.4" rel="31.1"/>
  <changelog author="hguo@suse.com" date="1465387200">- First version, only to help with building ISOs.
  Implement fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1467374400">- A preview version with most of the desired functions implemented:
  * Key database
  * Key RPC server
  * Client encryption and decryption routines
  Bump version to 1.1
  fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1468238400">- Implement mandatory features:
  * List and edit key records
  * Unlock file system via key record file
  * Use custom options to mount unlocked file system
  Enhance usability:
  * Make encryption procedure's pre-check more thorough
  * Improve overall command prompts
- Bump version to 1.2 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1470052800">- Implement mandatory features:
  * Encrypt empty directory skips backup steps.
  * Explain key revocation and TLS mechanisms in manual page.
- Bump version to 1.2.1 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1470225600">- Upon request, generate a self-signed TLS certificate for
  experimental purposes.
- Bump version to 1.2.2 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1471521600">- Implement mandatory enhancements:
  * Remove necessity for a backup directory to be involved for
    encryption routine.
  * Optimise certificate generation prompts.
  * Remove unused error messages and fix several of their typos.
  * Remove unnecessary safety checks.
  * Make the encryption routine work with btrfs and LVM.
- Bump version to 1.2.3 fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1472817600">- Implement mandatory enhancements:
  * Make workflow across all sub-commands consistent in invocation
    style.
  * Implement auto-unlocking of encrypted disks.
  * Show key record usage and details on demand.
- Bump version to 1.2.4 for fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1474027200">- Implement mandatory enhancements:
  * Do not allow encrypting a remote file system.
  * Implement command for erasing an encrypted file system.
- Bump version to 1.2.5 for fate#320367.</changelog>
  <changelog author="hguo@suse.com" date="1479297600">- Upgrade to 1.2.6 for accumulated bug fixes (bsc#1006219):
  * Prevent user from attempting to encrypt a disk with mounted
    partitions, or an existing encrypted+opened disk.
  * Ensure CA path input is an absolute path.
  * Fix two mistakes in handling of timeout input.
  * Fix minor formatting issue in manual page.
  * Suppress consecutive failure messages in the journal of
    ReportAlive and AutoOnlineUnlockFS routines.</changelog>
  <changelog author="hguo@suse.com" date="1493380800">- Upgrade to 1.99pre that introduces a library for decoding, encoding,
  and serialisation operations of KMIP v1.3 for fate#322979.</changelog>
  <changelog author="hguo@suse.com" date="1494504000">- Upgrade to upstream release 2.0 that brings a protocol evolution
  together with several new features:
  * Optionally utilise an external KMIP-v1.3 compatible service to
    store actual encryption key.
  * Optionally verify client identity before serving its key requests.
  * Password is hashed before transmitting over TLS-secured channel.
  * Fix an issue that previously allowed a malicious administrator
    to craft RPC request to overwrite files outside of key database.
  Implemented accordint to fate#322979 and fate#322293.</changelog>
  <changelog author="hguo@suse.com" date="1496318400">- Upgrade to upstream release 2.1 that brings important enhancements
  in effort of implementing fate#322979:
  * Improve KMIP compatibility with key prefix names and proper
    serialisation of authentication header.
  * Fail over KMIP connection using a server list.
  * Destroy key on KMIP after its tracking record is erased from DB.</changelog>
  <changelog author="hguo@suse.com" date="1496836800">- Upgrade to upstream release 2.2 that brings important enhancements
  in effort of implementing fate#322979:
  * System administrator may now optionally turn off TLS certificate
    verification on KMIP server. Note that, certificate verification
    is enforced by default.
  * Improve handling of boolean answers from interactive command line.
  * Improve error handling in KMIP client.</changelog>
  <changelog author="hguo@suse.com" date="1503921600">- Upgrade to upstream release 2.3 that brings a new feature to allow
  system administrators to issue mount/umount commands to client
  computers via key server. (bsc#1056082)</changelog>
  <changelog author="hguo@suse.com" date="1508760000">- Add previously missing systemd service cryptctl-client.service
  into RPM content, continue with bsc#1056082.</changelog>
  <changelog author="rbrown@suse.com" date="1511438400">- Replace references to /var/adm/fillup-templates with new
  %_fillupdir macro (boo#1069468)</changelog>
  <changelog author="dimstar@opensuse.org" date="1580731200">- BuildRequire pkgconfig(systemd|udev) instead of systemd and udev:
  Allow OBS to shortcut through -mini flavors.
- Name the rpmlintrc file according the policy: cryptctl-rpmlintrc.</changelog>
  <changelog author="dimstar@opensuse.org" date="1597838400">- Use %{_udevrulesdir} instead of abusing %{_libexecdir}.</changelog>
  <changelog author="paolo.perego@suse.com" date="1626868800">- Fixed build errors adding a "go mod init"
- Binaries are now compiled with PIE support
- Also client service is symlinked so to avoid warnings</changelog>
  <changelog author="varkoly@suse.com" date="1652097600">- Update to version 2.4:
  * (bsc#1186226) - (CVE-2019-18906) client side password hashing is equivalent to clear text password storage
  * Fix authentication on all places.
  * Fix sysconfig variable name.
  * First step to use plain text password instead of hashed password.
  * Move repository into the SUSE github organization
  * decorate readme with more usage instructions
  * in RPC server, if client comes from localhost, remember its ipv4 localhost address instead of ipv6 address
  * Test clear expired commands in TestDB_UpdateSeenFlag
  * tell a record to clear expired pending commands upon saving a command result; introduce pending commands RPC test case
  * avoid hard coding 127.0.0.1 in host ID of alive message test; let system administrator mount and unmount disks by issuing these two commands on key server.</changelog>
</package>
<package pkgid="a78366f8ef729bce7037951b85590efcb7462247a91e74dcf6f91aaddd593ec3" name="cryptsetup" arch="src">
  <version epoch="0" ver="2.7.5" rel="220.1"/>
  <changelog author="lnussel@suse.de" date="1631793600">- cryptsetup 2.4.1
  * Fix compilation for libc implementations without dlvsym().
  * Fix compilation and tests on systems with non-standard libraries
  * Try to workaround some issues on systems without udev support.
  * Fixes for OpenSSL3 crypto backend (including FIPS mode).
  * Print error message when assigning a token to an inactive keyslot.
  * Fix offset bug in LUKS2 encryption code if --offset option was used.
  * Do not allow LUKS2 decryption for devices with data offset.
  * Fix LUKS1 cryptsetup repair command for some specific problems.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1637236800">- cryptsetup 2.4.2:
  * Fix possible large memory allocation if LUKS2 header size is
    invalid.
  * Fix memory corruption in debug message printing LUKS2
    checksum.
  * veritysetup: remove link to the UUID library for the static
    build.
  * Remove link to pwquality library for integritysetup and
    veritysetup. These tools do not read passphrases.
  * OpenSSL3 backend: avoid remaining deprecated calls in API.
    Crypto backend no longer use API deprecated in OpenSSL 3.0
  * Check if kernel device-mapper create device failed in an early
    phase. This happens when a concurrent creation of device-mapper
    devices meets in the very early state.
  * Do not set compiler optimization flag for Argon2 KDF if the
    memory wipe is implemented in libc.
  * Do not attempt to unload LUKS2 tokens if external tokens are
    disabled. This allows building a static binary with
  - -disable-external-tokens.
  * LUKS convert: also check sysfs for device activity.
    If udev symlink is missing, code fallbacks to sysfs scan to
    prevent data corruption for the active device.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1642161600">- cryptsetup 2.4.3:
  * Fix possible attacks against data confidentiality through
    LUKS2 online reencryption extension crash recovery
    CVE-2021-4122, boo#1194469
  * Add configure option --disable-luks2-reencryption to completely
    disable LUKS2 reencryption code.
  * Improve internal metadata validation code for reencryption
    metadata
  * Add updated documentation for LUKS2 On-Disk Format
    Specification version 1.1.0
  * Fix support for bitlk (BitLocker compatible) startup key with
    new  metadata entry introduced in Windows 11
  * Fix space restriction for LUKS2 reencryption with data shift</changelog>
  <changelog author="lnussel@suse.de" date="1661169600">- cryptsetup 2.5.0:
  * Split manual pages into per-action pages and use AsciiDoc format.
  * Remove cryptsetup-reencrypt tool from the project and move reencryption
    to already existing "cryptsetup reencrypt" command.
    If you need to emulate the old cryptsetup-reencrypt binary, use simple
    wrappers script running "exec cryptsetup reencrypt $@".
  * LUKS2: implement --decryption option that allows LUKS removal.
  * Fix decryption operation with --active-name option and restrict
    it to be used only with LUKS2.
  * Do not refresh reencryption digest when not needed.
    This should speed up the reencryption resume process.
  * Store proper resilience data in LUKS2 reencrypt initialization.
    Resuming reencryption now does not require specification of resilience
    type parameters if these are the same as during initialization.
  * Properly wipe the unused area after reencryption with datashift in
    the forward direction.
  * Check datashift value against larger sector size.
    For example, it could cause an issue if misaligned 4K sector appears
    during decryption.
  * Do not allow sector size increase reencryption in offline mode.
  * Do not allow dangerous sector size change during reencryption.
  * Ask the user for confirmation before resuming reencryption.
  * Do not resume reencryption with conflicting parameters.
  * Add --force-offline-reencrypt option.
  * Do not allow nested encryption in LUKS reencrypt.
  * Support all options allowed with luksFormat with encrypt action.
  * Add resize action to integritysetup.
  * Remove obsolete dracut plugin reencryption example.
  * Fix possible keyslot area size overflow during conversion to LUKS2.
  * Allow use of --header option for cryptsetup close.
  * Fix activation of LUKS2 device with integrity and detached header.
  * Add ZEROOUT IOCTL support for crypt_wipe API call.
  * VERITY: set loopback sector size according to dm-verity block sizes.
  * veritysetup: dump device sizes.
  * LUKS2 token: prefer token PIN query before passphrase in some cases.
    When a user provides --token-type or specific --token-id, a token PIN
    query is preferred to a passphrase query.
  * LUKS2 token: allow tokens to be replaced with --token-replace option
    for cryptsetup token command.
  * LUKS2 token: do not continue operation when interrupted in PIN prompt.
  * Add --progress-json parameter to utilities.
  * Add support for --key-slot option in luksResume action.
- move man pages to separate subpackage
- drop backports handling</changelog>
  <changelog author="luca.boccassi@gmail.com" date="1663070400">- Add virtual provides for 'integritysetup' and 'veritysetup' to match
  package names provided by Fedora/RHEL, to allow the same set of
  dependencies to be used across all RPM distributions.</changelog>
  <changelog author="info@paolostivanin.com" date="1669636800">- cryptsetup 2.6.0:
  * Introduce support for handling macOS FileVault2 devices (FVAULT2).
  * libcryptsetup: no longer use global memory locking through mlockall()
  * libcryptsetup: process priority is increased only for key derivation
    (PBKDF) calls.
  * Add new LUKS keyslot context handling functions and API.
  * The volume key may now be extracted using a passphrase, keyfile, or
    token. For LUKS devices, it also returns the volume key after
    a successful crypt_format call.
  * Fix --disable-luks2-reencryption configuration option.
  * cryptsetup: Print a better error message and warning if the format
    produces an image without space available for data.
  * Print error if anti-forensic LUKS2 hash setting is not available.
    If the specified hash was not available, activation quietly failed.
  * Fix internal crypt segment compare routine if the user
    specified cipher in kernel format (capi: prefix).
  * cryptsetup: Add token unassign action.
    This action allows removing token binding on specific keyslot.
  * veritysetup: add support for --use-tasklets option.
    This option sets try_verify_in_tasklet kernel dm-verity option
    (available since Linux kernel 6.0) to allow some performance
    improvement on specific systems.
  * Provide pkgconfig Require.private settings.
    While we do not completely provide static build on udev systems,
    it helps produce statically linked binaries in certain situations.
  * Always update automake library files if autogen.sh is run.
    For several releases, we distributed older automake scripts by mistake.
  * reencryption: Fix user defined moved segment size in LUKS2 decryption.
    The --hotzone-size argument was ignored in cases where the actual data
    size was less than the original LUKS2 data offset.
  * Delegate FIPS mode detection to configured crypto backend.
    System FIPS mode check no longer depends on /etc/system-fips file.
  * Update documentation, including FAQ and man pages.</changelog>
  <changelog author="lnussel@suse.com" date="1672142400">- Replace transitional %usrmerged macro with regular version check (boo#1206798)</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1676203200">- cryptsetup 2.6.1
  * bitlk: Fixes for BitLocker-compatible on-disk metadata parser
  * Fix possible iteration overflow in OpenSSL2 PBKDF2 crypto
    backend
  * portability and compilation fixes
  * verity: Fix possible hash offset setting overflow.
  * bitlk: Fix use of startup BEK key on big-endian platforms.
  * Do not initiate encryption (reencryption command) when the
    header and data devices are the same. If data device reduction
    is not requsted, this leads to data corruption since LUKS
    metadata was written over the data device.
  * Fix possible memory leak if crypt_load() fails.
  * Always use passphrases with a minimal 8 chars length for
    benchmarking, as used in some implementation of FIPS mode</changelog>
  <changelog author="pmonreal@suse.com" date="1686744000">- FIPS: Remove not needed libcryptsetup12-hmac package that contains
  the HMAC checksums for integrity checking for FIPS. [bsc#1185116]
  * Remove the cryptsetup-rpmlintrc file.
  * Remove not needed fipscheck dependency.</changelog>
  <changelog author="pmonreal@suse.com" date="1686744001">- Enable running the regression test suite.
- Force a regeneration of the man pages from AsciiDoc.
- Add LUKS1 and LUKS2 On-Disk Format Specification pdfs to doc.</changelog>
  <changelog author="pmonreal@suse.com" date="1689249600">- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1706529600">- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1710331200">- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1712664000">- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.</changelog>
  <changelog author="pvorel@suse.cz" date="1720785600">- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).</changelog>
  <changelog author="pmonreal@suse.com" date="1722340800">- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.</changelog>
  <changelog author="martin.schreiner@suse.com" date="1722427200">- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.</changelog>
  <changelog author="meissner@suse.com" date="1725019200">- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)</changelog>
  <changelog author="pmonreal@suse.com" date="1726228800">- Update to 2.7.5:
  * Fix possible online reencryption data corruption (only in 2.7.x).
    In some situations (initializing a suspended device-mapper device),
    cryptsetup disabled direct-io device access. This caused unsafe
    online reencryption operations that could lead to data corruption.
    The code now adds strict checks (and aborts the operation) and
    changes direct-io detection code to prevent data corruption.
  * Fix a clang compilation error in SSH token plugin.
    As clang linker treats missing symbols as errors, the linker phase
    for the SSH token failed as the optional cryptsetup_token_buffer_free
    was not defined.
  * Fix crypto backend initialization in crypt_format_luks2_opal API call.</changelog>
  <changelog author="pmonreal@suse.com" date="1741953600">- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.</changelog>
</package>
<package pkgid="130f0722ef30dd052ec0e2a25768b2d5e40a1b2f1b75a167332450f5e6b65a93" name="cryptsetup" arch="x86_64">
  <version epoch="0" ver="2.7.5" rel="220.1"/>
  <changelog author="lnussel@suse.de" date="1631793600">- cryptsetup 2.4.1
  * Fix compilation for libc implementations without dlvsym().
  * Fix compilation and tests on systems with non-standard libraries
  * Try to workaround some issues on systems without udev support.
  * Fixes for OpenSSL3 crypto backend (including FIPS mode).
  * Print error message when assigning a token to an inactive keyslot.
  * Fix offset bug in LUKS2 encryption code if --offset option was used.
  * Do not allow LUKS2 decryption for devices with data offset.
  * Fix LUKS1 cryptsetup repair command for some specific problems.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1637236800">- cryptsetup 2.4.2:
  * Fix possible large memory allocation if LUKS2 header size is
    invalid.
  * Fix memory corruption in debug message printing LUKS2
    checksum.
  * veritysetup: remove link to the UUID library for the static
    build.
  * Remove link to pwquality library for integritysetup and
    veritysetup. These tools do not read passphrases.
  * OpenSSL3 backend: avoid remaining deprecated calls in API.
    Crypto backend no longer use API deprecated in OpenSSL 3.0
  * Check if kernel device-mapper create device failed in an early
    phase. This happens when a concurrent creation of device-mapper
    devices meets in the very early state.
  * Do not set compiler optimization flag for Argon2 KDF if the
    memory wipe is implemented in libc.
  * Do not attempt to unload LUKS2 tokens if external tokens are
    disabled. This allows building a static binary with
  - -disable-external-tokens.
  * LUKS convert: also check sysfs for device activity.
    If udev symlink is missing, code fallbacks to sysfs scan to
    prevent data corruption for the active device.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1642161600">- cryptsetup 2.4.3:
  * Fix possible attacks against data confidentiality through
    LUKS2 online reencryption extension crash recovery
    CVE-2021-4122, boo#1194469
  * Add configure option --disable-luks2-reencryption to completely
    disable LUKS2 reencryption code.
  * Improve internal metadata validation code for reencryption
    metadata
  * Add updated documentation for LUKS2 On-Disk Format
    Specification version 1.1.0
  * Fix support for bitlk (BitLocker compatible) startup key with
    new  metadata entry introduced in Windows 11
  * Fix space restriction for LUKS2 reencryption with data shift</changelog>
  <changelog author="lnussel@suse.de" date="1661169600">- cryptsetup 2.5.0:
  * Split manual pages into per-action pages and use AsciiDoc format.
  * Remove cryptsetup-reencrypt tool from the project and move reencryption
    to already existing "cryptsetup reencrypt" command.
    If you need to emulate the old cryptsetup-reencrypt binary, use simple
    wrappers script running "exec cryptsetup reencrypt $@".
  * LUKS2: implement --decryption option that allows LUKS removal.
  * Fix decryption operation with --active-name option and restrict
    it to be used only with LUKS2.
  * Do not refresh reencryption digest when not needed.
    This should speed up the reencryption resume process.
  * Store proper resilience data in LUKS2 reencrypt initialization.
    Resuming reencryption now does not require specification of resilience
    type parameters if these are the same as during initialization.
  * Properly wipe the unused area after reencryption with datashift in
    the forward direction.
  * Check datashift value against larger sector size.
    For example, it could cause an issue if misaligned 4K sector appears
    during decryption.
  * Do not allow sector size increase reencryption in offline mode.
  * Do not allow dangerous sector size change during reencryption.
  * Ask the user for confirmation before resuming reencryption.
  * Do not resume reencryption with conflicting parameters.
  * Add --force-offline-reencrypt option.
  * Do not allow nested encryption in LUKS reencrypt.
  * Support all options allowed with luksFormat with encrypt action.
  * Add resize action to integritysetup.
  * Remove obsolete dracut plugin reencryption example.
  * Fix possible keyslot area size overflow during conversion to LUKS2.
  * Allow use of --header option for cryptsetup close.
  * Fix activation of LUKS2 device with integrity and detached header.
  * Add ZEROOUT IOCTL support for crypt_wipe API call.
  * VERITY: set loopback sector size according to dm-verity block sizes.
  * veritysetup: dump device sizes.
  * LUKS2 token: prefer token PIN query before passphrase in some cases.
    When a user provides --token-type or specific --token-id, a token PIN
    query is preferred to a passphrase query.
  * LUKS2 token: allow tokens to be replaced with --token-replace option
    for cryptsetup token command.
  * LUKS2 token: do not continue operation when interrupted in PIN prompt.
  * Add --progress-json parameter to utilities.
  * Add support for --key-slot option in luksResume action.
- move man pages to separate subpackage
- drop backports handling</changelog>
  <changelog author="luca.boccassi@gmail.com" date="1663070400">- Add virtual provides for 'integritysetup' and 'veritysetup' to match
  package names provided by Fedora/RHEL, to allow the same set of
  dependencies to be used across all RPM distributions.</changelog>
  <changelog author="info@paolostivanin.com" date="1669636800">- cryptsetup 2.6.0:
  * Introduce support for handling macOS FileVault2 devices (FVAULT2).
  * libcryptsetup: no longer use global memory locking through mlockall()
  * libcryptsetup: process priority is increased only for key derivation
    (PBKDF) calls.
  * Add new LUKS keyslot context handling functions and API.
  * The volume key may now be extracted using a passphrase, keyfile, or
    token. For LUKS devices, it also returns the volume key after
    a successful crypt_format call.
  * Fix --disable-luks2-reencryption configuration option.
  * cryptsetup: Print a better error message and warning if the format
    produces an image without space available for data.
  * Print error if anti-forensic LUKS2 hash setting is not available.
    If the specified hash was not available, activation quietly failed.
  * Fix internal crypt segment compare routine if the user
    specified cipher in kernel format (capi: prefix).
  * cryptsetup: Add token unassign action.
    This action allows removing token binding on specific keyslot.
  * veritysetup: add support for --use-tasklets option.
    This option sets try_verify_in_tasklet kernel dm-verity option
    (available since Linux kernel 6.0) to allow some performance
    improvement on specific systems.
  * Provide pkgconfig Require.private settings.
    While we do not completely provide static build on udev systems,
    it helps produce statically linked binaries in certain situations.
  * Always update automake library files if autogen.sh is run.
    For several releases, we distributed older automake scripts by mistake.
  * reencryption: Fix user defined moved segment size in LUKS2 decryption.
    The --hotzone-size argument was ignored in cases where the actual data
    size was less than the original LUKS2 data offset.
  * Delegate FIPS mode detection to configured crypto backend.
    System FIPS mode check no longer depends on /etc/system-fips file.
  * Update documentation, including FAQ and man pages.</changelog>
  <changelog author="lnussel@suse.com" date="1672142400">- Replace transitional %usrmerged macro with regular version check (boo#1206798)</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1676203200">- cryptsetup 2.6.1
  * bitlk: Fixes for BitLocker-compatible on-disk metadata parser
  * Fix possible iteration overflow in OpenSSL2 PBKDF2 crypto
    backend
  * portability and compilation fixes
  * verity: Fix possible hash offset setting overflow.
  * bitlk: Fix use of startup BEK key on big-endian platforms.
  * Do not initiate encryption (reencryption command) when the
    header and data devices are the same. If data device reduction
    is not requsted, this leads to data corruption since LUKS
    metadata was written over the data device.
  * Fix possible memory leak if crypt_load() fails.
  * Always use passphrases with a minimal 8 chars length for
    benchmarking, as used in some implementation of FIPS mode</changelog>
  <changelog author="pmonreal@suse.com" date="1686744000">- FIPS: Remove not needed libcryptsetup12-hmac package that contains
  the HMAC checksums for integrity checking for FIPS. [bsc#1185116]
  * Remove the cryptsetup-rpmlintrc file.
  * Remove not needed fipscheck dependency.</changelog>
  <changelog author="pmonreal@suse.com" date="1686744001">- Enable running the regression test suite.
- Force a regeneration of the man pages from AsciiDoc.
- Add LUKS1 and LUKS2 On-Disk Format Specification pdfs to doc.</changelog>
  <changelog author="pmonreal@suse.com" date="1689249600">- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1706529600">- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1710331200">- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1712664000">- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.</changelog>
  <changelog author="pvorel@suse.cz" date="1720785600">- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).</changelog>
  <changelog author="pmonreal@suse.com" date="1722340800">- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.</changelog>
  <changelog author="martin.schreiner@suse.com" date="1722427200">- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.</changelog>
  <changelog author="meissner@suse.com" date="1725019200">- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)</changelog>
  <changelog author="pmonreal@suse.com" date="1726228800">- Update to 2.7.5:
  * Fix possible online reencryption data corruption (only in 2.7.x).
    In some situations (initializing a suspended device-mapper device),
    cryptsetup disabled direct-io device access. This caused unsafe
    online reencryption operations that could lead to data corruption.
    The code now adds strict checks (and aborts the operation) and
    changes direct-io detection code to prevent data corruption.
  * Fix a clang compilation error in SSH token plugin.
    As clang linker treats missing symbols as errors, the linker phase
    for the SSH token failed as the optional cryptsetup_token_buffer_free
    was not defined.
  * Fix crypto backend initialization in crypt_format_luks2_opal API call.</changelog>
  <changelog author="pmonreal@suse.com" date="1741953600">- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.</changelog>
</package>
<package pkgid="39d2d56e63f0829a9ef568c460fd5b9b5f438d0aace99d7b14d4ee3d9c4cc59c" name="cryptsetup-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.7.5" rel="220.1"/>
  <changelog author="lnussel@suse.de" date="1631793600">- cryptsetup 2.4.1
  * Fix compilation for libc implementations without dlvsym().
  * Fix compilation and tests on systems with non-standard libraries
  * Try to workaround some issues on systems without udev support.
  * Fixes for OpenSSL3 crypto backend (including FIPS mode).
  * Print error message when assigning a token to an inactive keyslot.
  * Fix offset bug in LUKS2 encryption code if --offset option was used.
  * Do not allow LUKS2 decryption for devices with data offset.
  * Fix LUKS1 cryptsetup repair command for some specific problems.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1637236800">- cryptsetup 2.4.2:
  * Fix possible large memory allocation if LUKS2 header size is
    invalid.
  * Fix memory corruption in debug message printing LUKS2
    checksum.
  * veritysetup: remove link to the UUID library for the static
    build.
  * Remove link to pwquality library for integritysetup and
    veritysetup. These tools do not read passphrases.
  * OpenSSL3 backend: avoid remaining deprecated calls in API.
    Crypto backend no longer use API deprecated in OpenSSL 3.0
  * Check if kernel device-mapper create device failed in an early
    phase. This happens when a concurrent creation of device-mapper
    devices meets in the very early state.
  * Do not set compiler optimization flag for Argon2 KDF if the
    memory wipe is implemented in libc.
  * Do not attempt to unload LUKS2 tokens if external tokens are
    disabled. This allows building a static binary with
  - -disable-external-tokens.
  * LUKS convert: also check sysfs for device activity.
    If udev symlink is missing, code fallbacks to sysfs scan to
    prevent data corruption for the active device.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1642161600">- cryptsetup 2.4.3:
  * Fix possible attacks against data confidentiality through
    LUKS2 online reencryption extension crash recovery
    CVE-2021-4122, boo#1194469
  * Add configure option --disable-luks2-reencryption to completely
    disable LUKS2 reencryption code.
  * Improve internal metadata validation code for reencryption
    metadata
  * Add updated documentation for LUKS2 On-Disk Format
    Specification version 1.1.0
  * Fix support for bitlk (BitLocker compatible) startup key with
    new  metadata entry introduced in Windows 11
  * Fix space restriction for LUKS2 reencryption with data shift</changelog>
  <changelog author="lnussel@suse.de" date="1661169600">- cryptsetup 2.5.0:
  * Split manual pages into per-action pages and use AsciiDoc format.
  * Remove cryptsetup-reencrypt tool from the project and move reencryption
    to already existing "cryptsetup reencrypt" command.
    If you need to emulate the old cryptsetup-reencrypt binary, use simple
    wrappers script running "exec cryptsetup reencrypt $@".
  * LUKS2: implement --decryption option that allows LUKS removal.
  * Fix decryption operation with --active-name option and restrict
    it to be used only with LUKS2.
  * Do not refresh reencryption digest when not needed.
    This should speed up the reencryption resume process.
  * Store proper resilience data in LUKS2 reencrypt initialization.
    Resuming reencryption now does not require specification of resilience
    type parameters if these are the same as during initialization.
  * Properly wipe the unused area after reencryption with datashift in
    the forward direction.
  * Check datashift value against larger sector size.
    For example, it could cause an issue if misaligned 4K sector appears
    during decryption.
  * Do not allow sector size increase reencryption in offline mode.
  * Do not allow dangerous sector size change during reencryption.
  * Ask the user for confirmation before resuming reencryption.
  * Do not resume reencryption with conflicting parameters.
  * Add --force-offline-reencrypt option.
  * Do not allow nested encryption in LUKS reencrypt.
  * Support all options allowed with luksFormat with encrypt action.
  * Add resize action to integritysetup.
  * Remove obsolete dracut plugin reencryption example.
  * Fix possible keyslot area size overflow during conversion to LUKS2.
  * Allow use of --header option for cryptsetup close.
  * Fix activation of LUKS2 device with integrity and detached header.
  * Add ZEROOUT IOCTL support for crypt_wipe API call.
  * VERITY: set loopback sector size according to dm-verity block sizes.
  * veritysetup: dump device sizes.
  * LUKS2 token: prefer token PIN query before passphrase in some cases.
    When a user provides --token-type or specific --token-id, a token PIN
    query is preferred to a passphrase query.
  * LUKS2 token: allow tokens to be replaced with --token-replace option
    for cryptsetup token command.
  * LUKS2 token: do not continue operation when interrupted in PIN prompt.
  * Add --progress-json parameter to utilities.
  * Add support for --key-slot option in luksResume action.
- move man pages to separate subpackage
- drop backports handling</changelog>
  <changelog author="luca.boccassi@gmail.com" date="1663070400">- Add virtual provides for 'integritysetup' and 'veritysetup' to match
  package names provided by Fedora/RHEL, to allow the same set of
  dependencies to be used across all RPM distributions.</changelog>
  <changelog author="info@paolostivanin.com" date="1669636800">- cryptsetup 2.6.0:
  * Introduce support for handling macOS FileVault2 devices (FVAULT2).
  * libcryptsetup: no longer use global memory locking through mlockall()
  * libcryptsetup: process priority is increased only for key derivation
    (PBKDF) calls.
  * Add new LUKS keyslot context handling functions and API.
  * The volume key may now be extracted using a passphrase, keyfile, or
    token. For LUKS devices, it also returns the volume key after
    a successful crypt_format call.
  * Fix --disable-luks2-reencryption configuration option.
  * cryptsetup: Print a better error message and warning if the format
    produces an image without space available for data.
  * Print error if anti-forensic LUKS2 hash setting is not available.
    If the specified hash was not available, activation quietly failed.
  * Fix internal crypt segment compare routine if the user
    specified cipher in kernel format (capi: prefix).
  * cryptsetup: Add token unassign action.
    This action allows removing token binding on specific keyslot.
  * veritysetup: add support for --use-tasklets option.
    This option sets try_verify_in_tasklet kernel dm-verity option
    (available since Linux kernel 6.0) to allow some performance
    improvement on specific systems.
  * Provide pkgconfig Require.private settings.
    While we do not completely provide static build on udev systems,
    it helps produce statically linked binaries in certain situations.
  * Always update automake library files if autogen.sh is run.
    For several releases, we distributed older automake scripts by mistake.
  * reencryption: Fix user defined moved segment size in LUKS2 decryption.
    The --hotzone-size argument was ignored in cases where the actual data
    size was less than the original LUKS2 data offset.
  * Delegate FIPS mode detection to configured crypto backend.
    System FIPS mode check no longer depends on /etc/system-fips file.
  * Update documentation, including FAQ and man pages.</changelog>
  <changelog author="lnussel@suse.com" date="1672142400">- Replace transitional %usrmerged macro with regular version check (boo#1206798)</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1676203200">- cryptsetup 2.6.1
  * bitlk: Fixes for BitLocker-compatible on-disk metadata parser
  * Fix possible iteration overflow in OpenSSL2 PBKDF2 crypto
    backend
  * portability and compilation fixes
  * verity: Fix possible hash offset setting overflow.
  * bitlk: Fix use of startup BEK key on big-endian platforms.
  * Do not initiate encryption (reencryption command) when the
    header and data devices are the same. If data device reduction
    is not requsted, this leads to data corruption since LUKS
    metadata was written over the data device.
  * Fix possible memory leak if crypt_load() fails.
  * Always use passphrases with a minimal 8 chars length for
    benchmarking, as used in some implementation of FIPS mode</changelog>
  <changelog author="pmonreal@suse.com" date="1686744000">- FIPS: Remove not needed libcryptsetup12-hmac package that contains
  the HMAC checksums for integrity checking for FIPS. [bsc#1185116]
  * Remove the cryptsetup-rpmlintrc file.
  * Remove not needed fipscheck dependency.</changelog>
  <changelog author="pmonreal@suse.com" date="1686744001">- Enable running the regression test suite.
- Force a regeneration of the man pages from AsciiDoc.
- Add LUKS1 and LUKS2 On-Disk Format Specification pdfs to doc.</changelog>
  <changelog author="pmonreal@suse.com" date="1689249600">- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1706529600">- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1710331200">- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1712664000">- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.</changelog>
  <changelog author="pvorel@suse.cz" date="1720785600">- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).</changelog>
  <changelog author="pmonreal@suse.com" date="1722340800">- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.</changelog>
  <changelog author="martin.schreiner@suse.com" date="1722427200">- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.</changelog>
  <changelog author="meissner@suse.com" date="1725019200">- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)</changelog>
  <changelog author="pmonreal@suse.com" date="1726228800">- Update to 2.7.5:
  * Fix possible online reencryption data corruption (only in 2.7.x).
    In some situations (initializing a suspended device-mapper device),
    cryptsetup disabled direct-io device access. This caused unsafe
    online reencryption operations that could lead to data corruption.
    The code now adds strict checks (and aborts the operation) and
    changes direct-io detection code to prevent data corruption.
  * Fix a clang compilation error in SSH token plugin.
    As clang linker treats missing symbols as errors, the linker phase
    for the SSH token failed as the optional cryptsetup_token_buffer_free
    was not defined.
  * Fix crypto backend initialization in crypt_format_luks2_opal API call.</changelog>
  <changelog author="pmonreal@suse.com" date="1741953600">- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.</changelog>
</package>
<package pkgid="6e3199b07f6da171866d5254552ae7078bcec23f8ef78e56443cf86ce9356d69" name="cryptsetup-debugsource" arch="x86_64">
  <version epoch="0" ver="2.7.5" rel="220.1"/>
  <changelog author="lnussel@suse.de" date="1631793600">- cryptsetup 2.4.1
  * Fix compilation for libc implementations without dlvsym().
  * Fix compilation and tests on systems with non-standard libraries
  * Try to workaround some issues on systems without udev support.
  * Fixes for OpenSSL3 crypto backend (including FIPS mode).
  * Print error message when assigning a token to an inactive keyslot.
  * Fix offset bug in LUKS2 encryption code if --offset option was used.
  * Do not allow LUKS2 decryption for devices with data offset.
  * Fix LUKS1 cryptsetup repair command for some specific problems.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1637236800">- cryptsetup 2.4.2:
  * Fix possible large memory allocation if LUKS2 header size is
    invalid.
  * Fix memory corruption in debug message printing LUKS2
    checksum.
  * veritysetup: remove link to the UUID library for the static
    build.
  * Remove link to pwquality library for integritysetup and
    veritysetup. These tools do not read passphrases.
  * OpenSSL3 backend: avoid remaining deprecated calls in API.
    Crypto backend no longer use API deprecated in OpenSSL 3.0
  * Check if kernel device-mapper create device failed in an early
    phase. This happens when a concurrent creation of device-mapper
    devices meets in the very early state.
  * Do not set compiler optimization flag for Argon2 KDF if the
    memory wipe is implemented in libc.
  * Do not attempt to unload LUKS2 tokens if external tokens are
    disabled. This allows building a static binary with
  - -disable-external-tokens.
  * LUKS convert: also check sysfs for device activity.
    If udev symlink is missing, code fallbacks to sysfs scan to
    prevent data corruption for the active device.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1642161600">- cryptsetup 2.4.3:
  * Fix possible attacks against data confidentiality through
    LUKS2 online reencryption extension crash recovery
    CVE-2021-4122, boo#1194469
  * Add configure option --disable-luks2-reencryption to completely
    disable LUKS2 reencryption code.
  * Improve internal metadata validation code for reencryption
    metadata
  * Add updated documentation for LUKS2 On-Disk Format
    Specification version 1.1.0
  * Fix support for bitlk (BitLocker compatible) startup key with
    new  metadata entry introduced in Windows 11
  * Fix space restriction for LUKS2 reencryption with data shift</changelog>
  <changelog author="lnussel@suse.de" date="1661169600">- cryptsetup 2.5.0:
  * Split manual pages into per-action pages and use AsciiDoc format.
  * Remove cryptsetup-reencrypt tool from the project and move reencryption
    to already existing "cryptsetup reencrypt" command.
    If you need to emulate the old cryptsetup-reencrypt binary, use simple
    wrappers script running "exec cryptsetup reencrypt $@".
  * LUKS2: implement --decryption option that allows LUKS removal.
  * Fix decryption operation with --active-name option and restrict
    it to be used only with LUKS2.
  * Do not refresh reencryption digest when not needed.
    This should speed up the reencryption resume process.
  * Store proper resilience data in LUKS2 reencrypt initialization.
    Resuming reencryption now does not require specification of resilience
    type parameters if these are the same as during initialization.
  * Properly wipe the unused area after reencryption with datashift in
    the forward direction.
  * Check datashift value against larger sector size.
    For example, it could cause an issue if misaligned 4K sector appears
    during decryption.
  * Do not allow sector size increase reencryption in offline mode.
  * Do not allow dangerous sector size change during reencryption.
  * Ask the user for confirmation before resuming reencryption.
  * Do not resume reencryption with conflicting parameters.
  * Add --force-offline-reencrypt option.
  * Do not allow nested encryption in LUKS reencrypt.
  * Support all options allowed with luksFormat with encrypt action.
  * Add resize action to integritysetup.
  * Remove obsolete dracut plugin reencryption example.
  * Fix possible keyslot area size overflow during conversion to LUKS2.
  * Allow use of --header option for cryptsetup close.
  * Fix activation of LUKS2 device with integrity and detached header.
  * Add ZEROOUT IOCTL support for crypt_wipe API call.
  * VERITY: set loopback sector size according to dm-verity block sizes.
  * veritysetup: dump device sizes.
  * LUKS2 token: prefer token PIN query before passphrase in some cases.
    When a user provides --token-type or specific --token-id, a token PIN
    query is preferred to a passphrase query.
  * LUKS2 token: allow tokens to be replaced with --token-replace option
    for cryptsetup token command.
  * LUKS2 token: do not continue operation when interrupted in PIN prompt.
  * Add --progress-json parameter to utilities.
  * Add support for --key-slot option in luksResume action.
- move man pages to separate subpackage
- drop backports handling</changelog>
  <changelog author="luca.boccassi@gmail.com" date="1663070400">- Add virtual provides for 'integritysetup' and 'veritysetup' to match
  package names provided by Fedora/RHEL, to allow the same set of
  dependencies to be used across all RPM distributions.</changelog>
  <changelog author="info@paolostivanin.com" date="1669636800">- cryptsetup 2.6.0:
  * Introduce support for handling macOS FileVault2 devices (FVAULT2).
  * libcryptsetup: no longer use global memory locking through mlockall()
  * libcryptsetup: process priority is increased only for key derivation
    (PBKDF) calls.
  * Add new LUKS keyslot context handling functions and API.
  * The volume key may now be extracted using a passphrase, keyfile, or
    token. For LUKS devices, it also returns the volume key after
    a successful crypt_format call.
  * Fix --disable-luks2-reencryption configuration option.
  * cryptsetup: Print a better error message and warning if the format
    produces an image without space available for data.
  * Print error if anti-forensic LUKS2 hash setting is not available.
    If the specified hash was not available, activation quietly failed.
  * Fix internal crypt segment compare routine if the user
    specified cipher in kernel format (capi: prefix).
  * cryptsetup: Add token unassign action.
    This action allows removing token binding on specific keyslot.
  * veritysetup: add support for --use-tasklets option.
    This option sets try_verify_in_tasklet kernel dm-verity option
    (available since Linux kernel 6.0) to allow some performance
    improvement on specific systems.
  * Provide pkgconfig Require.private settings.
    While we do not completely provide static build on udev systems,
    it helps produce statically linked binaries in certain situations.
  * Always update automake library files if autogen.sh is run.
    For several releases, we distributed older automake scripts by mistake.
  * reencryption: Fix user defined moved segment size in LUKS2 decryption.
    The --hotzone-size argument was ignored in cases where the actual data
    size was less than the original LUKS2 data offset.
  * Delegate FIPS mode detection to configured crypto backend.
    System FIPS mode check no longer depends on /etc/system-fips file.
  * Update documentation, including FAQ and man pages.</changelog>
  <changelog author="lnussel@suse.com" date="1672142400">- Replace transitional %usrmerged macro with regular version check (boo#1206798)</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1676203200">- cryptsetup 2.6.1
  * bitlk: Fixes for BitLocker-compatible on-disk metadata parser
  * Fix possible iteration overflow in OpenSSL2 PBKDF2 crypto
    backend
  * portability and compilation fixes
  * verity: Fix possible hash offset setting overflow.
  * bitlk: Fix use of startup BEK key on big-endian platforms.
  * Do not initiate encryption (reencryption command) when the
    header and data devices are the same. If data device reduction
    is not requsted, this leads to data corruption since LUKS
    metadata was written over the data device.
  * Fix possible memory leak if crypt_load() fails.
  * Always use passphrases with a minimal 8 chars length for
    benchmarking, as used in some implementation of FIPS mode</changelog>
  <changelog author="pmonreal@suse.com" date="1686744000">- FIPS: Remove not needed libcryptsetup12-hmac package that contains
  the HMAC checksums for integrity checking for FIPS. [bsc#1185116]
  * Remove the cryptsetup-rpmlintrc file.
  * Remove not needed fipscheck dependency.</changelog>
  <changelog author="pmonreal@suse.com" date="1686744001">- Enable running the regression test suite.
- Force a regeneration of the man pages from AsciiDoc.
- Add LUKS1 and LUKS2 On-Disk Format Specification pdfs to doc.</changelog>
  <changelog author="pmonreal@suse.com" date="1689249600">- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1706529600">- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1710331200">- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1712664000">- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.</changelog>
  <changelog author="pvorel@suse.cz" date="1720785600">- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).</changelog>
  <changelog author="pmonreal@suse.com" date="1722340800">- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.</changelog>
  <changelog author="martin.schreiner@suse.com" date="1722427200">- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.</changelog>
  <changelog author="meissner@suse.com" date="1725019200">- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)</changelog>
  <changelog author="pmonreal@suse.com" date="1726228800">- Update to 2.7.5:
  * Fix possible online reencryption data corruption (only in 2.7.x).
    In some situations (initializing a suspended device-mapper device),
    cryptsetup disabled direct-io device access. This caused unsafe
    online reencryption operations that could lead to data corruption.
    The code now adds strict checks (and aborts the operation) and
    changes direct-io detection code to prevent data corruption.
  * Fix a clang compilation error in SSH token plugin.
    As clang linker treats missing symbols as errors, the linker phase
    for the SSH token failed as the optional cryptsetup_token_buffer_free
    was not defined.
  * Fix crypto backend initialization in crypt_format_luks2_opal API call.</changelog>
  <changelog author="pmonreal@suse.com" date="1741953600">- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.</changelog>
</package>
<package pkgid="5878a419c3f2830a1bc7cb1a52d3d8181721ae8811b8ce8b0ff86c873935c0e1" name="cryptsetup-doc" arch="noarch">
  <version epoch="0" ver="2.7.5" rel="220.1"/>
  <changelog author="lnussel@suse.de" date="1631793600">- cryptsetup 2.4.1
  * Fix compilation for libc implementations without dlvsym().
  * Fix compilation and tests on systems with non-standard libraries
  * Try to workaround some issues on systems without udev support.
  * Fixes for OpenSSL3 crypto backend (including FIPS mode).
  * Print error message when assigning a token to an inactive keyslot.
  * Fix offset bug in LUKS2 encryption code if --offset option was used.
  * Do not allow LUKS2 decryption for devices with data offset.
  * Fix LUKS1 cryptsetup repair command for some specific problems.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1637236800">- cryptsetup 2.4.2:
  * Fix possible large memory allocation if LUKS2 header size is
    invalid.
  * Fix memory corruption in debug message printing LUKS2
    checksum.
  * veritysetup: remove link to the UUID library for the static
    build.
  * Remove link to pwquality library for integritysetup and
    veritysetup. These tools do not read passphrases.
  * OpenSSL3 backend: avoid remaining deprecated calls in API.
    Crypto backend no longer use API deprecated in OpenSSL 3.0
  * Check if kernel device-mapper create device failed in an early
    phase. This happens when a concurrent creation of device-mapper
    devices meets in the very early state.
  * Do not set compiler optimization flag for Argon2 KDF if the
    memory wipe is implemented in libc.
  * Do not attempt to unload LUKS2 tokens if external tokens are
    disabled. This allows building a static binary with
  - -disable-external-tokens.
  * LUKS convert: also check sysfs for device activity.
    If udev symlink is missing, code fallbacks to sysfs scan to
    prevent data corruption for the active device.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1642161600">- cryptsetup 2.4.3:
  * Fix possible attacks against data confidentiality through
    LUKS2 online reencryption extension crash recovery
    CVE-2021-4122, boo#1194469
  * Add configure option --disable-luks2-reencryption to completely
    disable LUKS2 reencryption code.
  * Improve internal metadata validation code for reencryption
    metadata
  * Add updated documentation for LUKS2 On-Disk Format
    Specification version 1.1.0
  * Fix support for bitlk (BitLocker compatible) startup key with
    new  metadata entry introduced in Windows 11
  * Fix space restriction for LUKS2 reencryption with data shift</changelog>
  <changelog author="lnussel@suse.de" date="1661169600">- cryptsetup 2.5.0:
  * Split manual pages into per-action pages and use AsciiDoc format.
  * Remove cryptsetup-reencrypt tool from the project and move reencryption
    to already existing "cryptsetup reencrypt" command.
    If you need to emulate the old cryptsetup-reencrypt binary, use simple
    wrappers script running "exec cryptsetup reencrypt $@".
  * LUKS2: implement --decryption option that allows LUKS removal.
  * Fix decryption operation with --active-name option and restrict
    it to be used only with LUKS2.
  * Do not refresh reencryption digest when not needed.
    This should speed up the reencryption resume process.
  * Store proper resilience data in LUKS2 reencrypt initialization.
    Resuming reencryption now does not require specification of resilience
    type parameters if these are the same as during initialization.
  * Properly wipe the unused area after reencryption with datashift in
    the forward direction.
  * Check datashift value against larger sector size.
    For example, it could cause an issue if misaligned 4K sector appears
    during decryption.
  * Do not allow sector size increase reencryption in offline mode.
  * Do not allow dangerous sector size change during reencryption.
  * Ask the user for confirmation before resuming reencryption.
  * Do not resume reencryption with conflicting parameters.
  * Add --force-offline-reencrypt option.
  * Do not allow nested encryption in LUKS reencrypt.
  * Support all options allowed with luksFormat with encrypt action.
  * Add resize action to integritysetup.
  * Remove obsolete dracut plugin reencryption example.
  * Fix possible keyslot area size overflow during conversion to LUKS2.
  * Allow use of --header option for cryptsetup close.
  * Fix activation of LUKS2 device with integrity and detached header.
  * Add ZEROOUT IOCTL support for crypt_wipe API call.
  * VERITY: set loopback sector size according to dm-verity block sizes.
  * veritysetup: dump device sizes.
  * LUKS2 token: prefer token PIN query before passphrase in some cases.
    When a user provides --token-type or specific --token-id, a token PIN
    query is preferred to a passphrase query.
  * LUKS2 token: allow tokens to be replaced with --token-replace option
    for cryptsetup token command.
  * LUKS2 token: do not continue operation when interrupted in PIN prompt.
  * Add --progress-json parameter to utilities.
  * Add support for --key-slot option in luksResume action.
- move man pages to separate subpackage
- drop backports handling</changelog>
  <changelog author="luca.boccassi@gmail.com" date="1663070400">- Add virtual provides for 'integritysetup' and 'veritysetup' to match
  package names provided by Fedora/RHEL, to allow the same set of
  dependencies to be used across all RPM distributions.</changelog>
  <changelog author="info@paolostivanin.com" date="1669636800">- cryptsetup 2.6.0:
  * Introduce support for handling macOS FileVault2 devices (FVAULT2).
  * libcryptsetup: no longer use global memory locking through mlockall()
  * libcryptsetup: process priority is increased only for key derivation
    (PBKDF) calls.
  * Add new LUKS keyslot context handling functions and API.
  * The volume key may now be extracted using a passphrase, keyfile, or
    token. For LUKS devices, it also returns the volume key after
    a successful crypt_format call.
  * Fix --disable-luks2-reencryption configuration option.
  * cryptsetup: Print a better error message and warning if the format
    produces an image without space available for data.
  * Print error if anti-forensic LUKS2 hash setting is not available.
    If the specified hash was not available, activation quietly failed.
  * Fix internal crypt segment compare routine if the user
    specified cipher in kernel format (capi: prefix).
  * cryptsetup: Add token unassign action.
    This action allows removing token binding on specific keyslot.
  * veritysetup: add support for --use-tasklets option.
    This option sets try_verify_in_tasklet kernel dm-verity option
    (available since Linux kernel 6.0) to allow some performance
    improvement on specific systems.
  * Provide pkgconfig Require.private settings.
    While we do not completely provide static build on udev systems,
    it helps produce statically linked binaries in certain situations.
  * Always update automake library files if autogen.sh is run.
    For several releases, we distributed older automake scripts by mistake.
  * reencryption: Fix user defined moved segment size in LUKS2 decryption.
    The --hotzone-size argument was ignored in cases where the actual data
    size was less than the original LUKS2 data offset.
  * Delegate FIPS mode detection to configured crypto backend.
    System FIPS mode check no longer depends on /etc/system-fips file.
  * Update documentation, including FAQ and man pages.</changelog>
  <changelog author="lnussel@suse.com" date="1672142400">- Replace transitional %usrmerged macro with regular version check (boo#1206798)</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1676203200">- cryptsetup 2.6.1
  * bitlk: Fixes for BitLocker-compatible on-disk metadata parser
  * Fix possible iteration overflow in OpenSSL2 PBKDF2 crypto
    backend
  * portability and compilation fixes
  * verity: Fix possible hash offset setting overflow.
  * bitlk: Fix use of startup BEK key on big-endian platforms.
  * Do not initiate encryption (reencryption command) when the
    header and data devices are the same. If data device reduction
    is not requsted, this leads to data corruption since LUKS
    metadata was written over the data device.
  * Fix possible memory leak if crypt_load() fails.
  * Always use passphrases with a minimal 8 chars length for
    benchmarking, as used in some implementation of FIPS mode</changelog>
  <changelog author="pmonreal@suse.com" date="1686744000">- FIPS: Remove not needed libcryptsetup12-hmac package that contains
  the HMAC checksums for integrity checking for FIPS. [bsc#1185116]
  * Remove the cryptsetup-rpmlintrc file.
  * Remove not needed fipscheck dependency.</changelog>
  <changelog author="pmonreal@suse.com" date="1686744001">- Enable running the regression test suite.
- Force a regeneration of the man pages from AsciiDoc.
- Add LUKS1 and LUKS2 On-Disk Format Specification pdfs to doc.</changelog>
  <changelog author="pmonreal@suse.com" date="1689249600">- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1706529600">- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1710331200">- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1712664000">- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.</changelog>
  <changelog author="pvorel@suse.cz" date="1720785600">- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).</changelog>
  <changelog author="pmonreal@suse.com" date="1722340800">- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.</changelog>
  <changelog author="martin.schreiner@suse.com" date="1722427200">- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.</changelog>
  <changelog author="meissner@suse.com" date="1725019200">- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)</changelog>
  <changelog author="pmonreal@suse.com" date="1726228800">- Update to 2.7.5:
  * Fix possible online reencryption data corruption (only in 2.7.x).
    In some situations (initializing a suspended device-mapper device),
    cryptsetup disabled direct-io device access. This caused unsafe
    online reencryption operations that could lead to data corruption.
    The code now adds strict checks (and aborts the operation) and
    changes direct-io detection code to prevent data corruption.
  * Fix a clang compilation error in SSH token plugin.
    As clang linker treats missing symbols as errors, the linker phase
    for the SSH token failed as the optional cryptsetup_token_buffer_free
    was not defined.
  * Fix crypto backend initialization in crypt_format_luks2_opal API call.</changelog>
  <changelog author="pmonreal@suse.com" date="1741953600">- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.</changelog>
</package>
<package pkgid="8dd3a5781610a3352c4ee9175cbf67a564dd8ff53cd083d41ac729030d78562f" name="cryptsetup-lang" arch="noarch">
  <version epoch="0" ver="2.7.5" rel="220.1"/>
  <changelog author="lnussel@suse.de" date="1631793600">- cryptsetup 2.4.1
  * Fix compilation for libc implementations without dlvsym().
  * Fix compilation and tests on systems with non-standard libraries
  * Try to workaround some issues on systems without udev support.
  * Fixes for OpenSSL3 crypto backend (including FIPS mode).
  * Print error message when assigning a token to an inactive keyslot.
  * Fix offset bug in LUKS2 encryption code if --offset option was used.
  * Do not allow LUKS2 decryption for devices with data offset.
  * Fix LUKS1 cryptsetup repair command for some specific problems.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1637236800">- cryptsetup 2.4.2:
  * Fix possible large memory allocation if LUKS2 header size is
    invalid.
  * Fix memory corruption in debug message printing LUKS2
    checksum.
  * veritysetup: remove link to the UUID library for the static
    build.
  * Remove link to pwquality library for integritysetup and
    veritysetup. These tools do not read passphrases.
  * OpenSSL3 backend: avoid remaining deprecated calls in API.
    Crypto backend no longer use API deprecated in OpenSSL 3.0
  * Check if kernel device-mapper create device failed in an early
    phase. This happens when a concurrent creation of device-mapper
    devices meets in the very early state.
  * Do not set compiler optimization flag for Argon2 KDF if the
    memory wipe is implemented in libc.
  * Do not attempt to unload LUKS2 tokens if external tokens are
    disabled. This allows building a static binary with
  - -disable-external-tokens.
  * LUKS convert: also check sysfs for device activity.
    If udev symlink is missing, code fallbacks to sysfs scan to
    prevent data corruption for the active device.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1642161600">- cryptsetup 2.4.3:
  * Fix possible attacks against data confidentiality through
    LUKS2 online reencryption extension crash recovery
    CVE-2021-4122, boo#1194469
  * Add configure option --disable-luks2-reencryption to completely
    disable LUKS2 reencryption code.
  * Improve internal metadata validation code for reencryption
    metadata
  * Add updated documentation for LUKS2 On-Disk Format
    Specification version 1.1.0
  * Fix support for bitlk (BitLocker compatible) startup key with
    new  metadata entry introduced in Windows 11
  * Fix space restriction for LUKS2 reencryption with data shift</changelog>
  <changelog author="lnussel@suse.de" date="1661169600">- cryptsetup 2.5.0:
  * Split manual pages into per-action pages and use AsciiDoc format.
  * Remove cryptsetup-reencrypt tool from the project and move reencryption
    to already existing "cryptsetup reencrypt" command.
    If you need to emulate the old cryptsetup-reencrypt binary, use simple
    wrappers script running "exec cryptsetup reencrypt $@".
  * LUKS2: implement --decryption option that allows LUKS removal.
  * Fix decryption operation with --active-name option and restrict
    it to be used only with LUKS2.
  * Do not refresh reencryption digest when not needed.
    This should speed up the reencryption resume process.
  * Store proper resilience data in LUKS2 reencrypt initialization.
    Resuming reencryption now does not require specification of resilience
    type parameters if these are the same as during initialization.
  * Properly wipe the unused area after reencryption with datashift in
    the forward direction.
  * Check datashift value against larger sector size.
    For example, it could cause an issue if misaligned 4K sector appears
    during decryption.
  * Do not allow sector size increase reencryption in offline mode.
  * Do not allow dangerous sector size change during reencryption.
  * Ask the user for confirmation before resuming reencryption.
  * Do not resume reencryption with conflicting parameters.
  * Add --force-offline-reencrypt option.
  * Do not allow nested encryption in LUKS reencrypt.
  * Support all options allowed with luksFormat with encrypt action.
  * Add resize action to integritysetup.
  * Remove obsolete dracut plugin reencryption example.
  * Fix possible keyslot area size overflow during conversion to LUKS2.
  * Allow use of --header option for cryptsetup close.
  * Fix activation of LUKS2 device with integrity and detached header.
  * Add ZEROOUT IOCTL support for crypt_wipe API call.
  * VERITY: set loopback sector size according to dm-verity block sizes.
  * veritysetup: dump device sizes.
  * LUKS2 token: prefer token PIN query before passphrase in some cases.
    When a user provides --token-type or specific --token-id, a token PIN
    query is preferred to a passphrase query.
  * LUKS2 token: allow tokens to be replaced with --token-replace option
    for cryptsetup token command.
  * LUKS2 token: do not continue operation when interrupted in PIN prompt.
  * Add --progress-json parameter to utilities.
  * Add support for --key-slot option in luksResume action.
- move man pages to separate subpackage
- drop backports handling</changelog>
  <changelog author="luca.boccassi@gmail.com" date="1663070400">- Add virtual provides for 'integritysetup' and 'veritysetup' to match
  package names provided by Fedora/RHEL, to allow the same set of
  dependencies to be used across all RPM distributions.</changelog>
  <changelog author="info@paolostivanin.com" date="1669636800">- cryptsetup 2.6.0:
  * Introduce support for handling macOS FileVault2 devices (FVAULT2).
  * libcryptsetup: no longer use global memory locking through mlockall()
  * libcryptsetup: process priority is increased only for key derivation
    (PBKDF) calls.
  * Add new LUKS keyslot context handling functions and API.
  * The volume key may now be extracted using a passphrase, keyfile, or
    token. For LUKS devices, it also returns the volume key after
    a successful crypt_format call.
  * Fix --disable-luks2-reencryption configuration option.
  * cryptsetup: Print a better error message and warning if the format
    produces an image without space available for data.
  * Print error if anti-forensic LUKS2 hash setting is not available.
    If the specified hash was not available, activation quietly failed.
  * Fix internal crypt segment compare routine if the user
    specified cipher in kernel format (capi: prefix).
  * cryptsetup: Add token unassign action.
    This action allows removing token binding on specific keyslot.
  * veritysetup: add support for --use-tasklets option.
    This option sets try_verify_in_tasklet kernel dm-verity option
    (available since Linux kernel 6.0) to allow some performance
    improvement on specific systems.
  * Provide pkgconfig Require.private settings.
    While we do not completely provide static build on udev systems,
    it helps produce statically linked binaries in certain situations.
  * Always update automake library files if autogen.sh is run.
    For several releases, we distributed older automake scripts by mistake.
  * reencryption: Fix user defined moved segment size in LUKS2 decryption.
    The --hotzone-size argument was ignored in cases where the actual data
    size was less than the original LUKS2 data offset.
  * Delegate FIPS mode detection to configured crypto backend.
    System FIPS mode check no longer depends on /etc/system-fips file.
  * Update documentation, including FAQ and man pages.</changelog>
  <changelog author="lnussel@suse.com" date="1672142400">- Replace transitional %usrmerged macro with regular version check (boo#1206798)</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1676203200">- cryptsetup 2.6.1
  * bitlk: Fixes for BitLocker-compatible on-disk metadata parser
  * Fix possible iteration overflow in OpenSSL2 PBKDF2 crypto
    backend
  * portability and compilation fixes
  * verity: Fix possible hash offset setting overflow.
  * bitlk: Fix use of startup BEK key on big-endian platforms.
  * Do not initiate encryption (reencryption command) when the
    header and data devices are the same. If data device reduction
    is not requsted, this leads to data corruption since LUKS
    metadata was written over the data device.
  * Fix possible memory leak if crypt_load() fails.
  * Always use passphrases with a minimal 8 chars length for
    benchmarking, as used in some implementation of FIPS mode</changelog>
  <changelog author="pmonreal@suse.com" date="1686744000">- FIPS: Remove not needed libcryptsetup12-hmac package that contains
  the HMAC checksums for integrity checking for FIPS. [bsc#1185116]
  * Remove the cryptsetup-rpmlintrc file.
  * Remove not needed fipscheck dependency.</changelog>
  <changelog author="pmonreal@suse.com" date="1686744001">- Enable running the regression test suite.
- Force a regeneration of the man pages from AsciiDoc.
- Add LUKS1 and LUKS2 On-Disk Format Specification pdfs to doc.</changelog>
  <changelog author="pmonreal@suse.com" date="1689249600">- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1706529600">- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1710331200">- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1712664000">- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.</changelog>
  <changelog author="pvorel@suse.cz" date="1720785600">- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).</changelog>
  <changelog author="pmonreal@suse.com" date="1722340800">- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.</changelog>
  <changelog author="martin.schreiner@suse.com" date="1722427200">- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.</changelog>
  <changelog author="meissner@suse.com" date="1725019200">- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)</changelog>
  <changelog author="pmonreal@suse.com" date="1726228800">- Update to 2.7.5:
  * Fix possible online reencryption data corruption (only in 2.7.x).
    In some situations (initializing a suspended device-mapper device),
    cryptsetup disabled direct-io device access. This caused unsafe
    online reencryption operations that could lead to data corruption.
    The code now adds strict checks (and aborts the operation) and
    changes direct-io detection code to prevent data corruption.
  * Fix a clang compilation error in SSH token plugin.
    As clang linker treats missing symbols as errors, the linker phase
    for the SSH token failed as the optional cryptsetup_token_buffer_free
    was not defined.
  * Fix crypto backend initialization in crypt_format_luks2_opal API call.</changelog>
  <changelog author="pmonreal@suse.com" date="1741953600">- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.</changelog>
</package>
<package pkgid="c41901729e287aaa8a2dcfbd54fb625a6a1e7645c7e63f1bb8c029a7db41cb07" name="cryptsetup-ssh" arch="x86_64">
  <version epoch="0" ver="2.7.5" rel="220.1"/>
  <changelog author="lnussel@suse.de" date="1631793600">- cryptsetup 2.4.1
  * Fix compilation for libc implementations without dlvsym().
  * Fix compilation and tests on systems with non-standard libraries
  * Try to workaround some issues on systems without udev support.
  * Fixes for OpenSSL3 crypto backend (including FIPS mode).
  * Print error message when assigning a token to an inactive keyslot.
  * Fix offset bug in LUKS2 encryption code if --offset option was used.
  * Do not allow LUKS2 decryption for devices with data offset.
  * Fix LUKS1 cryptsetup repair command for some specific problems.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1637236800">- cryptsetup 2.4.2:
  * Fix possible large memory allocation if LUKS2 header size is
    invalid.
  * Fix memory corruption in debug message printing LUKS2
    checksum.
  * veritysetup: remove link to the UUID library for the static
    build.
  * Remove link to pwquality library for integritysetup and
    veritysetup. These tools do not read passphrases.
  * OpenSSL3 backend: avoid remaining deprecated calls in API.
    Crypto backend no longer use API deprecated in OpenSSL 3.0
  * Check if kernel device-mapper create device failed in an early
    phase. This happens when a concurrent creation of device-mapper
    devices meets in the very early state.
  * Do not set compiler optimization flag for Argon2 KDF if the
    memory wipe is implemented in libc.
  * Do not attempt to unload LUKS2 tokens if external tokens are
    disabled. This allows building a static binary with
  - -disable-external-tokens.
  * LUKS convert: also check sysfs for device activity.
    If udev symlink is missing, code fallbacks to sysfs scan to
    prevent data corruption for the active device.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1642161600">- cryptsetup 2.4.3:
  * Fix possible attacks against data confidentiality through
    LUKS2 online reencryption extension crash recovery
    CVE-2021-4122, boo#1194469
  * Add configure option --disable-luks2-reencryption to completely
    disable LUKS2 reencryption code.
  * Improve internal metadata validation code for reencryption
    metadata
  * Add updated documentation for LUKS2 On-Disk Format
    Specification version 1.1.0
  * Fix support for bitlk (BitLocker compatible) startup key with
    new  metadata entry introduced in Windows 11
  * Fix space restriction for LUKS2 reencryption with data shift</changelog>
  <changelog author="lnussel@suse.de" date="1661169600">- cryptsetup 2.5.0:
  * Split manual pages into per-action pages and use AsciiDoc format.
  * Remove cryptsetup-reencrypt tool from the project and move reencryption
    to already existing "cryptsetup reencrypt" command.
    If you need to emulate the old cryptsetup-reencrypt binary, use simple
    wrappers script running "exec cryptsetup reencrypt $@".
  * LUKS2: implement --decryption option that allows LUKS removal.
  * Fix decryption operation with --active-name option and restrict
    it to be used only with LUKS2.
  * Do not refresh reencryption digest when not needed.
    This should speed up the reencryption resume process.
  * Store proper resilience data in LUKS2 reencrypt initialization.
    Resuming reencryption now does not require specification of resilience
    type parameters if these are the same as during initialization.
  * Properly wipe the unused area after reencryption with datashift in
    the forward direction.
  * Check datashift value against larger sector size.
    For example, it could cause an issue if misaligned 4K sector appears
    during decryption.
  * Do not allow sector size increase reencryption in offline mode.
  * Do not allow dangerous sector size change during reencryption.
  * Ask the user for confirmation before resuming reencryption.
  * Do not resume reencryption with conflicting parameters.
  * Add --force-offline-reencrypt option.
  * Do not allow nested encryption in LUKS reencrypt.
  * Support all options allowed with luksFormat with encrypt action.
  * Add resize action to integritysetup.
  * Remove obsolete dracut plugin reencryption example.
  * Fix possible keyslot area size overflow during conversion to LUKS2.
  * Allow use of --header option for cryptsetup close.
  * Fix activation of LUKS2 device with integrity and detached header.
  * Add ZEROOUT IOCTL support for crypt_wipe API call.
  * VERITY: set loopback sector size according to dm-verity block sizes.
  * veritysetup: dump device sizes.
  * LUKS2 token: prefer token PIN query before passphrase in some cases.
    When a user provides --token-type or specific --token-id, a token PIN
    query is preferred to a passphrase query.
  * LUKS2 token: allow tokens to be replaced with --token-replace option
    for cryptsetup token command.
  * LUKS2 token: do not continue operation when interrupted in PIN prompt.
  * Add --progress-json parameter to utilities.
  * Add support for --key-slot option in luksResume action.
- move man pages to separate subpackage
- drop backports handling</changelog>
  <changelog author="luca.boccassi@gmail.com" date="1663070400">- Add virtual provides for 'integritysetup' and 'veritysetup' to match
  package names provided by Fedora/RHEL, to allow the same set of
  dependencies to be used across all RPM distributions.</changelog>
  <changelog author="info@paolostivanin.com" date="1669636800">- cryptsetup 2.6.0:
  * Introduce support for handling macOS FileVault2 devices (FVAULT2).
  * libcryptsetup: no longer use global memory locking through mlockall()
  * libcryptsetup: process priority is increased only for key derivation
    (PBKDF) calls.
  * Add new LUKS keyslot context handling functions and API.
  * The volume key may now be extracted using a passphrase, keyfile, or
    token. For LUKS devices, it also returns the volume key after
    a successful crypt_format call.
  * Fix --disable-luks2-reencryption configuration option.
  * cryptsetup: Print a better error message and warning if the format
    produces an image without space available for data.
  * Print error if anti-forensic LUKS2 hash setting is not available.
    If the specified hash was not available, activation quietly failed.
  * Fix internal crypt segment compare routine if the user
    specified cipher in kernel format (capi: prefix).
  * cryptsetup: Add token unassign action.
    This action allows removing token binding on specific keyslot.
  * veritysetup: add support for --use-tasklets option.
    This option sets try_verify_in_tasklet kernel dm-verity option
    (available since Linux kernel 6.0) to allow some performance
    improvement on specific systems.
  * Provide pkgconfig Require.private settings.
    While we do not completely provide static build on udev systems,
    it helps produce statically linked binaries in certain situations.
  * Always update automake library files if autogen.sh is run.
    For several releases, we distributed older automake scripts by mistake.
  * reencryption: Fix user defined moved segment size in LUKS2 decryption.
    The --hotzone-size argument was ignored in cases where the actual data
    size was less than the original LUKS2 data offset.
  * Delegate FIPS mode detection to configured crypto backend.
    System FIPS mode check no longer depends on /etc/system-fips file.
  * Update documentation, including FAQ and man pages.</changelog>
  <changelog author="lnussel@suse.com" date="1672142400">- Replace transitional %usrmerged macro with regular version check (boo#1206798)</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1676203200">- cryptsetup 2.6.1
  * bitlk: Fixes for BitLocker-compatible on-disk metadata parser
  * Fix possible iteration overflow in OpenSSL2 PBKDF2 crypto
    backend
  * portability and compilation fixes
  * verity: Fix possible hash offset setting overflow.
  * bitlk: Fix use of startup BEK key on big-endian platforms.
  * Do not initiate encryption (reencryption command) when the
    header and data devices are the same. If data device reduction
    is not requsted, this leads to data corruption since LUKS
    metadata was written over the data device.
  * Fix possible memory leak if crypt_load() fails.
  * Always use passphrases with a minimal 8 chars length for
    benchmarking, as used in some implementation of FIPS mode</changelog>
  <changelog author="pmonreal@suse.com" date="1686744000">- FIPS: Remove not needed libcryptsetup12-hmac package that contains
  the HMAC checksums for integrity checking for FIPS. [bsc#1185116]
  * Remove the cryptsetup-rpmlintrc file.
  * Remove not needed fipscheck dependency.</changelog>
  <changelog author="pmonreal@suse.com" date="1686744001">- Enable running the regression test suite.
- Force a regeneration of the man pages from AsciiDoc.
- Add LUKS1 and LUKS2 On-Disk Format Specification pdfs to doc.</changelog>
  <changelog author="pmonreal@suse.com" date="1689249600">- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1706529600">- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1710331200">- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1712664000">- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.</changelog>
  <changelog author="pvorel@suse.cz" date="1720785600">- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).</changelog>
  <changelog author="pmonreal@suse.com" date="1722340800">- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.</changelog>
  <changelog author="martin.schreiner@suse.com" date="1722427200">- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.</changelog>
  <changelog author="meissner@suse.com" date="1725019200">- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)</changelog>
  <changelog author="pmonreal@suse.com" date="1726228800">- Update to 2.7.5:
  * Fix possible online reencryption data corruption (only in 2.7.x).
    In some situations (initializing a suspended device-mapper device),
    cryptsetup disabled direct-io device access. This caused unsafe
    online reencryption operations that could lead to data corruption.
    The code now adds strict checks (and aborts the operation) and
    changes direct-io detection code to prevent data corruption.
  * Fix a clang compilation error in SSH token plugin.
    As clang linker treats missing symbols as errors, the linker phase
    for the SSH token failed as the optional cryptsetup_token_buffer_free
    was not defined.
  * Fix crypto backend initialization in crypt_format_luks2_opal API call.</changelog>
  <changelog author="pmonreal@suse.com" date="1741953600">- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.</changelog>
</package>
<package pkgid="1e4b0476c6ee48e1195b29fe85a1a0fc40c04e439d04bf18edd1900ad0af0d9f" name="cryptsetup-ssh-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.7.5" rel="220.1"/>
  <changelog author="lnussel@suse.de" date="1631793600">- cryptsetup 2.4.1
  * Fix compilation for libc implementations without dlvsym().
  * Fix compilation and tests on systems with non-standard libraries
  * Try to workaround some issues on systems without udev support.
  * Fixes for OpenSSL3 crypto backend (including FIPS mode).
  * Print error message when assigning a token to an inactive keyslot.
  * Fix offset bug in LUKS2 encryption code if --offset option was used.
  * Do not allow LUKS2 decryption for devices with data offset.
  * Fix LUKS1 cryptsetup repair command for some specific problems.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1637236800">- cryptsetup 2.4.2:
  * Fix possible large memory allocation if LUKS2 header size is
    invalid.
  * Fix memory corruption in debug message printing LUKS2
    checksum.
  * veritysetup: remove link to the UUID library for the static
    build.
  * Remove link to pwquality library for integritysetup and
    veritysetup. These tools do not read passphrases.
  * OpenSSL3 backend: avoid remaining deprecated calls in API.
    Crypto backend no longer use API deprecated in OpenSSL 3.0
  * Check if kernel device-mapper create device failed in an early
    phase. This happens when a concurrent creation of device-mapper
    devices meets in the very early state.
  * Do not set compiler optimization flag for Argon2 KDF if the
    memory wipe is implemented in libc.
  * Do not attempt to unload LUKS2 tokens if external tokens are
    disabled. This allows building a static binary with
  - -disable-external-tokens.
  * LUKS convert: also check sysfs for device activity.
    If udev symlink is missing, code fallbacks to sysfs scan to
    prevent data corruption for the active device.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1642161600">- cryptsetup 2.4.3:
  * Fix possible attacks against data confidentiality through
    LUKS2 online reencryption extension crash recovery
    CVE-2021-4122, boo#1194469
  * Add configure option --disable-luks2-reencryption to completely
    disable LUKS2 reencryption code.
  * Improve internal metadata validation code for reencryption
    metadata
  * Add updated documentation for LUKS2 On-Disk Format
    Specification version 1.1.0
  * Fix support for bitlk (BitLocker compatible) startup key with
    new  metadata entry introduced in Windows 11
  * Fix space restriction for LUKS2 reencryption with data shift</changelog>
  <changelog author="lnussel@suse.de" date="1661169600">- cryptsetup 2.5.0:
  * Split manual pages into per-action pages and use AsciiDoc format.
  * Remove cryptsetup-reencrypt tool from the project and move reencryption
    to already existing "cryptsetup reencrypt" command.
    If you need to emulate the old cryptsetup-reencrypt binary, use simple
    wrappers script running "exec cryptsetup reencrypt $@".
  * LUKS2: implement --decryption option that allows LUKS removal.
  * Fix decryption operation with --active-name option and restrict
    it to be used only with LUKS2.
  * Do not refresh reencryption digest when not needed.
    This should speed up the reencryption resume process.
  * Store proper resilience data in LUKS2 reencrypt initialization.
    Resuming reencryption now does not require specification of resilience
    type parameters if these are the same as during initialization.
  * Properly wipe the unused area after reencryption with datashift in
    the forward direction.
  * Check datashift value against larger sector size.
    For example, it could cause an issue if misaligned 4K sector appears
    during decryption.
  * Do not allow sector size increase reencryption in offline mode.
  * Do not allow dangerous sector size change during reencryption.
  * Ask the user for confirmation before resuming reencryption.
  * Do not resume reencryption with conflicting parameters.
  * Add --force-offline-reencrypt option.
  * Do not allow nested encryption in LUKS reencrypt.
  * Support all options allowed with luksFormat with encrypt action.
  * Add resize action to integritysetup.
  * Remove obsolete dracut plugin reencryption example.
  * Fix possible keyslot area size overflow during conversion to LUKS2.
  * Allow use of --header option for cryptsetup close.
  * Fix activation of LUKS2 device with integrity and detached header.
  * Add ZEROOUT IOCTL support for crypt_wipe API call.
  * VERITY: set loopback sector size according to dm-verity block sizes.
  * veritysetup: dump device sizes.
  * LUKS2 token: prefer token PIN query before passphrase in some cases.
    When a user provides --token-type or specific --token-id, a token PIN
    query is preferred to a passphrase query.
  * LUKS2 token: allow tokens to be replaced with --token-replace option
    for cryptsetup token command.
  * LUKS2 token: do not continue operation when interrupted in PIN prompt.
  * Add --progress-json parameter to utilities.
  * Add support for --key-slot option in luksResume action.
- move man pages to separate subpackage
- drop backports handling</changelog>
  <changelog author="luca.boccassi@gmail.com" date="1663070400">- Add virtual provides for 'integritysetup' and 'veritysetup' to match
  package names provided by Fedora/RHEL, to allow the same set of
  dependencies to be used across all RPM distributions.</changelog>
  <changelog author="info@paolostivanin.com" date="1669636800">- cryptsetup 2.6.0:
  * Introduce support for handling macOS FileVault2 devices (FVAULT2).
  * libcryptsetup: no longer use global memory locking through mlockall()
  * libcryptsetup: process priority is increased only for key derivation
    (PBKDF) calls.
  * Add new LUKS keyslot context handling functions and API.
  * The volume key may now be extracted using a passphrase, keyfile, or
    token. For LUKS devices, it also returns the volume key after
    a successful crypt_format call.
  * Fix --disable-luks2-reencryption configuration option.
  * cryptsetup: Print a better error message and warning if the format
    produces an image without space available for data.
  * Print error if anti-forensic LUKS2 hash setting is not available.
    If the specified hash was not available, activation quietly failed.
  * Fix internal crypt segment compare routine if the user
    specified cipher in kernel format (capi: prefix).
  * cryptsetup: Add token unassign action.
    This action allows removing token binding on specific keyslot.
  * veritysetup: add support for --use-tasklets option.
    This option sets try_verify_in_tasklet kernel dm-verity option
    (available since Linux kernel 6.0) to allow some performance
    improvement on specific systems.
  * Provide pkgconfig Require.private settings.
    While we do not completely provide static build on udev systems,
    it helps produce statically linked binaries in certain situations.
  * Always update automake library files if autogen.sh is run.
    For several releases, we distributed older automake scripts by mistake.
  * reencryption: Fix user defined moved segment size in LUKS2 decryption.
    The --hotzone-size argument was ignored in cases where the actual data
    size was less than the original LUKS2 data offset.
  * Delegate FIPS mode detection to configured crypto backend.
    System FIPS mode check no longer depends on /etc/system-fips file.
  * Update documentation, including FAQ and man pages.</changelog>
  <changelog author="lnussel@suse.com" date="1672142400">- Replace transitional %usrmerged macro with regular version check (boo#1206798)</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1676203200">- cryptsetup 2.6.1
  * bitlk: Fixes for BitLocker-compatible on-disk metadata parser
  * Fix possible iteration overflow in OpenSSL2 PBKDF2 crypto
    backend
  * portability and compilation fixes
  * verity: Fix possible hash offset setting overflow.
  * bitlk: Fix use of startup BEK key on big-endian platforms.
  * Do not initiate encryption (reencryption command) when the
    header and data devices are the same. If data device reduction
    is not requsted, this leads to data corruption since LUKS
    metadata was written over the data device.
  * Fix possible memory leak if crypt_load() fails.
  * Always use passphrases with a minimal 8 chars length for
    benchmarking, as used in some implementation of FIPS mode</changelog>
  <changelog author="pmonreal@suse.com" date="1686744000">- FIPS: Remove not needed libcryptsetup12-hmac package that contains
  the HMAC checksums for integrity checking for FIPS. [bsc#1185116]
  * Remove the cryptsetup-rpmlintrc file.
  * Remove not needed fipscheck dependency.</changelog>
  <changelog author="pmonreal@suse.com" date="1686744001">- Enable running the regression test suite.
- Force a regeneration of the man pages from AsciiDoc.
- Add LUKS1 and LUKS2 On-Disk Format Specification pdfs to doc.</changelog>
  <changelog author="pmonreal@suse.com" date="1689249600">- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1706529600">- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1710331200">- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1712664000">- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.</changelog>
  <changelog author="pvorel@suse.cz" date="1720785600">- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).</changelog>
  <changelog author="pmonreal@suse.com" date="1722340800">- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.</changelog>
  <changelog author="martin.schreiner@suse.com" date="1722427200">- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.</changelog>
  <changelog author="meissner@suse.com" date="1725019200">- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)</changelog>
  <changelog author="pmonreal@suse.com" date="1726228800">- Update to 2.7.5:
  * Fix possible online reencryption data corruption (only in 2.7.x).
    In some situations (initializing a suspended device-mapper device),
    cryptsetup disabled direct-io device access. This caused unsafe
    online reencryption operations that could lead to data corruption.
    The code now adds strict checks (and aborts the operation) and
    changes direct-io detection code to prevent data corruption.
  * Fix a clang compilation error in SSH token plugin.
    As clang linker treats missing symbols as errors, the linker phase
    for the SSH token failed as the optional cryptsetup_token_buffer_free
    was not defined.
  * Fix crypto backend initialization in crypt_format_luks2_opal API call.</changelog>
  <changelog author="pmonreal@suse.com" date="1741953600">- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.</changelog>
</package>
<package pkgid="f3f9c78c486d2af02bcfe221bc6e840f32707740cf6a1ad60f320478c81559ca" name="fipscheck" arch="src">
  <version epoch="0" ver="1.7.0" rel="46.1"/>
  <changelog author="meissner@suse.com" date="1390219200">- imported a generic fips helper to verify fips modules, linked
  to openssl.</changelog>
  <changelog author="cfarrell@suse.com" date="1390305600">- license update: BSD-2-Clause
  See LICENSE</changelog>
  <changelog author="meissner@suse.com" date="1401192000">- updated to 1.4.1
  - added manpages
  - fipscheck/fipshmac: Add -s option to specify the hmac suffix
  - fipshmac: Add '-d' option to specify where to put the .hmac files
  - various bugfixes</changelog>
  <changelog author="meissner@suse.com" date="1401710400">- add baselibs.conf</changelog>
  <changelog author="jengelh@inai.de" date="1428926400">- Set RPM groups anew. Drop implicit cleaning parts.</changelog>
  <changelog author="daniel.molkentin@suse.com" date="1497268800">- Port to OpenSSL 1.1 (bsc#1042649)
  Adds openssl-1_1-port.patch</changelog>
  <changelog author="jsikes@suse.de" date="1536667200">- Updated fipscheck to 1.5.0
  * Changed source to local file since latest official release
    is not in the official releases directory.
  * Downgraded libopenssl-devel to libopenssl-1_0_0-devel because
    1.0.2 supports FIPS.</changelog>
  <changelog author="jsikes@suse.de" date="1537444800">- Changed source back to http now that current release folder
  has current tarball.</changelog>
  <changelog author="vcizek@suse.com" date="1546516800">- Use the shipped manpages instead of building them with xmlto
  in order to avoid a build cycle (fipscheck, xmlto, libxslt, libgcrypt)
  * add fipscheck-dont_generate_manpages.patch
- fix build on older distributions</changelog>
  <changelog author="vcizek@suse.com" date="1568635200">- Remove #include of unused fips.h to fix build with OpenSSL 1.1.1
  (bsc#1149792)
  * add fipscheck-fips.h_not_needed.patch
- Drop obsolete openssl-1_1-port.patch (upstream)</changelog>
  <changelog author="lnussel@suse.de" date="1605873600">- move libs to %_libdir (boo#1029961)</changelog>
  <changelog author="meissner@suse.com" date="1667390400">- updated to 1.7.0 (from a different supplier)
  - openssl 3 support
- dropped fipscheck-dont_generate_manpages.patch (not needed)
- dropped fipscheck-fips.h_not_needed.patch (not needed)</changelog>
  <changelog author="mjambor@suse.com" date="1720440000">- Backport upstream patches fipscheck-fix_check_openssl_version.patch
  and fipscheck-fix_incorrect_length_type.patch to fix C99 violations
  which are errors by default with GCC 14 [boo#1221714] - although the
  first one looks like it possibly fixes some more substantial error.</changelog>
</package>
<package pkgid="99d75f90e27eb379415fec53bed31333174c946f3ec73ad138a86010bfe32e53" name="fipscheck" arch="x86_64">
  <version epoch="0" ver="1.7.0" rel="46.1"/>
  <changelog author="meissner@suse.com" date="1401710400">- add baselibs.conf</changelog>
  <changelog author="jengelh@inai.de" date="1428926400">- Set RPM groups anew. Drop implicit cleaning parts.</changelog>
  <changelog author="daniel.molkentin@suse.com" date="1497268800">- Port to OpenSSL 1.1 (bsc#1042649)
  Adds openssl-1_1-port.patch</changelog>
  <changelog author="jsikes@suse.de" date="1536667200">- Updated fipscheck to 1.5.0
  * Changed source to local file since latest official release
    is not in the official releases directory.
  * Downgraded libopenssl-devel to libopenssl-1_0_0-devel because
    1.0.2 supports FIPS.</changelog>
  <changelog author="jsikes@suse.de" date="1537444800">- Changed source back to http now that current release folder
  has current tarball.</changelog>
  <changelog author="vcizek@suse.com" date="1546516800">- Use the shipped manpages instead of building them with xmlto
  in order to avoid a build cycle (fipscheck, xmlto, libxslt, libgcrypt)
  * add fipscheck-dont_generate_manpages.patch
- fix build on older distributions</changelog>
  <changelog author="vcizek@suse.com" date="1568635200">- Remove #include of unused fips.h to fix build with OpenSSL 1.1.1
  (bsc#1149792)
  * add fipscheck-fips.h_not_needed.patch
- Drop obsolete openssl-1_1-port.patch (upstream)</changelog>
  <changelog author="lnussel@suse.de" date="1605873600">- move libs to %_libdir (boo#1029961)</changelog>
  <changelog author="meissner@suse.com" date="1667390400">- updated to 1.7.0 (from a different supplier)
  - openssl 3 support
- dropped fipscheck-dont_generate_manpages.patch (not needed)
- dropped fipscheck-fips.h_not_needed.patch (not needed)</changelog>
  <changelog author="mjambor@suse.com" date="1720440000">- Backport upstream patches fipscheck-fix_check_openssl_version.patch
  and fipscheck-fix_incorrect_length_type.patch to fix C99 violations
  which are errors by default with GCC 14 [boo#1221714] - although the
  first one looks like it possibly fixes some more substantial error.</changelog>
</package>
<package pkgid="44018b749f4705204cc786381925ad7820b0b960b6a02d498c5145b8085c2bff" name="fipscheck-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.7.0" rel="46.1"/>
  <changelog author="meissner@suse.com" date="1401710400">- add baselibs.conf</changelog>
  <changelog author="jengelh@inai.de" date="1428926400">- Set RPM groups anew. Drop implicit cleaning parts.</changelog>
  <changelog author="daniel.molkentin@suse.com" date="1497268800">- Port to OpenSSL 1.1 (bsc#1042649)
  Adds openssl-1_1-port.patch</changelog>
  <changelog author="jsikes@suse.de" date="1536667200">- Updated fipscheck to 1.5.0
  * Changed source to local file since latest official release
    is not in the official releases directory.
  * Downgraded libopenssl-devel to libopenssl-1_0_0-devel because
    1.0.2 supports FIPS.</changelog>
  <changelog author="jsikes@suse.de" date="1537444800">- Changed source back to http now that current release folder
  has current tarball.</changelog>
  <changelog author="vcizek@suse.com" date="1546516800">- Use the shipped manpages instead of building them with xmlto
  in order to avoid a build cycle (fipscheck, xmlto, libxslt, libgcrypt)
  * add fipscheck-dont_generate_manpages.patch
- fix build on older distributions</changelog>
  <changelog author="vcizek@suse.com" date="1568635200">- Remove #include of unused fips.h to fix build with OpenSSL 1.1.1
  (bsc#1149792)
  * add fipscheck-fips.h_not_needed.patch
- Drop obsolete openssl-1_1-port.patch (upstream)</changelog>
  <changelog author="lnussel@suse.de" date="1605873600">- move libs to %_libdir (boo#1029961)</changelog>
  <changelog author="meissner@suse.com" date="1667390400">- updated to 1.7.0 (from a different supplier)
  - openssl 3 support
- dropped fipscheck-dont_generate_manpages.patch (not needed)
- dropped fipscheck-fips.h_not_needed.patch (not needed)</changelog>
  <changelog author="mjambor@suse.com" date="1720440000">- Backport upstream patches fipscheck-fix_check_openssl_version.patch
  and fipscheck-fix_incorrect_length_type.patch to fix C99 violations
  which are errors by default with GCC 14 [boo#1221714] - although the
  first one looks like it possibly fixes some more substantial error.</changelog>
</package>
<package pkgid="0d3601390bb204cf98fdf67106cd2b0a65a8a1b3d82e35061842c75759b90fac" name="fipscheck-debugsource" arch="x86_64">
  <version epoch="0" ver="1.7.0" rel="46.1"/>
  <changelog author="meissner@suse.com" date="1401710400">- add baselibs.conf</changelog>
  <changelog author="jengelh@inai.de" date="1428926400">- Set RPM groups anew. Drop implicit cleaning parts.</changelog>
  <changelog author="daniel.molkentin@suse.com" date="1497268800">- Port to OpenSSL 1.1 (bsc#1042649)
  Adds openssl-1_1-port.patch</changelog>
  <changelog author="jsikes@suse.de" date="1536667200">- Updated fipscheck to 1.5.0
  * Changed source to local file since latest official release
    is not in the official releases directory.
  * Downgraded libopenssl-devel to libopenssl-1_0_0-devel because
    1.0.2 supports FIPS.</changelog>
  <changelog author="jsikes@suse.de" date="1537444800">- Changed source back to http now that current release folder
  has current tarball.</changelog>
  <changelog author="vcizek@suse.com" date="1546516800">- Use the shipped manpages instead of building them with xmlto
  in order to avoid a build cycle (fipscheck, xmlto, libxslt, libgcrypt)
  * add fipscheck-dont_generate_manpages.patch
- fix build on older distributions</changelog>
  <changelog author="vcizek@suse.com" date="1568635200">- Remove #include of unused fips.h to fix build with OpenSSL 1.1.1
  (bsc#1149792)
  * add fipscheck-fips.h_not_needed.patch
- Drop obsolete openssl-1_1-port.patch (upstream)</changelog>
  <changelog author="lnussel@suse.de" date="1605873600">- move libs to %_libdir (boo#1029961)</changelog>
  <changelog author="meissner@suse.com" date="1667390400">- updated to 1.7.0 (from a different supplier)
  - openssl 3 support
- dropped fipscheck-dont_generate_manpages.patch (not needed)
- dropped fipscheck-fips.h_not_needed.patch (not needed)</changelog>
  <changelog author="mjambor@suse.com" date="1720440000">- Backport upstream patches fipscheck-fix_check_openssl_version.patch
  and fipscheck-fix_incorrect_length_type.patch to fix C99 violations
  which are errors by default with GCC 14 [boo#1221714] - although the
  first one looks like it possibly fixes some more substantial error.</changelog>
</package>
<package pkgid="99d80009997705ff3c6974d7bf7270e6d02fb1cb59e0e45542bccb9113ded8cb" name="fipscheck-devel" arch="x86_64">
  <version epoch="0" ver="1.7.0" rel="46.1"/>
  <changelog author="meissner@suse.com" date="1401710400">- add baselibs.conf</changelog>
  <changelog author="jengelh@inai.de" date="1428926400">- Set RPM groups anew. Drop implicit cleaning parts.</changelog>
  <changelog author="daniel.molkentin@suse.com" date="1497268800">- Port to OpenSSL 1.1 (bsc#1042649)
  Adds openssl-1_1-port.patch</changelog>
  <changelog author="jsikes@suse.de" date="1536667200">- Updated fipscheck to 1.5.0
  * Changed source to local file since latest official release
    is not in the official releases directory.
  * Downgraded libopenssl-devel to libopenssl-1_0_0-devel because
    1.0.2 supports FIPS.</changelog>
  <changelog author="jsikes@suse.de" date="1537444800">- Changed source back to http now that current release folder
  has current tarball.</changelog>
  <changelog author="vcizek@suse.com" date="1546516800">- Use the shipped manpages instead of building them with xmlto
  in order to avoid a build cycle (fipscheck, xmlto, libxslt, libgcrypt)
  * add fipscheck-dont_generate_manpages.patch
- fix build on older distributions</changelog>
  <changelog author="vcizek@suse.com" date="1568635200">- Remove #include of unused fips.h to fix build with OpenSSL 1.1.1
  (bsc#1149792)
  * add fipscheck-fips.h_not_needed.patch
- Drop obsolete openssl-1_1-port.patch (upstream)</changelog>
  <changelog author="lnussel@suse.de" date="1605873600">- move libs to %_libdir (boo#1029961)</changelog>
  <changelog author="meissner@suse.com" date="1667390400">- updated to 1.7.0 (from a different supplier)
  - openssl 3 support
- dropped fipscheck-dont_generate_manpages.patch (not needed)
- dropped fipscheck-fips.h_not_needed.patch (not needed)</changelog>
  <changelog author="mjambor@suse.com" date="1720440000">- Backport upstream patches fipscheck-fix_check_openssl_version.patch
  and fipscheck-fix_incorrect_length_type.patch to fix C99 violations
  which are errors by default with GCC 14 [boo#1221714] - although the
  first one looks like it possibly fixes some more substantial error.</changelog>
</package>
<package pkgid="37fad8721a312223857c26b70382265f98a07786d67394770dc1d6910a4f0667" name="hmaccalc" arch="src">
  <version epoch="0" ver="0.9.14" rel="18.1"/>
  <changelog author="meissner@suse.com" date="1397476800">- new package, generate certifiable HMACs for FIPS usage.
  uses the Mozilla NSS library for cryptography.</changelog>
  <changelog author="coolo@suse.com" date="1399464000">- remove prelink buildrequire - completely unneeded and unnecessarily
  increases core ring</changelog>
  <changelog author="p.drouand@gmail.com" date="1421582400">- Update to version 0.9.14
  * No changelog available</changelog>
  <changelog author="wr@rosenauer.org" date="1565784000">- hmac signatures were split from NSS core libs for SLE packaging
  compatibility but recommended and therefore not installed by
  the build process; now a build requirement (boo#1145414)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708603200">- Use %autosetup macro. Allows to eliminate the usage of deprecated
  %patchN</changelog>
</package>
<package pkgid="7610db42847e79b17feb27b4ec7c08d36a9783371bee50af902839a8456520eb" name="hmaccalc" arch="x86_64">
  <version epoch="0" ver="0.9.14" rel="18.1"/>
  <changelog author="meissner@suse.com" date="1397476800">- new package, generate certifiable HMACs for FIPS usage.
  uses the Mozilla NSS library for cryptography.</changelog>
  <changelog author="coolo@suse.com" date="1399464000">- remove prelink buildrequire - completely unneeded and unnecessarily
  increases core ring</changelog>
  <changelog author="p.drouand@gmail.com" date="1421582400">- Update to version 0.9.14
  * No changelog available</changelog>
  <changelog author="wr@rosenauer.org" date="1565784000">- hmac signatures were split from NSS core libs for SLE packaging
  compatibility but recommended and therefore not installed by
  the build process; now a build requirement (boo#1145414)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708603200">- Use %autosetup macro. Allows to eliminate the usage of deprecated
  %patchN</changelog>
</package>
<package pkgid="a3bddcb61020fba42e1da88054d28abdee0b1be240c1194a6381342a9bd15cee" name="hmaccalc-debuginfo" arch="x86_64">
  <version epoch="0" ver="0.9.14" rel="18.1"/>
  <changelog author="meissner@suse.com" date="1397476800">- new package, generate certifiable HMACs for FIPS usage.
  uses the Mozilla NSS library for cryptography.</changelog>
  <changelog author="coolo@suse.com" date="1399464000">- remove prelink buildrequire - completely unneeded and unnecessarily
  increases core ring</changelog>
  <changelog author="p.drouand@gmail.com" date="1421582400">- Update to version 0.9.14
  * No changelog available</changelog>
  <changelog author="wr@rosenauer.org" date="1565784000">- hmac signatures were split from NSS core libs for SLE packaging
  compatibility but recommended and therefore not installed by
  the build process; now a build requirement (boo#1145414)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708603200">- Use %autosetup macro. Allows to eliminate the usage of deprecated
  %patchN</changelog>
</package>
<package pkgid="20abf8742ae004fc6e7c8278f93b9b1b602b92ad881059e8c3e15553f964504b" name="hmaccalc-debugsource" arch="x86_64">
  <version epoch="0" ver="0.9.14" rel="18.1"/>
  <changelog author="meissner@suse.com" date="1397476800">- new package, generate certifiable HMACs for FIPS usage.
  uses the Mozilla NSS library for cryptography.</changelog>
  <changelog author="coolo@suse.com" date="1399464000">- remove prelink buildrequire - completely unneeded and unnecessarily
  increases core ring</changelog>
  <changelog author="p.drouand@gmail.com" date="1421582400">- Update to version 0.9.14
  * No changelog available</changelog>
  <changelog author="wr@rosenauer.org" date="1565784000">- hmac signatures were split from NSS core libs for SLE packaging
  compatibility but recommended and therefore not installed by
  the build process; now a build requirement (boo#1145414)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708603200">- Use %autosetup macro. Allows to eliminate the usage of deprecated
  %patchN</changelog>
</package>
<package pkgid="041924f99894bcffe9bc16246e50fddeb7ed7644df8337c861f8df5abb41a5e2" name="john" arch="src">
  <version epoch="0" ver="1.9.0" rel="98.1"/>
  <changelog author="dvaleev@suse.com" date="1389355200">- Fix build on ppc64le
- added patches:
  * ppc64le.patch</changelog>
  <changelog author="lars@linux-schulserver.de" date="1418644800">- include "jumbo patch" into the build - special thanks to
  Mark Draheim for the specfile patch (closes bnc #839246)</changelog>
  <changelog author="astieger@suse.com" date="1435233600">- fix SLE 11 SP3 build</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1455710400">- as follow on of previous "jumbo patch" need two powerpc changes:
  new john-1.7.9-powerpc_BE_need_rhash_u32_swap_copy.patch
  place ppc64le.patch after application of "jumbo patch" in spec
  allow to solve partially boo #940498  for ppc64le
  but still have 4 FAILED tests for ppc64 tracked upstream by
  http://www.openwall.com/lists/john-dev/2016/02/16/1</changelog>
  <changelog author="meissner@suse.com" date="1481198400">- remove incorrect too large john.keyring ...
  The signature of these tarballs is currently with a key with MD5 hash,
  which is rejected by default.</changelog>
  <changelog author="bwiedemann@suse.com" date="1495886400">- Add reproducible.patch to sort input files to make build reproducible
  (boo#1041090)</changelog>
  <changelog author="dimstar@opensuse.org" date="1522152000">- Build against openSSL 1.0 until upstream catches up
  (boo#1078844).</changelog>
  <changelog author="simmphonie@opensuse.org" date="1559822400">- spec-file changes
  + add jumbo scripts and remove "env" from shebang
  + remove patches. In upstream already:
    + john-1.7.9-powerpc_BE_need_rhash_u32_swap_copy.patch
    + ppc64le.patch
    + reproducible.patch
  + use configure to find dependenices and CPU architecture
    + openCL support
    + multicore support with fork option
    + require CPU with AVX support at least
  + root rights are no longer required
- update to 1.9.0
  + Increased the interleaving for bcrypt on x86-64 from 2x to 3x for a major
    speedup on CPUs without SMT.  Unfortunately, this sometimes results in a minor
    performance regression when running multiple threads on CPUs with SMT.
  + Recognize the $2b$ bcrypt prefix.
  + In the generic crypt(3) format, detect descrypt with valid vs. invalid salts
    as separate id's for our heuristics on supported hash types.
  + Introduced a number of optimizations for faster handling of large password
    hash files, including loading, cracking, and "--show".  Some of these use more
    memory than before, yet in a more efficient manner.
  + Benchmark using all-different candidate passwords of length 7 by default.
  + Dropped undocumented special handling of "Mc" in 'c' and 'C' rule commands.
  + Dropped undocumented limitation of the 'M' and 'Q' rule commands where they
    would sometimes memorize/check only up to the current hash type's length limit
    yet this optimization wouldn't necessarily be transparent (e.g., if a later
    command would extract a substring from above the hash type's length limit and
    bring it to within the limit).
  + Implemented special-case handling of repeated rule commands '$', '^', '[',
    ']', '{', and '}', as well as faster handling of the 'D' command.
  + When built with "--fork" support, disallow session names with all-digit
    suffixes since these clash with those produced by "--fork".
  + Forward SIGTERM to --fork'ed children.
  + Set stdout to line buffered (rather than potentially fully buffered), except
    for "--stdout", "--show", and auxiliary programs such as "unshadow".
  + On Windows, restore normal processing of Ctrl-C in case our parent (such as
    Johnny the GUI) had disabled it.
  + Added linux-x86*-avx512 and linux-x86*-avx2 make targets, which use
    respectively AVX-512 and AVX2 for bitslice DES.
  + Added linux-mic make target for Intel MIC (first generation Xeon Phi, aka
    Knights Corner), which uses its 512-bit SIMD intrinsics for bitslice DES.
    (For second generation Xeon Phi, aka Knights Landing, use linux-x86-64-avx512.)
  + Added linux-arm64le, linux-arm32le-neon, and linux-arm32le make targets.
    (The first two of these make use of ASIMD or NEON for bitslice DES.)
  + Added linux-sparc64 make target.
  + Made a minor optimization to MMX and SSE2 assembly code for LM hash.
  + Dropped Ultrix and SCO support.
  + Don't probe for alternate config file names (like john.ini when on Unix).
  + "DokuWiki" external mode sample has been added to the default john.conf.
  + Fixed operator precedence in the external mode compiler to be the same as C.
  + Fixed an out of bounds write bug in the external mode virtual machine.
  + Fixed a bug introduced in version 1.7.4 in the wordlist rules engine, where
    some sequences of rule commands could overflow a word buffer.
  + Fixed a bug where unaligned access SSE/AVX instructions would unnecessarily
    be generated by GCC 4.6+ in the bitslice DES code in non-OpenMP builds.
  + Fixed a bug where "Warning: no OpenMP support for this hash type" could be
    printed in "--stdout" mode.
  + Made assorted other bugfixes, portability and documentation enhancements.
- version 1.7.9.8
  + Revised the incremental mode to let the current character counts grow for
    each character position independently, with the aim to improve efficiency in
    terms of successful guesses per candidate passwords tested.
  + Revised the pre-defined incremental modes, as well as external mode filters
    that are used to generate .chr files.
  + Added makechr, a script to (re-)generate .chr files.
  + Enhanced the status reporting to include four distinct speed metrics (g/s,
    p/s, c/s, and C/s).
  + Added the "--fork=N" and "--node=MIN[-MAX]/TOTAL" options for trivial
    parallel and distributed processing.
  + In the external mode compiler, treat character literals as unsigned.
  + Renamed many of the formats.
  + Updated the documentation.
  + Relaxed the license for many source files to cut-down BSD.
  + Relaxed the license for John the Ripper as a whole from GPLv2 (exact version)
    to GPLv2 or newer with optional OpenSSL and unRAR exceptions.
  + Assorted other changes have been made.</changelog>
  <changelog author="christophe@krop.fr" date="1567425600">- Fix the sources URL. Use https.</changelog>
  <changelog author="simmphonie@opensuse.org" date="1568030400">- remove setBadness from rpmlintrc</changelog>
  <changelog author="jengelh@inai.de" date="1568116800">- Use noun phrase in summary. Reword description to avoid
  unspecific "Unix password".</changelog>
  <changelog author="simmphonie@opensuse.org" date="1568116801">- Fixed build for ARM and PPC. CPU with AVX support at least is
  only available for x86_64 architecture now.</changelog>
  <changelog author="simmphonie@opensuse.org" date="1570881600">- Remove fdupes check (build fails with debug packages)</changelog>
  <changelog author="mpluskal@suse.com" date="1591963200">- Fix building with gcc10
- Small cleanup of spec file with spec-cleaner</changelog>
  <changelog author="simmphonie@opensuse.org" date="1601985600">- Add cl-device.patch to handle systems that already defined
  CL_DEVICE_TOPOLOGY_AMD  gh#4331</changelog>
  <changelog author="dmueller@suse.com" date="1615636800">- enable ztex support (fix usb dependency):
  add john-1.9.0-jumbo-gcc10.patch to fix fcommon related build failures</changelog>
  <changelog author="simmphonie@opensuse.org" date="1623153600">- add john-1.9.0-jumbo-gcc11.patch to fix alignment compile errors
  on GCC 11 gh#4611</changelog>
  <changelog author="sarah.kriesch@opensuse.org" date="1634040000">- Upstream patch for Big Endians in s390x-upstream.patch
- Include johnswap.h in opencl_7z_fmt_plug.c with s390x.patch</changelog>
  <changelog author="lars@linux-schulserver.de - 1.9.0" date="1663243200">- disable enforcement of AVX support in the CPU: let john handle this
  during runtime automatically (bsc#1202318)</changelog>
  <changelog author="bwiedemann@suse.com" date="1683547200">- Add john-1.9-python3.patch to not require python2 anymore (boo#1210583)
- Use %autopatch</changelog>
</package>
<package pkgid="58cdf3d099c4ed20f819e9c2542f651c6ecb699122d5b4adf89d0758c8ea37df" name="john" arch="x86_64">
  <version epoch="0" ver="1.9.0" rel="98.1"/>
  <changelog author="lars@linux-schulserver.de" date="1418644800">- include "jumbo patch" into the build - special thanks to
  Mark Draheim for the specfile patch (closes bnc #839246)</changelog>
  <changelog author="astieger@suse.com" date="1435233600">- fix SLE 11 SP3 build</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1455710400">- as follow on of previous "jumbo patch" need two powerpc changes:
  new john-1.7.9-powerpc_BE_need_rhash_u32_swap_copy.patch
  place ppc64le.patch after application of "jumbo patch" in spec
  allow to solve partially boo #940498  for ppc64le
  but still have 4 FAILED tests for ppc64 tracked upstream by
  http://www.openwall.com/lists/john-dev/2016/02/16/1</changelog>
  <changelog author="meissner@suse.com" date="1481198400">- remove incorrect too large john.keyring ...
  The signature of these tarballs is currently with a key with MD5 hash,
  which is rejected by default.</changelog>
  <changelog author="bwiedemann@suse.com" date="1495886400">- Add reproducible.patch to sort input files to make build reproducible
  (boo#1041090)</changelog>
  <changelog author="dimstar@opensuse.org" date="1522152000">- Build against openSSL 1.0 until upstream catches up
  (boo#1078844).</changelog>
  <changelog author="simmphonie@opensuse.org" date="1559822400">- spec-file changes
  + add jumbo scripts and remove "env" from shebang
  + remove patches. In upstream already:
    + john-1.7.9-powerpc_BE_need_rhash_u32_swap_copy.patch
    + ppc64le.patch
    + reproducible.patch
  + use configure to find dependenices and CPU architecture
    + openCL support
    + multicore support with fork option
    + require CPU with AVX support at least
  + root rights are no longer required
- update to 1.9.0
  + Increased the interleaving for bcrypt on x86-64 from 2x to 3x for a major
    speedup on CPUs without SMT.  Unfortunately, this sometimes results in a minor
    performance regression when running multiple threads on CPUs with SMT.
  + Recognize the $2b$ bcrypt prefix.
  + In the generic crypt(3) format, detect descrypt with valid vs. invalid salts
    as separate id's for our heuristics on supported hash types.
  + Introduced a number of optimizations for faster handling of large password
    hash files, including loading, cracking, and "--show".  Some of these use more
    memory than before, yet in a more efficient manner.
  + Benchmark using all-different candidate passwords of length 7 by default.
  + Dropped undocumented special handling of "Mc" in 'c' and 'C' rule commands.
  + Dropped undocumented limitation of the 'M' and 'Q' rule commands where they
    would sometimes memorize/check only up to the current hash type's length limit
    yet this optimization wouldn't necessarily be transparent (e.g., if a later
    command would extract a substring from above the hash type's length limit and
    bring it to within the limit).
  + Implemented special-case handling of repeated rule commands '$', '^', '[',
    ']', '{', and '}', as well as faster handling of the 'D' command.
  + When built with "--fork" support, disallow session names with all-digit
    suffixes since these clash with those produced by "--fork".
  + Forward SIGTERM to --fork'ed children.
  + Set stdout to line buffered (rather than potentially fully buffered), except
    for "--stdout", "--show", and auxiliary programs such as "unshadow".
  + On Windows, restore normal processing of Ctrl-C in case our parent (such as
    Johnny the GUI) had disabled it.
  + Added linux-x86*-avx512 and linux-x86*-avx2 make targets, which use
    respectively AVX-512 and AVX2 for bitslice DES.
  + Added linux-mic make target for Intel MIC (first generation Xeon Phi, aka
    Knights Corner), which uses its 512-bit SIMD intrinsics for bitslice DES.
    (For second generation Xeon Phi, aka Knights Landing, use linux-x86-64-avx512.)
  + Added linux-arm64le, linux-arm32le-neon, and linux-arm32le make targets.
    (The first two of these make use of ASIMD or NEON for bitslice DES.)
  + Added linux-sparc64 make target.
  + Made a minor optimization to MMX and SSE2 assembly code for LM hash.
  + Dropped Ultrix and SCO support.
  + Don't probe for alternate config file names (like john.ini when on Unix).
  + "DokuWiki" external mode sample has been added to the default john.conf.
  + Fixed operator precedence in the external mode compiler to be the same as C.
  + Fixed an out of bounds write bug in the external mode virtual machine.
  + Fixed a bug introduced in version 1.7.4 in the wordlist rules engine, where
    some sequences of rule commands could overflow a word buffer.
  + Fixed a bug where unaligned access SSE/AVX instructions would unnecessarily
    be generated by GCC 4.6+ in the bitslice DES code in non-OpenMP builds.
  + Fixed a bug where "Warning: no OpenMP support for this hash type" could be
    printed in "--stdout" mode.
  + Made assorted other bugfixes, portability and documentation enhancements.
- version 1.7.9.8
  + Revised the incremental mode to let the current character counts grow for
    each character position independently, with the aim to improve efficiency in
    terms of successful guesses per candidate passwords tested.
  + Revised the pre-defined incremental modes, as well as external mode filters
    that are used to generate .chr files.
  + Added makechr, a script to (re-)generate .chr files.
  + Enhanced the status reporting to include four distinct speed metrics (g/s,
    p/s, c/s, and C/s).
  + Added the "--fork=N" and "--node=MIN[-MAX]/TOTAL" options for trivial
    parallel and distributed processing.
  + In the external mode compiler, treat character literals as unsigned.
  + Renamed many of the formats.
  + Updated the documentation.
  + Relaxed the license for many source files to cut-down BSD.
  + Relaxed the license for John the Ripper as a whole from GPLv2 (exact version)
    to GPLv2 or newer with optional OpenSSL and unRAR exceptions.
  + Assorted other changes have been made.</changelog>
  <changelog author="christophe@krop.fr" date="1567425600">- Fix the sources URL. Use https.</changelog>
  <changelog author="simmphonie@opensuse.org" date="1568030400">- remove setBadness from rpmlintrc</changelog>
  <changelog author="jengelh@inai.de" date="1568116800">- Use noun phrase in summary. Reword description to avoid
  unspecific "Unix password".</changelog>
  <changelog author="simmphonie@opensuse.org" date="1568116801">- Fixed build for ARM and PPC. CPU with AVX support at least is
  only available for x86_64 architecture now.</changelog>
  <changelog author="simmphonie@opensuse.org" date="1570881600">- Remove fdupes check (build fails with debug packages)</changelog>
  <changelog author="mpluskal@suse.com" date="1591963200">- Fix building with gcc10
- Small cleanup of spec file with spec-cleaner</changelog>
  <changelog author="simmphonie@opensuse.org" date="1601985600">- Add cl-device.patch to handle systems that already defined
  CL_DEVICE_TOPOLOGY_AMD  gh#4331</changelog>
  <changelog author="dmueller@suse.com" date="1615636800">- enable ztex support (fix usb dependency):
  add john-1.9.0-jumbo-gcc10.patch to fix fcommon related build failures</changelog>
  <changelog author="simmphonie@opensuse.org" date="1623153600">- add john-1.9.0-jumbo-gcc11.patch to fix alignment compile errors
  on GCC 11 gh#4611</changelog>
  <changelog author="sarah.kriesch@opensuse.org" date="1634040000">- Upstream patch for Big Endians in s390x-upstream.patch
- Include johnswap.h in opencl_7z_fmt_plug.c with s390x.patch</changelog>
  <changelog author="lars@linux-schulserver.de - 1.9.0" date="1663243200">- disable enforcement of AVX support in the CPU: let john handle this
  during runtime automatically (bsc#1202318)</changelog>
  <changelog author="bwiedemann@suse.com" date="1683547200">- Add john-1.9-python3.patch to not require python2 anymore (boo#1210583)
- Use %autopatch</changelog>
</package>
<package pkgid="57326b8e7ee25d78d0f7730ef22977d72cc378d668426c86b4944304a220fdb5" name="john-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.9.0" rel="98.1"/>
  <changelog author="lars@linux-schulserver.de" date="1418644800">- include "jumbo patch" into the build - special thanks to
  Mark Draheim for the specfile patch (closes bnc #839246)</changelog>
  <changelog author="astieger@suse.com" date="1435233600">- fix SLE 11 SP3 build</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1455710400">- as follow on of previous "jumbo patch" need two powerpc changes:
  new john-1.7.9-powerpc_BE_need_rhash_u32_swap_copy.patch
  place ppc64le.patch after application of "jumbo patch" in spec
  allow to solve partially boo #940498  for ppc64le
  but still have 4 FAILED tests for ppc64 tracked upstream by
  http://www.openwall.com/lists/john-dev/2016/02/16/1</changelog>
  <changelog author="meissner@suse.com" date="1481198400">- remove incorrect too large john.keyring ...
  The signature of these tarballs is currently with a key with MD5 hash,
  which is rejected by default.</changelog>
  <changelog author="bwiedemann@suse.com" date="1495886400">- Add reproducible.patch to sort input files to make build reproducible
  (boo#1041090)</changelog>
  <changelog author="dimstar@opensuse.org" date="1522152000">- Build against openSSL 1.0 until upstream catches up
  (boo#1078844).</changelog>
  <changelog author="simmphonie@opensuse.org" date="1559822400">- spec-file changes
  + add jumbo scripts and remove "env" from shebang
  + remove patches. In upstream already:
    + john-1.7.9-powerpc_BE_need_rhash_u32_swap_copy.patch
    + ppc64le.patch
    + reproducible.patch
  + use configure to find dependenices and CPU architecture
    + openCL support
    + multicore support with fork option
    + require CPU with AVX support at least
  + root rights are no longer required
- update to 1.9.0
  + Increased the interleaving for bcrypt on x86-64 from 2x to 3x for a major
    speedup on CPUs without SMT.  Unfortunately, this sometimes results in a minor
    performance regression when running multiple threads on CPUs with SMT.
  + Recognize the $2b$ bcrypt prefix.
  + In the generic crypt(3) format, detect descrypt with valid vs. invalid salts
    as separate id's for our heuristics on supported hash types.
  + Introduced a number of optimizations for faster handling of large password
    hash files, including loading, cracking, and "--show".  Some of these use more
    memory than before, yet in a more efficient manner.
  + Benchmark using all-different candidate passwords of length 7 by default.
  + Dropped undocumented special handling of "Mc" in 'c' and 'C' rule commands.
  + Dropped undocumented limitation of the 'M' and 'Q' rule commands where they
    would sometimes memorize/check only up to the current hash type's length limit
    yet this optimization wouldn't necessarily be transparent (e.g., if a later
    command would extract a substring from above the hash type's length limit and
    bring it to within the limit).
  + Implemented special-case handling of repeated rule commands '$', '^', '[',
    ']', '{', and '}', as well as faster handling of the 'D' command.
  + When built with "--fork" support, disallow session names with all-digit
    suffixes since these clash with those produced by "--fork".
  + Forward SIGTERM to --fork'ed children.
  + Set stdout to line buffered (rather than potentially fully buffered), except
    for "--stdout", "--show", and auxiliary programs such as "unshadow".
  + On Windows, restore normal processing of Ctrl-C in case our parent (such as
    Johnny the GUI) had disabled it.
  + Added linux-x86*-avx512 and linux-x86*-avx2 make targets, which use
    respectively AVX-512 and AVX2 for bitslice DES.
  + Added linux-mic make target for Intel MIC (first generation Xeon Phi, aka
    Knights Corner), which uses its 512-bit SIMD intrinsics for bitslice DES.
    (For second generation Xeon Phi, aka Knights Landing, use linux-x86-64-avx512.)
  + Added linux-arm64le, linux-arm32le-neon, and linux-arm32le make targets.
    (The first two of these make use of ASIMD or NEON for bitslice DES.)
  + Added linux-sparc64 make target.
  + Made a minor optimization to MMX and SSE2 assembly code for LM hash.
  + Dropped Ultrix and SCO support.
  + Don't probe for alternate config file names (like john.ini when on Unix).
  + "DokuWiki" external mode sample has been added to the default john.conf.
  + Fixed operator precedence in the external mode compiler to be the same as C.
  + Fixed an out of bounds write bug in the external mode virtual machine.
  + Fixed a bug introduced in version 1.7.4 in the wordlist rules engine, where
    some sequences of rule commands could overflow a word buffer.
  + Fixed a bug where unaligned access SSE/AVX instructions would unnecessarily
    be generated by GCC 4.6+ in the bitslice DES code in non-OpenMP builds.
  + Fixed a bug where "Warning: no OpenMP support for this hash type" could be
    printed in "--stdout" mode.
  + Made assorted other bugfixes, portability and documentation enhancements.
- version 1.7.9.8
  + Revised the incremental mode to let the current character counts grow for
    each character position independently, with the aim to improve efficiency in
    terms of successful guesses per candidate passwords tested.
  + Revised the pre-defined incremental modes, as well as external mode filters
    that are used to generate .chr files.
  + Added makechr, a script to (re-)generate .chr files.
  + Enhanced the status reporting to include four distinct speed metrics (g/s,
    p/s, c/s, and C/s).
  + Added the "--fork=N" and "--node=MIN[-MAX]/TOTAL" options for trivial
    parallel and distributed processing.
  + In the external mode compiler, treat character literals as unsigned.
  + Renamed many of the formats.
  + Updated the documentation.
  + Relaxed the license for many source files to cut-down BSD.
  + Relaxed the license for John the Ripper as a whole from GPLv2 (exact version)
    to GPLv2 or newer with optional OpenSSL and unRAR exceptions.
  + Assorted other changes have been made.</changelog>
  <changelog author="christophe@krop.fr" date="1567425600">- Fix the sources URL. Use https.</changelog>
  <changelog author="simmphonie@opensuse.org" date="1568030400">- remove setBadness from rpmlintrc</changelog>
  <changelog author="jengelh@inai.de" date="1568116800">- Use noun phrase in summary. Reword description to avoid
  unspecific "Unix password".</changelog>
  <changelog author="simmphonie@opensuse.org" date="1568116801">- Fixed build for ARM and PPC. CPU with AVX support at least is
  only available for x86_64 architecture now.</changelog>
  <changelog author="simmphonie@opensuse.org" date="1570881600">- Remove fdupes check (build fails with debug packages)</changelog>
  <changelog author="mpluskal@suse.com" date="1591963200">- Fix building with gcc10
- Small cleanup of spec file with spec-cleaner</changelog>
  <changelog author="simmphonie@opensuse.org" date="1601985600">- Add cl-device.patch to handle systems that already defined
  CL_DEVICE_TOPOLOGY_AMD  gh#4331</changelog>
  <changelog author="dmueller@suse.com" date="1615636800">- enable ztex support (fix usb dependency):
  add john-1.9.0-jumbo-gcc10.patch to fix fcommon related build failures</changelog>
  <changelog author="simmphonie@opensuse.org" date="1623153600">- add john-1.9.0-jumbo-gcc11.patch to fix alignment compile errors
  on GCC 11 gh#4611</changelog>
  <changelog author="sarah.kriesch@opensuse.org" date="1634040000">- Upstream patch for Big Endians in s390x-upstream.patch
- Include johnswap.h in opencl_7z_fmt_plug.c with s390x.patch</changelog>
  <changelog author="lars@linux-schulserver.de - 1.9.0" date="1663243200">- disable enforcement of AVX support in the CPU: let john handle this
  during runtime automatically (bsc#1202318)</changelog>
  <changelog author="bwiedemann@suse.com" date="1683547200">- Add john-1.9-python3.patch to not require python2 anymore (boo#1210583)
- Use %autopatch</changelog>
</package>
<package pkgid="f6bc0807df01677fc66b7f8a1d2d1e4dafba7e9e3ba4b94ec2a65d16b4cb33d7" name="john-debugsource" arch="x86_64">
  <version epoch="0" ver="1.9.0" rel="98.1"/>
  <changelog author="lars@linux-schulserver.de" date="1418644800">- include "jumbo patch" into the build - special thanks to
  Mark Draheim for the specfile patch (closes bnc #839246)</changelog>
  <changelog author="astieger@suse.com" date="1435233600">- fix SLE 11 SP3 build</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1455710400">- as follow on of previous "jumbo patch" need two powerpc changes:
  new john-1.7.9-powerpc_BE_need_rhash_u32_swap_copy.patch
  place ppc64le.patch after application of "jumbo patch" in spec
  allow to solve partially boo #940498  for ppc64le
  but still have 4 FAILED tests for ppc64 tracked upstream by
  http://www.openwall.com/lists/john-dev/2016/02/16/1</changelog>
  <changelog author="meissner@suse.com" date="1481198400">- remove incorrect too large john.keyring ...
  The signature of these tarballs is currently with a key with MD5 hash,
  which is rejected by default.</changelog>
  <changelog author="bwiedemann@suse.com" date="1495886400">- Add reproducible.patch to sort input files to make build reproducible
  (boo#1041090)</changelog>
  <changelog author="dimstar@opensuse.org" date="1522152000">- Build against openSSL 1.0 until upstream catches up
  (boo#1078844).</changelog>
  <changelog author="simmphonie@opensuse.org" date="1559822400">- spec-file changes
  + add jumbo scripts and remove "env" from shebang
  + remove patches. In upstream already:
    + john-1.7.9-powerpc_BE_need_rhash_u32_swap_copy.patch
    + ppc64le.patch
    + reproducible.patch
  + use configure to find dependenices and CPU architecture
    + openCL support
    + multicore support with fork option
    + require CPU with AVX support at least
  + root rights are no longer required
- update to 1.9.0
  + Increased the interleaving for bcrypt on x86-64 from 2x to 3x for a major
    speedup on CPUs without SMT.  Unfortunately, this sometimes results in a minor
    performance regression when running multiple threads on CPUs with SMT.
  + Recognize the $2b$ bcrypt prefix.
  + In the generic crypt(3) format, detect descrypt with valid vs. invalid salts
    as separate id's for our heuristics on supported hash types.
  + Introduced a number of optimizations for faster handling of large password
    hash files, including loading, cracking, and "--show".  Some of these use more
    memory than before, yet in a more efficient manner.
  + Benchmark using all-different candidate passwords of length 7 by default.
  + Dropped undocumented special handling of "Mc" in 'c' and 'C' rule commands.
  + Dropped undocumented limitation of the 'M' and 'Q' rule commands where they
    would sometimes memorize/check only up to the current hash type's length limit
    yet this optimization wouldn't necessarily be transparent (e.g., if a later
    command would extract a substring from above the hash type's length limit and
    bring it to within the limit).
  + Implemented special-case handling of repeated rule commands '$', '^', '[',
    ']', '{', and '}', as well as faster handling of the 'D' command.
  + When built with "--fork" support, disallow session names with all-digit
    suffixes since these clash with those produced by "--fork".
  + Forward SIGTERM to --fork'ed children.
  + Set stdout to line buffered (rather than potentially fully buffered), except
    for "--stdout", "--show", and auxiliary programs such as "unshadow".
  + On Windows, restore normal processing of Ctrl-C in case our parent (such as
    Johnny the GUI) had disabled it.
  + Added linux-x86*-avx512 and linux-x86*-avx2 make targets, which use
    respectively AVX-512 and AVX2 for bitslice DES.
  + Added linux-mic make target for Intel MIC (first generation Xeon Phi, aka
    Knights Corner), which uses its 512-bit SIMD intrinsics for bitslice DES.
    (For second generation Xeon Phi, aka Knights Landing, use linux-x86-64-avx512.)
  + Added linux-arm64le, linux-arm32le-neon, and linux-arm32le make targets.
    (The first two of these make use of ASIMD or NEON for bitslice DES.)
  + Added linux-sparc64 make target.
  + Made a minor optimization to MMX and SSE2 assembly code for LM hash.
  + Dropped Ultrix and SCO support.
  + Don't probe for alternate config file names (like john.ini when on Unix).
  + "DokuWiki" external mode sample has been added to the default john.conf.
  + Fixed operator precedence in the external mode compiler to be the same as C.
  + Fixed an out of bounds write bug in the external mode virtual machine.
  + Fixed a bug introduced in version 1.7.4 in the wordlist rules engine, where
    some sequences of rule commands could overflow a word buffer.
  + Fixed a bug where unaligned access SSE/AVX instructions would unnecessarily
    be generated by GCC 4.6+ in the bitslice DES code in non-OpenMP builds.
  + Fixed a bug where "Warning: no OpenMP support for this hash type" could be
    printed in "--stdout" mode.
  + Made assorted other bugfixes, portability and documentation enhancements.
- version 1.7.9.8
  + Revised the incremental mode to let the current character counts grow for
    each character position independently, with the aim to improve efficiency in
    terms of successful guesses per candidate passwords tested.
  + Revised the pre-defined incremental modes, as well as external mode filters
    that are used to generate .chr files.
  + Added makechr, a script to (re-)generate .chr files.
  + Enhanced the status reporting to include four distinct speed metrics (g/s,
    p/s, c/s, and C/s).
  + Added the "--fork=N" and "--node=MIN[-MAX]/TOTAL" options for trivial
    parallel and distributed processing.
  + In the external mode compiler, treat character literals as unsigned.
  + Renamed many of the formats.
  + Updated the documentation.
  + Relaxed the license for many source files to cut-down BSD.
  + Relaxed the license for John the Ripper as a whole from GPLv2 (exact version)
    to GPLv2 or newer with optional OpenSSL and unRAR exceptions.
  + Assorted other changes have been made.</changelog>
  <changelog author="christophe@krop.fr" date="1567425600">- Fix the sources URL. Use https.</changelog>
  <changelog author="simmphonie@opensuse.org" date="1568030400">- remove setBadness from rpmlintrc</changelog>
  <changelog author="jengelh@inai.de" date="1568116800">- Use noun phrase in summary. Reword description to avoid
  unspecific "Unix password".</changelog>
  <changelog author="simmphonie@opensuse.org" date="1568116801">- Fixed build for ARM and PPC. CPU with AVX support at least is
  only available for x86_64 architecture now.</changelog>
  <changelog author="simmphonie@opensuse.org" date="1570881600">- Remove fdupes check (build fails with debug packages)</changelog>
  <changelog author="mpluskal@suse.com" date="1591963200">- Fix building with gcc10
- Small cleanup of spec file with spec-cleaner</changelog>
  <changelog author="simmphonie@opensuse.org" date="1601985600">- Add cl-device.patch to handle systems that already defined
  CL_DEVICE_TOPOLOGY_AMD  gh#4331</changelog>
  <changelog author="dmueller@suse.com" date="1615636800">- enable ztex support (fix usb dependency):
  add john-1.9.0-jumbo-gcc10.patch to fix fcommon related build failures</changelog>
  <changelog author="simmphonie@opensuse.org" date="1623153600">- add john-1.9.0-jumbo-gcc11.patch to fix alignment compile errors
  on GCC 11 gh#4611</changelog>
  <changelog author="sarah.kriesch@opensuse.org" date="1634040000">- Upstream patch for Big Endians in s390x-upstream.patch
- Include johnswap.h in opencl_7z_fmt_plug.c with s390x.patch</changelog>
  <changelog author="lars@linux-schulserver.de - 1.9.0" date="1663243200">- disable enforcement of AVX support in the CPU: let john handle this
  during runtime automatically (bsc#1202318)</changelog>
  <changelog author="bwiedemann@suse.com" date="1683547200">- Add john-1.9-python3.patch to not require python2 anymore (boo#1210583)
- Use %autopatch</changelog>
</package>
<package pkgid="127bf22ec355b0854bae1faf0f843d04f536b2462165f6b3e59693b94b60d256" name="libclamav9" arch="x86_64">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="2dfd6b1a3d049393211982883fd008cc94029481f0f8d6c3fd9ffa494434bbac" name="libclamav9-debuginfo" arch="x86_64">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="a7bc48a71be8c590955aee5a39683eecea91cb3f6392f8cffb96bbe041889c25" name="libcryptsetup-devel" arch="x86_64">
  <version epoch="0" ver="2.7.5" rel="220.1"/>
  <changelog author="lnussel@suse.de" date="1631793600">- cryptsetup 2.4.1
  * Fix compilation for libc implementations without dlvsym().
  * Fix compilation and tests on systems with non-standard libraries
  * Try to workaround some issues on systems without udev support.
  * Fixes for OpenSSL3 crypto backend (including FIPS mode).
  * Print error message when assigning a token to an inactive keyslot.
  * Fix offset bug in LUKS2 encryption code if --offset option was used.
  * Do not allow LUKS2 decryption for devices with data offset.
  * Fix LUKS1 cryptsetup repair command for some specific problems.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1637236800">- cryptsetup 2.4.2:
  * Fix possible large memory allocation if LUKS2 header size is
    invalid.
  * Fix memory corruption in debug message printing LUKS2
    checksum.
  * veritysetup: remove link to the UUID library for the static
    build.
  * Remove link to pwquality library for integritysetup and
    veritysetup. These tools do not read passphrases.
  * OpenSSL3 backend: avoid remaining deprecated calls in API.
    Crypto backend no longer use API deprecated in OpenSSL 3.0
  * Check if kernel device-mapper create device failed in an early
    phase. This happens when a concurrent creation of device-mapper
    devices meets in the very early state.
  * Do not set compiler optimization flag for Argon2 KDF if the
    memory wipe is implemented in libc.
  * Do not attempt to unload LUKS2 tokens if external tokens are
    disabled. This allows building a static binary with
  - -disable-external-tokens.
  * LUKS convert: also check sysfs for device activity.
    If udev symlink is missing, code fallbacks to sysfs scan to
    prevent data corruption for the active device.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1642161600">- cryptsetup 2.4.3:
  * Fix possible attacks against data confidentiality through
    LUKS2 online reencryption extension crash recovery
    CVE-2021-4122, boo#1194469
  * Add configure option --disable-luks2-reencryption to completely
    disable LUKS2 reencryption code.
  * Improve internal metadata validation code for reencryption
    metadata
  * Add updated documentation for LUKS2 On-Disk Format
    Specification version 1.1.0
  * Fix support for bitlk (BitLocker compatible) startup key with
    new  metadata entry introduced in Windows 11
  * Fix space restriction for LUKS2 reencryption with data shift</changelog>
  <changelog author="lnussel@suse.de" date="1661169600">- cryptsetup 2.5.0:
  * Split manual pages into per-action pages and use AsciiDoc format.
  * Remove cryptsetup-reencrypt tool from the project and move reencryption
    to already existing "cryptsetup reencrypt" command.
    If you need to emulate the old cryptsetup-reencrypt binary, use simple
    wrappers script running "exec cryptsetup reencrypt $@".
  * LUKS2: implement --decryption option that allows LUKS removal.
  * Fix decryption operation with --active-name option and restrict
    it to be used only with LUKS2.
  * Do not refresh reencryption digest when not needed.
    This should speed up the reencryption resume process.
  * Store proper resilience data in LUKS2 reencrypt initialization.
    Resuming reencryption now does not require specification of resilience
    type parameters if these are the same as during initialization.
  * Properly wipe the unused area after reencryption with datashift in
    the forward direction.
  * Check datashift value against larger sector size.
    For example, it could cause an issue if misaligned 4K sector appears
    during decryption.
  * Do not allow sector size increase reencryption in offline mode.
  * Do not allow dangerous sector size change during reencryption.
  * Ask the user for confirmation before resuming reencryption.
  * Do not resume reencryption with conflicting parameters.
  * Add --force-offline-reencrypt option.
  * Do not allow nested encryption in LUKS reencrypt.
  * Support all options allowed with luksFormat with encrypt action.
  * Add resize action to integritysetup.
  * Remove obsolete dracut plugin reencryption example.
  * Fix possible keyslot area size overflow during conversion to LUKS2.
  * Allow use of --header option for cryptsetup close.
  * Fix activation of LUKS2 device with integrity and detached header.
  * Add ZEROOUT IOCTL support for crypt_wipe API call.
  * VERITY: set loopback sector size according to dm-verity block sizes.
  * veritysetup: dump device sizes.
  * LUKS2 token: prefer token PIN query before passphrase in some cases.
    When a user provides --token-type or specific --token-id, a token PIN
    query is preferred to a passphrase query.
  * LUKS2 token: allow tokens to be replaced with --token-replace option
    for cryptsetup token command.
  * LUKS2 token: do not continue operation when interrupted in PIN prompt.
  * Add --progress-json parameter to utilities.
  * Add support for --key-slot option in luksResume action.
- move man pages to separate subpackage
- drop backports handling</changelog>
  <changelog author="luca.boccassi@gmail.com" date="1663070400">- Add virtual provides for 'integritysetup' and 'veritysetup' to match
  package names provided by Fedora/RHEL, to allow the same set of
  dependencies to be used across all RPM distributions.</changelog>
  <changelog author="info@paolostivanin.com" date="1669636800">- cryptsetup 2.6.0:
  * Introduce support for handling macOS FileVault2 devices (FVAULT2).
  * libcryptsetup: no longer use global memory locking through mlockall()
  * libcryptsetup: process priority is increased only for key derivation
    (PBKDF) calls.
  * Add new LUKS keyslot context handling functions and API.
  * The volume key may now be extracted using a passphrase, keyfile, or
    token. For LUKS devices, it also returns the volume key after
    a successful crypt_format call.
  * Fix --disable-luks2-reencryption configuration option.
  * cryptsetup: Print a better error message and warning if the format
    produces an image without space available for data.
  * Print error if anti-forensic LUKS2 hash setting is not available.
    If the specified hash was not available, activation quietly failed.
  * Fix internal crypt segment compare routine if the user
    specified cipher in kernel format (capi: prefix).
  * cryptsetup: Add token unassign action.
    This action allows removing token binding on specific keyslot.
  * veritysetup: add support for --use-tasklets option.
    This option sets try_verify_in_tasklet kernel dm-verity option
    (available since Linux kernel 6.0) to allow some performance
    improvement on specific systems.
  * Provide pkgconfig Require.private settings.
    While we do not completely provide static build on udev systems,
    it helps produce statically linked binaries in certain situations.
  * Always update automake library files if autogen.sh is run.
    For several releases, we distributed older automake scripts by mistake.
  * reencryption: Fix user defined moved segment size in LUKS2 decryption.
    The --hotzone-size argument was ignored in cases where the actual data
    size was less than the original LUKS2 data offset.
  * Delegate FIPS mode detection to configured crypto backend.
    System FIPS mode check no longer depends on /etc/system-fips file.
  * Update documentation, including FAQ and man pages.</changelog>
  <changelog author="lnussel@suse.com" date="1672142400">- Replace transitional %usrmerged macro with regular version check (boo#1206798)</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1676203200">- cryptsetup 2.6.1
  * bitlk: Fixes for BitLocker-compatible on-disk metadata parser
  * Fix possible iteration overflow in OpenSSL2 PBKDF2 crypto
    backend
  * portability and compilation fixes
  * verity: Fix possible hash offset setting overflow.
  * bitlk: Fix use of startup BEK key on big-endian platforms.
  * Do not initiate encryption (reencryption command) when the
    header and data devices are the same. If data device reduction
    is not requsted, this leads to data corruption since LUKS
    metadata was written over the data device.
  * Fix possible memory leak if crypt_load() fails.
  * Always use passphrases with a minimal 8 chars length for
    benchmarking, as used in some implementation of FIPS mode</changelog>
  <changelog author="pmonreal@suse.com" date="1686744000">- FIPS: Remove not needed libcryptsetup12-hmac package that contains
  the HMAC checksums for integrity checking for FIPS. [bsc#1185116]
  * Remove the cryptsetup-rpmlintrc file.
  * Remove not needed fipscheck dependency.</changelog>
  <changelog author="pmonreal@suse.com" date="1686744001">- Enable running the regression test suite.
- Force a regeneration of the man pages from AsciiDoc.
- Add LUKS1 and LUKS2 On-Disk Format Specification pdfs to doc.</changelog>
  <changelog author="pmonreal@suse.com" date="1689249600">- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1706529600">- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1710331200">- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1712664000">- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.</changelog>
  <changelog author="pvorel@suse.cz" date="1720785600">- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).</changelog>
  <changelog author="pmonreal@suse.com" date="1722340800">- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.</changelog>
  <changelog author="martin.schreiner@suse.com" date="1722427200">- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.</changelog>
  <changelog author="meissner@suse.com" date="1725019200">- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)</changelog>
  <changelog author="pmonreal@suse.com" date="1726228800">- Update to 2.7.5:
  * Fix possible online reencryption data corruption (only in 2.7.x).
    In some situations (initializing a suspended device-mapper device),
    cryptsetup disabled direct-io device access. This caused unsafe
    online reencryption operations that could lead to data corruption.
    The code now adds strict checks (and aborts the operation) and
    changes direct-io detection code to prevent data corruption.
  * Fix a clang compilation error in SSH token plugin.
    As clang linker treats missing symbols as errors, the linker phase
    for the SSH token failed as the optional cryptsetup_token_buffer_free
    was not defined.
  * Fix crypto backend initialization in crypt_format_luks2_opal API call.</changelog>
  <changelog author="pmonreal@suse.com" date="1741953600">- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.</changelog>
</package>
<package pkgid="dd4e467ad6305ca1a753a6e7ce292e966f729ae08320e438bde1fd225505566e" name="libcryptsetup12" arch="x86_64">
  <version epoch="0" ver="2.7.5" rel="220.1"/>
  <changelog author="lnussel@suse.de" date="1631793600">- cryptsetup 2.4.1
  * Fix compilation for libc implementations without dlvsym().
  * Fix compilation and tests on systems with non-standard libraries
  * Try to workaround some issues on systems without udev support.
  * Fixes for OpenSSL3 crypto backend (including FIPS mode).
  * Print error message when assigning a token to an inactive keyslot.
  * Fix offset bug in LUKS2 encryption code if --offset option was used.
  * Do not allow LUKS2 decryption for devices with data offset.
  * Fix LUKS1 cryptsetup repair command for some specific problems.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1637236800">- cryptsetup 2.4.2:
  * Fix possible large memory allocation if LUKS2 header size is
    invalid.
  * Fix memory corruption in debug message printing LUKS2
    checksum.
  * veritysetup: remove link to the UUID library for the static
    build.
  * Remove link to pwquality library for integritysetup and
    veritysetup. These tools do not read passphrases.
  * OpenSSL3 backend: avoid remaining deprecated calls in API.
    Crypto backend no longer use API deprecated in OpenSSL 3.0
  * Check if kernel device-mapper create device failed in an early
    phase. This happens when a concurrent creation of device-mapper
    devices meets in the very early state.
  * Do not set compiler optimization flag for Argon2 KDF if the
    memory wipe is implemented in libc.
  * Do not attempt to unload LUKS2 tokens if external tokens are
    disabled. This allows building a static binary with
  - -disable-external-tokens.
  * LUKS convert: also check sysfs for device activity.
    If udev symlink is missing, code fallbacks to sysfs scan to
    prevent data corruption for the active device.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1642161600">- cryptsetup 2.4.3:
  * Fix possible attacks against data confidentiality through
    LUKS2 online reencryption extension crash recovery
    CVE-2021-4122, boo#1194469
  * Add configure option --disable-luks2-reencryption to completely
    disable LUKS2 reencryption code.
  * Improve internal metadata validation code for reencryption
    metadata
  * Add updated documentation for LUKS2 On-Disk Format
    Specification version 1.1.0
  * Fix support for bitlk (BitLocker compatible) startup key with
    new  metadata entry introduced in Windows 11
  * Fix space restriction for LUKS2 reencryption with data shift</changelog>
  <changelog author="lnussel@suse.de" date="1661169600">- cryptsetup 2.5.0:
  * Split manual pages into per-action pages and use AsciiDoc format.
  * Remove cryptsetup-reencrypt tool from the project and move reencryption
    to already existing "cryptsetup reencrypt" command.
    If you need to emulate the old cryptsetup-reencrypt binary, use simple
    wrappers script running "exec cryptsetup reencrypt $@".
  * LUKS2: implement --decryption option that allows LUKS removal.
  * Fix decryption operation with --active-name option and restrict
    it to be used only with LUKS2.
  * Do not refresh reencryption digest when not needed.
    This should speed up the reencryption resume process.
  * Store proper resilience data in LUKS2 reencrypt initialization.
    Resuming reencryption now does not require specification of resilience
    type parameters if these are the same as during initialization.
  * Properly wipe the unused area after reencryption with datashift in
    the forward direction.
  * Check datashift value against larger sector size.
    For example, it could cause an issue if misaligned 4K sector appears
    during decryption.
  * Do not allow sector size increase reencryption in offline mode.
  * Do not allow dangerous sector size change during reencryption.
  * Ask the user for confirmation before resuming reencryption.
  * Do not resume reencryption with conflicting parameters.
  * Add --force-offline-reencrypt option.
  * Do not allow nested encryption in LUKS reencrypt.
  * Support all options allowed with luksFormat with encrypt action.
  * Add resize action to integritysetup.
  * Remove obsolete dracut plugin reencryption example.
  * Fix possible keyslot area size overflow during conversion to LUKS2.
  * Allow use of --header option for cryptsetup close.
  * Fix activation of LUKS2 device with integrity and detached header.
  * Add ZEROOUT IOCTL support for crypt_wipe API call.
  * VERITY: set loopback sector size according to dm-verity block sizes.
  * veritysetup: dump device sizes.
  * LUKS2 token: prefer token PIN query before passphrase in some cases.
    When a user provides --token-type or specific --token-id, a token PIN
    query is preferred to a passphrase query.
  * LUKS2 token: allow tokens to be replaced with --token-replace option
    for cryptsetup token command.
  * LUKS2 token: do not continue operation when interrupted in PIN prompt.
  * Add --progress-json parameter to utilities.
  * Add support for --key-slot option in luksResume action.
- move man pages to separate subpackage
- drop backports handling</changelog>
  <changelog author="luca.boccassi@gmail.com" date="1663070400">- Add virtual provides for 'integritysetup' and 'veritysetup' to match
  package names provided by Fedora/RHEL, to allow the same set of
  dependencies to be used across all RPM distributions.</changelog>
  <changelog author="info@paolostivanin.com" date="1669636800">- cryptsetup 2.6.0:
  * Introduce support for handling macOS FileVault2 devices (FVAULT2).
  * libcryptsetup: no longer use global memory locking through mlockall()
  * libcryptsetup: process priority is increased only for key derivation
    (PBKDF) calls.
  * Add new LUKS keyslot context handling functions and API.
  * The volume key may now be extracted using a passphrase, keyfile, or
    token. For LUKS devices, it also returns the volume key after
    a successful crypt_format call.
  * Fix --disable-luks2-reencryption configuration option.
  * cryptsetup: Print a better error message and warning if the format
    produces an image without space available for data.
  * Print error if anti-forensic LUKS2 hash setting is not available.
    If the specified hash was not available, activation quietly failed.
  * Fix internal crypt segment compare routine if the user
    specified cipher in kernel format (capi: prefix).
  * cryptsetup: Add token unassign action.
    This action allows removing token binding on specific keyslot.
  * veritysetup: add support for --use-tasklets option.
    This option sets try_verify_in_tasklet kernel dm-verity option
    (available since Linux kernel 6.0) to allow some performance
    improvement on specific systems.
  * Provide pkgconfig Require.private settings.
    While we do not completely provide static build on udev systems,
    it helps produce statically linked binaries in certain situations.
  * Always update automake library files if autogen.sh is run.
    For several releases, we distributed older automake scripts by mistake.
  * reencryption: Fix user defined moved segment size in LUKS2 decryption.
    The --hotzone-size argument was ignored in cases where the actual data
    size was less than the original LUKS2 data offset.
  * Delegate FIPS mode detection to configured crypto backend.
    System FIPS mode check no longer depends on /etc/system-fips file.
  * Update documentation, including FAQ and man pages.</changelog>
  <changelog author="lnussel@suse.com" date="1672142400">- Replace transitional %usrmerged macro with regular version check (boo#1206798)</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1676203200">- cryptsetup 2.6.1
  * bitlk: Fixes for BitLocker-compatible on-disk metadata parser
  * Fix possible iteration overflow in OpenSSL2 PBKDF2 crypto
    backend
  * portability and compilation fixes
  * verity: Fix possible hash offset setting overflow.
  * bitlk: Fix use of startup BEK key on big-endian platforms.
  * Do not initiate encryption (reencryption command) when the
    header and data devices are the same. If data device reduction
    is not requsted, this leads to data corruption since LUKS
    metadata was written over the data device.
  * Fix possible memory leak if crypt_load() fails.
  * Always use passphrases with a minimal 8 chars length for
    benchmarking, as used in some implementation of FIPS mode</changelog>
  <changelog author="pmonreal@suse.com" date="1686744000">- FIPS: Remove not needed libcryptsetup12-hmac package that contains
  the HMAC checksums for integrity checking for FIPS. [bsc#1185116]
  * Remove the cryptsetup-rpmlintrc file.
  * Remove not needed fipscheck dependency.</changelog>
  <changelog author="pmonreal@suse.com" date="1686744001">- Enable running the regression test suite.
- Force a regeneration of the man pages from AsciiDoc.
- Add LUKS1 and LUKS2 On-Disk Format Specification pdfs to doc.</changelog>
  <changelog author="pmonreal@suse.com" date="1689249600">- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1706529600">- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1710331200">- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1712664000">- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.</changelog>
  <changelog author="pvorel@suse.cz" date="1720785600">- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).</changelog>
  <changelog author="pmonreal@suse.com" date="1722340800">- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.</changelog>
  <changelog author="martin.schreiner@suse.com" date="1722427200">- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.</changelog>
  <changelog author="meissner@suse.com" date="1725019200">- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)</changelog>
  <changelog author="pmonreal@suse.com" date="1726228800">- Update to 2.7.5:
  * Fix possible online reencryption data corruption (only in 2.7.x).
    In some situations (initializing a suspended device-mapper device),
    cryptsetup disabled direct-io device access. This caused unsafe
    online reencryption operations that could lead to data corruption.
    The code now adds strict checks (and aborts the operation) and
    changes direct-io detection code to prevent data corruption.
  * Fix a clang compilation error in SSH token plugin.
    As clang linker treats missing symbols as errors, the linker phase
    for the SSH token failed as the optional cryptsetup_token_buffer_free
    was not defined.
  * Fix crypto backend initialization in crypt_format_luks2_opal API call.</changelog>
  <changelog author="pmonreal@suse.com" date="1741953600">- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.</changelog>
</package>
<package pkgid="41d012925df18b71ef3ea058726ece5d8ca3e7f5c7bc13945422f97d2c3637d5" name="libcryptsetup12-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.7.5" rel="220.1"/>
  <changelog author="lnussel@suse.de" date="1631793600">- cryptsetup 2.4.1
  * Fix compilation for libc implementations without dlvsym().
  * Fix compilation and tests on systems with non-standard libraries
  * Try to workaround some issues on systems without udev support.
  * Fixes for OpenSSL3 crypto backend (including FIPS mode).
  * Print error message when assigning a token to an inactive keyslot.
  * Fix offset bug in LUKS2 encryption code if --offset option was used.
  * Do not allow LUKS2 decryption for devices with data offset.
  * Fix LUKS1 cryptsetup repair command for some specific problems.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1637236800">- cryptsetup 2.4.2:
  * Fix possible large memory allocation if LUKS2 header size is
    invalid.
  * Fix memory corruption in debug message printing LUKS2
    checksum.
  * veritysetup: remove link to the UUID library for the static
    build.
  * Remove link to pwquality library for integritysetup and
    veritysetup. These tools do not read passphrases.
  * OpenSSL3 backend: avoid remaining deprecated calls in API.
    Crypto backend no longer use API deprecated in OpenSSL 3.0
  * Check if kernel device-mapper create device failed in an early
    phase. This happens when a concurrent creation of device-mapper
    devices meets in the very early state.
  * Do not set compiler optimization flag for Argon2 KDF if the
    memory wipe is implemented in libc.
  * Do not attempt to unload LUKS2 tokens if external tokens are
    disabled. This allows building a static binary with
  - -disable-external-tokens.
  * LUKS convert: also check sysfs for device activity.
    If udev symlink is missing, code fallbacks to sysfs scan to
    prevent data corruption for the active device.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1642161600">- cryptsetup 2.4.3:
  * Fix possible attacks against data confidentiality through
    LUKS2 online reencryption extension crash recovery
    CVE-2021-4122, boo#1194469
  * Add configure option --disable-luks2-reencryption to completely
    disable LUKS2 reencryption code.
  * Improve internal metadata validation code for reencryption
    metadata
  * Add updated documentation for LUKS2 On-Disk Format
    Specification version 1.1.0
  * Fix support for bitlk (BitLocker compatible) startup key with
    new  metadata entry introduced in Windows 11
  * Fix space restriction for LUKS2 reencryption with data shift</changelog>
  <changelog author="lnussel@suse.de" date="1661169600">- cryptsetup 2.5.0:
  * Split manual pages into per-action pages and use AsciiDoc format.
  * Remove cryptsetup-reencrypt tool from the project and move reencryption
    to already existing "cryptsetup reencrypt" command.
    If you need to emulate the old cryptsetup-reencrypt binary, use simple
    wrappers script running "exec cryptsetup reencrypt $@".
  * LUKS2: implement --decryption option that allows LUKS removal.
  * Fix decryption operation with --active-name option and restrict
    it to be used only with LUKS2.
  * Do not refresh reencryption digest when not needed.
    This should speed up the reencryption resume process.
  * Store proper resilience data in LUKS2 reencrypt initialization.
    Resuming reencryption now does not require specification of resilience
    type parameters if these are the same as during initialization.
  * Properly wipe the unused area after reencryption with datashift in
    the forward direction.
  * Check datashift value against larger sector size.
    For example, it could cause an issue if misaligned 4K sector appears
    during decryption.
  * Do not allow sector size increase reencryption in offline mode.
  * Do not allow dangerous sector size change during reencryption.
  * Ask the user for confirmation before resuming reencryption.
  * Do not resume reencryption with conflicting parameters.
  * Add --force-offline-reencrypt option.
  * Do not allow nested encryption in LUKS reencrypt.
  * Support all options allowed with luksFormat with encrypt action.
  * Add resize action to integritysetup.
  * Remove obsolete dracut plugin reencryption example.
  * Fix possible keyslot area size overflow during conversion to LUKS2.
  * Allow use of --header option for cryptsetup close.
  * Fix activation of LUKS2 device with integrity and detached header.
  * Add ZEROOUT IOCTL support for crypt_wipe API call.
  * VERITY: set loopback sector size according to dm-verity block sizes.
  * veritysetup: dump device sizes.
  * LUKS2 token: prefer token PIN query before passphrase in some cases.
    When a user provides --token-type or specific --token-id, a token PIN
    query is preferred to a passphrase query.
  * LUKS2 token: allow tokens to be replaced with --token-replace option
    for cryptsetup token command.
  * LUKS2 token: do not continue operation when interrupted in PIN prompt.
  * Add --progress-json parameter to utilities.
  * Add support for --key-slot option in luksResume action.
- move man pages to separate subpackage
- drop backports handling</changelog>
  <changelog author="luca.boccassi@gmail.com" date="1663070400">- Add virtual provides for 'integritysetup' and 'veritysetup' to match
  package names provided by Fedora/RHEL, to allow the same set of
  dependencies to be used across all RPM distributions.</changelog>
  <changelog author="info@paolostivanin.com" date="1669636800">- cryptsetup 2.6.0:
  * Introduce support for handling macOS FileVault2 devices (FVAULT2).
  * libcryptsetup: no longer use global memory locking through mlockall()
  * libcryptsetup: process priority is increased only for key derivation
    (PBKDF) calls.
  * Add new LUKS keyslot context handling functions and API.
  * The volume key may now be extracted using a passphrase, keyfile, or
    token. For LUKS devices, it also returns the volume key after
    a successful crypt_format call.
  * Fix --disable-luks2-reencryption configuration option.
  * cryptsetup: Print a better error message and warning if the format
    produces an image without space available for data.
  * Print error if anti-forensic LUKS2 hash setting is not available.
    If the specified hash was not available, activation quietly failed.
  * Fix internal crypt segment compare routine if the user
    specified cipher in kernel format (capi: prefix).
  * cryptsetup: Add token unassign action.
    This action allows removing token binding on specific keyslot.
  * veritysetup: add support for --use-tasklets option.
    This option sets try_verify_in_tasklet kernel dm-verity option
    (available since Linux kernel 6.0) to allow some performance
    improvement on specific systems.
  * Provide pkgconfig Require.private settings.
    While we do not completely provide static build on udev systems,
    it helps produce statically linked binaries in certain situations.
  * Always update automake library files if autogen.sh is run.
    For several releases, we distributed older automake scripts by mistake.
  * reencryption: Fix user defined moved segment size in LUKS2 decryption.
    The --hotzone-size argument was ignored in cases where the actual data
    size was less than the original LUKS2 data offset.
  * Delegate FIPS mode detection to configured crypto backend.
    System FIPS mode check no longer depends on /etc/system-fips file.
  * Update documentation, including FAQ and man pages.</changelog>
  <changelog author="lnussel@suse.com" date="1672142400">- Replace transitional %usrmerged macro with regular version check (boo#1206798)</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1676203200">- cryptsetup 2.6.1
  * bitlk: Fixes for BitLocker-compatible on-disk metadata parser
  * Fix possible iteration overflow in OpenSSL2 PBKDF2 crypto
    backend
  * portability and compilation fixes
  * verity: Fix possible hash offset setting overflow.
  * bitlk: Fix use of startup BEK key on big-endian platforms.
  * Do not initiate encryption (reencryption command) when the
    header and data devices are the same. If data device reduction
    is not requsted, this leads to data corruption since LUKS
    metadata was written over the data device.
  * Fix possible memory leak if crypt_load() fails.
  * Always use passphrases with a minimal 8 chars length for
    benchmarking, as used in some implementation of FIPS mode</changelog>
  <changelog author="pmonreal@suse.com" date="1686744000">- FIPS: Remove not needed libcryptsetup12-hmac package that contains
  the HMAC checksums for integrity checking for FIPS. [bsc#1185116]
  * Remove the cryptsetup-rpmlintrc file.
  * Remove not needed fipscheck dependency.</changelog>
  <changelog author="pmonreal@suse.com" date="1686744001">- Enable running the regression test suite.
- Force a regeneration of the man pages from AsciiDoc.
- Add LUKS1 and LUKS2 On-Disk Format Specification pdfs to doc.</changelog>
  <changelog author="pmonreal@suse.com" date="1689249600">- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1706529600">- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch</changelog>
  <changelog author="pmonreal@suse.com" date="1710331200">- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1712664000">- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.</changelog>
  <changelog author="pvorel@suse.cz" date="1720785600">- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).</changelog>
  <changelog author="pmonreal@suse.com" date="1722340800">- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.</changelog>
  <changelog author="martin.schreiner@suse.com" date="1722427200">- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.</changelog>
  <changelog author="meissner@suse.com" date="1725019200">- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)</changelog>
  <changelog author="pmonreal@suse.com" date="1726228800">- Update to 2.7.5:
  * Fix possible online reencryption data corruption (only in 2.7.x).
    In some situations (initializing a suspended device-mapper device),
    cryptsetup disabled direct-io device access. This caused unsafe
    online reencryption operations that could lead to data corruption.
    The code now adds strict checks (and aborts the operation) and
    changes direct-io detection code to prevent data corruption.
  * Fix a clang compilation error in SSH token plugin.
    As clang linker treats missing symbols as errors, the linker phase
    for the SSH token failed as the optional cryptsetup_token_buffer_free
    was not defined.
  * Fix crypto backend initialization in crypt_format_luks2_opal API call.</changelog>
  <changelog author="pmonreal@suse.com" date="1741953600">- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.</changelog>
</package>
<package pkgid="70911786db3beb85606f8d91425313c463a48344c9490ccdb9a65cd5deb4ec54" name="libfipscheck1" arch="x86_64">
  <version epoch="0" ver="1.7.0" rel="46.1"/>
  <changelog author="meissner@suse.com" date="1401710400">- add baselibs.conf</changelog>
  <changelog author="jengelh@inai.de" date="1428926400">- Set RPM groups anew. Drop implicit cleaning parts.</changelog>
  <changelog author="daniel.molkentin@suse.com" date="1497268800">- Port to OpenSSL 1.1 (bsc#1042649)
  Adds openssl-1_1-port.patch</changelog>
  <changelog author="jsikes@suse.de" date="1536667200">- Updated fipscheck to 1.5.0
  * Changed source to local file since latest official release
    is not in the official releases directory.
  * Downgraded libopenssl-devel to libopenssl-1_0_0-devel because
    1.0.2 supports FIPS.</changelog>
  <changelog author="jsikes@suse.de" date="1537444800">- Changed source back to http now that current release folder
  has current tarball.</changelog>
  <changelog author="vcizek@suse.com" date="1546516800">- Use the shipped manpages instead of building them with xmlto
  in order to avoid a build cycle (fipscheck, xmlto, libxslt, libgcrypt)
  * add fipscheck-dont_generate_manpages.patch
- fix build on older distributions</changelog>
  <changelog author="vcizek@suse.com" date="1568635200">- Remove #include of unused fips.h to fix build with OpenSSL 1.1.1
  (bsc#1149792)
  * add fipscheck-fips.h_not_needed.patch
- Drop obsolete openssl-1_1-port.patch (upstream)</changelog>
  <changelog author="lnussel@suse.de" date="1605873600">- move libs to %_libdir (boo#1029961)</changelog>
  <changelog author="meissner@suse.com" date="1667390400">- updated to 1.7.0 (from a different supplier)
  - openssl 3 support
- dropped fipscheck-dont_generate_manpages.patch (not needed)
- dropped fipscheck-fips.h_not_needed.patch (not needed)</changelog>
  <changelog author="mjambor@suse.com" date="1720440000">- Backport upstream patches fipscheck-fix_check_openssl_version.patch
  and fipscheck-fix_incorrect_length_type.patch to fix C99 violations
  which are errors by default with GCC 14 [boo#1221714] - although the
  first one looks like it possibly fixes some more substantial error.</changelog>
</package>
<package pkgid="e5d13740237bb2ec2136e7e72c4682196c814009691b7b51bd637c62ef0f7a47" name="libfipscheck1-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.7.0" rel="46.1"/>
  <changelog author="meissner@suse.com" date="1401710400">- add baselibs.conf</changelog>
  <changelog author="jengelh@inai.de" date="1428926400">- Set RPM groups anew. Drop implicit cleaning parts.</changelog>
  <changelog author="daniel.molkentin@suse.com" date="1497268800">- Port to OpenSSL 1.1 (bsc#1042649)
  Adds openssl-1_1-port.patch</changelog>
  <changelog author="jsikes@suse.de" date="1536667200">- Updated fipscheck to 1.5.0
  * Changed source to local file since latest official release
    is not in the official releases directory.
  * Downgraded libopenssl-devel to libopenssl-1_0_0-devel because
    1.0.2 supports FIPS.</changelog>
  <changelog author="jsikes@suse.de" date="1537444800">- Changed source back to http now that current release folder
  has current tarball.</changelog>
  <changelog author="vcizek@suse.com" date="1546516800">- Use the shipped manpages instead of building them with xmlto
  in order to avoid a build cycle (fipscheck, xmlto, libxslt, libgcrypt)
  * add fipscheck-dont_generate_manpages.patch
- fix build on older distributions</changelog>
  <changelog author="vcizek@suse.com" date="1568635200">- Remove #include of unused fips.h to fix build with OpenSSL 1.1.1
  (bsc#1149792)
  * add fipscheck-fips.h_not_needed.patch
- Drop obsolete openssl-1_1-port.patch (upstream)</changelog>
  <changelog author="lnussel@suse.de" date="1605873600">- move libs to %_libdir (boo#1029961)</changelog>
  <changelog author="meissner@suse.com" date="1667390400">- updated to 1.7.0 (from a different supplier)
  - openssl 3 support
- dropped fipscheck-dont_generate_manpages.patch (not needed)
- dropped fipscheck-fips.h_not_needed.patch (not needed)</changelog>
  <changelog author="mjambor@suse.com" date="1720440000">- Backport upstream patches fipscheck-fix_check_openssl_version.patch
  and fipscheck-fix_incorrect_length_type.patch to fix C99 violations
  which are errors by default with GCC 14 [boo#1221714] - although the
  first one looks like it possibly fixes some more substantial error.</changelog>
</package>
<package pkgid="4ee3e23d097658880205cc2a40c418dae04765d5adefcd83de39b82aa9bfefe9" name="libfreshclam2" arch="x86_64">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="4cba7a2d69b0d4b46f3a150e233fc4c460f31b062c66d39153ee62251d5196d8" name="libfreshclam2-debuginfo" arch="x86_64">
  <version epoch="0" ver="0.103.11" rel="268.1"/>
  <changelog author="suse+build@de-korte.org" date="1600084800">- Update to 0.103.0
  * clamd can now reload the signature database without blocking
    scanning. This multi-threaded database reload improvement was made
    possible thanks to a community effort.
  - Non-blocking database reloads are now the default behavior. Some
    systems that are more constrained on RAM may need to disable
    non-blocking reloads as it will temporarily consume two times as
    much memory. We added a new clamd config option
    ConcurrentDatabaseReload, which may be set to no.
  * Dropped clamav-str-h.patch (no longer needed)
  * Fix clamav-milter.service (requires clamd.service to run)</changelog>
  <changelog author="max@suse.com" date="1605009600">- Sync Factory to SLE-15 to implement jsc#ECO-3010 and bsc#1118459.
- bsc#1119353, clamav-fips.patch: Fix freshclam crash in FIPS mode.
- Keep OBS from installing an existing clamav instance to scan the
  sources, because this makes "make check" use the old library
  instead of the just built one. This is only a workaround until
  we found a way to keep libtool from adding libdir to rpath and
  LD_LIBRARY_PATH of the binaries in the testsuite.</changelog>
  <changelog author="dimstar@opensuse.org" date="1605182400">- Do not hard-depend on systemd: use systemd_ordering instead of
  systemd_requires.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612612800">- Update to 0.103.1
  * Added a new scan option to alert on broken media (graphics) file
    formats. This feature mitigates the risk of malformed media files
    intended to exploit vulnerabilities in other software. At present
    media validation exists for JPEG, TIFF, PNG, and GIF files. To
    enable this feature, set AlertBrokenMedia yes in clamd.conf, or
    use the --alert-broken-media option when using clamscan. These
    options are disabled by default in this patch release, but may be
    enabled in a subsequent release. Application developers may enable
    this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for
    the heuristic scan option bit field.
  * Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing
    behavior. BMP and JPEG 2000 files will continue to detect as
    CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG
    2000 format checking capabilities.
  * Fixed PNG parser logic bugs that caused an excess of parsing
    errors and fixed a stack exhaustion issue affecting some systems
    when scanning PNG files. PNG file type detection was disabled via
    signature database update for ClamAV version 0.103.0 to mitigate
    the effects from these bugs.
  * Fixed an issue where PNG and GIF files no longer work with
    Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather
    than as CL_TYPE_GRAPHICS. Target types now support up to 10
    possible file types to make way for additional graphics types in
    future releases.
  * Fixed clamonacc's --fdpass option.
  - Interprocess file descriptor passing for clamonacc was broken
    since version 0.102.0 due to a bug introduced by the switch to
    curl for communicating with clamd. On Linux, passing file
    descriptors from one process to another is handled by the
    kernel, so we reverted clamonacc to use standard system calls
    for socket communication when fd passing is enabled.
  * Fixed a clamonacc stack corruption issue on some systems when
    using an older version of libcurl.
  * Allow clamscan and clamdscan scans to proceed even if the
    realpath lookup failed. This alleviates an issue on Windows
    scanning files hosted on file- systems that do not support the
    GetMappedFileNameW() API such as on ImDisk RAM-disks.
  * Fixed freshclam --on-update-execute=EXIT_1 temporary directory
    cleanup issue.
  * clamd's log output and VirusEvent now provide the scan target's
    file path instead of a file descriptor. The clamd socket API for
    submitting a scan by FD-passing doesn't include a file path, this
    feature works by looking up the file path by file descriptor.
    This feature works on Mac and Linux but is not yet implemented
    for other UNIX operating systems. FD-passing is not available for
    Windows.
  * Fixed an issue where freshclam database validation didn't work
    correctly when run in daemon mode on Linux/Unix.</changelog>
  <changelog author="suse+build@de-korte.org" date="1612872000">- Don't daemonize freshclam, but use a systemd timer instead to
  trigger updates
  + timer.freshclam
  % service.freshclam
  % clamav-conf.patch
- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH)
  - clamav-disable-timestamps.patch
- Fix unit test
  + clamav-ck_assert_msg.patch
- Cleanup spec
  * use pkgconfig() to resolve BuildRequires where upstream uses it
  * rework creating vscan user (new system-user in Tumbleweed)
  * remove obsolete configure option --disable-zlib-vcheck</changelog>
  <changelog author="suse+build@de-korte.org" date="1614254400">- Package clamav-milter in a subpackage
- Remove virus signatures upon uninstall
- Check for database existence before starting clamd
- Restart clamd when it exits</changelog>
  <changelog author="suse+build@de-korte.org" date="1617796800">- Update to 0.103.2
  * CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite
    loop. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read;
    possible crash. Affects 0.103.0 and 0.103.1 only.
  * CVE-2021-1405, bsc#1184534: Fix for mail parser
    NULL-dereference crash. Affects 0.103.1 and prior.
  * Fix possible memory leak in PNG parser.
  * Fix ClamOnAcc scan on file-creation race condition so files are
    scanned after their contents are written.
  * FreshClam: Deprecate the SafeBrowsing config option. The
    SafeBrowsing option will no longer do anything.
  * For more details, see our blog post from last year about the
    future of the ClamAV Safe Browsing database.
  * FreshClam: Improved HTTP 304, 403, &amp; 429 handling.
  * FreshClam: Added back the mirrors.dat file to the database directory.
  * FreshClam will now exit with a failure in daemon mode if an HTTP 403
    (Forbidden) was received, because retrying later won't help any. The
    FreshClam user will have to take actions to get unblocked.
  * Fix the FreshClam mirror-sync issue where a downloaded database is
    "older than the version advertised."
  * bsc#1181256: Fix errors when scanning files &gt; 4G
- Update package signing key (from https://www.clamav.net/downloads)
  % clamav.keyring</changelog>
  <changelog author="max@suse.com" date="1617969600">- Use a split-provides for clamav-milter instead of recommending it.</changelog>
  <changelog author="suse+build@de-korte.org" date="1624276800">- bsc#1188284: Update to 0.103.3
  * Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is
    enabled. This issue did not impacted most users but for those
    affected it caused every scanned file to be copied to the temp
    directory before the scan.
  * Fix ClamDScan crashes when using the --fdpass --multiscan
    command-line options in combination with the ClamD ExcludePath
    config file options.
  * Fixed an issue where the mirrors.dat file is owned by root when
    starting as root (or with sudo) and using daemon-mode. File
    ownership will be set to the DatabaseOwner just before FreshClam
    switches to run as that user.
  * Renamed the mirrors.dat file to freshclam.dat.
  * Disabled the HTTPUserAgent config option if the DatabaseMirror uses
    clamav.net. This will prevent users from being inadvertently blocked
    and will ensure that we can keep better metrics on which ClamAV
    versions are being used.
  * Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the
    ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes)
    option. This type of PNG issue appears to be common enough to be an
    annoyance, and the CVE is old enough that no one should be
    vulnerable at this point.
  * Fix ClamSubmit failures after changes to Cloudflare "__cfduid"
    cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/</changelog>
  <changelog author="meissner@suse.com" date="1625054400">- clamav-document-maxsize.patch: in the "clamscan" and "clamdscan" manpages,
  document that files over a certain size by default will silently not be
  scanned and how this can be adjusted (bsc#1187509)</changelog>
  <changelog author="suse+build@de-korte.org" date="1635940800">- bsc#1192346: Update to 0.103.4
  * FreshClam:
  - Add a 24-hour cool-down for FreshClam clients that have received
    an HTTP 403 (Forbidden) response from the CDN. This is to reduce
    the volume of 403-response data served to blocked FreshClam
    clients that are configured with a tight update-loop.
  - Fixed a bug where FreshClam treats an empty CDIFF as an
    incremental update failure instead of as an intentional request
    to download the whole CVD.
  * ClamDScan: Fix a scan error when broken symlinks are encountered on
    macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks"
    options disabled.
  * Overhauled the scan recursion / nested archive extraction logic and
    added new limits on embedded file-type recognition performed during
    the "raw" scan of each file. This limits embedded file-type
    misidentification and prevents detecting embedded file content that
    is found/extracted and scanned at other layers in the scanning
    process.
  * Fix an issue with the FMap module that failed to read from some
    nested files.
  * Fixed an issue where failing to load some rules from a Yara file
    containing multiple rules may cause a crash.
  * Fixed assorted compiler warnings.
  * Fixed assorted Coverity static code analysis issues.
  * Scan limits:
  - Added virus-name suffixes to the alerts that trigger when a scan
    limit has been exceeded. Rather than simply
    Heuristics.Limits.Exceeded, you may now see limit-specific
    virus-names, to include:
    + Heuristics.Limits.Exceeded.MaxFileSize
    + Heuristics.Limits.Exceeded.MaxScanSize
    + Heuristics.Limits.Exceeded.MaxFiles
    + Heuristics.Limits.Exceeded.MaxRecursion
    + Heuristics.Limits.Exceeded.MaxScanTime
  - Renamed the Heuristics.Email.ExceedsMax.* alerts to align with
    the other limit alerts names. These alerts include:
    + Heuristics.Limits.Exceeded.EmailLineFoldcnt
    + Heuristics.Limits.Exceeded.EmailHeaderBytes
    + Heuristics.Limits.Exceeded.EmailHeaders
    + Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
    + Heuristics.Limits.Exceeded.EmailMIMEArguments
  - Fixed an issue where the Email-related scan limits would alert
    even when the "AlertExceedsMax" (--alert-exceeds-max) scan option
    is not enabled.
  - Fixes an issue in the Zip parser where exceeding the "MaxFiles"
    limit or the "MaxFileSize" limit would abort the scan but would
    fail to alert. The Zip scan limit issues were independently
    identified and reported by Aaron Leliaert and Max Allan.
  * Fixed a leak in the Email parser when using the --gen-json scan
    option.
  * Fixed an issue where a failure to record metadata in the Email
    parser when using the --gen-json scan option could cause the Email
    parser to abort the scan early and fail to extract and scan
    additional content.
  * Fixed a file name memory leak in the Zip parser.
  * Fixed an issue where certain signature patterns may cause a crash or
    cause unintended matches on some systems when converting characters
    to uppercase if a UTF-8 unicode single-byte grapheme becomes a
    multi-byte grapheme. Patch courtesy of Andrea De Pasquale.</changelog>
  <changelog author="suse+build@de-korte.org" date="1641988800">- Update to 0.103.5
  * CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
    This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled
    with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option
    (the clamscan --gen-json option) is enabled.
  * Fixed ability to disable the file size limit with libclamav C API,
    like this:
    cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0);
    This issue didn't affect ClamD or ClamScan which also can disable the
    limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD,
    or clamscan --max-filesize=0 for ClamScan.
    Note: Internally, the max file size is still set to 2 GiB. Disabling the
    limit for a scan will fall back on the internal 2 GiB limitation.
  * Increased the maximum line length for ClamAV config files from 512 bytes
    to 1,024 bytes to allow for longer config option strings.
  * SigTool: Fix insufficient buffer size for --list-sigs that caused a
    failure when listing a database containing one or more very long
    signatures. This fix was backported from 0.104.</changelog>
  <changelog author="meissner@suse.com" date="1649764800">- https source urls</changelog>
  <changelog author="suse+build@de-korte.org" date="1651752000">- Update to 0.103.6
  * CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM
    file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS
    version 0.103.5 and prior versions. (boo#1199242)
  * CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the
    scan verdict cache check. Issue affects versions 0.103.4, 0.103.5,
    0.104.1, and 0.104.2. (boo#1199246)
  * CVE-2022-20771: Fixed a possible infinite loop vulnerability in the
    TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and
    LTS version 0.103.5 and prior versions. The issue only occurs if the
    "--alert-broken-media" ClamScan option is enabled. For ClamD, the
    affected option is "AlertBrokenMedia yes", and for libclamav it is the
    "CL_SCAN_HEURISTIC_BROKEN_MEDIA" scan option. (boo#1199244)
  * CVE-2022-20785: Fixed a possible memory leak in the HTML file parser /
    Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2
    and LTS version 0.103.5 and prior versions. (boo#1199245)
  * CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write
    vulnerability in the signature database load module. The fix was to
    update the vendored regex library to the latest version. Issue affects
    versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior
    versions. (boo#1199274)
  * ClamOnAcc: Fixed a number of assorted stability issues and added
    niceties for debugging ClamOnAcc.
  * Fixed an issue causing byte-compare subsignatures to cause an alert
    when they match even if other conditions of the given logical
    signatures were not met.
  * Fix memleak when using multiple byte-compare subsignatures. This fix
    was backported from 0.104.0.
  * Assorted bug fixes and improvements.
- Remove upstreamed clamav-ck_assert_msg.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1659700800">- Update to 0.103.7
  - Zip parser: tolerate 2-byte overlap in file entries
  - Fix bug with logical signature Intermediates feature
  - Update to UnRAR v6.1.7
  - Patch UnRAR: allow skipping files in solid archives
  - Patch UnRAR: limit dict winsize to 1GB</changelog>
  <changelog author="suse+build@de-korte.org" date="1676462400">- Update to 0.103.8
  * CVE-2023-20032: Fixed a possible remote code execution vulnerability
    in the HFS+ file parser. Issue affects versions 1.0.0 and earlier,
    0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
  * CVE-2023-20052: Fixed a possible remote information leak
    vulnerability in the DMG file parser. Issue affects versions 1.0.0
    and earlier, 0.105.1 and earlier, and 0.103.7 and earlier.
    (bsc#1208365)
  * Update vendored libmspack library to version 0.11alpha.
- Package huge .html documentation in a separate subpackage.</changelog>
  <changelog author="suse+build@de-korte.org" date="1692187200">- Update to 0.103.9
  * CVE-2023-20197: Fixed a possible denial of service vulnerability in
    the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through
    1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8
    through 0.103.0. (boo#1214342)
  * Fixed compiler warnings that may turn into errors in Clang 16.</changelog>
  <changelog author="max@suse.com" date="1692360000">- Renew clamav.keyring .</changelog>
  <changelog author="suse+build@de-korte.org" date="1698235200">- Update to 0.103.11
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
  * Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
  * Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
- Update to 0.103.10
  * Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10.
    (bsc#1216625, CVE-2023-40477)</changelog>
  <changelog author="dimstar@opensuse.org" date="1708948800">- Use %patch -P N instead of deprecated %patchN.</changelog>
</package>
<package pkgid="9d37bf7cc0641fec2f0a154d3c03f383cc2ef607c66fd510513ce0b089262aa2" name="scap-security-guide" arch="noarch">
  <version epoch="0" ver="0.1.77" rel="161.1"/>
  <changelog author="meissner@suse.com" date="1702987200">- updated to 0.1.71 (jsc#ECO-3319)
  - Add RHEL 9 STIG
  - Add support for Debian 12
  - Update PCI-DSS profile for RHEL
  - lots of bugfixes and improvements for SLE
- removed left over file
  0001-Revert-fix-aide-remediations-add-crontabs.patch upstreamed in 0.1.69</changelog>
  <changelog author="meissner@suse.com" date="1707825600">- updated to 0.1.72 (jsc#ECO-3319)
  - ANSSI BP 028 profile for debian12 (#11368)
  - Building on Windows (#11406)
  - Control for BSI APP.4.4 (#11342)
  - update to CIS RHEL 7 and RHEL 8 profiles aligning them with the latest benchmarks
  - various fixes to SLE profiles
- add openeuler to -redhat package
- removed ssg-fix-journald.patch: fixed upstream</changelog>
  <changelog author="rumen.chikov@suse.com" date="1717156800">- updated to 0.1.73 (jsc#ECO-3319)
  - CMP 2417: Implement PCI-DSS v4.0 outline for OpenShift (#11651)
  - Update all RHEL ANSSI BP028 profiles to be aligned with configuration recommendations version 2.0
  - Generate rule references from control files (#11540)
  - Initial implementation of STIG V1R1 profile for Ubuntu 22.04 LTS (#11820)</changelog>
  <changelog author="rumen.chikov@suse.com" date="1725278400">- updated to 0.1.74 (jsc#ECO-3319)
  - Add Amazon Linux 2023 product (#12006)
  - Introduce new remediation type Kickstart (#12144)
  - Make PAM macros more flexible to variables (#12133)
  - Remove Debian 10 Product (#12205)
  - Remove Red Hat Enterprise Linux 7 product (#12093)
  - Update CIS RHEL9 control file to v2.0.0 (#12067)</changelog>
  <changelog author="rumen.chikov@suse.com" date="1733313600">- updated to 0.1.75 (jsc#ECO-3319)
  - Add new product kylinserver10
  - Create OL10 product
  - Update PCI-DSS control file for version 4.0.1
  - Add Ism profile for ol8, ol9
  - Release SLMicro5 product
  - Various updates for SLE 12/15</changelog>
  <changelog author="meissner@suse.com" date="1733400000">- ssg-reproducable.patch: replace two date injections by SOURCE_DATE_EPOCH
  to make reproducible. bsc#1230361</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741003200">- updated to 0.1.76 (jsc#ECO-3319)
  - Add new product for Ubuntu 24.04 and draft CIS profiles
  - Add pyproject.toml for the ssg package
  - AlmaLinux OS 9 as a new product
  - Documentation for ssg library
  - Extend SSG library to more easily collect profile selections
  - Extend SSG with functions to manage variables</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741089600">- removed ssg-reproducable.patch: upstream</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741089601">- added build support for almalinux9</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176000">- updates redhat package to include almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176001">- fix a bug in redhad package description for almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176002">- removed tables reference related to almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741694400">- creation of a new request</changelog>
  <changelog author="sfalken@opensuse.org" date="1742644800">- Add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to fix FTBFS with cmake4
- Remove Group: declarations, no longer used</changelog>
  <changelog author="meissner@suse.com" date="1742731200">- ssg-fix-python.patch: fix build with older python3.</changelog>
  <changelog author="rumen.chikov@suse.com" date="1749729600">- updated to 0.1.77 (jsc#ECO-3319)
  - Introduce Architecture Decisions Records
  - Move stablization to the third Monday of the second month
  - Remove CCI References
  - Remove macOS content
- removed ssg-fix-python.patch: upstream
- Added support for tencentos4</changelog>
  <changelog author="meissner@suse.com" date="1750766400">- buildrequire cmake3 on older SLES versions for build</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1753876800">- ssg-remove-cis.patch: remove cis profiles
- Update description: remove cis profiles</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1755777600">- Remove ssg-remove-cis.patch: tarball
- Add check if cis profiles exists in the tarball</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1755777601">- Remove the cis profiles from the tarball</changelog>
</package>
<package pkgid="90abb3c7ac9d19c1a6de7e24c0c099e905ace7d451548dac79ef34eb0f2aff13" name="scap-security-guide" arch="src">
  <version epoch="0" ver="0.1.77" rel="161.1"/>
  <changelog author="meissner@suse.com" date="1702987200">- updated to 0.1.71 (jsc#ECO-3319)
  - Add RHEL 9 STIG
  - Add support for Debian 12
  - Update PCI-DSS profile for RHEL
  - lots of bugfixes and improvements for SLE
- removed left over file
  0001-Revert-fix-aide-remediations-add-crontabs.patch upstreamed in 0.1.69</changelog>
  <changelog author="meissner@suse.com" date="1707825600">- updated to 0.1.72 (jsc#ECO-3319)
  - ANSSI BP 028 profile for debian12 (#11368)
  - Building on Windows (#11406)
  - Control for BSI APP.4.4 (#11342)
  - update to CIS RHEL 7 and RHEL 8 profiles aligning them with the latest benchmarks
  - various fixes to SLE profiles
- add openeuler to -redhat package
- removed ssg-fix-journald.patch: fixed upstream</changelog>
  <changelog author="rumen.chikov@suse.com" date="1717156800">- updated to 0.1.73 (jsc#ECO-3319)
  - CMP 2417: Implement PCI-DSS v4.0 outline for OpenShift (#11651)
  - Update all RHEL ANSSI BP028 profiles to be aligned with configuration recommendations version 2.0
  - Generate rule references from control files (#11540)
  - Initial implementation of STIG V1R1 profile for Ubuntu 22.04 LTS (#11820)</changelog>
  <changelog author="rumen.chikov@suse.com" date="1725278400">- updated to 0.1.74 (jsc#ECO-3319)
  - Add Amazon Linux 2023 product (#12006)
  - Introduce new remediation type Kickstart (#12144)
  - Make PAM macros more flexible to variables (#12133)
  - Remove Debian 10 Product (#12205)
  - Remove Red Hat Enterprise Linux 7 product (#12093)
  - Update CIS RHEL9 control file to v2.0.0 (#12067)</changelog>
  <changelog author="rumen.chikov@suse.com" date="1733313600">- updated to 0.1.75 (jsc#ECO-3319)
  - Add new product kylinserver10
  - Create OL10 product
  - Update PCI-DSS control file for version 4.0.1
  - Add Ism profile for ol8, ol9
  - Release SLMicro5 product
  - Various updates for SLE 12/15</changelog>
  <changelog author="meissner@suse.com" date="1733400000">- ssg-reproducable.patch: replace two date injections by SOURCE_DATE_EPOCH
  to make reproducible. bsc#1230361</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741003200">- updated to 0.1.76 (jsc#ECO-3319)
  - Add new product for Ubuntu 24.04 and draft CIS profiles
  - Add pyproject.toml for the ssg package
  - AlmaLinux OS 9 as a new product
  - Documentation for ssg library
  - Extend SSG library to more easily collect profile selections
  - Extend SSG with functions to manage variables</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741089600">- removed ssg-reproducable.patch: upstream</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741089601">- added build support for almalinux9</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176000">- updates redhat package to include almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176001">- fix a bug in redhad package description for almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176002">- removed tables reference related to almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741694400">- creation of a new request</changelog>
  <changelog author="sfalken@opensuse.org" date="1742644800">- Add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to fix FTBFS with cmake4
- Remove Group: declarations, no longer used</changelog>
  <changelog author="meissner@suse.com" date="1742731200">- ssg-fix-python.patch: fix build with older python3.</changelog>
  <changelog author="rumen.chikov@suse.com" date="1749729600">- updated to 0.1.77 (jsc#ECO-3319)
  - Introduce Architecture Decisions Records
  - Move stablization to the third Monday of the second month
  - Remove CCI References
  - Remove macOS content
- removed ssg-fix-python.patch: upstream
- Added support for tencentos4</changelog>
  <changelog author="meissner@suse.com" date="1750766400">- buildrequire cmake3 on older SLES versions for build</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1753876800">- ssg-remove-cis.patch: remove cis profiles
- Update description: remove cis profiles</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1755777600">- Remove ssg-remove-cis.patch: tarball
- Add check if cis profiles exists in the tarball</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1755777601">- Remove the cis profiles from the tarball</changelog>
</package>
<package pkgid="29c162bb41bbf026e907b4f1d6efc895b4e2bb52de0b314acf10ba958fa3f6d2" name="scap-security-guide-debian" arch="noarch">
  <version epoch="0" ver="0.1.77" rel="161.1"/>
  <changelog author="meissner@suse.com" date="1702987200">- updated to 0.1.71 (jsc#ECO-3319)
  - Add RHEL 9 STIG
  - Add support for Debian 12
  - Update PCI-DSS profile for RHEL
  - lots of bugfixes and improvements for SLE
- removed left over file
  0001-Revert-fix-aide-remediations-add-crontabs.patch upstreamed in 0.1.69</changelog>
  <changelog author="meissner@suse.com" date="1707825600">- updated to 0.1.72 (jsc#ECO-3319)
  - ANSSI BP 028 profile for debian12 (#11368)
  - Building on Windows (#11406)
  - Control for BSI APP.4.4 (#11342)
  - update to CIS RHEL 7 and RHEL 8 profiles aligning them with the latest benchmarks
  - various fixes to SLE profiles
- add openeuler to -redhat package
- removed ssg-fix-journald.patch: fixed upstream</changelog>
  <changelog author="rumen.chikov@suse.com" date="1717156800">- updated to 0.1.73 (jsc#ECO-3319)
  - CMP 2417: Implement PCI-DSS v4.0 outline for OpenShift (#11651)
  - Update all RHEL ANSSI BP028 profiles to be aligned with configuration recommendations version 2.0
  - Generate rule references from control files (#11540)
  - Initial implementation of STIG V1R1 profile for Ubuntu 22.04 LTS (#11820)</changelog>
  <changelog author="rumen.chikov@suse.com" date="1725278400">- updated to 0.1.74 (jsc#ECO-3319)
  - Add Amazon Linux 2023 product (#12006)
  - Introduce new remediation type Kickstart (#12144)
  - Make PAM macros more flexible to variables (#12133)
  - Remove Debian 10 Product (#12205)
  - Remove Red Hat Enterprise Linux 7 product (#12093)
  - Update CIS RHEL9 control file to v2.0.0 (#12067)</changelog>
  <changelog author="rumen.chikov@suse.com" date="1733313600">- updated to 0.1.75 (jsc#ECO-3319)
  - Add new product kylinserver10
  - Create OL10 product
  - Update PCI-DSS control file for version 4.0.1
  - Add Ism profile for ol8, ol9
  - Release SLMicro5 product
  - Various updates for SLE 12/15</changelog>
  <changelog author="meissner@suse.com" date="1733400000">- ssg-reproducable.patch: replace two date injections by SOURCE_DATE_EPOCH
  to make reproducible. bsc#1230361</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741003200">- updated to 0.1.76 (jsc#ECO-3319)
  - Add new product for Ubuntu 24.04 and draft CIS profiles
  - Add pyproject.toml for the ssg package
  - AlmaLinux OS 9 as a new product
  - Documentation for ssg library
  - Extend SSG library to more easily collect profile selections
  - Extend SSG with functions to manage variables</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741089600">- removed ssg-reproducable.patch: upstream</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741089601">- added build support for almalinux9</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176000">- updates redhat package to include almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176001">- fix a bug in redhad package description for almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176002">- removed tables reference related to almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741694400">- creation of a new request</changelog>
  <changelog author="sfalken@opensuse.org" date="1742644800">- Add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to fix FTBFS with cmake4
- Remove Group: declarations, no longer used</changelog>
  <changelog author="meissner@suse.com" date="1742731200">- ssg-fix-python.patch: fix build with older python3.</changelog>
  <changelog author="rumen.chikov@suse.com" date="1749729600">- updated to 0.1.77 (jsc#ECO-3319)
  - Introduce Architecture Decisions Records
  - Move stablization to the third Monday of the second month
  - Remove CCI References
  - Remove macOS content
- removed ssg-fix-python.patch: upstream
- Added support for tencentos4</changelog>
  <changelog author="meissner@suse.com" date="1750766400">- buildrequire cmake3 on older SLES versions for build</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1753876800">- ssg-remove-cis.patch: remove cis profiles
- Update description: remove cis profiles</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1755777600">- Remove ssg-remove-cis.patch: tarball
- Add check if cis profiles exists in the tarball</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1755777601">- Remove the cis profiles from the tarball</changelog>
</package>
<package pkgid="0911dba744694aef2cc42ee298cdb6937b8c67ec2ae8e35d985831fd50f4a5b9" name="scap-security-guide-redhat" arch="noarch">
  <version epoch="0" ver="0.1.77" rel="161.1"/>
  <changelog author="meissner@suse.com" date="1702987200">- updated to 0.1.71 (jsc#ECO-3319)
  - Add RHEL 9 STIG
  - Add support for Debian 12
  - Update PCI-DSS profile for RHEL
  - lots of bugfixes and improvements for SLE
- removed left over file
  0001-Revert-fix-aide-remediations-add-crontabs.patch upstreamed in 0.1.69</changelog>
  <changelog author="meissner@suse.com" date="1707825600">- updated to 0.1.72 (jsc#ECO-3319)
  - ANSSI BP 028 profile for debian12 (#11368)
  - Building on Windows (#11406)
  - Control for BSI APP.4.4 (#11342)
  - update to CIS RHEL 7 and RHEL 8 profiles aligning them with the latest benchmarks
  - various fixes to SLE profiles
- add openeuler to -redhat package
- removed ssg-fix-journald.patch: fixed upstream</changelog>
  <changelog author="rumen.chikov@suse.com" date="1717156800">- updated to 0.1.73 (jsc#ECO-3319)
  - CMP 2417: Implement PCI-DSS v4.0 outline for OpenShift (#11651)
  - Update all RHEL ANSSI BP028 profiles to be aligned with configuration recommendations version 2.0
  - Generate rule references from control files (#11540)
  - Initial implementation of STIG V1R1 profile for Ubuntu 22.04 LTS (#11820)</changelog>
  <changelog author="rumen.chikov@suse.com" date="1725278400">- updated to 0.1.74 (jsc#ECO-3319)
  - Add Amazon Linux 2023 product (#12006)
  - Introduce new remediation type Kickstart (#12144)
  - Make PAM macros more flexible to variables (#12133)
  - Remove Debian 10 Product (#12205)
  - Remove Red Hat Enterprise Linux 7 product (#12093)
  - Update CIS RHEL9 control file to v2.0.0 (#12067)</changelog>
  <changelog author="rumen.chikov@suse.com" date="1733313600">- updated to 0.1.75 (jsc#ECO-3319)
  - Add new product kylinserver10
  - Create OL10 product
  - Update PCI-DSS control file for version 4.0.1
  - Add Ism profile for ol8, ol9
  - Release SLMicro5 product
  - Various updates for SLE 12/15</changelog>
  <changelog author="meissner@suse.com" date="1733400000">- ssg-reproducable.patch: replace two date injections by SOURCE_DATE_EPOCH
  to make reproducible. bsc#1230361</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741003200">- updated to 0.1.76 (jsc#ECO-3319)
  - Add new product for Ubuntu 24.04 and draft CIS profiles
  - Add pyproject.toml for the ssg package
  - AlmaLinux OS 9 as a new product
  - Documentation for ssg library
  - Extend SSG library to more easily collect profile selections
  - Extend SSG with functions to manage variables</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741089600">- removed ssg-reproducable.patch: upstream</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741089601">- added build support for almalinux9</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176000">- updates redhat package to include almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176001">- fix a bug in redhad package description for almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176002">- removed tables reference related to almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741694400">- creation of a new request</changelog>
  <changelog author="sfalken@opensuse.org" date="1742644800">- Add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to fix FTBFS with cmake4
- Remove Group: declarations, no longer used</changelog>
  <changelog author="meissner@suse.com" date="1742731200">- ssg-fix-python.patch: fix build with older python3.</changelog>
  <changelog author="rumen.chikov@suse.com" date="1749729600">- updated to 0.1.77 (jsc#ECO-3319)
  - Introduce Architecture Decisions Records
  - Move stablization to the third Monday of the second month
  - Remove CCI References
  - Remove macOS content
- removed ssg-fix-python.patch: upstream
- Added support for tencentos4</changelog>
  <changelog author="meissner@suse.com" date="1750766400">- buildrequire cmake3 on older SLES versions for build</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1753876800">- ssg-remove-cis.patch: remove cis profiles
- Update description: remove cis profiles</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1755777600">- Remove ssg-remove-cis.patch: tarball
- Add check if cis profiles exists in the tarball</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1755777601">- Remove the cis profiles from the tarball</changelog>
</package>
<package pkgid="3a7ea08109e913a5b60e987bcd4d7b70fd2e6325711bd3f7aeee79e3128627eb" name="scap-security-guide-ubuntu" arch="noarch">
  <version epoch="0" ver="0.1.77" rel="161.1"/>
  <changelog author="meissner@suse.com" date="1702987200">- updated to 0.1.71 (jsc#ECO-3319)
  - Add RHEL 9 STIG
  - Add support for Debian 12
  - Update PCI-DSS profile for RHEL
  - lots of bugfixes and improvements for SLE
- removed left over file
  0001-Revert-fix-aide-remediations-add-crontabs.patch upstreamed in 0.1.69</changelog>
  <changelog author="meissner@suse.com" date="1707825600">- updated to 0.1.72 (jsc#ECO-3319)
  - ANSSI BP 028 profile for debian12 (#11368)
  - Building on Windows (#11406)
  - Control for BSI APP.4.4 (#11342)
  - update to CIS RHEL 7 and RHEL 8 profiles aligning them with the latest benchmarks
  - various fixes to SLE profiles
- add openeuler to -redhat package
- removed ssg-fix-journald.patch: fixed upstream</changelog>
  <changelog author="rumen.chikov@suse.com" date="1717156800">- updated to 0.1.73 (jsc#ECO-3319)
  - CMP 2417: Implement PCI-DSS v4.0 outline for OpenShift (#11651)
  - Update all RHEL ANSSI BP028 profiles to be aligned with configuration recommendations version 2.0
  - Generate rule references from control files (#11540)
  - Initial implementation of STIG V1R1 profile for Ubuntu 22.04 LTS (#11820)</changelog>
  <changelog author="rumen.chikov@suse.com" date="1725278400">- updated to 0.1.74 (jsc#ECO-3319)
  - Add Amazon Linux 2023 product (#12006)
  - Introduce new remediation type Kickstart (#12144)
  - Make PAM macros more flexible to variables (#12133)
  - Remove Debian 10 Product (#12205)
  - Remove Red Hat Enterprise Linux 7 product (#12093)
  - Update CIS RHEL9 control file to v2.0.0 (#12067)</changelog>
  <changelog author="rumen.chikov@suse.com" date="1733313600">- updated to 0.1.75 (jsc#ECO-3319)
  - Add new product kylinserver10
  - Create OL10 product
  - Update PCI-DSS control file for version 4.0.1
  - Add Ism profile for ol8, ol9
  - Release SLMicro5 product
  - Various updates for SLE 12/15</changelog>
  <changelog author="meissner@suse.com" date="1733400000">- ssg-reproducable.patch: replace two date injections by SOURCE_DATE_EPOCH
  to make reproducible. bsc#1230361</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741003200">- updated to 0.1.76 (jsc#ECO-3319)
  - Add new product for Ubuntu 24.04 and draft CIS profiles
  - Add pyproject.toml for the ssg package
  - AlmaLinux OS 9 as a new product
  - Documentation for ssg library
  - Extend SSG library to more easily collect profile selections
  - Extend SSG with functions to manage variables</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741089600">- removed ssg-reproducable.patch: upstream</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741089601">- added build support for almalinux9</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176000">- updates redhat package to include almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176001">- fix a bug in redhad package description for almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741176002">- removed tables reference related to almalinux9 builds</changelog>
  <changelog author="rumen.chikov@suse.com" date="1741694400">- creation of a new request</changelog>
  <changelog author="sfalken@opensuse.org" date="1742644800">- Add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to fix FTBFS with cmake4
- Remove Group: declarations, no longer used</changelog>
  <changelog author="meissner@suse.com" date="1742731200">- ssg-fix-python.patch: fix build with older python3.</changelog>
  <changelog author="rumen.chikov@suse.com" date="1749729600">- updated to 0.1.77 (jsc#ECO-3319)
  - Introduce Architecture Decisions Records
  - Move stablization to the third Monday of the second month
  - Remove CCI References
  - Remove macOS content
- removed ssg-fix-python.patch: upstream
- Added support for tencentos4</changelog>
  <changelog author="meissner@suse.com" date="1750766400">- buildrequire cmake3 on older SLES versions for build</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1753876800">- ssg-remove-cis.patch: remove cis profiles
- Update description: remove cis profiles</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1755777600">- Remove ssg-remove-cis.patch: tarball
- Add check if cis profiles exists in the tarball</changelog>
  <changelog author="svetlin.boychev@suse.com" date="1755777601">- Remove the cis profiles from the tarball</changelog>
</package>
<package pkgid="02b1c37d930a737c8c26fbaf24ba9c045bbfddb595287e561637597c58a4d9fd" name="softhsm" arch="src">
  <version epoch="0" ver="2.6.1" rel="28.1"/>
  <changelog author="paul@xelerance.com" date="1299153600">- Initial package for Fedora</changelog>
  <changelog author="paul@xelerance.com" date="1317816000">- Upgraded to 1.3.0</changelog>
  <changelog author="paul@xelerance.com" date="1319544000">- Fix description texts w.r.t. include files</changelog>
  <changelog author="paul@xelerance.com" date="1319716800">- Initial Fedora package
- Do not install the .a file
- Use a separate "opendnssec" user to own /var/sofhsm</changelog>
  <changelog author="pwouters@redhat.com" date="1333454400">- Updated to 1.3.2.
- Changed user from opendnssec to ods, as used in the opendnssec package</changelog>
  <changelog author="pwouters@redhat.com" date="1338811200">- Updated to 1.3.3</changelog>
  <changelog author="pwouters@redhat.com" date="1383480000">- Updated to 1.3.5 (rhbz#987721)</changelog>
  <changelog author="pwouters@redhat.com" date="1397822400">- Updated to 1.3.6 (rhbz#1070196)
- Provide a p11-kit module file (rhbz#1085327)</changelog>
  <changelog author="pwouters@redhat.com" date="1412078400">- Add support for CKM_RSA_PKCS_OAEP key un/wrapping [Petr Spacek]
- Use OpenSSL EVP interface for AES key wrapping [Petr Spacek]
- Fix softhsm2-pk11install buid and post call
- Do not use --with-objectstore-backend-db (causes issues on i686)
- Change install directory to /usr/lib*/pkcs11/
- Install pkcs11 module file
- Use official upstream tar ball
- Create ods user to own softhsm/token files
- Enable migration tools (for softhsm-v1 installs)
- Add softlink for softhsm-v1 .so (needed for opendnssec's conf.xml)
- Require p11-kit, nss-tools, for SoftHSM PKCS #11 Module file
- Copy pk11install.c from coolkey package
- Enable hardened build
- Add upstream official source url</changelog>
  <changelog author="hguo@suse.com" date="1431086400">- Source extracted from Fedora 21 release SRPM with minor modifications.</changelog>
  <changelog author="meissner@suse.com" date="1444305600">- softhsm-rsakeys.patch: do not test odd bit RSA keys, this breaks
  with the FIPS enabled openssl from leap/sle12, as thats rounds
  up the keylength to the next even number. bsc#949492</changelog>
  <changelog author="meissner@suse.com" date="1494158400">- softhsm-newcppunit.patch: new cppunit uses pkg-config now, not
  cppunit-config</changelog>
  <changelog author="mardnh@gmx.de" date="1513512000">- Update to version 2.3.0
  * Upgraded to PKCS#11 v2.40.
  * Minor changes to some return values.
  * Added CKA_DESTROYABLE to all objects. Used by C_DestroyObject().
  * Added CKA_PUBLIC_KEY_INFO to certificates, private, and public key
    objects. Will be accepted from application, but SoftHSM will
    currently not calculate it.
  * Support for CKM_AES_CTR.
  * Add unit tests for SessionManager.
  * C_DigestKey returns CKR_KEY_INDIGESTIBLE when key
    attribute CKA_EXTRACTABLE = false. Whitelist SHA algorithms to allow
    C_DigestKey in this case.
  * Show slot id after initialization.
  * Run AppVeyor (Windows CI) for each PR and merge.
  * Set CKA_DECRYPT/CKA_ENCRYPT flags on key import to true.
  * Add support for libeaycompat lib for FIPS on Windows.
  * Support importing ECDSA P-521 in softhsm-util.
  * Support for Botan 2.0.
  * Editorial changes from Mountain Lion to Sierra.
  * More detailed error messages when initializing SoftHSM.
  * Support for LibreSSL.
  * Change to enable builds and reports on new Jenkinks environment.
  * Detect cppunit in autoconf.
  * CKO_CERTIFICATE and CKO_PUBLIC_KEY now defaults to CKA_PRIVATE=false.
  * Update README with information about logging.
  * Adjust log levels for failing to enumerate object store.
  * Better handling of CRYPTO_set_locking_callback() for OpenSSL.
  * Fix deriving shared secret with ECC.
  * HMAC with sizes less than L bytes is strongly discouraged.
    Set a lower bound equal to L bytes in ulMinKeySize and check it when
    initializing the operation.
  * Fix test of p11 shared library.
  * Minor fix of 'EVP_CipherFinal_ex'.
  * Fix build with cppunit.
  * Export PKCS#11 symbols from the library.
  * Zero pad key to fit the block in CKM_AES_KEY_WRAP.
  * Detecting CppUnit when using Macports.
- Update to version 2.2.0
  * Delete a token using softhsm2-util.
  * Change access mode bits for /var/lib/softhsm/tokens/
    to 1777. All users can now create tokens, but only access their own.
  * Reinitializing a token will now keep the token, but all
    token objects are deleted, the user PIN is removed and the token
    label is updated.
  * Support for OpenSSL 1.1.0.
  * Calling C_GetSlotList with NULL_PTR will make sure that
    there is always a slot with an uninitialized token available.
  * The token serial number will be used when setting the slot
    number. The serial number is set after the token has been initialized.
  * Update the command utils to use the token label or serial
    to find the token and its slot number.
  * Possibility to test other PKCS#11 implementations with the CppUnit test.
  * Mark public key as non private by default.
  * Install p11-kit module, to disable use --disable-p11-kit.
  * Add windows continuous integration build.
  * Missing new source file and test configuration in the
    Windows build project.
  * ECDSA P-521 support for OpenSSL and better test coverage.
  * Fix segmentation faults in loadLibrary function.
  * Crash on module unload with OpenSSL.
  * C++11 not detected.
  * API changes in Botan 1.11.27.
  * Fix include guard to check WITH_FIPS.
  * p11test fails on 32-bit systems.
  * Build warning about "converting a string constant".
  * Fix C++11 check to look for unique_ptr.
- Update to version 2.1.0
  * Improved guide and build scripts for Windows.
  * The password prompt in softhsm2-util can now be
    interrupted (ctrl-c).
  * Add slots.removable config option.
  * Prioritize the return values in C_GetAttributeValue.
  * Handle the CKA_CHECK_VALUE correctly for certificates
    and symmetric key objects.
  * Not possible to create certificate objects containing
    CKA_CERTIFICATE_CATEGORY, CKA_NAME_HASH_ALGORITHM, or
    CKA_JAVA_MIDP_SECURITY_DOMAIN.
  * Do not attempt decryption of empty byte strings.
  * Minor changes after a PVS-Studio code analysis, and
    C_EncryptUpdate crash if no ciphered data is produced.
  * One-byte buffer overflow in call to EVP_DecryptUpdate.
  * Problem while closing library that is initialized but
    improperly finalized.
  * Adjust return values for the template parsing.
  * C_DeriveKey() error with leading zero bytes.
  * CKA_NEVER_EXTRACTABLE set to CK_FALSE on objects
    created with C_CreateObject.
  * Stop discarding the global OpenSSL libcrypto state.
- Drop not longer needed patches (fixed upstream):
  * softhsm-v2.0.0b1-aes-key-wrap.patch
  * softhsm-v2.0.0b1-ckm-rsa-pkcs-oaep-key-wrap.patch
  * softhsm-newcppunit.patch
- Rebase patches:
  * softhsm-rsakeys.patch
- Fix URL</changelog>
  <changelog author="mardnh@gmx.de" date="1519732800">- Update to version 2.4.0
  * Support PKCS#8 for GOST.
  * Support for CKA_ALLOWED_MECHANISMS.
  * Support CKA_ALWAYS_AUTHENTICATE for private key objects.
  * Support for CKM_DES3_CMAC and CKM_AES_CMAC.
  * Support for CKM_AES_GCM.
  * Document that initialized tokens will be reassigned to another
    slot (based on the token serial number).
  * Support for CKM_RSA_PKCS_PSS.
  * Import AES keys with softhsm2-util.
  * softhsm2-util will check the configuration and report any
    issues before loading the PKCS#11 library.</changelog>
  <changelog author="michael@stroeder.com" date="1537790400">- Update to version 2.5.0
  Updates:
  * Issue #323: Support for EDDSA with vendor defined mechanisms.
  * Issue #362: CMake Build System Support for SoftHSM.
  * Issue #368: Support migrating 32-bit SoftHSMv1 DB on 64-bit system (LP64).
  * Issue #385: Default is not to build EDDSA since it has not been released in OpenSSL.
  * Issue #387: Windows: Add VS2017 detection to Configure.py.
  * Issue #412: Replace PKCS11 headers with a version from p11-kit.
  Bugfixes:
  * Issue #366: Support cross-compilation.
  * Issue #377: Duplicate symbol error with custom p11test.
  * Issue #386: Use RDRAND in OpenSSL if that engine is available.
  * Issue #388: Update DBTests.cpp to fix x86 test failure.
  * Issue #393: Not setting CKA_PUBLIC_KEY_INFO correctly.
  * Issue #401: Wrong key and keyserver mentioned in installation documentation.
  * Issue #408: Remove mutex callbacks after C_Finalize().</changelog>
  <changelog author="christophe@krop.fr" date="1558353600">- Add the missing zlib requirement.</changelog>
  <changelog author="mardnh@gmx.de" date="1584446400">- Update to version 2.6.0
  Changes:
  * Issue #493: Upgrade to Botan 2.
  * Issue #530: Update appveyor build.
  * Issue #438: Detect crypto algorithms by default.
  * Issue #455: Provide a new configuration option to allow enabling and
    disabling various mechanisms (slots.mechanisms in the softhsm2.conf).
  * Issue #479: Increase SQLite busy timeout from 15 seconds to 3 minutes.
  * Issue #513: Add configuration option to reset state on fork closing all
    sessions rather than keeping all sessions open in duplicate process.
  * Issue #500: C_WaitForSlotEvent implementation.
  * Issue #445: Add wrap support with CKM_AES_CBC.
  Bugfixes:
  * Issue #418: Set fields to NULL to avoid double free.
  * Issue #423: ENGINE_load_rdrand is not supported with older openssl.
  * Issue #429: Updated prerequisite to build from repository.
  * Issue #434: Fix build issues with CMake.
  * Issue #435: Fix botan build without EDDSA.
  * Issue #442: Release resources from OSSLEVPSymmetricAlgorithm.
  * Issue #449/#502: Do not copy zero sized buffer avoid null pointer reference.
  * Issue #464: Race condition with multiple threads closing last session and
    opening a newer sessions.
  * Issue #452: Fixes to automake build fir undefined macros.
  * Issue #462: User PIN count wrongly calculated.
  * Issue #516: Fix memory leak in OSSLCryptoFactory.
  * Issue #494: Allow null pointers as arguments when count is zero.
  * Issue #518: Sporadic problem in closing sessions because of lookup of
    object without prior locking.
  * Issue #506: Check key type for C_EncryptInit and C_DecryptInit.
  * Issue #526: Adjust EDDSA code to return valid EC_PARAMS.
  * Issue #452: Autogen failure on undefined macro AC_MSG_ERROR.
  * Issue #527: Fixed some build errors for GCC 10.
  * Issue #470: Null pointer arguments validation for C_EncryptFinal, etc.</changelog>
  <changelog author="mardnh@gmx.de" date="1588248000">- Update to version 2.6.1
  * Issue #542: Support Ed448/X448 for OpenSSL
  * Issue #538: Improved warning and compilation issues for GCC10</changelog>
  <changelog author="meissner@suse.com" date="1650542400">- switched URL to https</changelog>
  <changelog author="meissner@suse.com" date="1676289600">- fixed build, uses upstream fixes:
  0001-Issue-548-Don-t-clean-up-engines-after-OpenSSL-has-a.patch
  0001-Fix-OPENSSL_cleanup-detection-without-using-our-own-.patch</changelog>
</package>
<package pkgid="c906cd4ebf2e3393e3e14ac4f5c3089f29a278ddbc4d0ee6a894c021039b0609" name="softhsm" arch="x86_64">
  <version epoch="0" ver="2.6.1" rel="28.1"/>
  <changelog author="hguo@suse.com" date="1431086400">- Source extracted from Fedora 21 release SRPM with minor modifications.</changelog>
  <changelog author="meissner@suse.com" date="1444305600">- softhsm-rsakeys.patch: do not test odd bit RSA keys, this breaks
  with the FIPS enabled openssl from leap/sle12, as thats rounds
  up the keylength to the next even number. bsc#949492</changelog>
  <changelog author="meissner@suse.com" date="1494158400">- softhsm-newcppunit.patch: new cppunit uses pkg-config now, not
  cppunit-config</changelog>
  <changelog author="mardnh@gmx.de" date="1513512000">- Update to version 2.3.0
  * Upgraded to PKCS#11 v2.40.
  * Minor changes to some return values.
  * Added CKA_DESTROYABLE to all objects. Used by C_DestroyObject().
  * Added CKA_PUBLIC_KEY_INFO to certificates, private, and public key
    objects. Will be accepted from application, but SoftHSM will
    currently not calculate it.
  * Support for CKM_AES_CTR.
  * Add unit tests for SessionManager.
  * C_DigestKey returns CKR_KEY_INDIGESTIBLE when key
    attribute CKA_EXTRACTABLE = false. Whitelist SHA algorithms to allow
    C_DigestKey in this case.
  * Show slot id after initialization.
  * Run AppVeyor (Windows CI) for each PR and merge.
  * Set CKA_DECRYPT/CKA_ENCRYPT flags on key import to true.
  * Add support for libeaycompat lib for FIPS on Windows.
  * Support importing ECDSA P-521 in softhsm-util.
  * Support for Botan 2.0.
  * Editorial changes from Mountain Lion to Sierra.
  * More detailed error messages when initializing SoftHSM.
  * Support for LibreSSL.
  * Change to enable builds and reports on new Jenkinks environment.
  * Detect cppunit in autoconf.
  * CKO_CERTIFICATE and CKO_PUBLIC_KEY now defaults to CKA_PRIVATE=false.
  * Update README with information about logging.
  * Adjust log levels for failing to enumerate object store.
  * Better handling of CRYPTO_set_locking_callback() for OpenSSL.
  * Fix deriving shared secret with ECC.
  * HMAC with sizes less than L bytes is strongly discouraged.
    Set a lower bound equal to L bytes in ulMinKeySize and check it when
    initializing the operation.
  * Fix test of p11 shared library.
  * Minor fix of 'EVP_CipherFinal_ex'.
  * Fix build with cppunit.
  * Export PKCS#11 symbols from the library.
  * Zero pad key to fit the block in CKM_AES_KEY_WRAP.
  * Detecting CppUnit when using Macports.
- Update to version 2.2.0
  * Delete a token using softhsm2-util.
  * Change access mode bits for /var/lib/softhsm/tokens/
    to 1777. All users can now create tokens, but only access their own.
  * Reinitializing a token will now keep the token, but all
    token objects are deleted, the user PIN is removed and the token
    label is updated.
  * Support for OpenSSL 1.1.0.
  * Calling C_GetSlotList with NULL_PTR will make sure that
    there is always a slot with an uninitialized token available.
  * The token serial number will be used when setting the slot
    number. The serial number is set after the token has been initialized.
  * Update the command utils to use the token label or serial
    to find the token and its slot number.
  * Possibility to test other PKCS#11 implementations with the CppUnit test.
  * Mark public key as non private by default.
  * Install p11-kit module, to disable use --disable-p11-kit.
  * Add windows continuous integration build.
  * Missing new source file and test configuration in the
    Windows build project.
  * ECDSA P-521 support for OpenSSL and better test coverage.
  * Fix segmentation faults in loadLibrary function.
  * Crash on module unload with OpenSSL.
  * C++11 not detected.
  * API changes in Botan 1.11.27.
  * Fix include guard to check WITH_FIPS.
  * p11test fails on 32-bit systems.
  * Build warning about "converting a string constant".
  * Fix C++11 check to look for unique_ptr.
- Update to version 2.1.0
  * Improved guide and build scripts for Windows.
  * The password prompt in softhsm2-util can now be
    interrupted (ctrl-c).
  * Add slots.removable config option.
  * Prioritize the return values in C_GetAttributeValue.
  * Handle the CKA_CHECK_VALUE correctly for certificates
    and symmetric key objects.
  * Not possible to create certificate objects containing
    CKA_CERTIFICATE_CATEGORY, CKA_NAME_HASH_ALGORITHM, or
    CKA_JAVA_MIDP_SECURITY_DOMAIN.
  * Do not attempt decryption of empty byte strings.
  * Minor changes after a PVS-Studio code analysis, and
    C_EncryptUpdate crash if no ciphered data is produced.
  * One-byte buffer overflow in call to EVP_DecryptUpdate.
  * Problem while closing library that is initialized but
    improperly finalized.
  * Adjust return values for the template parsing.
  * C_DeriveKey() error with leading zero bytes.
  * CKA_NEVER_EXTRACTABLE set to CK_FALSE on objects
    created with C_CreateObject.
  * Stop discarding the global OpenSSL libcrypto state.
- Drop not longer needed patches (fixed upstream):
  * softhsm-v2.0.0b1-aes-key-wrap.patch
  * softhsm-v2.0.0b1-ckm-rsa-pkcs-oaep-key-wrap.patch
  * softhsm-newcppunit.patch
- Rebase patches:
  * softhsm-rsakeys.patch
- Fix URL</changelog>
  <changelog author="mardnh@gmx.de" date="1519732800">- Update to version 2.4.0
  * Support PKCS#8 for GOST.
  * Support for CKA_ALLOWED_MECHANISMS.
  * Support CKA_ALWAYS_AUTHENTICATE for private key objects.
  * Support for CKM_DES3_CMAC and CKM_AES_CMAC.
  * Support for CKM_AES_GCM.
  * Document that initialized tokens will be reassigned to another
    slot (based on the token serial number).
  * Support for CKM_RSA_PKCS_PSS.
  * Import AES keys with softhsm2-util.
  * softhsm2-util will check the configuration and report any
    issues before loading the PKCS#11 library.</changelog>
  <changelog author="michael@stroeder.com" date="1537790400">- Update to version 2.5.0
  Updates:
  * Issue #323: Support for EDDSA with vendor defined mechanisms.
  * Issue #362: CMake Build System Support for SoftHSM.
  * Issue #368: Support migrating 32-bit SoftHSMv1 DB on 64-bit system (LP64).
  * Issue #385: Default is not to build EDDSA since it has not been released in OpenSSL.
  * Issue #387: Windows: Add VS2017 detection to Configure.py.
  * Issue #412: Replace PKCS11 headers with a version from p11-kit.
  Bugfixes:
  * Issue #366: Support cross-compilation.
  * Issue #377: Duplicate symbol error with custom p11test.
  * Issue #386: Use RDRAND in OpenSSL if that engine is available.
  * Issue #388: Update DBTests.cpp to fix x86 test failure.
  * Issue #393: Not setting CKA_PUBLIC_KEY_INFO correctly.
  * Issue #401: Wrong key and keyserver mentioned in installation documentation.
  * Issue #408: Remove mutex callbacks after C_Finalize().</changelog>
  <changelog author="christophe@krop.fr" date="1558353600">- Add the missing zlib requirement.</changelog>
  <changelog author="mardnh@gmx.de" date="1584446400">- Update to version 2.6.0
  Changes:
  * Issue #493: Upgrade to Botan 2.
  * Issue #530: Update appveyor build.
  * Issue #438: Detect crypto algorithms by default.
  * Issue #455: Provide a new configuration option to allow enabling and
    disabling various mechanisms (slots.mechanisms in the softhsm2.conf).
  * Issue #479: Increase SQLite busy timeout from 15 seconds to 3 minutes.
  * Issue #513: Add configuration option to reset state on fork closing all
    sessions rather than keeping all sessions open in duplicate process.
  * Issue #500: C_WaitForSlotEvent implementation.
  * Issue #445: Add wrap support with CKM_AES_CBC.
  Bugfixes:
  * Issue #418: Set fields to NULL to avoid double free.
  * Issue #423: ENGINE_load_rdrand is not supported with older openssl.
  * Issue #429: Updated prerequisite to build from repository.
  * Issue #434: Fix build issues with CMake.
  * Issue #435: Fix botan build without EDDSA.
  * Issue #442: Release resources from OSSLEVPSymmetricAlgorithm.
  * Issue #449/#502: Do not copy zero sized buffer avoid null pointer reference.
  * Issue #464: Race condition with multiple threads closing last session and
    opening a newer sessions.
  * Issue #452: Fixes to automake build fir undefined macros.
  * Issue #462: User PIN count wrongly calculated.
  * Issue #516: Fix memory leak in OSSLCryptoFactory.
  * Issue #494: Allow null pointers as arguments when count is zero.
  * Issue #518: Sporadic problem in closing sessions because of lookup of
    object without prior locking.
  * Issue #506: Check key type for C_EncryptInit and C_DecryptInit.
  * Issue #526: Adjust EDDSA code to return valid EC_PARAMS.
  * Issue #452: Autogen failure on undefined macro AC_MSG_ERROR.
  * Issue #527: Fixed some build errors for GCC 10.
  * Issue #470: Null pointer arguments validation for C_EncryptFinal, etc.</changelog>
  <changelog author="mardnh@gmx.de" date="1588248000">- Update to version 2.6.1
  * Issue #542: Support Ed448/X448 for OpenSSL
  * Issue #538: Improved warning and compilation issues for GCC10</changelog>
  <changelog author="meissner@suse.com" date="1650542400">- switched URL to https</changelog>
  <changelog author="meissner@suse.com" date="1676289600">- fixed build, uses upstream fixes:
  0001-Issue-548-Don-t-clean-up-engines-after-OpenSSL-has-a.patch
  0001-Fix-OPENSSL_cleanup-detection-without-using-our-own-.patch</changelog>
</package>
<package pkgid="40379238538167c95b96cafdb12c0cd55764edc21a2f07c6c13385716d85327f" name="softhsm-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.6.1" rel="28.1"/>
  <changelog author="hguo@suse.com" date="1431086400">- Source extracted from Fedora 21 release SRPM with minor modifications.</changelog>
  <changelog author="meissner@suse.com" date="1444305600">- softhsm-rsakeys.patch: do not test odd bit RSA keys, this breaks
  with the FIPS enabled openssl from leap/sle12, as thats rounds
  up the keylength to the next even number. bsc#949492</changelog>
  <changelog author="meissner@suse.com" date="1494158400">- softhsm-newcppunit.patch: new cppunit uses pkg-config now, not
  cppunit-config</changelog>
  <changelog author="mardnh@gmx.de" date="1513512000">- Update to version 2.3.0
  * Upgraded to PKCS#11 v2.40.
  * Minor changes to some return values.
  * Added CKA_DESTROYABLE to all objects. Used by C_DestroyObject().
  * Added CKA_PUBLIC_KEY_INFO to certificates, private, and public key
    objects. Will be accepted from application, but SoftHSM will
    currently not calculate it.
  * Support for CKM_AES_CTR.
  * Add unit tests for SessionManager.
  * C_DigestKey returns CKR_KEY_INDIGESTIBLE when key
    attribute CKA_EXTRACTABLE = false. Whitelist SHA algorithms to allow
    C_DigestKey in this case.
  * Show slot id after initialization.
  * Run AppVeyor (Windows CI) for each PR and merge.
  * Set CKA_DECRYPT/CKA_ENCRYPT flags on key import to true.
  * Add support for libeaycompat lib for FIPS on Windows.
  * Support importing ECDSA P-521 in softhsm-util.
  * Support for Botan 2.0.
  * Editorial changes from Mountain Lion to Sierra.
  * More detailed error messages when initializing SoftHSM.
  * Support for LibreSSL.
  * Change to enable builds and reports on new Jenkinks environment.
  * Detect cppunit in autoconf.
  * CKO_CERTIFICATE and CKO_PUBLIC_KEY now defaults to CKA_PRIVATE=false.
  * Update README with information about logging.
  * Adjust log levels for failing to enumerate object store.
  * Better handling of CRYPTO_set_locking_callback() for OpenSSL.
  * Fix deriving shared secret with ECC.
  * HMAC with sizes less than L bytes is strongly discouraged.
    Set a lower bound equal to L bytes in ulMinKeySize and check it when
    initializing the operation.
  * Fix test of p11 shared library.
  * Minor fix of 'EVP_CipherFinal_ex'.
  * Fix build with cppunit.
  * Export PKCS#11 symbols from the library.
  * Zero pad key to fit the block in CKM_AES_KEY_WRAP.
  * Detecting CppUnit when using Macports.
- Update to version 2.2.0
  * Delete a token using softhsm2-util.
  * Change access mode bits for /var/lib/softhsm/tokens/
    to 1777. All users can now create tokens, but only access their own.
  * Reinitializing a token will now keep the token, but all
    token objects are deleted, the user PIN is removed and the token
    label is updated.
  * Support for OpenSSL 1.1.0.
  * Calling C_GetSlotList with NULL_PTR will make sure that
    there is always a slot with an uninitialized token available.
  * The token serial number will be used when setting the slot
    number. The serial number is set after the token has been initialized.
  * Update the command utils to use the token label or serial
    to find the token and its slot number.
  * Possibility to test other PKCS#11 implementations with the CppUnit test.
  * Mark public key as non private by default.
  * Install p11-kit module, to disable use --disable-p11-kit.
  * Add windows continuous integration build.
  * Missing new source file and test configuration in the
    Windows build project.
  * ECDSA P-521 support for OpenSSL and better test coverage.
  * Fix segmentation faults in loadLibrary function.
  * Crash on module unload with OpenSSL.
  * C++11 not detected.
  * API changes in Botan 1.11.27.
  * Fix include guard to check WITH_FIPS.
  * p11test fails on 32-bit systems.
  * Build warning about "converting a string constant".
  * Fix C++11 check to look for unique_ptr.
- Update to version 2.1.0
  * Improved guide and build scripts for Windows.
  * The password prompt in softhsm2-util can now be
    interrupted (ctrl-c).
  * Add slots.removable config option.
  * Prioritize the return values in C_GetAttributeValue.
  * Handle the CKA_CHECK_VALUE correctly for certificates
    and symmetric key objects.
  * Not possible to create certificate objects containing
    CKA_CERTIFICATE_CATEGORY, CKA_NAME_HASH_ALGORITHM, or
    CKA_JAVA_MIDP_SECURITY_DOMAIN.
  * Do not attempt decryption of empty byte strings.
  * Minor changes after a PVS-Studio code analysis, and
    C_EncryptUpdate crash if no ciphered data is produced.
  * One-byte buffer overflow in call to EVP_DecryptUpdate.
  * Problem while closing library that is initialized but
    improperly finalized.
  * Adjust return values for the template parsing.
  * C_DeriveKey() error with leading zero bytes.
  * CKA_NEVER_EXTRACTABLE set to CK_FALSE on objects
    created with C_CreateObject.
  * Stop discarding the global OpenSSL libcrypto state.
- Drop not longer needed patches (fixed upstream):
  * softhsm-v2.0.0b1-aes-key-wrap.patch
  * softhsm-v2.0.0b1-ckm-rsa-pkcs-oaep-key-wrap.patch
  * softhsm-newcppunit.patch
- Rebase patches:
  * softhsm-rsakeys.patch
- Fix URL</changelog>
  <changelog author="mardnh@gmx.de" date="1519732800">- Update to version 2.4.0
  * Support PKCS#8 for GOST.
  * Support for CKA_ALLOWED_MECHANISMS.
  * Support CKA_ALWAYS_AUTHENTICATE for private key objects.
  * Support for CKM_DES3_CMAC and CKM_AES_CMAC.
  * Support for CKM_AES_GCM.
  * Document that initialized tokens will be reassigned to another
    slot (based on the token serial number).
  * Support for CKM_RSA_PKCS_PSS.
  * Import AES keys with softhsm2-util.
  * softhsm2-util will check the configuration and report any
    issues before loading the PKCS#11 library.</changelog>
  <changelog author="michael@stroeder.com" date="1537790400">- Update to version 2.5.0
  Updates:
  * Issue #323: Support for EDDSA with vendor defined mechanisms.
  * Issue #362: CMake Build System Support for SoftHSM.
  * Issue #368: Support migrating 32-bit SoftHSMv1 DB on 64-bit system (LP64).
  * Issue #385: Default is not to build EDDSA since it has not been released in OpenSSL.
  * Issue #387: Windows: Add VS2017 detection to Configure.py.
  * Issue #412: Replace PKCS11 headers with a version from p11-kit.
  Bugfixes:
  * Issue #366: Support cross-compilation.
  * Issue #377: Duplicate symbol error with custom p11test.
  * Issue #386: Use RDRAND in OpenSSL if that engine is available.
  * Issue #388: Update DBTests.cpp to fix x86 test failure.
  * Issue #393: Not setting CKA_PUBLIC_KEY_INFO correctly.
  * Issue #401: Wrong key and keyserver mentioned in installation documentation.
  * Issue #408: Remove mutex callbacks after C_Finalize().</changelog>
  <changelog author="christophe@krop.fr" date="1558353600">- Add the missing zlib requirement.</changelog>
  <changelog author="mardnh@gmx.de" date="1584446400">- Update to version 2.6.0
  Changes:
  * Issue #493: Upgrade to Botan 2.
  * Issue #530: Update appveyor build.
  * Issue #438: Detect crypto algorithms by default.
  * Issue #455: Provide a new configuration option to allow enabling and
    disabling various mechanisms (slots.mechanisms in the softhsm2.conf).
  * Issue #479: Increase SQLite busy timeout from 15 seconds to 3 minutes.
  * Issue #513: Add configuration option to reset state on fork closing all
    sessions rather than keeping all sessions open in duplicate process.
  * Issue #500: C_WaitForSlotEvent implementation.
  * Issue #445: Add wrap support with CKM_AES_CBC.
  Bugfixes:
  * Issue #418: Set fields to NULL to avoid double free.
  * Issue #423: ENGINE_load_rdrand is not supported with older openssl.
  * Issue #429: Updated prerequisite to build from repository.
  * Issue #434: Fix build issues with CMake.
  * Issue #435: Fix botan build without EDDSA.
  * Issue #442: Release resources from OSSLEVPSymmetricAlgorithm.
  * Issue #449/#502: Do not copy zero sized buffer avoid null pointer reference.
  * Issue #464: Race condition with multiple threads closing last session and
    opening a newer sessions.
  * Issue #452: Fixes to automake build fir undefined macros.
  * Issue #462: User PIN count wrongly calculated.
  * Issue #516: Fix memory leak in OSSLCryptoFactory.
  * Issue #494: Allow null pointers as arguments when count is zero.
  * Issue #518: Sporadic problem in closing sessions because of lookup of
    object without prior locking.
  * Issue #506: Check key type for C_EncryptInit and C_DecryptInit.
  * Issue #526: Adjust EDDSA code to return valid EC_PARAMS.
  * Issue #452: Autogen failure on undefined macro AC_MSG_ERROR.
  * Issue #527: Fixed some build errors for GCC 10.
  * Issue #470: Null pointer arguments validation for C_EncryptFinal, etc.</changelog>
  <changelog author="mardnh@gmx.de" date="1588248000">- Update to version 2.6.1
  * Issue #542: Support Ed448/X448 for OpenSSL
  * Issue #538: Improved warning and compilation issues for GCC10</changelog>
  <changelog author="meissner@suse.com" date="1650542400">- switched URL to https</changelog>
  <changelog author="meissner@suse.com" date="1676289600">- fixed build, uses upstream fixes:
  0001-Issue-548-Don-t-clean-up-engines-after-OpenSSL-has-a.patch
  0001-Fix-OPENSSL_cleanup-detection-without-using-our-own-.patch</changelog>
</package>
<package pkgid="3369a460cf51bac7446694ee2e976989a105dec2e6f7195dea4fc4a2a78cdc52" name="softhsm-debugsource" arch="x86_64">
  <version epoch="0" ver="2.6.1" rel="28.1"/>
  <changelog author="hguo@suse.com" date="1431086400">- Source extracted from Fedora 21 release SRPM with minor modifications.</changelog>
  <changelog author="meissner@suse.com" date="1444305600">- softhsm-rsakeys.patch: do not test odd bit RSA keys, this breaks
  with the FIPS enabled openssl from leap/sle12, as thats rounds
  up the keylength to the next even number. bsc#949492</changelog>
  <changelog author="meissner@suse.com" date="1494158400">- softhsm-newcppunit.patch: new cppunit uses pkg-config now, not
  cppunit-config</changelog>
  <changelog author="mardnh@gmx.de" date="1513512000">- Update to version 2.3.0
  * Upgraded to PKCS#11 v2.40.
  * Minor changes to some return values.
  * Added CKA_DESTROYABLE to all objects. Used by C_DestroyObject().
  * Added CKA_PUBLIC_KEY_INFO to certificates, private, and public key
    objects. Will be accepted from application, but SoftHSM will
    currently not calculate it.
  * Support for CKM_AES_CTR.
  * Add unit tests for SessionManager.
  * C_DigestKey returns CKR_KEY_INDIGESTIBLE when key
    attribute CKA_EXTRACTABLE = false. Whitelist SHA algorithms to allow
    C_DigestKey in this case.
  * Show slot id after initialization.
  * Run AppVeyor (Windows CI) for each PR and merge.
  * Set CKA_DECRYPT/CKA_ENCRYPT flags on key import to true.
  * Add support for libeaycompat lib for FIPS on Windows.
  * Support importing ECDSA P-521 in softhsm-util.
  * Support for Botan 2.0.
  * Editorial changes from Mountain Lion to Sierra.
  * More detailed error messages when initializing SoftHSM.
  * Support for LibreSSL.
  * Change to enable builds and reports on new Jenkinks environment.
  * Detect cppunit in autoconf.
  * CKO_CERTIFICATE and CKO_PUBLIC_KEY now defaults to CKA_PRIVATE=false.
  * Update README with information about logging.
  * Adjust log levels for failing to enumerate object store.
  * Better handling of CRYPTO_set_locking_callback() for OpenSSL.
  * Fix deriving shared secret with ECC.
  * HMAC with sizes less than L bytes is strongly discouraged.
    Set a lower bound equal to L bytes in ulMinKeySize and check it when
    initializing the operation.
  * Fix test of p11 shared library.
  * Minor fix of 'EVP_CipherFinal_ex'.
  * Fix build with cppunit.
  * Export PKCS#11 symbols from the library.
  * Zero pad key to fit the block in CKM_AES_KEY_WRAP.
  * Detecting CppUnit when using Macports.
- Update to version 2.2.0
  * Delete a token using softhsm2-util.
  * Change access mode bits for /var/lib/softhsm/tokens/
    to 1777. All users can now create tokens, but only access their own.
  * Reinitializing a token will now keep the token, but all
    token objects are deleted, the user PIN is removed and the token
    label is updated.
  * Support for OpenSSL 1.1.0.
  * Calling C_GetSlotList with NULL_PTR will make sure that
    there is always a slot with an uninitialized token available.
  * The token serial number will be used when setting the slot
    number. The serial number is set after the token has been initialized.
  * Update the command utils to use the token label or serial
    to find the token and its slot number.
  * Possibility to test other PKCS#11 implementations with the CppUnit test.
  * Mark public key as non private by default.
  * Install p11-kit module, to disable use --disable-p11-kit.
  * Add windows continuous integration build.
  * Missing new source file and test configuration in the
    Windows build project.
  * ECDSA P-521 support for OpenSSL and better test coverage.
  * Fix segmentation faults in loadLibrary function.
  * Crash on module unload with OpenSSL.
  * C++11 not detected.
  * API changes in Botan 1.11.27.
  * Fix include guard to check WITH_FIPS.
  * p11test fails on 32-bit systems.
  * Build warning about "converting a string constant".
  * Fix C++11 check to look for unique_ptr.
- Update to version 2.1.0
  * Improved guide and build scripts for Windows.
  * The password prompt in softhsm2-util can now be
    interrupted (ctrl-c).
  * Add slots.removable config option.
  * Prioritize the return values in C_GetAttributeValue.
  * Handle the CKA_CHECK_VALUE correctly for certificates
    and symmetric key objects.
  * Not possible to create certificate objects containing
    CKA_CERTIFICATE_CATEGORY, CKA_NAME_HASH_ALGORITHM, or
    CKA_JAVA_MIDP_SECURITY_DOMAIN.
  * Do not attempt decryption of empty byte strings.
  * Minor changes after a PVS-Studio code analysis, and
    C_EncryptUpdate crash if no ciphered data is produced.
  * One-byte buffer overflow in call to EVP_DecryptUpdate.
  * Problem while closing library that is initialized but
    improperly finalized.
  * Adjust return values for the template parsing.
  * C_DeriveKey() error with leading zero bytes.
  * CKA_NEVER_EXTRACTABLE set to CK_FALSE on objects
    created with C_CreateObject.
  * Stop discarding the global OpenSSL libcrypto state.
- Drop not longer needed patches (fixed upstream):
  * softhsm-v2.0.0b1-aes-key-wrap.patch
  * softhsm-v2.0.0b1-ckm-rsa-pkcs-oaep-key-wrap.patch
  * softhsm-newcppunit.patch
- Rebase patches:
  * softhsm-rsakeys.patch
- Fix URL</changelog>
  <changelog author="mardnh@gmx.de" date="1519732800">- Update to version 2.4.0
  * Support PKCS#8 for GOST.
  * Support for CKA_ALLOWED_MECHANISMS.
  * Support CKA_ALWAYS_AUTHENTICATE for private key objects.
  * Support for CKM_DES3_CMAC and CKM_AES_CMAC.
  * Support for CKM_AES_GCM.
  * Document that initialized tokens will be reassigned to another
    slot (based on the token serial number).
  * Support for CKM_RSA_PKCS_PSS.
  * Import AES keys with softhsm2-util.
  * softhsm2-util will check the configuration and report any
    issues before loading the PKCS#11 library.</changelog>
  <changelog author="michael@stroeder.com" date="1537790400">- Update to version 2.5.0
  Updates:
  * Issue #323: Support for EDDSA with vendor defined mechanisms.
  * Issue #362: CMake Build System Support for SoftHSM.
  * Issue #368: Support migrating 32-bit SoftHSMv1 DB on 64-bit system (LP64).
  * Issue #385: Default is not to build EDDSA since it has not been released in OpenSSL.
  * Issue #387: Windows: Add VS2017 detection to Configure.py.
  * Issue #412: Replace PKCS11 headers with a version from p11-kit.
  Bugfixes:
  * Issue #366: Support cross-compilation.
  * Issue #377: Duplicate symbol error with custom p11test.
  * Issue #386: Use RDRAND in OpenSSL if that engine is available.
  * Issue #388: Update DBTests.cpp to fix x86 test failure.
  * Issue #393: Not setting CKA_PUBLIC_KEY_INFO correctly.
  * Issue #401: Wrong key and keyserver mentioned in installation documentation.
  * Issue #408: Remove mutex callbacks after C_Finalize().</changelog>
  <changelog author="christophe@krop.fr" date="1558353600">- Add the missing zlib requirement.</changelog>
  <changelog author="mardnh@gmx.de" date="1584446400">- Update to version 2.6.0
  Changes:
  * Issue #493: Upgrade to Botan 2.
  * Issue #530: Update appveyor build.
  * Issue #438: Detect crypto algorithms by default.
  * Issue #455: Provide a new configuration option to allow enabling and
    disabling various mechanisms (slots.mechanisms in the softhsm2.conf).
  * Issue #479: Increase SQLite busy timeout from 15 seconds to 3 minutes.
  * Issue #513: Add configuration option to reset state on fork closing all
    sessions rather than keeping all sessions open in duplicate process.
  * Issue #500: C_WaitForSlotEvent implementation.
  * Issue #445: Add wrap support with CKM_AES_CBC.
  Bugfixes:
  * Issue #418: Set fields to NULL to avoid double free.
  * Issue #423: ENGINE_load_rdrand is not supported with older openssl.
  * Issue #429: Updated prerequisite to build from repository.
  * Issue #434: Fix build issues with CMake.
  * Issue #435: Fix botan build without EDDSA.
  * Issue #442: Release resources from OSSLEVPSymmetricAlgorithm.
  * Issue #449/#502: Do not copy zero sized buffer avoid null pointer reference.
  * Issue #464: Race condition with multiple threads closing last session and
    opening a newer sessions.
  * Issue #452: Fixes to automake build fir undefined macros.
  * Issue #462: User PIN count wrongly calculated.
  * Issue #516: Fix memory leak in OSSLCryptoFactory.
  * Issue #494: Allow null pointers as arguments when count is zero.
  * Issue #518: Sporadic problem in closing sessions because of lookup of
    object without prior locking.
  * Issue #506: Check key type for C_EncryptInit and C_DecryptInit.
  * Issue #526: Adjust EDDSA code to return valid EC_PARAMS.
  * Issue #452: Autogen failure on undefined macro AC_MSG_ERROR.
  * Issue #527: Fixed some build errors for GCC 10.
  * Issue #470: Null pointer arguments validation for C_EncryptFinal, etc.</changelog>
  <changelog author="mardnh@gmx.de" date="1588248000">- Update to version 2.6.1
  * Issue #542: Support Ed448/X448 for OpenSSL
  * Issue #538: Improved warning and compilation issues for GCC10</changelog>
  <changelog author="meissner@suse.com" date="1650542400">- switched URL to https</changelog>
  <changelog author="meissner@suse.com" date="1676289600">- fixed build, uses upstream fixes:
  0001-Issue-548-Don-t-clean-up-engines-after-OpenSSL-has-a.patch
  0001-Fix-OPENSSL_cleanup-detection-without-using-our-own-.patch</changelog>
</package>
<package pkgid="dcb857a0b6b12316508243de278f5ca821877fd78eb8a88d27a05d051574c191" name="softhsm-devel" arch="x86_64">
  <version epoch="0" ver="2.6.1" rel="28.1"/>
  <changelog author="hguo@suse.com" date="1431086400">- Source extracted from Fedora 21 release SRPM with minor modifications.</changelog>
  <changelog author="meissner@suse.com" date="1444305600">- softhsm-rsakeys.patch: do not test odd bit RSA keys, this breaks
  with the FIPS enabled openssl from leap/sle12, as thats rounds
  up the keylength to the next even number. bsc#949492</changelog>
  <changelog author="meissner@suse.com" date="1494158400">- softhsm-newcppunit.patch: new cppunit uses pkg-config now, not
  cppunit-config</changelog>
  <changelog author="mardnh@gmx.de" date="1513512000">- Update to version 2.3.0
  * Upgraded to PKCS#11 v2.40.
  * Minor changes to some return values.
  * Added CKA_DESTROYABLE to all objects. Used by C_DestroyObject().
  * Added CKA_PUBLIC_KEY_INFO to certificates, private, and public key
    objects. Will be accepted from application, but SoftHSM will
    currently not calculate it.
  * Support for CKM_AES_CTR.
  * Add unit tests for SessionManager.
  * C_DigestKey returns CKR_KEY_INDIGESTIBLE when key
    attribute CKA_EXTRACTABLE = false. Whitelist SHA algorithms to allow
    C_DigestKey in this case.
  * Show slot id after initialization.
  * Run AppVeyor (Windows CI) for each PR and merge.
  * Set CKA_DECRYPT/CKA_ENCRYPT flags on key import to true.
  * Add support for libeaycompat lib for FIPS on Windows.
  * Support importing ECDSA P-521 in softhsm-util.
  * Support for Botan 2.0.
  * Editorial changes from Mountain Lion to Sierra.
  * More detailed error messages when initializing SoftHSM.
  * Support for LibreSSL.
  * Change to enable builds and reports on new Jenkinks environment.
  * Detect cppunit in autoconf.
  * CKO_CERTIFICATE and CKO_PUBLIC_KEY now defaults to CKA_PRIVATE=false.
  * Update README with information about logging.
  * Adjust log levels for failing to enumerate object store.
  * Better handling of CRYPTO_set_locking_callback() for OpenSSL.
  * Fix deriving shared secret with ECC.
  * HMAC with sizes less than L bytes is strongly discouraged.
    Set a lower bound equal to L bytes in ulMinKeySize and check it when
    initializing the operation.
  * Fix test of p11 shared library.
  * Minor fix of 'EVP_CipherFinal_ex'.
  * Fix build with cppunit.
  * Export PKCS#11 symbols from the library.
  * Zero pad key to fit the block in CKM_AES_KEY_WRAP.
  * Detecting CppUnit when using Macports.
- Update to version 2.2.0
  * Delete a token using softhsm2-util.
  * Change access mode bits for /var/lib/softhsm/tokens/
    to 1777. All users can now create tokens, but only access their own.
  * Reinitializing a token will now keep the token, but all
    token objects are deleted, the user PIN is removed and the token
    label is updated.
  * Support for OpenSSL 1.1.0.
  * Calling C_GetSlotList with NULL_PTR will make sure that
    there is always a slot with an uninitialized token available.
  * The token serial number will be used when setting the slot
    number. The serial number is set after the token has been initialized.
  * Update the command utils to use the token label or serial
    to find the token and its slot number.
  * Possibility to test other PKCS#11 implementations with the CppUnit test.
  * Mark public key as non private by default.
  * Install p11-kit module, to disable use --disable-p11-kit.
  * Add windows continuous integration build.
  * Missing new source file and test configuration in the
    Windows build project.
  * ECDSA P-521 support for OpenSSL and better test coverage.
  * Fix segmentation faults in loadLibrary function.
  * Crash on module unload with OpenSSL.
  * C++11 not detected.
  * API changes in Botan 1.11.27.
  * Fix include guard to check WITH_FIPS.
  * p11test fails on 32-bit systems.
  * Build warning about "converting a string constant".
  * Fix C++11 check to look for unique_ptr.
- Update to version 2.1.0
  * Improved guide and build scripts for Windows.
  * The password prompt in softhsm2-util can now be
    interrupted (ctrl-c).
  * Add slots.removable config option.
  * Prioritize the return values in C_GetAttributeValue.
  * Handle the CKA_CHECK_VALUE correctly for certificates
    and symmetric key objects.
  * Not possible to create certificate objects containing
    CKA_CERTIFICATE_CATEGORY, CKA_NAME_HASH_ALGORITHM, or
    CKA_JAVA_MIDP_SECURITY_DOMAIN.
  * Do not attempt decryption of empty byte strings.
  * Minor changes after a PVS-Studio code analysis, and
    C_EncryptUpdate crash if no ciphered data is produced.
  * One-byte buffer overflow in call to EVP_DecryptUpdate.
  * Problem while closing library that is initialized but
    improperly finalized.
  * Adjust return values for the template parsing.
  * C_DeriveKey() error with leading zero bytes.
  * CKA_NEVER_EXTRACTABLE set to CK_FALSE on objects
    created with C_CreateObject.
  * Stop discarding the global OpenSSL libcrypto state.
- Drop not longer needed patches (fixed upstream):
  * softhsm-v2.0.0b1-aes-key-wrap.patch
  * softhsm-v2.0.0b1-ckm-rsa-pkcs-oaep-key-wrap.patch
  * softhsm-newcppunit.patch
- Rebase patches:
  * softhsm-rsakeys.patch
- Fix URL</changelog>
  <changelog author="mardnh@gmx.de" date="1519732800">- Update to version 2.4.0
  * Support PKCS#8 for GOST.
  * Support for CKA_ALLOWED_MECHANISMS.
  * Support CKA_ALWAYS_AUTHENTICATE for private key objects.
  * Support for CKM_DES3_CMAC and CKM_AES_CMAC.
  * Support for CKM_AES_GCM.
  * Document that initialized tokens will be reassigned to another
    slot (based on the token serial number).
  * Support for CKM_RSA_PKCS_PSS.
  * Import AES keys with softhsm2-util.
  * softhsm2-util will check the configuration and report any
    issues before loading the PKCS#11 library.</changelog>
  <changelog author="michael@stroeder.com" date="1537790400">- Update to version 2.5.0
  Updates:
  * Issue #323: Support for EDDSA with vendor defined mechanisms.
  * Issue #362: CMake Build System Support for SoftHSM.
  * Issue #368: Support migrating 32-bit SoftHSMv1 DB on 64-bit system (LP64).
  * Issue #385: Default is not to build EDDSA since it has not been released in OpenSSL.
  * Issue #387: Windows: Add VS2017 detection to Configure.py.
  * Issue #412: Replace PKCS11 headers with a version from p11-kit.
  Bugfixes:
  * Issue #366: Support cross-compilation.
  * Issue #377: Duplicate symbol error with custom p11test.
  * Issue #386: Use RDRAND in OpenSSL if that engine is available.
  * Issue #388: Update DBTests.cpp to fix x86 test failure.
  * Issue #393: Not setting CKA_PUBLIC_KEY_INFO correctly.
  * Issue #401: Wrong key and keyserver mentioned in installation documentation.
  * Issue #408: Remove mutex callbacks after C_Finalize().</changelog>
  <changelog author="christophe@krop.fr" date="1558353600">- Add the missing zlib requirement.</changelog>
  <changelog author="mardnh@gmx.de" date="1584446400">- Update to version 2.6.0
  Changes:
  * Issue #493: Upgrade to Botan 2.
  * Issue #530: Update appveyor build.
  * Issue #438: Detect crypto algorithms by default.
  * Issue #455: Provide a new configuration option to allow enabling and
    disabling various mechanisms (slots.mechanisms in the softhsm2.conf).
  * Issue #479: Increase SQLite busy timeout from 15 seconds to 3 minutes.
  * Issue #513: Add configuration option to reset state on fork closing all
    sessions rather than keeping all sessions open in duplicate process.
  * Issue #500: C_WaitForSlotEvent implementation.
  * Issue #445: Add wrap support with CKM_AES_CBC.
  Bugfixes:
  * Issue #418: Set fields to NULL to avoid double free.
  * Issue #423: ENGINE_load_rdrand is not supported with older openssl.
  * Issue #429: Updated prerequisite to build from repository.
  * Issue #434: Fix build issues with CMake.
  * Issue #435: Fix botan build without EDDSA.
  * Issue #442: Release resources from OSSLEVPSymmetricAlgorithm.
  * Issue #449/#502: Do not copy zero sized buffer avoid null pointer reference.
  * Issue #464: Race condition with multiple threads closing last session and
    opening a newer sessions.
  * Issue #452: Fixes to automake build fir undefined macros.
  * Issue #462: User PIN count wrongly calculated.
  * Issue #516: Fix memory leak in OSSLCryptoFactory.
  * Issue #494: Allow null pointers as arguments when count is zero.
  * Issue #518: Sporadic problem in closing sessions because of lookup of
    object without prior locking.
  * Issue #506: Check key type for C_EncryptInit and C_DecryptInit.
  * Issue #526: Adjust EDDSA code to return valid EC_PARAMS.
  * Issue #452: Autogen failure on undefined macro AC_MSG_ERROR.
  * Issue #527: Fixed some build errors for GCC 10.
  * Issue #470: Null pointer arguments validation for C_EncryptFinal, etc.</changelog>
  <changelog author="mardnh@gmx.de" date="1588248000">- Update to version 2.6.1
  * Issue #542: Support Ed448/X448 for OpenSSL
  * Issue #538: Improved warning and compilation issues for GCC10</changelog>
  <changelog author="meissner@suse.com" date="1650542400">- switched URL to https</changelog>
  <changelog author="meissner@suse.com" date="1676289600">- fixed build, uses upstream fixes:
  0001-Issue-548-Don-t-clean-up-engines-after-OpenSSL-has-a.patch
  0001-Fix-OPENSSL_cleanup-detection-without-using-our-own-.patch</changelog>
</package>
<package pkgid="747df2ffe210560a7e7ea6e0bd8f43f360e77663bef63e1138b5355aa947b025" name="xca" arch="src">
  <version epoch="0" ver="2.4.0" rel="17.1"/>
  <changelog author="chris@computersalat.de" date="1286193600">- update to 0.9.0
  * support loading more than one PKCS#11 library
  * remove the need for engine_pkcs11
    now more than one PKCS#11 library can be loaded and used in parallel
  * Add de/selection of columns and add a lot of new possible columns
    All Subject entries, the subject hash and whole name,
    Certificate fingerprints, dates, CA info, CRL number,
    corresponding key of certs and requests
  * Improve CRL generation [3035294] CRLNumber, CRLReason
  * improve creating templates from cert
  - enhance parsing of CRL-DP, SAN, IAN and AuthInfoAcc
  - add support for CertificatePolicies
  - unknown extension are written as generic DER
  * improve date handling. "notBefore" is not reset to now anymore
    when applying a time range
  * Support dropping files onto the application
  * russian translation by Pavel Belly
  * support loading DER formatted PKCS#8 keys
  * ease commandline use
  * add DH param generation menu entry
  * improve token handling and PIN changing dialogs
  * improve key-value table input for "additional DN entries"
  * PIN and PUK changing implemented
  * apply partial template-contents
  - applying the subject only or the extensions only is possible now
  * add informational messageboxes
  - whenever an item was successfully created or imported
  * add support for random serial numbers
  * improve messages, usability and german translation
  * improve token support
  - token initializing
  - creating keys on a token
  - store existing keys on a token
  - delete keys and certs from a token
- xca 0.8.1 Tue Jan 5 07:52:03 2010
  * fix string conversion from QString to ASN1
- xca 0.8.0 Thu Dec 10 18:44:03 2009
  * improve documentation
  * improve file-dialog handling
  * Generate Template from certificate or PKCS#10 request
  - &gt; Feature request [2213094] and [1108304]
  * add hash algos "ripemd160" and "SHA384"
  * add the "no well-defined date" from RFC 5280 as checkbox
  * Feature request [1996192]
    Include "OCSPSigning" in misc/eku.txt
  * Support for EC keys
  * Update Step-by-step documentation
    Thanks Devin Reade
  * Support for Smart Cards
  * set proper file-extension .xdb on opening databases
- reworked patches
  o Makefile, configure, desktop patch
- remove obsolete uint32_t patch</changelog>
  <changelog author="chris@computersalat.de" date="1320753600">- update to 0.9.1
  * Close bug [ 3372449 ] All numeric names cannot be used
  * add search functionality for PKCS#11 libraries
  * fix ASN.1 encoding of PKCS#10 request
  * Close bug [ 3318203 ] Build failure with GNU gold linker
  * Add x509v3 extensions to the list of selectable columns
  * Close bug [ 3314262 ] Incorrect "Path length" template parameter handling
  * Close bug [ 3314263 ] Unrevoking a certificate does not make it "Trusted"
  * Feature Request [3286442] Make success/import messges optional
  * improve Password entry
  * Improve SPKAC import
  * add french translation by Patrick Monnerat
  * Export requests or certificates as openssl config file
  * Support building with EC disabled
  * Close bug [3091576] Private key export is always PKCS#8 encoded
  * Feature Request [3058196] Autoload database
  * Feature Request [3058195] Export directly to the clipboard
  * Close bug [3062711] Additional OIDs
  * Close bug [3062708] Invalid user configuration file path name
  * Fix PKCS#11 library handling
- remove obsolete Makefile patch
- rework configure, desktop patch
  * remove version from name
- fix deps
  * remove obsolete dos2unix (COPYRIGHT got fixed)</changelog>
  <changelog author="chris@computersalat.de" date="1336392000">- update to 0.9.2
  * Support for Local timezone dates.
    Differentiate between invalid and undefined dates.
  * Fix Bug #3461403 Error when create certificate with CRL distribution point
    User error -&gt; Improve user-friendlyness
  * Fix Bug #3485139 Exception when creating certificates in passwordless db
  * Avoid very long names resulting in duplicate names in the database.
  * Add warning colors for expired dates.
- rebase patches</changelog>
  <changelog author="chris@computersalat.de" date="1338984000">- update to 0.9.3
  * Fix double free in a1time resulting in random crashes
- fix License (http://spdx.org/licenses/)
  * BSD-3-Clause
- rebase patches</changelog>
  <changelog author="mrueckert@suse.de" date="1412856000">- added 0001-Fix-for-openssl-1.0.1i.patch
  From http://sourceforge.net/p/xca/patches/14/</changelog>
  <changelog author="chris@computersalat.de" date="1417089600">- update to 1.1.0
  * SF#xca#79 Template export from WinXP cannot be imported in Linux
    and Mac OS X
  * Support for Brainpool windows and MacOSX binaries
  * SF Feat. Req. #70 ability to search certificates
  * SF Feat. Req. #75 show SHA-256 digest
  * RedHat Bug #1164340 - segfault when viewing a RHEL entitlement
    certificate
  * Database hardening
  * Delete invalid items (on demand)
  * Be more tolerant against database errors
  * Gracefully handle and repair corrupt databases
  * Add "xca_db_stat(.exe)" binary to all installations
  * Translation updates
  * Optionally allow hash algos not supported by the token
  * Select whether to translate established x509 terms
  * Finish Token EC and DSA support - generate, import, export, sign
  * SF Feat. Req. #57 More options for Distinguished Name
  * Switch to autoconf for the configure script
  * SF Feature Req. #76 Export private keys to clipboard
  * EC Keys: show Curve name in table
  * Support EC key generation on PKCS#11 token
  * PKCS#11: Make EC and RSA signatures work
  * PKCS#11: Fix reading EC keys from card
  * SF#xca#82 Certificate Creation out of Spec
  * SF#xca#95 XCA 1.0 only runs in French on a UK English Mac
- xca 1.0.0
  * SF#xca#89 Validating CRL distribution point results in error
  * SF Feature Req. #69 Create "Recent databases..." file menu item
  * SF#xca#75 authorityInfoAccess set error
  * SF#xca#88 Minor spelling error
  * SF#xca#87 Unable to set default key length The Key generation
    dialog now allows to remember the current settings
  * Do not interpret HTML tags in message boxes
  * Overwite extensions from the PKCS#10 request by local extensions
    This avoids duplication errors and allows to overwrite some
    extensions from the request
  * SF#xca#78 replace path separators in export filenames
  * SF Feature Req. #71 Add KDC Authentication OIDs to default files
  * SF#xca#82 Certificate Creation out of Spec
  * Add Croatian translation
  * SF#xca#83 Inappropriate gcc argument order in configure script
- update dependencies
  * qt &gt;= 4.6.0
- remove obsolete 0001-Fix-for-openssl-1.0.1i.patch
- replace xca-configure.patch with xca-linuxdoc.patch
- rebase xca-desktop.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1427803200">- update to 1.2.0
  * Update to OpenSSL 1.0.2a for Windows and MAC drop brainpool
    extra builds
  * Use CTRL +/- to change the font size in the view
  * Add Row numbering for easy item counting
  * Support SSH2 public key format for import and export
  * Add support for SHA-224
  * add "xca extract" to export items from the database on the
    commandline</changelog>
  <changelog author="ecsos@opensuse.org" date="1444996800">- update to 1.3.2
  * Gentoo Bug #562288 linking fails
  * Add OID resolver, move some Menu items to "Extra"
  * SF. Bug. #81 Make xca qt5 compatible
  * SF. Bug. #107 error:0D0680A8:asn1 encoding
  * Don't validate notBefore and notAfter if they are disabled.
- xca 1.3.1
  * Fix endless loop while searching for a signer of a CRL
- xca 1.3.0
  * Update to OpenSSL 1.0.2d for Windows and MAC
  * SF Bug #105 1.2.0 OS X Retina Display Support
  * Digitaly sign Windows and MAC binaries with a valid certificate
  * Refactor the context menu. Exporting many selected items
    to the clipboard or a PEM file now works. Certificate renewal
    and revocation may now be performed on a batch of certificates.
  * Feat. Reg. #83 Option to revoke old certificate when renewing
  * Refactor revocation handling. All revocation information is
    stored with the CA and may be modified.
    Revoked certificates may now be deleted from the database
  * Support nameConstraints, policyMappings, InhibitAnyPolicy,
    PolicyConstraint and (OSCP)noCheck when transforming
    certificates to templates or OpenSSL configs
  * Fix SF Bug #104 Export to template introduces spaces
  * Add option for disabling legacy Netscape extensions
  * Support exporting SSH2 public key to the clipboard
  * SF Bug #102 Weak entropy source used for key generation:
    Use /dev/random, mouse/kbd entropy, token RNG
  * SF Feat. Req. #80 Create new certificate,
    based on existing certificate, same for requests
  * Add Cert/Req Column for Signature Algorithm
  * SF Feat. Req. #81 Show key size in New Certificate dialog
  * Distinguish export from transform:
  - Export writes to an external file,
  - Transform generates another XCA item</changelog>
  <changelog author="chris@computersalat.de" date="1454068800">- fix Changelog
- fix deps
  * openssl-devel &gt;= 0.9.8
  * openssl &gt;= 0.9.8
- fix missing help files
- fix rpmlint
  * spurious-executable-perm /usr/share/man/man1/xca.1.gz
  * spurious-executable-perm /usr/share/man/man1/xca.1.gz
- add xca-doc_Makefile.patch</changelog>
  <changelog author="ro@suse.de" date="1512475200">- add xca-1.3.2-openssl11.patch to fix build on factory with
  openssl-1.1</changelog>
  <changelog author="chris@computersalat.de" date="1540900800">- update to 1.4.1
  * Replace links to XCA on Sourceforge in the software and
  * documentation by links to my Site.
  * SF Bug #122 isValid() tried to convert the serial to 64 bit
  * Beautify mandatory distinguished name entry errors
  * Support dragging certificates and other items as PEM text
  * Show User settings and installation path in the about dialog
  * Remove SPKAC support. Netscape is not of this world anymore.
  * SF bug #124 Wrong assumptions about slots returned by PKCS11 library
  * Cleanup and improve the OID text files, remove senseless aia.txt
  * Update HTML documentation
  * Refine and document Entropy gathering
  * Indicate development and release version by git commit hash
  * Fix dumping private keys during "Dump database"
  * Fix Null pointer exception when importing PKCS#12 with OpenSSL 1.1.0
  * SF Bug #110 Exported private key from 4096 bit SSH key is wrong
  * SF Bug #109 Revoked.png isn't a valid image
  * SF Bug #121 CA serial number is ignored in hierarchical view
  * Improve speed of Bulk import.
  * Fix starting xca with a database as first arg
- xca 1.4.0
  * Update OpenSSL version for MacOSX and W32 to 1.1.0g
  * Change default hash to SHA-256 and
  * add a warning if the default hash algorithm is SHA1 or less
  * Switch to Qt5 for Windows build and installation
  * Do not apply the default template when creating a similar cert
  * Close SF #120 Crash when importing CA certificate
  * Close SF #116 db_x509.cpp:521: Mismatching allocation and deallocation
  * Add support for OpenSSL 1.1 (by Patrick Monnerat)
  * Support generating an OpenSSL "index.txt" (by Adam Dawidowski)
  * Thales nCipher key generation changes for EC and DSA keys
  * Add Slovak translation
- remove obsolete
  * xca-1.3.2-openssl11.patch
  * xca-doc_Makefile.patch
- add xca-configure.patch
  * fix sgml2html command
- cleanup spec, fix deps</changelog>
  <changelog author="jengelh@inai.de" date="1540987200">- Fix grammar in %description -l de.
- Throw out old %__-type macro indirections and $RPM_ shell vars.</changelog>
  <changelog author="liedke@rz.uni-mannheim.de" date="1548158400">-Update to 2.1.2
  * Close #40 macOS: Crash after xca v2.0.1 quit
  * Close #37: XCA 2: EVP_DecryptFinal_ex:bad decrypt
  * Close #74: Exiting XCA 2.1.1 corrupts database
  * Make PKCS11 libs, working dir and main-window size host-dependent
  * Support for XCA as portable App
  * Close #69 Library not loaded: @rpath/ contains local directory
  * Close #60: Fix MacOSX 2.1.1 binary
  * Add new maintained languages: Polish, Spanish, Portuguese
-Update to 2.1.1
  * Allow manual override of the CSR signed flag
  * Close #56: Duplicate Serials after Upgrade 2.1.0
  * Close #57: SAN IP not working in 2.1.0
  * Close #55: Calculate "CSR signed" information from legacy database
  * Close #55: Add Certificate counter column for CSR
  * Fix slovak translation
  * Close #50: Hang while importing 1.4.1 database into 2.1.0
-Update to 2.1.0
  * Close #48: The SKI tickbox isn't generating an SKI extension for CSRs
  * Fix translation of dates
  * Add private key icon to the key name
  * Inspired by #42: display dates relative (seconds ago, yesterday, ...)
    while column ordering is still strict by age. The ToolTip shows date
    and time.
  * Related to #39: Dynamically adjust explicit DN entries
  * Close #39: Subject entries shuffled
  * Close #36: Support adding CN to X509v3 SAN automatically
  * Close #35: Configurable size of serial number.
  * Close #34: Improve Mac OSX installation
  * Close #27: Configurable certificate expiry warning threshold
  * Generate calender (.ics) files for certificate and CRL expiries
-Update to 2.0.1
  * Close #32: Version field contains "Created by Qt/QMake" on MacOSX
  * Review and update russian ltranslation
  * Close #31: Closing certificate details window toggles tree folding
  * Close #25: Certificates are no longer coloured
  * Close #24: Add LibreSSL support. Tested with LibreSSL 2.7.2
  * Close #23: Improve limiting to pattern in certificate tree view
  * Close #20: Unable to chose remote database type (dropdown empty)
  * Close #19: Replace 3DES encryption by AES-256 during key export
-Update to 2.0.0
  * Open database before starting a transaction
  * Fix default hash during startup
  * Fix Importing PKCS#12 and PKCS#7 files
  * Improve automatic setting of the certificate internal name
  * Don't use remote DB descriptor as local database filename proposal
  * Usability: Preset remote database input values with previous ones
  * Add another missing windows postgres library
  * xca 2.0.0-pre04 Thu Mar 22 2018
  * Accept drivers that don't support transactions
  * Install MySQL and PostgreSQL drivers on windows
  * Closes #10: Warn if certificate without any extension is created
  * Add table prefix to be prepended to each table for remote SQL DB
  * Update translations
  * xca 2.0.0-pre03 Thu Mar 15 2018
  * Fix installation of sql plugins in the Windows installer
  * Fix opening, importing and dropping databases
  * xca 2.0.0-pre02 Tue Mar 13 2018
  * Fix crash during PKCS#12 export
  * Update HTTPS_server template and add example SAN
  * Acceppt empty password for private key decryption
  * Fix legacy database-without-password import
  * xca 2.0.0-pre01 Sun Mar 11 2018
  * Close GitHub Bug #5: Exporting a private key results in too-permissive
    permissions
  * Close GitHub Bug #4: Workaround QT bug of editing in QDateTimeEdit
  * Fix display of dates in the Certificate details (local time displayed a GMT)
  * The internal name is not neccessarily unique anymore and can be edited
    in the details dialog as well as the comment.
  * CSR signing is now statically stored in the database and the comment of the
    issued certificate.
  * Private keys in the database are PKCS#8 encrypted and can be exported and
    decrypted without XCA.
  * No more incrementing serials. Only unique random serial numbers.
  * "xca_db_stat" application removed. Use the SQLite3 browser "sqlitebrowser".
  * "xca extract" functionality removed. SQL views may be used instead.
  * Each item may be commented. XCA itself comments important events in the item.
  * Each item knows its time and origin of appearance.
  * Change database format to SQL(ite) and support MySQL and PostgreSQL.</changelog>
  <changelog author="idonmez@suse.com" date="1549281600">- Cleanup spec file
- Use Qt5
- Refresh patches</changelog>
  <changelog author="mardnh@gmx.de" date="1579521600">- Run spec-cleaner</changelog>
  <changelog author="mardnh@gmx.de" date="1580299200">- Update to version 2.2.0
  * Most notable improvements:
    + Support concurrent database access
    + Support ODBC database driver
  A detailled changelog can be found here:
  http://hohnstaedt.de/xca/index.php/software/changelog</changelog>
  <changelog author="mardnh@gmx.de" date="1580385600">- Update to version 2.2.1
  * This is a patch release, fixing Issue #159: "Opening existing
    database" which prevented the current version opening databases
    of XCA 2.1.2</changelog>
  <changelog author="chris@computersalat.de" date="1595764800">- xca 2.3.0 Wed Apr 29 2020
  * Close #191 OID LN differs warning popups at startup
  * Close #189 Database compaction #189
  * Improve PKCS11 library loading for portable app
  * Refactor native separators / and \ on windows.
  * Support TLS encrypted MariaDB and PostgreSQL connection
  * Close #182: UI not using Windows native theme in 2.2.1 portable
  * Close #70: cant open ics file in ical on macos mojave
  * Close #72: Add checkbox for OCSP staple feature
  * Use DESTDIR instead of destdir when installing. Follows autotools convention.
  * Close #172 #46: Multiple OCSP Responders
  * Close #170 xca-portable-2.2.1 cannot change language
  * Fix certificate assignment when importing a CA certificate
  * Close #163: Show key type/size on column of Certificates tab
- rebase patches</changelog>
  <changelog author="mardnh@gmx.de" date="1620907200">- Update to version 2.4.0
  * Unify XCA icon (certificate) on all platforms
  * Add Microsoft BitLocker extended key usage
  * Disregard OpenSSL 0.9.8 compatibility
  * Add bash completion script
  * Add context sensitive help
  * Convert documentation from linuxdoc/SGML to sphinxdoc
  * Close #258: xca aborts on exit and on access to own templates
  * Close #142: Support Ed25519 Import / Export private SSH2 key
  * Close #142: Support Ed25519: Key-generation, import, export
  * Close #251: AuthorityKeyIdentifier: use issuer:always
  * Change language maintainer of brazilian portuguese
  * Close #230: Change PKCS12 export extension from .p12 to .pfx
  * Close #208: XCA hung when importing EC keys. For example prime256v1
  * Close #210: Make dialog to edit SAN less strict
  * Close #224: Store original path/filename on import
  * Close #213: configure.ac: add description to AC_DEFINE_UNQUOTED
  * Close #172 #46: Multiple OCSP Responders
  * Store default database and recently opened file as UTF8
  * Close #157 Generate and export CRLs from commandline
  * Add command line support for creating CRLs, keys and analyzing items
- Drop patch:
  * xca-configure.patch (not longer needed)</changelog>
  <changelog author="ro@suse.de" date="1676894400">- change buildrequires for openssl on factory to use openssl-1.1
  openSSL 3 is not supported in xca-2.4.0 yet</changelog>
</package>
<package pkgid="2791d29efcd15eaaca4e3dca889d3d7faef2165a13914f1aee2f8419341d813b" name="xca" arch="x86_64">
  <version epoch="0" ver="2.4.0" rel="17.1"/>
  <changelog author="chris@computersalat.de" date="1417089600">- update to 1.1.0
  * SF#xca#79 Template export from WinXP cannot be imported in Linux
    and Mac OS X
  * Support for Brainpool windows and MacOSX binaries
  * SF Feat. Req. #70 ability to search certificates
  * SF Feat. Req. #75 show SHA-256 digest
  * RedHat Bug #1164340 - segfault when viewing a RHEL entitlement
    certificate
  * Database hardening
  * Delete invalid items (on demand)
  * Be more tolerant against database errors
  * Gracefully handle and repair corrupt databases
  * Add "xca_db_stat(.exe)" binary to all installations
  * Translation updates
  * Optionally allow hash algos not supported by the token
  * Select whether to translate established x509 terms
  * Finish Token EC and DSA support - generate, import, export, sign
  * SF Feat. Req. #57 More options for Distinguished Name
  * Switch to autoconf for the configure script
  * SF Feature Req. #76 Export private keys to clipboard
  * EC Keys: show Curve name in table
  * Support EC key generation on PKCS#11 token
  * PKCS#11: Make EC and RSA signatures work
  * PKCS#11: Fix reading EC keys from card
  * SF#xca#82 Certificate Creation out of Spec
  * SF#xca#95 XCA 1.0 only runs in French on a UK English Mac
- xca 1.0.0
  * SF#xca#89 Validating CRL distribution point results in error
  * SF Feature Req. #69 Create "Recent databases..." file menu item
  * SF#xca#75 authorityInfoAccess set error
  * SF#xca#88 Minor spelling error
  * SF#xca#87 Unable to set default key length The Key generation
    dialog now allows to remember the current settings
  * Do not interpret HTML tags in message boxes
  * Overwite extensions from the PKCS#10 request by local extensions
    This avoids duplication errors and allows to overwrite some
    extensions from the request
  * SF#xca#78 replace path separators in export filenames
  * SF Feature Req. #71 Add KDC Authentication OIDs to default files
  * SF#xca#82 Certificate Creation out of Spec
  * Add Croatian translation
  * SF#xca#83 Inappropriate gcc argument order in configure script
- update dependencies
  * qt &gt;= 4.6.0
- remove obsolete 0001-Fix-for-openssl-1.0.1i.patch
- replace xca-configure.patch with xca-linuxdoc.patch
- rebase xca-desktop.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1427803200">- update to 1.2.0
  * Update to OpenSSL 1.0.2a for Windows and MAC drop brainpool
    extra builds
  * Use CTRL +/- to change the font size in the view
  * Add Row numbering for easy item counting
  * Support SSH2 public key format for import and export
  * Add support for SHA-224
  * add "xca extract" to export items from the database on the
    commandline</changelog>
  <changelog author="ecsos@opensuse.org" date="1444996800">- update to 1.3.2
  * Gentoo Bug #562288 linking fails
  * Add OID resolver, move some Menu items to "Extra"
  * SF. Bug. #81 Make xca qt5 compatible
  * SF. Bug. #107 error:0D0680A8:asn1 encoding
  * Don't validate notBefore and notAfter if they are disabled.
- xca 1.3.1
  * Fix endless loop while searching for a signer of a CRL
- xca 1.3.0
  * Update to OpenSSL 1.0.2d for Windows and MAC
  * SF Bug #105 1.2.0 OS X Retina Display Support
  * Digitaly sign Windows and MAC binaries with a valid certificate
  * Refactor the context menu. Exporting many selected items
    to the clipboard or a PEM file now works. Certificate renewal
    and revocation may now be performed on a batch of certificates.
  * Feat. Reg. #83 Option to revoke old certificate when renewing
  * Refactor revocation handling. All revocation information is
    stored with the CA and may be modified.
    Revoked certificates may now be deleted from the database
  * Support nameConstraints, policyMappings, InhibitAnyPolicy,
    PolicyConstraint and (OSCP)noCheck when transforming
    certificates to templates or OpenSSL configs
  * Fix SF Bug #104 Export to template introduces spaces
  * Add option for disabling legacy Netscape extensions
  * Support exporting SSH2 public key to the clipboard
  * SF Bug #102 Weak entropy source used for key generation:
    Use /dev/random, mouse/kbd entropy, token RNG
  * SF Feat. Req. #80 Create new certificate,
    based on existing certificate, same for requests
  * Add Cert/Req Column for Signature Algorithm
  * SF Feat. Req. #81 Show key size in New Certificate dialog
  * Distinguish export from transform:
  - Export writes to an external file,
  - Transform generates another XCA item</changelog>
  <changelog author="chris@computersalat.de" date="1454068800">- fix Changelog
- fix deps
  * openssl-devel &gt;= 0.9.8
  * openssl &gt;= 0.9.8
- fix missing help files
- fix rpmlint
  * spurious-executable-perm /usr/share/man/man1/xca.1.gz
  * spurious-executable-perm /usr/share/man/man1/xca.1.gz
- add xca-doc_Makefile.patch</changelog>
  <changelog author="ro@suse.de" date="1512475200">- add xca-1.3.2-openssl11.patch to fix build on factory with
  openssl-1.1</changelog>
  <changelog author="chris@computersalat.de" date="1540900800">- update to 1.4.1
  * Replace links to XCA on Sourceforge in the software and
  * documentation by links to my Site.
  * SF Bug #122 isValid() tried to convert the serial to 64 bit
  * Beautify mandatory distinguished name entry errors
  * Support dragging certificates and other items as PEM text
  * Show User settings and installation path in the about dialog
  * Remove SPKAC support. Netscape is not of this world anymore.
  * SF bug #124 Wrong assumptions about slots returned by PKCS11 library
  * Cleanup and improve the OID text files, remove senseless aia.txt
  * Update HTML documentation
  * Refine and document Entropy gathering
  * Indicate development and release version by git commit hash
  * Fix dumping private keys during "Dump database"
  * Fix Null pointer exception when importing PKCS#12 with OpenSSL 1.1.0
  * SF Bug #110 Exported private key from 4096 bit SSH key is wrong
  * SF Bug #109 Revoked.png isn't a valid image
  * SF Bug #121 CA serial number is ignored in hierarchical view
  * Improve speed of Bulk import.
  * Fix starting xca with a database as first arg
- xca 1.4.0
  * Update OpenSSL version for MacOSX and W32 to 1.1.0g
  * Change default hash to SHA-256 and
  * add a warning if the default hash algorithm is SHA1 or less
  * Switch to Qt5 for Windows build and installation
  * Do not apply the default template when creating a similar cert
  * Close SF #120 Crash when importing CA certificate
  * Close SF #116 db_x509.cpp:521: Mismatching allocation and deallocation
  * Add support for OpenSSL 1.1 (by Patrick Monnerat)
  * Support generating an OpenSSL "index.txt" (by Adam Dawidowski)
  * Thales nCipher key generation changes for EC and DSA keys
  * Add Slovak translation
- remove obsolete
  * xca-1.3.2-openssl11.patch
  * xca-doc_Makefile.patch
- add xca-configure.patch
  * fix sgml2html command
- cleanup spec, fix deps</changelog>
  <changelog author="jengelh@inai.de" date="1540987200">- Fix grammar in %description -l de.
- Throw out old %__-type macro indirections and $RPM_ shell vars.</changelog>
  <changelog author="liedke@rz.uni-mannheim.de" date="1548158400">-Update to 2.1.2
  * Close #40 macOS: Crash after xca v2.0.1 quit
  * Close #37: XCA 2: EVP_DecryptFinal_ex:bad decrypt
  * Close #74: Exiting XCA 2.1.1 corrupts database
  * Make PKCS11 libs, working dir and main-window size host-dependent
  * Support for XCA as portable App
  * Close #69 Library not loaded: @rpath/ contains local directory
  * Close #60: Fix MacOSX 2.1.1 binary
  * Add new maintained languages: Polish, Spanish, Portuguese
-Update to 2.1.1
  * Allow manual override of the CSR signed flag
  * Close #56: Duplicate Serials after Upgrade 2.1.0
  * Close #57: SAN IP not working in 2.1.0
  * Close #55: Calculate "CSR signed" information from legacy database
  * Close #55: Add Certificate counter column for CSR
  * Fix slovak translation
  * Close #50: Hang while importing 1.4.1 database into 2.1.0
-Update to 2.1.0
  * Close #48: The SKI tickbox isn't generating an SKI extension for CSRs
  * Fix translation of dates
  * Add private key icon to the key name
  * Inspired by #42: display dates relative (seconds ago, yesterday, ...)
    while column ordering is still strict by age. The ToolTip shows date
    and time.
  * Related to #39: Dynamically adjust explicit DN entries
  * Close #39: Subject entries shuffled
  * Close #36: Support adding CN to X509v3 SAN automatically
  * Close #35: Configurable size of serial number.
  * Close #34: Improve Mac OSX installation
  * Close #27: Configurable certificate expiry warning threshold
  * Generate calender (.ics) files for certificate and CRL expiries
-Update to 2.0.1
  * Close #32: Version field contains "Created by Qt/QMake" on MacOSX
  * Review and update russian ltranslation
  * Close #31: Closing certificate details window toggles tree folding
  * Close #25: Certificates are no longer coloured
  * Close #24: Add LibreSSL support. Tested with LibreSSL 2.7.2
  * Close #23: Improve limiting to pattern in certificate tree view
  * Close #20: Unable to chose remote database type (dropdown empty)
  * Close #19: Replace 3DES encryption by AES-256 during key export
-Update to 2.0.0
  * Open database before starting a transaction
  * Fix default hash during startup
  * Fix Importing PKCS#12 and PKCS#7 files
  * Improve automatic setting of the certificate internal name
  * Don't use remote DB descriptor as local database filename proposal
  * Usability: Preset remote database input values with previous ones
  * Add another missing windows postgres library
  * xca 2.0.0-pre04 Thu Mar 22 2018
  * Accept drivers that don't support transactions
  * Install MySQL and PostgreSQL drivers on windows
  * Closes #10: Warn if certificate without any extension is created
  * Add table prefix to be prepended to each table for remote SQL DB
  * Update translations
  * xca 2.0.0-pre03 Thu Mar 15 2018
  * Fix installation of sql plugins in the Windows installer
  * Fix opening, importing and dropping databases
  * xca 2.0.0-pre02 Tue Mar 13 2018
  * Fix crash during PKCS#12 export
  * Update HTTPS_server template and add example SAN
  * Acceppt empty password for private key decryption
  * Fix legacy database-without-password import
  * xca 2.0.0-pre01 Sun Mar 11 2018
  * Close GitHub Bug #5: Exporting a private key results in too-permissive
    permissions
  * Close GitHub Bug #4: Workaround QT bug of editing in QDateTimeEdit
  * Fix display of dates in the Certificate details (local time displayed a GMT)
  * The internal name is not neccessarily unique anymore and can be edited
    in the details dialog as well as the comment.
  * CSR signing is now statically stored in the database and the comment of the
    issued certificate.
  * Private keys in the database are PKCS#8 encrypted and can be exported and
    decrypted without XCA.
  * No more incrementing serials. Only unique random serial numbers.
  * "xca_db_stat" application removed. Use the SQLite3 browser "sqlitebrowser".
  * "xca extract" functionality removed. SQL views may be used instead.
  * Each item may be commented. XCA itself comments important events in the item.
  * Each item knows its time and origin of appearance.
  * Change database format to SQL(ite) and support MySQL and PostgreSQL.</changelog>
  <changelog author="idonmez@suse.com" date="1549281600">- Cleanup spec file
- Use Qt5
- Refresh patches</changelog>
  <changelog author="mardnh@gmx.de" date="1579521600">- Run spec-cleaner</changelog>
  <changelog author="mardnh@gmx.de" date="1580299200">- Update to version 2.2.0
  * Most notable improvements:
    + Support concurrent database access
    + Support ODBC database driver
  A detailled changelog can be found here:
  http://hohnstaedt.de/xca/index.php/software/changelog</changelog>
  <changelog author="mardnh@gmx.de" date="1580385600">- Update to version 2.2.1
  * This is a patch release, fixing Issue #159: "Opening existing
    database" which prevented the current version opening databases
    of XCA 2.1.2</changelog>
  <changelog author="chris@computersalat.de" date="1595764800">- xca 2.3.0 Wed Apr 29 2020
  * Close #191 OID LN differs warning popups at startup
  * Close #189 Database compaction #189
  * Improve PKCS11 library loading for portable app
  * Refactor native separators / and \ on windows.
  * Support TLS encrypted MariaDB and PostgreSQL connection
  * Close #182: UI not using Windows native theme in 2.2.1 portable
  * Close #70: cant open ics file in ical on macos mojave
  * Close #72: Add checkbox for OCSP staple feature
  * Use DESTDIR instead of destdir when installing. Follows autotools convention.
  * Close #172 #46: Multiple OCSP Responders
  * Close #170 xca-portable-2.2.1 cannot change language
  * Fix certificate assignment when importing a CA certificate
  * Close #163: Show key type/size on column of Certificates tab
- rebase patches</changelog>
  <changelog author="mardnh@gmx.de" date="1620907200">- Update to version 2.4.0
  * Unify XCA icon (certificate) on all platforms
  * Add Microsoft BitLocker extended key usage
  * Disregard OpenSSL 0.9.8 compatibility
  * Add bash completion script
  * Add context sensitive help
  * Convert documentation from linuxdoc/SGML to sphinxdoc
  * Close #258: xca aborts on exit and on access to own templates
  * Close #142: Support Ed25519 Import / Export private SSH2 key
  * Close #142: Support Ed25519: Key-generation, import, export
  * Close #251: AuthorityKeyIdentifier: use issuer:always
  * Change language maintainer of brazilian portuguese
  * Close #230: Change PKCS12 export extension from .p12 to .pfx
  * Close #208: XCA hung when importing EC keys. For example prime256v1
  * Close #210: Make dialog to edit SAN less strict
  * Close #224: Store original path/filename on import
  * Close #213: configure.ac: add description to AC_DEFINE_UNQUOTED
  * Close #172 #46: Multiple OCSP Responders
  * Store default database and recently opened file as UTF8
  * Close #157 Generate and export CRLs from commandline
  * Add command line support for creating CRLs, keys and analyzing items
- Drop patch:
  * xca-configure.patch (not longer needed)</changelog>
  <changelog author="ro@suse.de" date="1676894400">- change buildrequires for openssl on factory to use openssl-1.1
  openSSL 3 is not supported in xca-2.4.0 yet</changelog>
</package>
<package pkgid="3c89f57688f42f40683094b5ca14feb6cc5cceb1b58b55feac95c07bf971a0ec" name="xca-bash-completion" arch="noarch">
  <version epoch="0" ver="2.4.0" rel="17.1"/>
  <changelog author="chris@computersalat.de" date="1417089600">- update to 1.1.0
  * SF#xca#79 Template export from WinXP cannot be imported in Linux
    and Mac OS X
  * Support for Brainpool windows and MacOSX binaries
  * SF Feat. Req. #70 ability to search certificates
  * SF Feat. Req. #75 show SHA-256 digest
  * RedHat Bug #1164340 - segfault when viewing a RHEL entitlement
    certificate
  * Database hardening
  * Delete invalid items (on demand)
  * Be more tolerant against database errors
  * Gracefully handle and repair corrupt databases
  * Add "xca_db_stat(.exe)" binary to all installations
  * Translation updates
  * Optionally allow hash algos not supported by the token
  * Select whether to translate established x509 terms
  * Finish Token EC and DSA support - generate, import, export, sign
  * SF Feat. Req. #57 More options for Distinguished Name
  * Switch to autoconf for the configure script
  * SF Feature Req. #76 Export private keys to clipboard
  * EC Keys: show Curve name in table
  * Support EC key generation on PKCS#11 token
  * PKCS#11: Make EC and RSA signatures work
  * PKCS#11: Fix reading EC keys from card
  * SF#xca#82 Certificate Creation out of Spec
  * SF#xca#95 XCA 1.0 only runs in French on a UK English Mac
- xca 1.0.0
  * SF#xca#89 Validating CRL distribution point results in error
  * SF Feature Req. #69 Create "Recent databases..." file menu item
  * SF#xca#75 authorityInfoAccess set error
  * SF#xca#88 Minor spelling error
  * SF#xca#87 Unable to set default key length The Key generation
    dialog now allows to remember the current settings
  * Do not interpret HTML tags in message boxes
  * Overwite extensions from the PKCS#10 request by local extensions
    This avoids duplication errors and allows to overwrite some
    extensions from the request
  * SF#xca#78 replace path separators in export filenames
  * SF Feature Req. #71 Add KDC Authentication OIDs to default files
  * SF#xca#82 Certificate Creation out of Spec
  * Add Croatian translation
  * SF#xca#83 Inappropriate gcc argument order in configure script
- update dependencies
  * qt &gt;= 4.6.0
- remove obsolete 0001-Fix-for-openssl-1.0.1i.patch
- replace xca-configure.patch with xca-linuxdoc.patch
- rebase xca-desktop.patch</changelog>
  <changelog author="ecsos@opensuse.org" date="1427803200">- update to 1.2.0
  * Update to OpenSSL 1.0.2a for Windows and MAC drop brainpool
    extra builds
  * Use CTRL +/- to change the font size in the view
  * Add Row numbering for easy item counting
  * Support SSH2 public key format for import and export
  * Add support for SHA-224
  * add "xca extract" to export items from the database on the
    commandline</changelog>
  <changelog author="ecsos@opensuse.org" date="1444996800">- update to 1.3.2
  * Gentoo Bug #562288 linking fails
  * Add OID resolver, move some Menu items to "Extra"
  * SF. Bug. #81 Make xca qt5 compatible
  * SF. Bug. #107 error:0D0680A8:asn1 encoding
  * Don't validate notBefore and notAfter if they are disabled.
- xca 1.3.1
  * Fix endless loop while searching for a signer of a CRL
- xca 1.3.0
  * Update to OpenSSL 1.0.2d for Windows and MAC
  * SF Bug #105 1.2.0 OS X Retina Display Support
  * Digitaly sign Windows and MAC binaries with a valid certificate
  * Refactor the context menu. Exporting many selected items
    to the clipboard or a PEM file now works. Certificate renewal
    and revocation may now be performed on a batch of certificates.
  * Feat. Reg. #83 Option to revoke old certificate when renewing
  * Refactor revocation handling. All revocation information is
    stored with the CA and may be modified.
    Revoked certificates may now be deleted from the database
  * Support nameConstraints, policyMappings, InhibitAnyPolicy,
    PolicyConstraint and (OSCP)noCheck when transforming
    certificates to templates or OpenSSL configs
  * Fix SF Bug #104 Export to template introduces spaces
  * Add option for disabling legacy Netscape extensions
  * Support exporting SSH2 public key to the clipboard
  * SF Bug #102 Weak entropy source used for key generation:
    Use /dev/random, mouse/kbd entropy, token RNG
  * SF Feat. Req. #80 Create new certificate,
    based on existing certificate, same for requests
  * Add Cert/Req Column for Signature Algorithm
  * SF Feat. Req. #81 Show key size in New Certificate dialog
  * Distinguish export from transform:
  - Export writes to an external file,
  - Transform generates another XCA item</changelog>
  <changelog author="chris@computersalat.de" date="1454068800">- fix Changelog
- fix deps
  * openssl-devel &gt;= 0.9.8
  * openssl &gt;= 0.9.8
- fix missing help files
- fix rpmlint
  * spurious-executable-perm /usr/share/man/man1/xca.1.gz
  * spurious-executable-perm /usr/share/man/man1/xca.1.gz
- add xca-doc_Makefile.patch</changelog>
  <changelog author="ro@suse.de" date="1512475200">- add xca-1.3.2-openssl11.patch to fix build on factory with
  openssl-1.1</changelog>
  <changelog author="chris@computersalat.de" date="1540900800">- update to 1.4.1
  * Replace links to XCA on Sourceforge in the software and
  * documentation by links to my Site.
  * SF Bug #122 isValid() tried to convert the serial to 64 bit
  * Beautify mandatory distinguished name entry errors
  * Support dragging certificates and other items as PEM text
  * Show User settings and installation path in the about dialog
  * Remove SPKAC support. Netscape is not of this world anymore.
  * SF bug #124 Wrong assumptions about slots returned by PKCS11 library
  * Cleanup and improve the OID text files, remove senseless aia.txt
  * Update HTML documentation
  * Refine and document Entropy gathering
  * Indicate development and release version by git commit hash
  * Fix dumping private keys during "Dump database"
  * Fix Null pointer exception when importing PKCS#12 with OpenSSL 1.1.0
  * SF Bug #110 Exported private key from 4096 bit SSH key is wrong
  * SF Bug #109 Revoked.png isn't a valid image
  * SF Bug #121 CA serial number is ignored in hierarchical view
  * Improve speed of Bulk import.
  * Fix starting xca with a database as first arg
- xca 1.4.0
  * Update OpenSSL version for MacOSX and W32 to 1.1.0g
  * Change default hash to SHA-256 and
  * add a warning if the default hash algorithm is SHA1 or less
  * Switch to Qt5 for Windows build and installation
  * Do not apply the default template when creating a similar cert
  * Close SF #120 Crash when importing CA certificate
  * Close SF #116 db_x509.cpp:521: Mismatching allocation and deallocation
  * Add support for OpenSSL 1.1 (by Patrick Monnerat)
  * Support generating an OpenSSL "index.txt" (by Adam Dawidowski)
  * Thales nCipher key generation changes for EC and DSA keys
  * Add Slovak translation
- remove obsolete
  * xca-1.3.2-openssl11.patch
  * xca-doc_Makefile.patch
- add xca-configure.patch
  * fix sgml2html command
- cleanup spec, fix deps</changelog>
  <changelog author="jengelh@inai.de" date="1540987200">- Fix grammar in %description -l de.
- Throw out old %__-type macro indirections and $RPM_ shell vars.</changelog>
  <changelog author="liedke@rz.uni-mannheim.de" date="1548158400">-Update to 2.1.2
  * Close #40 macOS: Crash after xca v2.0.1 quit
  * Close #37: XCA 2: EVP_DecryptFinal_ex:bad decrypt
  * Close #74: Exiting XCA 2.1.1 corrupts database
  * Make PKCS11 libs, working dir and main-window size host-dependent
  * Support for XCA as portable App
  * Close #69 Library not loaded: @rpath/ contains local directory
  * Close #60: Fix MacOSX 2.1.1 binary
  * Add new maintained languages: Polish, Spanish, Portuguese
-Update to 2.1.1
  * Allow manual override of the CSR signed flag
  * Close #56: Duplicate Serials after Upgrade 2.1.0
  * Close #57: SAN IP not working in 2.1.0
  * Close #55: Calculate "CSR signed" information from legacy database
  * Close #55: Add Certificate counter column for CSR
  * Fix slovak translation
  * Close #50: Hang while importing 1.4.1 database into 2.1.0
-Update to 2.1.0
  * Close #48: The SKI tickbox isn't generating an SKI extension for CSRs
  * Fix translation of dates
  * Add private key icon to the key name
  * Inspired by #42: display dates relative (seconds ago, yesterday, ...)
    while column ordering is still strict by age. The ToolTip shows date
    and time.
  * Related to #39: Dynamically adjust explicit DN entries
  * Close #39: Subject entries shuffled
  * Close #36: Support adding CN to X509v3 SAN automatically
  * Close #35: Configurable size of serial number.
  * Close #34: Improve Mac OSX installation
  * Close #27: Configurable certificate expiry warning threshold
  * Generate calender (.ics) files for certificate and CRL expiries
-Update to 2.0.1
  * Close #32: Version field contains "Created by Qt/QMake" on MacOSX
  * Review and update russian ltranslation
  * Close #31: Closing certificate details window toggles tree folding
  * Close #25: Certificates are no longer coloured
  * Close #24: Add LibreSSL support. Tested with LibreSSL 2.7.2
  * Close #23: Improve limiting to pattern in certificate tree view
  * Close #20: Unable to chose remote database type (dropdown empty)
  * Close #19: Replace 3DES encryption by AES-256 during key export
-Update to 2.0.0
  * Open database before starting a transaction
  * Fix default hash during startup
  * Fix Importing PKCS#12 and PKCS#7 files
  * Improve automatic setting of the certificate internal name
  * Don't use remote DB descriptor as local database filename proposal
  * Usability: Preset remote database input values with previous ones
  * Add another missing windows postgres library
  * xca 2.0.0-pre04 Thu Mar 22 2018
  * Accept drivers that don't support transactions
  * Install MySQL and PostgreSQL drivers on windows
  * Closes #10: Warn if certificate without any extension is created
  * Add table prefix to be prepended to each table for remote SQL DB
  * Update translations
  * xca 2.0.0-pre03 Thu Mar 15 2018
  * Fix installation of sql plugins in the Windows installer
  * Fix opening, importing and dropping databases
  * xca 2.0.0-pre02 Tue Mar 13 2018
  * Fix crash during PKCS#12 export
  * Update HTTPS_server template and add example SAN
  * Acceppt empty password for private key decryption
  * Fix legacy database-without-password import
  * xca 2.0.0-pre01 Sun Mar 11 2018
  * Close GitHub Bug #5: Exporting a private key results in too-permissive
    permissions
  * Close GitHub Bug #4: Workaround QT bug of editing in QDateTimeEdit
  * Fix display of dates in the Certificate details (local time displayed a GMT)
  * The internal name is not neccessarily unique anymore and can be edited
    in the details dialog as well as the comment.
  * CSR signing is now statically stored in the database and the comment of the
    issued certificate.
  * Private keys in the database are PKCS#8 encrypted and can be exported and
    decrypted without XCA.
  * No more incrementing serials. Only unique random serial numbers.
  * "xca_db_stat" application removed. Use the SQLite3 browser "sqlitebrowser".
  * "xca extract" functionality removed. SQL views may be used instead.
  * Each item may be commented. XCA itself comments important events in the item.
  * Each item knows its time and origin of appearance.
  * Change database format to SQL(ite) and support MySQL and PostgreSQL.</changelog>
  <changelog author="idonmez@suse.com" date="1549281600">- Cleanup spec file
- Use Qt5
- Refresh patches</changelog>
  <changelog author="mardnh@gmx.de" date="1579521600">- Run spec-cleaner</changelog>
  <changelog author="mardnh@gmx.de" date="1580299200">- Update to version 2.2.0
  * Most notable improvements:
    + Support concurrent database access
    + Support ODBC database driver
  A detailled changelog can be found here:
  http://hohnstaedt.de/xca/index.php/software/changelog</changelog>
  <changelog author="mardnh@gmx.de" date="1580385600">- Update to version 2.2.1
  * This is a patch release, fixing Issue #159: "Opening existing
    database" which prevented the current version opening databases
    of XCA 2.1.2</changelog>
  <changelog author="chris@computersalat.de" date="1595764800">- xca 2.3.0 Wed Apr 29 2020
  * Close #191 OID LN differs warning popups at startup
  * Close #189 Database compaction #189
  * Improve PKCS11 library loading for portable app
  * Refactor native separators / and \ on windows.
  * Support TLS encrypted MariaDB and PostgreSQL connection
  * Close #182: UI not using Windows native theme in 2.2.1 portable
  * Close #70: cant open ics file in ical on macos mojave
  * Close #72: Add checkbox for OCSP staple feature
  * Use DESTDIR instead of destdir when installing. Follows autotools convention.
  * Close #172 #46: Multiple OCSP Responders
  * Close #170 xca-portable-2.2.1 cannot change language
  * Fix certificate assignment when importing a CA certificate
  * Close #163: Show key type/size on column of Certificates tab
- rebase patches</changelog>
  <changelog author="mardnh@gmx.de" date="1620907200">- Update to version 2.4.0
  * Unify XCA icon (certificate) on all platforms
  * Add Microsoft BitLocker extended key usage
  * Disregard OpenSSL 0.9.8 compatibility
  * Add bash completion script
  * Add context sensitive help
  * Convert documentation from linuxdoc/SGML to sphinxdoc
  * Close #258: xca aborts on exit and on access to own templates
  * Close #142: Support Ed25519 Import / Export private SSH2 key
  * Close #142: Support Ed25519: Key-generation, import, export
  * Close #251: AuthorityKeyIdentifier: use issuer:always
  * Change language maintainer of brazilian portuguese
  * Close #230: Change PKCS12 export extension from .p12 to .pfx
  * Close #208: XCA hung when importing EC keys. For example prime256v1
  * Close #210: Make dialog to edit SAN less strict
  * Close #224: Store original path/filename on import
  * Close #213: configure.ac: add description to AC_DEFINE_UNQUOTED
  * Close #172 #46: Multiple OCSP Responders
  * Store default database and recently opened file as UTF8
  * Close #157 Generate and export CRLs from commandline
  * Add command line support for creating CRLs, keys and analyzing items
- Drop patch:
  * xca-configure.patch (not longer needed)</changelog>
  <changelog author="ro@suse.de" date="1676894400">- change buildrequires for openssl on factory to use openssl-1.1
  openSSL 3 is not supported in xca-2.4.0 yet</changelog>
</package>
</otherdata>