node-forge 0.9.2 → 0.10.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,6 +1,24 @@
1
1
  Forge ChangeLog
2
2
  ===============
3
3
 
4
+ ## 0.10.0 - 2019-09-01
5
+
6
+ ### Changed
7
+ - **BREAKING**: Node.js 4 no longer supported. The code *may* still work, and
8
+ non-invasive patches to keep it working will be considered. However, more
9
+ modern tools no longer support old Node.js versions making testing difficult.
10
+
11
+ ### Removed
12
+ - **BREAKING**: Remove `util.getPath`, `util.setPath`, and `util.deletePath`.
13
+ `util.setPath` had a potential prototype pollution security issue when used
14
+ with unsafe inputs. These functions are not used by `forge` itself. They date
15
+ from an early time when `forge` was targeted at providing general helper
16
+ functions. The library direction changed to be more focused on cryptography.
17
+ Many other excellent libraries are more suitable for general utilities. If
18
+ you need a replacement for these functions, consier `get`, `set`, and `unset`
19
+ from [lodash](https://lodash.com/). But also consider the potential similar
20
+ security issues with those APIs.
21
+
4
22
  ## 0.9.2 - 2019-09-01
5
23
 
6
24
  ### Changed
package/README.md CHANGED
@@ -2035,8 +2035,6 @@ When using this code please keep the following in mind:
2035
2035
  - Certain features in this library are less susceptible to attacks depending on
2036
2036
  usage. This primarily includes features that deal with data format
2037
2037
  manipulation or those that are not involved in communication.
2038
- - Do not pass unsafe inputs to `util.setPath`. Doing so could expose a
2039
- prototype pollution security issue.
2040
2038
 
2041
2039
  Library Background
2042
2040
  ------------------