Yakyak: Support corporate proxies by allowing users to specify a trusted SSL root certificate

[ivanatpr]

For people behind HTTPS corporate proxies yakyak currently does not work. These proxies will dynamically generate replacement SSL certs for HTTPS connections which use the company's own root certificate, which is included as a trusted root certificate in the system-wide cert store of all of the company's PCs.

Since yakyak does not appear to use the systemwide cert store, the connection to hangouts fails, causing an endless loops where it seems like yakyak tries to connect, fails, closes (crashes?), and then automatically starts up again and tries again, repeating the same pattern.

In order for this to work, if yakyak isn't going to use the systemwide cert store, then there needs to be a way for users to specify a trusted cert. An example of this Firefox, which keeps its own cert store but allows you to import certs into it.

[averissimo]

thanks for reporting this :)

edit: I had a wrong understanding of what I've written before and deleted most of my comment

[vmus]

This worked for me. https://stackoverflow.com/a/21961005/1283098

[Curros]

@vmus where you change the code?

[vmus]

@Curros, in resources/app/main.js:

app.on('ready', function() {
  process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";

or just start with NODE_TLS_REJECT_UNAUTHORIZED=0 ./yakyak

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.