Thought/Question about code signing, UPnP, AV/Firewalls and user connection problems.

This is a question for Frontier Devs really. First a confession for which I hope I'm not flamed into cinders. I'm a former employee of Symantec, makers of Norton (everything). I haven't worked there for about 6 years now, but for over 15 years I worked in their Support teams.
Old habits die hard and when I saw this thread in the EDC Facebook group, it made me think. (You'll need to be a member of the group to see the thread I guess). For those who can't see it, essentially an Elite player (not me) updated the game on April 29th and Norton Security popped up a "reputation" warning, advising him to "block" traffic from elitedangerous64.exe. Specifically, it's advising him to block the traffic that sets up UPnP devices to allow (other) traffic through the router.
Now, if memory serves (and it is a rusty memory), Norton's "Reputation" engine, probably like other desktop security software, takes into account a number of factors (amongst other things) when deciding whether something is safe.
  • How new is it?
  • How many people in the Norton community are already using it and have "trusted" it in their application
  • Whether the application is trying to reconfigure routers/firewalls to open ports
  • Whether the executable is digitally signed
The last point is the one that got me thinking. Norton's reputation engine should probably see this as "safe" if it is signed. But here's the thing...
For some reason, as far as I can tell, while Frontier digitally sign the Launcher executable, the elitedangerous64.exe is NOT digitally signed. I cannot fathom out why not.
So this gets me wondering... Norton's user base, particularly in the "not-so-technical-middle-aged-and-like-a-deal-at-PCWorld/BestBuy-or-don't-know-how-to-uninstall-OEM-software" demographic is HUGE.

Could this be part of why (as I understand it) many ED users have had problems with connections? I know there will be many other factors, but I thought this was worth raising in case it helped in the ongoing research into connectivity issues.

If there is a solid reason for not digitally signing the 64 bit executable, so be it. I completely accept the fact that I could be wrong about this whole thing! :)

Please don't flame me all you flamy types! Only trying to help make this awesome game even better. :eek:
 
Last edited:
it's a good question :)

Another one is why use Norton's in the first place the last time I did was in the win98 days it would protect me from the Internet all right but it killed the driver for the modem. Yes some may see that as good protection but I thought just a tad over zealous so uninstalled it immediately.
 
This is a question for Frontier Devs really. First a confession for which I hope I'm not flamed into cinders. I'm a former employee of Symantec, makers of Norton (everything). I haven't worked there for about 6 years now, but for over 15 years I worked in their Support teams.
Old habits die hard and when I saw this thread in the EDC Facebook group, it made me think. (You'll need to be a member of the group to see the thread I guess). For those who can't see it, essentially an Elite player (not me) updated the game on April 29th and Norton Security popped up a "reputation" warning, advising him to "block" traffic from elitedangerous64.exe. Specifically, it's advising him to block the traffic that sets up UPnP devices to allow (other) traffic through the router.
Now, if memory serves (and it is a rusty memory), Norton's "Reputation" engine, probably like other desktop security software, takes into account a number of factors (amongst other things) when deciding whether something is safe.
  • How new is it?
  • How many people in the Norton community are already using it and have "trusted" it in their application
  • Whether the application is trying to reconfigure routers/firewalls to open ports
  • Whether the executable is digitally signed
The last point is the one that got me thinking. Norton's reputation engine should probably see this as "safe" if it is signed. But here's the thing...
For some reason, as far as I can tell, while Frontier digitally sign the Launcher executable, the elitedangerous64.exe is NOT digitally signed. I cannot fathom out why not.
So this gets me wondering... Norton's user base, particularly in the "not-so-technical-middle-aged-and-like-a-deal-at-PCWorld/BestBuy-or-don't-know-how-to-uninstall-OEM-software" demographic is HUGE.

Could this be part of why (as I understand it) many ED users have had problems with connections? I know there will be many other factors, but I thought this was worth raising in case it helped in the ongoing research into connectivity issues.

If there is a solid reason for not digitally signing the 64 bit executable, so be it. I completely accept the fact that I could be wrong about this whole thing! :)

Please don't flame me all you flamy types! Only trying to help make this awesome game even better. :eek:

Hi,

Could you please check if this program is set to "Allow" in the "Program Exclusion" list under Firewall settings? Did you also try submitting an instance of this file to our false positive portal?

Please let us know!

Thanks!
Abilash P
Norton Support
 
Back
Top Bottom