Firefox users like you and me considered as the most secure. According to new study Firefox offers the most secure browsing experience to its user. According to study paper called – Understanding the Web browser threat: Examination of vulnerable online Web browser populations and the “insecurity iceberg” :
=> Firefox users most likely to use the latest version and well secured from the Internet attacks.
=> Failed to update browsers will result in increases the chance for remote attacks executed by attacker.
=> Internet explorer security is bad because most users stuck with older version. Most people can’t uninstall IE, therefore they end up using it outdated default browser version.
See study paper for all the details.
If you just want to see how secure your network is or you would like to audit your own network, and to determine the insecurity of cleartext network protocols then you need to use sniffer programs. There are tons of Network protocol analyzer for Unix and Linux exist that allows examination of data from a live network, or from a capture file on disk For example Ethereal is one of such a program.
However, if you just interested in a password related auditing then nothing can beat dsniff program. It is simple and easy to use. dsniff capture passwords through http, ftp, smtp, pop3, telnet and many other cleartext protocols. dsniff includes various sniffing utilities for penetration testing.
Step # 1: Install dsniff
Install dsniff under Debian / Ubuntu Linux:
# apt-get install dsniff
If you are using FreeBSD then you can install it using ports or binary package:
# pkg_add -r dsniff
On the other hand, use ports collection:
># cd /usr/ports/security/dsniff
# make; make install; make clean
Step # 2: Start dsniff
dsniff automatically detects and minimally parses each application protocol, only saving the interesting bits, and uses Berkeley DB as its output file format, only logging unique authentication attempts. Login as a root user and type dsniff command:
For example, if user use ftp, telnet, or other cleartext protocol then you can capture passwords:
03/16/06 23:34:02 udp 192.168.1.2.1195 -> router.161 (snmp)
03/16/06 23:36:10 tcp 192.168.1.2.49522 -> f100.somedomain.com.21 (ftp)
Depend upon this audit report:
- You can block cleartext port
- Educate your user and ask them to use secure version of each of these protocols