Internet Download Manager 歷史版本列表
更新時間：2019-08-26
更新細節：
What's new in this version:
- Fixed the recognition of video file names on some web sites
- Resolved compatibility problems with older versions of Firefox browsers
- Fixed bugs
更新時間：2019-08-23
更新細節：
What's new in this version:
- Compressed downloads database; error handling for monthly download days; tool tips for texts that don't fit into the available space
更新時間：2019-08-22
更新細節：
What's new in this version:
- Updated default registry and file permissions for Windows 7, 8.1 and 10
更新時間：2019-08-22
更新細節：
What's new in this version:
- Fixed a critical bug with Linpack parsing on CPUs with a huge number of cores - false positives were reported in some (thankfully rare) cases
更新時間：2019-08-22
更新細節：
What's new in this version:
- Fixed access date being parsed as previous year in some time zones on Windows 10 version 1903
- When transferring a document between word processors, modified citations were left as code
- For now, modified citations will be silently reset on transfer. We hope to preserve modified citations in a future version.
- Fixed potential file sync error when using eCryptfs on Linux
- Translator Editor improvements
- Update UI based on Zotero UI font size pref
- Load translator on double-click in translator list
- Support Cmd/Ctrl-= for zooming in code editor in addition to Cmd/Ctrl-+
更新時間：2019-08-22
更新細節：
What's new in this version:
- Added Insider and developer versions up to build 18963; added Windows Admin Center previews up to build 1908; added Office 2019 for Mac build 16.28; added database of 85,000 downloads from Microsoft (applications, disc images, slides, white papers, business presentations, podcasts, videos, e-books, product sheets etc.
更新時間：2019-08-21
更新細節：
What's new in this version:
Changes:
Crypto:
- Added an oaepHash option to asymmetric encryption which allows users to specify a hash function when using OAEP padding
Deps:
- Updated V8 to 7.6.303.29
- Improves the performance of various APIs such as JSON.parse and methods called on frozen arrays
- Adds the Promise.allSettled method
- Improves support of BigInt in Intl methods
- Updated libuv to 1.31.0
- UV_FS_O_FILEMAP has been added for faster access to memory mapped files on Windows
- uv_fs_mkdir() now returns UV_EINVAL for invalid filenames on Windows. It previously returned UV_ENOENT
- The uv_fs_statfs() API has been added
- The uv_os_environ() and uv_os_free_environ() APIs have been added
Fs:
- Added fs.writev, fs.writevSync and filehandle.writev (promise version) methods. They allow to write an array of ArrayBufferViews to a file descriptor
Http:
- Added three properties to OutgoingMessage.prototype: writableObjectMode, writableLength and writableHighWaterMark
Stream:
- Added an new property readableEnded to readable streams. Its value is set to true when the 'end' event is emitted
- Added an new property writableEnded to writable streams. Its value is set to true after writable.end() has been called
更新時間：2019-08-20
更新細節：
更新時間：2019-08-20
更新細節：
更新時間：2019-08-16
更新細節：
What's new in this version:
Fixed:
- “Data Dribble”: The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.
- “Ping Flood”: The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.
- “Resource Loop”: The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU, potentially leading to a denial of service.
- “Reset Flood”: The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both, potentially leading to a denial of service.
- “Settings Flood”: The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.
- “0-Length Headers Leak”: The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory, potentially leading to a denial of service.
- “Internal Data Buffering”: The attacker opens the HTTP/2 window so the peer can send without constraint; however, they leave the TCP window closed so the peer cannot actually write (many of) the bytes on the wire. The attacker then sends a stream of requests for a large response object. Depending on how the servers queue the responses, this can consume excess memory, CPU, or both, potentially leading to a denial of service.
C- “Empty Frames Flood”: The attacker sends a stream of frames with an empty payload and without the end-of-stream flag. These frames can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE. The peer spends time processing each frame disproportionate to attack bandwidth. This can consume excess CPU, potentially leading to a denial of service.