Segfault when using additional_trust_anchors
See original GitHub issueOS: Windows 10 (x64) Build: 0.17.0 SDK Win64
When additional_trust_anchors
is used in package.json
app wont start. Starting from terminal gives me Segmentation Fault error. Without this parameter application starts normally.
This issue may be somehow related to: https://github.com/nwjs/nw.js/pull/4210
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Identify what's causing segmentation faults (segfaults)
A segmentation fault (aka segfault) is a common condition that causes programs to crash; they are often associated with a file named core...
Read more >Segfault when using scanf() - Stack Overflow
This is a simple program that prompts for a name from keyboard input, creates a greeting using the name, then prints it. At...
Read more >Common Causes of Segmentation Faults (Segfaults)
A segmentation fault (often called a segfault) can occur if a program you are running attempts to access an invalid memory location.
Read more >Segmentation fault - Wikipedia
In computing, a segmentation fault (often shortened to segfault) or access violation is a fault, or failure condition, raised by hardware with memory...
Read more >Core Dump (Segmentation fault) in C/C++ - GeeksforGeeks
C++ program to demonstrate segmentation fault/core dump. // by modifying a string literal. #include <iostream>. using namespace std;.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
fixed in git and will be released with upcoming 0.17.5.
Hmm, it’s been a long time since I was working on this and I currently don’t have a Windows dev environment to test locally.
From what I remember, the verification code stopped at the first unknown certificate, which I think was the CA certificate (assuming the server sends the complete certificate chain). This certificate is then compared against the additional trust anchor list. Thinking about it, this should probably be changed to check if that unknown certificate was issued by one of the certs in the trust anchors list, so you don’t have to modify your testcase for Windows.