[WebDNA] Encode cookies ONLY via "method=Base64"

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 101259
interpreted = N
texte = > sometimes a second decrypt and/or unurl=20 > is needed.=20 A different number of decrypts and encrypts never works, you=20 must always use the same number of these contexts. A=20 different number of urls and unurls is definitely necessary=20 sometimes: > Syntax reminder on variable (straight), and database > encryption: > Straight encryption: same amount of [url]'s going in as > comming out=20 > Database encryption: one more [url] going in=20 > than comming out Right, thanks for the reminder. =20 With the cookies I first tried the same number of urls and=20 unurls but it was failing, so then I tried using one more=20 url going in -- because I thought that *maybe* using=20 cookies is similar to using a database. But this theory=20 was wrong because an extra url with cookies does not fix=20 the problem like it does with a database. > Could you please tell us what server you're using? My client's Windows server running WebDNA 6.? > I have found the same thing as Ken has, and that it=20 > is on our list of potential bugs that we are addressing. =A0 > The scope appears to be only in cookie and orderfile=20 > interaction so far. =20 Orderfile too? =20 Thanks Donovan, that's two scopes we should avoid when using=20 the standard WebDNA encryption. Too bad though, since I=20 want to use encrypted cookies for security reasons. =20 PROBABLE CONCLUSION: Although Base64 is an encoding method (not an encryption=20 method) it is the ONLY method that actually works when=20 trying to obfuscate cookie values. Base64 is certainly not secure like an encrypted value might=20 be, but it is better than nothing I guess. I tested all=20 methods using cookies with the following results: standard webdna encryption --> fails 1/4 of the time method=3DCyberCash --> cannot be decrypted method=3DAPOP --> cannot be decrypted method=3DBase64 --> 100% reliable in dozens of tests Sincerely, Ken Grome Associated Messages, from the most recent to the oldest:

    
> sometimes a second decrypt and/or unurl=20 > is needed.=20 A different number of decrypts and encrypts never works, you=20 must always use the same number of these contexts. A=20 different number of urls and unurls is definitely necessary=20 sometimes: > Syntax reminder on variable (straight), and database > encryption: > Straight encryption: same amount of [url]'s going in as > comming out=20 > Database encryption: one more [url] going in=20 > than comming out Right, thanks for the reminder. =20 With the cookies I first tried the same number of urls and=20 unurls but it was failing, so then I tried using one more=20 url going in -- because I thought that *maybe* using=20 cookies is similar to using a database. But this theory=20 was wrong because an extra url with cookies does not fix=20 the problem like it does with a database. > Could you please tell us what server you're using? My client's Windows server running WebDNA 6.? > I have found the same thing as Ken has, and that it=20 > is on our list of potential bugs that we are addressing. =A0 > The scope appears to be only in cookie and orderfile=20 > interaction so far. =20 Orderfile too? =20 Thanks Donovan, that's two scopes we should avoid when using=20 the standard WebDNA encryption. Too bad though, since I=20 want to use encrypted cookies for security reasons. =20 PROBABLE CONCLUSION: Although Base64 is an encoding method (not an encryption=20 method) it is the ONLY method that actually works when=20 trying to obfuscate cookie values. Base64 is certainly not secure like an encrypted value might=20 be, but it is better than nothing I guess. I tested all=20 methods using cookies with the following results: standard webdna encryption --> fails 1/4 of the time method=3DCyberCash --> cannot be decrypted method=3DAPOP --> cannot be decrypted method=3DBase64 --> 100% reliable in dozens of tests Sincerely, Ken Grome Kenneth Grome

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:

I give up!! (1997) Using Applescript to process WebCatalog functions (1998) ANother SHOWIF problem (1997) WebDNA 5.0 Questions (2003) Help with Repost Data msg from form (1997) Does [Sendmail] create html? (2002) How do I hyperlink to returned image filename? (2000) sort links (2002) TCPConnect to Telnet (2003) [WebDNA] Friendly urls and multipart/form-data (2011) Server slowing down. (1997) founditem align (1998) WebCat2b13MacPlugIn - syntax to convert date (1997) WC1.6 to WC2 date formatting (1997) [AppendFile] problem (WebCat2b13 Mac .acgi) (1997) Large sites (2003) WebCatalog Technical Reference (1997) taxTotal, grandTotal (1997) splitting numbers in webDNA? (1997) OT: Backup Strategies (2007)