| Index: > A B C D E F G H I J K L M N O P Q R S T U V W X Y Z |
|
|||||
| First Prev [ 1 2 ] Next Last |
Cookies can contain any arbitrary information the server chooses and are used to maintain state between otherwise stateless HTTP transactions. Typically this is used to authenticate or identify a registered user of a web site as part of their first login process or initial site registration without requiring them to sign in again every time they access that site. Other uses are maintaining a "shopping basket" of goods selected for purchase during a session at a site, site personalisation (presenting different pages to different users), and tracking a particular user's access to a site.
A browser may or may not allow the use of cookies. The user can usually choose a setting.
Tools > Internet Options > Privacy Tab
Tools > Options > Privacy OR Edit > Preferences > Privacy
A cookie often stays on the user's computer for use in the next session (though it can be erased by the user in between), but it can also be for use within a session and be erased at the end of the session.
If more than one browser is used on a computer, each has a separate storage area for cookies. Hence cookies do not identify a person, but a combination of a computer and a web browser. Thus, a single person who uses multiple browsers and/or computers will have a distinct set of cookies for each computer/browser combination. On the other hand, cookies do not differentiate between multiple users who share a computer and browser, unless they use different user accounts.
Some people are opposed to the use of cookies on the Web. Below are some of their reasons.
See above.
Cookies also have some important implications with respect to a user's privacy and anonymity on the web. One way is that some companies monitor users' visits to disparate web sites for marketing purposes. Some sites contain images called web bugs (that are transparent and only one pixel in size, so that they are not visible) that place cookies on all computers that access them. E-commerce websites can then read those cookies, find out what websites placed them, and send e-mail spam advertisements for products related to those websites.
Companies that use this system defend it as an effective way to give consumers access to products in which they are likely to be interested. If sites that place these tracking cookies are paid by the commercial operator, the revenue can allow them to place their content online at no cost to the creators.
SwedenThe Kingdom of Sweden Konungariket Sverige in Swedish) is a Nordic country in Scandinavia, in Northern Europe. It is bordered by Norway on the west, Finland on the northeast, the Skagerrak and the Kattegat on the southwest, and the Baltic Sea and the Gulf has passed legislationLegislation refers to the set of statutory laws in a state. Legislation is passed by a legislature and, in some states, must also be confirmed by the executive. When a bill becomes a law the law is said to be 'promulgated' or 'enacted'. For information on concerning cookies, mandating that sites that use them include a statement to that fact, and includes instructions on how the user can avoid them.Even if cookies are not dangerous per se, they contain information corresponding to a particular context : user, computer, web browser, and above all domain served by the web server from where it originated. Bypassing this context, i.e. having this information 'leak' out of this context is undesirable for the user, especially when the cookie data contains personal information. This bypassing in turn represents a valuable undertaking for an attacker. Cross site scriptingCross site scripting XSS is a type of computer security exploit where information from one context, where it is not trusted, can be inserted into another context, where it is. From the trusted context, an attack can be launched. A classic example of cross is the tool of choice to achieve this goal. Among the threats of cross site scriptingCross site scripting XSS is a type of computer security exploit where information from one context, where it is not trusted, can be inserted into another context, where it is. From the trusted context, an attack can be launched. A classic example of cross attacks, cookie theft and cookie poisoning present a risk to the user, in that they enable a transgression of the context and the trust it carries.