TGE and Norton Internet Security
by Ian Omroth Hardingham · in Torque Game Engine · 06/06/2005 (2:43 pm) · 6 replies
Hey everyone.
Try as I might, I have been unable to get Norton Internet Security to stop asking me for permission status every time I recompile Torque. Has anyone had any success with this, and tell me what to do? I've tried allowing all UDP and TCP on some ports, but no luck.
Any help much appreciated.
Ian
Try as I might, I have been unable to get Norton Internet Security to stop asking me for permission status every time I recompile Torque. Has anyone had any success with this, and tell me what to do? I've tried allowing all UDP and TCP on some ports, but no luck.
Any help much appreciated.
Ian
About the author
Designer and lead programmer on Frozen Synapse, Frozen Endzone, and Determinance. Co-owner of Mode 7 Games.
#2
06/06/2005 (4:49 pm)
In Zone Alarm, you could force it to accept changing .exe files and not ask all the time (on a user-selectable basis). There is no option to do that in NIS?
#3
06/06/2005 (7:27 pm)
You can? That's awesome, how do you do it? (w/ Zone Alarm)
#4
In Zone Alarm, goto program control, select the program, click options and change the authentication options (none, authenticate by full name only or authenticate components). Authenticate components checks the size of the program and any dlls it uses, name makes sure it is where it was last time it ran and none does erm ... none :)
06/07/2005 (12:50 am)
@ BenIn Zone Alarm, goto program control, select the program, click options and change the authentication options (none, authenticate by full name only or authenticate components). Authenticate components checks the size of the program and any dlls it uses, name makes sure it is where it was last time it ran and none does erm ... none :)
#5
Now, I do agree, NIS should have an option to allow a "category" of executable types to be excluded from this check, but disabling the check completely for all executables is a risk.
06/07/2005 (8:30 am)
Just realize that NIS isn't actually being "dumb" about making sure you re-confirm each "new" executable: it's a common hacking tactic to trojan horse an existing executable--especially low level system functions like "dir", or even explorer) so that those programs do what the hacker wants, while fooling the user into thinking it's doing what the user wants. Executable tracking is a safety net for protecting against this type of attack.Now, I do agree, NIS should have an option to allow a "category" of executable types to be excluded from this check, but disabling the check completely for all executables is a risk.
#6
Thanks for the replies everyone, I guess I'll just have to use Windows Firewall while I'm devving.
Ian
06/07/2005 (8:49 am)
I wasn't under the impression NIS was being dumb: of course it should re-scan an exe if it's checksum changes but, like you say, the option to turn this off is an important one.Thanks for the replies everyone, I guess I'll just have to use Windows Firewall while I'm devving.
Ian
Torque Owner Chris Byars
Ion Productions
Sorry...