Page 1 of 1
connection to customer.teliacarrier
Posted: Fri Oct 31, 2014 11:48 am
by white31
After last update (v.2.6.9.3) NoScriprt connects to 213-155-158-72.customer.teliacarrier.com at every browser startup, if I disable add-on and restart then no such connection is made. Could you tell me why it needs customer.teliacarrier.com which is also Akamai??
Re: connection to customer.teliacarrier
Posted: Fri Oct 31, 2014 3:36 pm
by barbaz
NS connects to Giorgio's server on startup to fetch your WAN IP, what you're seeing is your browser connecting to an OCSP server to verify Giorgio's server's certificate
(It didn't do that before the update??)
Re: connection to customer.teliacarrier
Posted: Fri Oct 31, 2014 4:03 pm
by white31
I don't know about OCSP server connection but I remember that there was not such connection in version 2.6.9.2 at browser startup, maybe after some time, but not at startup.
Re: connection to customer.teliacarrier
Posted: Fri Oct 31, 2014 6:18 pm
by therube
WAN IP check can be disabled, if you want.
NoScript | Options | Advanced -> ABE => WAN IP
Test disabled & see if the requests subside.
Re: connection to customer.teliacarrier
Posted: Fri Oct 31, 2014 8:11 pm
by white31
Unchecking WAN IP in options removes connections but what I'd like to know is how akamai is involved in this?! I have read that NS needs to connect to
https://secure.informaction.com/ipecho server and I'm not against this but why akamai?
Re: connection to customer.teliacarrier
Posted: Fri Oct 31, 2014 9:52 pm
by Giorgio Maone
That one is probably your own (dynamic?) IP.
See
http://noscript.net/abe/wan for details.
Re: connection to customer.teliacarrier
Posted: Sat Nov 01, 2014 11:06 am
by white31
I'm on single PC here and my ip is 95.104.xxx.xx which haven't changed more than 2 years. I checked NS release notes in my browser and found this:
v 2.6.9.3
=============================================================
x More accurate referrer checks for some edge cases (thanks
AlbertMTom for reporting)
x [ABE] More restrictive local IP checks (thanks AlbertMTom
for reporting)
+ More permissive AddressMatcher IP parser
+ [XSS] Improved sensitivity (thanks Masato Kinugawa)
so, maybe those 2 rules about IP are the reason?
I rechecked and installed previous v.2.6.9.2 from third party site just to be sure and can confirm that old version of NoScript isn't making connection to customer.teliacarrier.com. You can test this in your browsers too.