Re: Base64 encryption limitations?
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 24952
interpreted = N
texte = Once again, you have been bitten by the quite reasonable desire to perform allof your work in one package, even if that does not make any sense. Not knowingwhy you want to encode 20k files using Base64, I cannot make very intelligentsuggestions for alternates. However, I can tell you that the 48 byte limit isalmost certainly related to the exact algorithm employed and the buffer sizesallocated. All Base64 lines should wind up as a multiple of 4, with a maximumsize of 76 characters. I would have thought the algorithm in question wouldhave had a maximum of 57 characters, since 76 == 57*4/3. For more informationabout Base64 encoding, see RFC 2045 - MIME (Multipurpose Internet MailExtensions).There are many other packages out there that can encode files, both for the Macand PC (not to mention Unix). If you are trying to include a file in an e-mail,you should look at Perl and the MIME::Lite module. A simple 20 line program caneasily include a file attachment in an e-mail.HTHJohn Peacock____________________Reply Separator____________________Subject: Base64 encryption limitations? Author:
(WebCatalog Talk)Date: 11/30/99 8:23 PM>From the online docs concerning [encrypt]:Base64 is the encoding (not safe for encryption) that standard HTML browsers use for Basic Authentication. Do not attempt to encrypt more than 48 bytes using method=Base64.Why the 48 byte limit? I want to encode (encrypt) files of 20K and up. Granted, my little test with 800 bytes crashed the development server, but it would be great if the encryption was more robust.Rob MarquardtDesigner/Resident WireheadToast Design800 Washington Avenue NorthMinneapolis MN 55401612.330.9863 v612.321.9424 fwww.toastdesign.com-------------------------------------------------------------Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server.To end your Mail problems go to .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-------------------------------------------------------------Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server.To end your Mail problems go to .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:
Once again, you have been bitten by the quite reasonable desire to perform allof your work in one package, even if that does not make any sense. Not knowingwhy you want to encode 20k files using Base64, I cannot make very intelligentsuggestions for alternates. However, I can tell you that the 48 byte limit isalmost certainly related to the exact algorithm employed and the buffer sizesallocated. All Base64 lines should wind up as a multiple of 4, with a maximumsize of 76 characters. I would have thought the algorithm in question wouldhave had a maximum of 57 characters, since 76 == 57*4/3. For more informationabout Base64 encoding, see RFC 2045 - MIME (Multipurpose Internet MailExtensions).There are many other packages out there that can encode files, both for the Macand PC (not to mention Unix). If you are trying to include a file in an e-mail,you should look at Perl and the MIME::Lite module. A simple 20 line program caneasily include a file attachment in an e-mail.HTHJohn Peacock____________________Reply Separator____________________Subject: Base64 encryption limitations? Author: (WebCatalog Talk)Date: 11/30/99 8:23 PM>From the online docs concerning [encrypt]:Base64 is the encoding (not safe for encryption) that standard HTML browsers use for Basic Authentication. Do not attempt to encrypt more than 48 bytes using method=Base64.Why the 48 byte limit? I want to encode (encrypt) files of 20K and up. Granted, my little test with 800 bytes crashed the development server, but it would be great if the encryption was more robust.Rob MarquardtDesigner/Resident WireheadToast Design800 Washington Avenue NorthMinneapolis MN 55401612.330.9863 v612.321.9424 fwww.toastdesign.com-------------------------------------------------------------Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server.To end your Mail problems go to .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-------------------------------------------------------------Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server.To end your Mail problems go to .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:
WebCat2 Append problem (B14Macacgi) (1997)
Sort on time (2003)
%@#*& back button!!! (1999)
WebCatalog Technical Reference (1997)
ShowNext Command (1997)
Emailer setup (1997)
Bill To - Ship To Information display (1997)
RE: Error -108 (1997)
For you Unix gurus [OT] (2002)
Showing specific [cart] contents (1998)
What about an ends with operator? (2000)
WebCat2b15MacPlugin - showing [math] (1997)
WebCatalog Hosting (1996)
orderfile headers (was: 2nd Request for help/adviceonvariable pricing) (2000)
Roundup function? (1997)
[WebDNA] Build Name for 6.1 (2008)
WebCat2 - [format thousands] (1997)
Searching for Email Address (2004)
WebCatalog Upgrade Pricing? (1997)
Size/Color Options (2002)