lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <00c701c475b5$7e77d750$6500a8c0@p41700>
From: chows at ozemail.com.au (Gregh)
Subject: Cool Web Search

JFYI of anyone interested:

On Nanog a short time back, most of the list there decided that CWS couldn't
easily be removed. I first stumbled across it maybe around the start of July
and have had many instances of it, since, in many places.

Adaware does bugger-all to remove it. Spybot recognised it, got rid of it
and upon reboot it was back. It was never quite clear from a simple
inspection, what was putting it back.

When I first found it, I had also found "HiJackThis" and ran it. That prog
brought up the proper registry entries to enable me to correctly identify
CWS, remove the entries and delete files. It took some time the first time I
saw it but it takes about 10 mins (if that) to get rid of it, now. Nanog
disagreed and said it wasn't that easy. It simply WAS that easy. I just
happened to experience "dumb luck" and be one of the first (if not the
first) to easily get rid of it through HiJackThis.

So, for those of you who don't think Nanog is full of "Gods of Correctness",
if you are having probs with removal of CWS, get HiJackThis, let it scan and
then you will see, sticking out like a wart on your......nose :)........ the
entries you need to delete in order to properly rid that machine of CWS. It
wasn't hard using that prog.

Greg.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ