Slashdot Mirror

← Back to Domains

Domain: cookiecentral.com

Stories and comments across the archive that link to cookiecentral.com.

Comments · 8

  1. Re:torrent? by fm6 · · Score: 1 · on Star Wars Sith Trailer and the O.C.

    Gee, thanks.

  2. Is this really a threat? by sonnerbob · · Score: 2 · on MSIE's Cookies Are Public
    And here I am trying to dampen paranoia about cookies. (I love the Slashdot FAQ on cookies.)

    But this bothers me and sounds similar to the bug reported at CookieCentral a long time ago. I'm trying to digest how this is different and what danger (and likelihood of appearance) this represents "in the wild".

    Answers here or to me by email would be appreciated.

  3. Re:Rejecting offsite cookies by Anonymous Coward · · Score: 0 · on DoubleClick Workaround: IDcide

    Cookie Central has info on this.

  4. Re:a rare event by Anonymous Coward · · Score: 0 · on DoubleClick DoublesBack

    Cookie Central has info on this. These dominate corperations try to force anything upon the consumer, it's good to see they buckle under pressure.

  5. Re:Fist prost by Anonymous Coward · · Score: 0 · on DoubleClick Taken to Court

    Cookie Central have been writing about the goings on of DoubleClick for quite a while.

  6. Re:Another Danger by penguinicide · · Score: 2 · on DoubleClick Taken to Court
    Buy placing "..." at the end of the domain being set, some browsers (i don't know if this has been fixed yet) can get confused as to the top level domain being set, and let everyone read the cookie.

    Here is where I read about it.

    And you are correct about second level domains sharing cookies. It depends on how you set the cookie. If you were to set it to "somerandomsite.com" it can be shared. If you were to set it to "www.somerandomsite.com" only www.somerandomsite.com can read it.

    Here is the reference I use anytime I need to use cookies: Cookie FAQ

  7. Re:Another Danger by penguinicide · · Score: 2 · on DoubleClick Taken to Court
    Buy placing "..." at the end of the domain being set, some browsers (i don't know if this has been fixed yet) can get confused as to the top level domain being set, and let everyone read the cookie.

    Here is where I read about it.

    And you are correct about second level domains sharing cookies. It depends on how you set the cookie. If you were to set it to "somerandomsite.com" it can be shared. If you were to set it to "www.somerandomsite.com" only www.somerandomsite.com can read it.

    Here is the reference I use anytime I need to use cookies: Cookie FAQ

  8. Please dont waste time. Read this instead by Manifest · · Score: 2 · on Novell CEO Attacked by Cookie Monster

    Please dont waste time. Read this artic le on the evils of cookies instead. Atleast these people know a bit about what they are talking about.

    If I am not mistaken, it talks about the security loophole that was created when GIF images were allowed to embed cookies in computers. This has been discussed on /.