npm-base: Move cache dir to persistent location #70
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Will you merge this? |
|
I'll land this along with Node.js v8.0.0 |
|
8.0.0 already? Makes me miss the days when applications sat on the same major version for 10 years. |
|
Yes, Node.js upstream is dropping support for the now previous- I'm going to keep following Node.js upstream release and maintenance schedule with |
added 2 commits
August 31, 2017 10:55
Notable Changes
* configure:
- add mips64el to valid_arch (Aditya Anand) #13620
* crypto:
- Updated root certificates based on NSS 3.30 (Ben Noordhuis)
- #13279
- #12402
* deps:
- upgrade OpenSSL to version 1.0.2.l (Shigeki Ohtsu) #12913
* http:
- parse errors are now reported when NODE_DEBUG=http (SamRoberts) #13206
- Agent construction can now be envoked without new (cjihrig)
-#12927
* zlib:
- node will now throw an Error when zlib rejects the value of windowBits, instead of crashing (Alexey Orlenko) #13098
Notable changes
* build:
- Disable V8 snapshots - The hashseed embedded in the
snapshot is currently the same for all runs of the binary. This opens
node up to collision attacks which could result in a Denial of Service.
We have temporarily disabled snapshots until a more robust solution is
found (Ali Ijaz Sheikh)
* deps:
- CVE-2017-1000381 - The c-ares function ares_parse_naptr_reply(), which
is used for parsing NAPTR responses, could be triggered to read memory
outside of the given input buffer if the passed in DNS response packet
was crafted in a particular way. This patch checks that there is enough
data for the required elements of an NAPTR record (2 int16, 3 bytes for
string lengths) before processing a record. (David Drysdale)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.