Re: Heads up, cookies *may* be outlawed in Europe

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 40051
interpreted = N
texte = On 11/12/01 6:35 PM, Alex McCombie wrote:> Specifically, a foreseeable issue is someone that uses cookies to allow > logins, or access to critical or sensitive information. Once that cookie > information is 'mined' through this new crack, that information could be > replicated and thus used to allow access to this information. But you can't just allow cookie existance to provide access, instead it has to be a compound of things based on the need to protect data. If you don't mind losing it then stick it in a cookie, but this should not be new. Just the very nature of a cookie is insecure and unreliable. If however you put in a username that allows quick access via a password then I think you can be relatively sure that you are ok.Lets say you allow people to quickpay based on stored data. In fact you store there credit card. You should require that they enter a password and that they only ship to the bill to or the data on record. And you would NEVER show them the whole card number. While you remembered who they were as a username you didn't give anything away that could be used without some sort of additional knowledge.The logic has to be sound, it is your job as a developer to do the best you can to secure the customers data or you will likely find yourself on the end of a lawsuit.Robert Minor Director of Internet Services ------------------------------------------------------------ Cybermill Communications http://www.cybermill.com http://www.merchantmaker.comProviding Ecommerce and interactive website development and hosting services on Macintosh, Windows NT, Unix, and AS/400.All your websites are belong to us! ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Heads up, cookies *may* be outlawed in Europe (Alex McCombie 2001)
  2. Re: Heads up, cookies *may* be outlawed in Europe (Bob Minor 2001)
  3. Re: Heads up, cookies *may* be outlawed in Europe (Bob Minor 2001)
  4. Re: Heads up, cookies *may* be outlawed in Europe (Paul Uttermohlen 2001)
  5. Re: Heads up, cookies *may* be outlawed in Europe (Alex McCombie 2001)
  6. Re: Heads up, cookies *may* be outlawed in Europe (Bob Minor 2001)
  7. Re: Heads up, cookies *may* be outlawed in Europe (Alex McCombie 2001)
  8. Re: Heads up, cookies *may* be outlawed in Europe (John Peacock 2001)
  9. Re: Heads up, cookies *may* be outlawed in Europe (John Peacock 2001)
  10. Re: Heads up, cookies *may* be outlawed in Europe (Glenn Busbin 2001)
  11. Re: Heads up, cookies *may* be outlawed in Europe (Bob Minor 2001)
  12. Re: Heads up, cookies *may* be outlawed in Europe (Alex McCombie 2001)
  13. Re: Heads up, cookies *may* be outlawed in Europe (dale 2001)
  14. Re: Heads up, cookies *may* be outlawed in Europe (John Peacock 2001)
  15. Heads up, cookies *may* be outlawed in Europe (dale 2001)
On 11/12/01 6:35 PM, Alex McCombie wrote:> Specifically, a foreseeable issue is someone that uses cookies to allow > logins, or access to critical or sensitive information. Once that cookie > information is 'mined' through this new crack, that information could be > replicated and thus used to allow access to this information. But you can't just allow cookie existance to provide access, instead it has to be a compound of things based on the need to protect data. If you don't mind losing it then stick it in a cookie, but this should not be new. Just the very nature of a cookie is insecure and unreliable. If however you put in a username that allows quick access via a password then I think you can be relatively sure that you are ok.Lets say you allow people to quickpay based on stored data. In fact you store there credit card. You should require that they enter a password and that they only ship to the bill to or the data on record. And you would NEVER show them the whole card number. While you remembered who they were as a username you didn't give anything away that could be used without some sort of additional knowledge.The logic has to be sound, it is your job as a developer to do the best you can to secure the customers data or you will likely find yourself on the end of a lawsuit.Robert Minor Director of Internet Services ------------------------------------------------------------ Cybermill Communications http://www.cybermill.com http://www.merchantmaker.comProviding Ecommerce and interactive website development and hosting services on Macintosh, Windows NT, Unix, and AS/400.All your websites are belong to us! ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Bob Minor

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[showif] with ! (2000) WebDNA Developer Edition - Host config problem (2003) Limit on nested [ShowIf]'s? (1997) List Address Changed! (1998) Mac -Shareware Listserver (1998) Problem displaying search result (1997) What am I missing (1997) Robert Minor duplicate mail (1997) WebCat2b15MacPlugIn - [authenticate] not [protect] (1997) Users.db [encrypt seed=????] (1998) Error: Missing c in orderfile???? (2005) PSC recommends what date format yr 2000??? (1997) For those of you not on the WebCatalog Beta... (1997) Webstar 1.3.1 PPC (1997) RE: [WebDNA] TCPconnect and Bitcoin rate (2017) [OT] Puget Sound Meteorites? (2004) Reselecting popup menu (2002) A Global Variable (1997) [cart] not being interpreted inside [founditems] (1997) [WebDNA] Clarifying talklist emails (2020)