nod327.net

[March 08, 2010]Fresh nod32 keys

admin — Sun, 07 Mar 2010 10:27:53 +0000

Username:EAV-27532236
nod32key:55tfju7mmc

Username:EAV-27530795
nod32key:3r3p5xhfp7

Username:EAV-27533673
nod32key:ucrn8u7btc

Username:EAV-27532214
nod32key:vc2s57dje4

Username:EAV-28499813
nod32key:ura3pxnv8s

Username:EAV-27969600
nod32key:487sth3ffs

How do I uninstall ESET Smart Security/ESET NOD32 Antivirus? (4.0)

admin — Wed, 17 Feb 2010 15:11:17 +0000

Due to corrupted installations or newer program releases, reinstalling your ESET security product is sometimes necessary.

Uninstall

Click Start → All Programs → ESET → Uninstall. After you uninstall, you will need to restart your computer.

Warning: Do not attempt to uninstall your ESET security product using the Windows Add or Remove Programs utility from the Control Panel.

After restarting, confirm that you can see hidden files and folders by clicking Start → Control Panel → Folder Options → View and select the Show hidden files and folders option.

Click Start → My Computer and then navigate to and delete the following folders:

C:\Program Files\ESET
C:\Documents and Settings\All Users\Application Data\ESET
C:\Documents and Settings\%USER%\Application Data\ESET

Windows Vista and Windows 7 Users must delete the following folders:

C:\Program Files\ESET
C:\Program Data\ESET

NOTE: The uninstaller may remove the above folders automatically. If you are unable to find the folders after selecting Show hidden files and folders, the removal is complete.

Why does the file scan not indicate the presence of malware on a NSS volume?

admin — Tue, 16 Feb 2010 15:07:54 +0000

When scanning files with ESET File Security for Linux the scan detects no malware on a mounted NSS volume, even if present. Upon finishing, the scanner displays a list of scanned objects. Are some of the scanned objects infected, however, all items on the list will appear as clean.

The reason for this is that Novell Storage Services (NSS) distort common unix security principles the scanner relies on, limiting its privileges. This can result in threats not being detected on NSS mounted volumes.

To fix this problem:

Open the configuration file (with root permissions) in a text editor.
user@machine:~$ sudo nano /etc/esets/esets.cfg
[sudo] password for user:

Find the [global] section

Find the line:

esets_user = “esets”

and replace it by:

esets_user = “root”

Save the configuration file and exit.

Restart the esets_daemon.

NOTE: It is important to restart the ESETS daemon after saving the changes for the new settings to apply.