Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Web-App-Sec
[Top] [All Lists]

Re: Web site cookie overload?

Subject: Re: Web site cookie overload?
Date: Tue, 25 Jan 2005 09:36:17 +0000
Alexander Klimov wrote:

On Wed, 19 Jan 2005, Nick wrote:


Most sites will not use cookies as a way of counting the number of
visitors since they are unreliable just like you mentioned. Instead
they would track the number of unique ip addresses that access their
website. This would then be the total number of unique visitors to
their site which is much more reliable then a cookie count.



As was said many times before, unique IPs are by no means indicate unique users: whole company could be behind a single proxy (1 IP for many users) and due to dynamic IPs implemented by most ISPs a single user could have multiple IPs (1 user many IP). If a website wants to make any real counting of its users it can implement some kind of sign on service (with UID and password) so that users be interested in storing cookies in order to avoid relogins.



What if a website doesn't use logins to track visitors? Granted unique IP's are not always unique as you have mentioned. What would be the best way to track these visitors?

Nick

<Prev in Thread] Current Thread [Next in Thread>