Quote from: SatoNatomato on February 06, 2017, 11:01:14 AM

Quote from: vlom on February 06, 2017, 10:48:29 AM

Quote from: SatoNatomato on February 05, 2017, 09:13:14 PM

Quote from: vlom on February 05, 2017, 08:38:28 PM

Quote from: tonych on February 03, 2017, 11:50:51 PM

Quote from: vlom on February 03, 2017, 06:28:36 PM

why does the OS X app try to connect to google?

plus.google.com TCP-Port 443 (https)

What makes you think so?
There are no references to any sites (except the default hub) in the source code.

because little snitch tells my that the app wants to connect.

Seems to be nwjs, the component used by Byteball. Maybe it means NodeWebKit.js and is the browser-bundled up.

Google is known for adding a bunch of shit in every source-code they touch to "resolve" something on their servers. This could be information leakage, especially when using it over Tor - who knows what it sends to Google even if it is the hostname and datetime its too much.

@tonych, maybe see if there is a default option which has to be turned off when importing/using nwjs?

edit: https://github.com/nwjs/nw.js/issues/5343 just one issue, expect 100 more "accidents" by google. edit2: if using the chromiu-args proxy workaround, make it something else than 127.0.0.1, like 127.6.6.6 to avoid more other problems.

everyone how is happy that i posted this can send my some bytes. i still don't have any.

ZLQAYBCCZT2DBBD6KSLXJYCYR6QMU2VK

thank you very much.

i am not sure if this is a security problem if you use a VPN.
but with tor? if not every connections is torified then this could really leak your IP.

i don't want to fud. i am just concerned about privacy. and i am not a hardcore techie.

Sent you some as thanks for reporting this finding.

If wallet is torified/socksify/proxychains-ng, the call to google will also go over Tor. Will not leak your public IP, but still not good.

Let me add, and even more so if you use whonix.
I can attest it works.