HWMonitor 歷史版本列表
更新時間：2021-02-04
更新細節：
What's new in this version:
Notable changes:
- 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 for use with ClamD, 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 and 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.
Bug-fixes:
- 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 or CL_TYPE_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:
- File descriptor passing (or "FD-passing") is a mechanism by which ClamOnAcc and ClamDScan may transfer an open file to ClamD to scan, even if ClamD is running as a non-privileged user and wouldn't otherwise have read-access to the file. This enables ClamD to scan all files without having to run ClamD as root. If possible, ClamD should never be run as root to mitigate the risk in case ClamD is somehow compromised while scanning malware.
- 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. Patch courtesy of Emilio Pozuelo Monfort.
- 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's --on-update-execute=EXIT_1 temporary directory cleanup issue
- ClamD's log output and VirusEvent feature 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 the 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.
- Fixed scan speed performance issues accidentally introduced in ClamAV 0.103.0 caused by hashing file maps more than once when parsing a file as a new type, and caused by frequent scanning of non-HTML text data with the HTML parser.
Other improvements:
- Scanning JPEG, TIFF, PNG and GIF files will no longer return "parse" errors when file format validation fails. Instead, the scan will alert with the "Heuristics.Broken.Media" signature prefix and a descriptive suffix to indicate the issue, provided that the "alert broken media" feature is enabled.
- GIF format validation will no longer fail if the GIF image is missing the trailer byte, as this appears to be a relatively common issue in otherwise functional GIFs
- Added a TIFF dynamic configuration (DCONF) option that was missing. This will allow us to disable TIFF format validation via signature database update in the event that it proves to be problematic. This feature already exists for many other file types.
Acknowledgments:
- The ClamAV team thanks Emilio Pozuelo Monfort for their code submissions
更新時間：2021-02-03
更新細節：
What's new in this version:
- Enhancement: "Safe save" and backups: when saving files, the file is only overwritten after the save terminated successfully. This will avoid loss of data for full volumes or network share dropouts. In addition, a configurable number of back files can be kept (see File/Setup: Application/General).
Fixed:
- GDS export issue fixed (breaking of polygons was filling holes)
- LVS compare enters infinite loop when it encounters two entirely identical subcircuits
- Qt binding: missing support for binary strings as QByteArray representative
- QJsonValue's string constructor is ambiguous
- Rational Splines not supported DXF
- MAGIC files won't find subcells when reading from command line
- HTTP stream reading issue with redirect At least on MacOS a segfault happened when reading HTTP stream data (e.g. for package manager) from addresses which are redirected.
- Enhancement: Removed %APPDATA% from DLL search path on Windows This will avoid installation poisoning by the one from %APPDATA% (which ironically is the default installation path). Eventually multiple versions can be used in parallel.
更新時間：2021-01-08
更新細節：
What's new in this version:
New features:
- The install4j GUI and compiler now run natively on ARM macOS (Apple M1)
- Code signing: Added support for AES256 encrypted PKCS12 key files
- JetBrains JDK provider: macos-aarch64 platform can now be used and notarized
Bugs fixed:
- Fixed notarization for Zulu Java 11 macos-aarch64 builds
- Older Java 11 and 8 releases were not shown for the AdoptOpenJDK JDK provider
- JetBrains JDK provider: Releases were not sorted correctly in the selection dialog
- Regression in 8.0.9: Under some circumstances, scripts and multi-line strings were not saved after closing the editor.
- Calling ApplicationInfo.getInstallerVariable() always returned variables for the first project it was used on
更新時間：2020-12-01
更新細節：
更新時間：2020-11-29
更新細節：
What's new in this version:
- Bugfix: #685 A potential crash was fixed happening when a PCell library is deleted
- Bugfix: #658 Menu items were not put into the right place on MacOS
- Bugfix: #652 "M" factor scaling was not working for Spice reader
- Bugfix: #651 Fixed an issue with DRC "select"
- Bugfix: #647 Text orientation was not considered properly in search & replace
- Bugfix: Display bug Cell placements with small magnification factors (such that the viewport dimensions exceeded the DBU space when seem from inside the cell) lead to display errors
更新時間：2020-11-26
更新細節：
What's new in this version:
New:
- Support for ARM macOS (Apple M1). The desired architecture (x64 or arm64) can be chosen in the media wizard
- Added a "Custom fragment for Info.plist" property for installer applications
API changes:
- Added FormEnvironment#scrollComponentToVisible(FormComponent) to scroll the form panel to the specified form component
Fixed:
- "Installation type" screen and "Installation components selector" form component: If descriptions were expanded initially, the layout of the description could be broken
- "Default execution mode" property of installer applications: Compiler variables were not replaced.
- "Create program group" action: Modified settings could get lost when saving while the program group entries tab was visible
- "Install a service" action: On Unix, if systemd is not used and the link in /etc/init.d could not be created, the action did not fail
- "Console handler" form component: When hitting CTRL-D, instead of cancelling during a terminal prompt, an exception was printed and the installer application continued
- "Require installer privileges" action: Wrong failure message was displayed in the uninstaller (Regression in 8.0.8)
- Fixed layout of form components that are made visible and are not within the displayed viewport
- Dissolving a bean group did not mark the project as modified
- Changing a variable in the dialog for pre-defined installer variables did not mark the project as modified
- Regression: Changes in coupled form components would no longer be saved
- When using the dialog to insert a form component ID, the saved form components instead of the current form components were used
- When cancelling installer applications with CTRL-C in console mode while input was read from the console, execution continued for a short time in some cases
- In generated install4j launchers, runtime messages were always in English and not in the auto-detected locale
- When the installer icon was customized and no cross-platform images or ICNS file was specified, the fallback to the default macOS icon was announced in a warning, but the build failed subsequently
- In the Japanese translation, the product name install4j was translated by mistake
- "Choose" button in file chooser was not translated anymore
- Specifying relative path names to createbundle did not work
更新時間：2020-11-24
更新細節：
更新時間：2020-11-24
更新細節：
What's new in this version:
- AMD Ryzen 5000 "Zen 3" Vermeer support
- AMD Radeon 6800 and 6800 XT GPUs
- Intel Rocket Lake processors preliminary support
- Intel Tiger Lake-U and Tiger Lake-H processors
- Intel Z590 chipset
- NVIDIA RTX 3090, 3080, 3070 GPUs
更新時間：2020-11-24
更新細節：
What's new in this version:
UI:
- Major optimization work (less CPU Usage for the UI, more responsive tab changes for graphs)
- You can maximize/restore OCCT's window by double-clicking the title bar
- Added HwInfo version in the about window
Main:
- fixed margins of the screenshot function
- Optimized startup time ( ~10% faster on some points) (the new single table view will probably make OCCT startup slightly slower though)
- MEMORY: SSE was made the default (seems to give better results overall than AVX in practice)
- SETTINGS: Added a "stop on first error found" option in the settings
Monitoring: Added a single table mode to OCCT's monitoring
- Added filters to the single table mode
- CPU reaching TJunction won't have an invalid temperature reported anymore
- Updated HWInfo to 6.35 ( @Austin rejoice ! )
- Added a corsair / asetek checkbox (disabled by default) to enable reading the sensor from those devices. This can cause conflicts with their drivers/software, so beware !
- Optimized CPU Usage of graphs
- Greatly optimized memory usage when testing for prolonged periods of time
- Greatly lowered the report generation time for long tests
- Disabled sensor will now properly disappear when unchecked
- REPORTS : Removed the smoothing function in the reports as it was conflicting with the previous optimizations. The graphs look sharper, but more precise.
Enterprise:
- The close button now disappears when there's only one test in the test chain, rather than displaying a message
- fixed "System" header translation in report
- fixed a few icons in component usage incorrectly displayed as CPU
- the report save path is now part of OCCT's settings (as the free edition)
- Added a switch "--auto-enable-sensors" to allow for forcing the auto-enabling of sensors upon startup ( using the supplied rules file, or the default one is none is specified)
- Added max temperature limit to the report, if enabled
- Added the OCCT Version on top of the report
- The HTML report won't be overwritten if auto save is enabled, a small counter will be appended
更新時間：2020-11-24
更新細節：