Re: Problem with encrypted cookies
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 28862
interpreted = N
texte = The most appropriate way to employ cookies (IMNSHO) is to store only the unique identifier in the cookie, the [CART] value being a good example. The remainder of the data, including anything being worthy of encrypting, is stored in a database on the server. This way, there is no chance that any information that should remain secure will be sent over the public network, even inside an SSL transaction and then encrypted. Remember that cookies are sent for every single page and graphic in your domain. KISS - Keep It Small and Simple...I believe that Grant has stated that the encryption routine requires high-ascii characters. You can use [Encrypt method=base64] to make it non-human readable, which is 7-bit safe, but easy to decode.John Peacock ____________________Reply Separator____________________ Subject: Problem with encrypted cookies Author:
(WebCatalog Talk) Date: 3/10/00 12:52 PMI would like to save the values in my cookies as encrypted.Problem is, the information is sometimes corrupted because of some of the characters in the encrypted version.Is there a way to make encrypted values contain ascii characters from 32 to 127?Thanks! ------------------------------------------------------------- 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
Associated Messages, from the most recent to the oldest:
| |
- Re: Problem with encrypted cookies (jpeacock@univpress.com 2000)
|
The most appropriate way to employ cookies (IMNSHO) is to store only the unique identifier in the cookie, the [cart] value being a good example. The remainder of the data, including anything being worthy of encrypting, is stored in a database on the server. This way, there is no chance that any information that should remain secure will be sent over the public network, even inside an SSL transaction and then encrypted. Remember that cookies are sent for every single page and graphic in your domain. KISS - Keep It Small and Simple...I believe that Grant has stated that the encryption routine requires high-ascii characters. You can use [Encrypt method=base64] to make it non-human readable, which is 7-bit safe, but easy to decode.John Peacock ____________________Reply Separator____________________ Subject: Problem with encrypted cookies Author: (WebCatalog Talk) Date: 3/10/00 12:52 PMI would like to save the values in my cookies as encrypted.Problem is, the information is sometimes corrupted because of some of the characters in the encrypted version.Is there a way to make encrypted values contain ascii characters from 32 to 127?Thanks! ------------------------------------------------------------- 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
jpeacock@univpress.com
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:
NT vs Mac (1997)
HELP - NONE STOP DIGESTS. Digest for 4/24/97) (1997)
Frames and WebCat (1997)
WebCatalog 2.0 b 15 mac (1997)
WebCat2final1 crashes (1997)
Server crash (1997)
WebCatalog f2 Installation (1997)
WebCat2 - [SendNews] (1997)
WebDNA - fun to compare (2005)
Generating unique SKU from [cart] (1997)
Separate SSL Server (1997)
Cart Question (1998)
Attn: Bug in GeneralStore example b15 (1997)
moving to Redhat Enterprise 3 when is WebDNA 5.2? (2003)
Netscape 3.01 can't see db in form (was problems problemsproblems) (1997)
WCS Newbie question (1997)
Thanks and Big News!!! (1997)
Frames and WebCat (1997)
OK, my turn... TEST (2003)
select multiple 2 more cents (1997)