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 all of your work in one package, even if that does not make any sense. Not knowing why you want to encode 20k files using Base64, I cannot make very intelligent suggestions for alternates. However, I can tell you that the 48 byte limit is almost certainly related to the exact algorithm employed and the buffer sizes allocated. All Base64 lines should wind up as a multiple of 4, with a maximum size of 76 characters. I would have thought the algorithm in question would have had a maximum of 57 characters, since 76 == 57*4/3. For more information about Base64 encoding, see RFC 2045 - MIME (Multipurpose Internet Mail Extensions).There are many other packages out there that can encode files, both for the Mac and 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 can easily 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 Marquardt Designer/Resident Wirehead Toast Design800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.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 all of your work in one package, even if that does not make any sense. Not knowing why you want to encode 20k files using Base64, I cannot make very intelligent suggestions for alternates. However, I can tell you that the 48 byte limit is almost certainly related to the exact algorithm employed and the buffer sizes allocated. All Base64 lines should wind up as a multiple of 4, with a maximum size of 76 characters. I would have thought the algorithm in question would have had a maximum of 57 characters, since 76 == 57*4/3. For more information about Base64 encoding, see RFC 2045 - MIME (Multipurpose Internet Mail Extensions).There are many other packages out there that can encode files, both for the Mac and 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 can easily 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 Marquardt Designer/Resident Wirehead Toast Design800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.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:
Re:Emailer and encryption (1997)
Wierd quantities (2000)
[WebDNA] Sendmail BCC bug still exists (2015)
Setting a range in a search (1998)
Multiple Search Fields (1998)
HELP-1!!! (1998)
More on the email templates (1997)
Authorize.Net (2003)
FREE Web Server Monitor FREE (1997)
Has this happened to you? (was:Emailer Chokes on bad address) (1997)
Hiding HTML and breaking the page (1997)
Using Cookie for client specific info? (1997)
RE: Nesting [ListFiles] (1998)
Mixing and/or in searches (1998)
OT: zipcodes (2002)
Bug Report, maybe (1997)
Hello??? (1997)
Multiple cart additions (1997)
Remove me from your list immeadiately (1998)
Attn: Bug in GeneralStore example b15 (1997)