CSV conflicts with NOD32
I was pretty pissed about the fact the NOD32 makes CSV feature failed even when both CSV client and server were in the same machine. MY collegue uninstalled NOD32, and suddenly CSV started working on his own machine (with both CSV server and client in the same machine). Later he also verified that the problem is actually on the server side, since he still cannot access the remote CSV Files (and that server still has the NOD32 running).So I was so pissed that I uninstalled NOD32 from my local computer. And I was a bit surprised to found out that I can grab the ESET directory can treated it as a portable version of NOD32. However, this portable version has the following shortcoming:
- Cannot have virus definition updated
- Cannot has setting (profile) saved
Otherwise it worked pretty OK. I will keep that in mind when I need to create a lean environment for combating virus on other machine.
Speaking of CSV, I was very surprised that the CSV "database" is only as secure as the operating system it's running on. In fact, I can copy the whole CSV database from our production server, put it in my machine, and then use accounts in my local OS machine to access, and I have TOTALLY ACCESS of every source in the version control database. Darn, I thought they encrypted the whole thing :-I
P.S. My colleague said that the problem has been resolved by copying Certain file to certain place. I better ask him for more detail information later....
posted by Deecay @ 10:43 PM
0 comments
