Why are there LFs in my base64? Post: 302397048

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Why are there LFs in my base64? Post 302397048 by SilversleevesX on Saturday 20th of February 2010 02:34:22 PM

02-20-2010

Registered User

Why are there LFs in my base64?

And is there a good way of taking them out?

I've been playing around a bit with using b64 to embed images in HTML (and trying to stay within the spec). I've noticed that with openssl's base64 encoder, the output files have newline characters @ every 65th column or so. This renders them useless, at least in Firefox and SeaMonkey (where this method usually works). After pasting the base64 from the output file into an HTML document, and adding the appropriate HTML tags, instead of a visible image I get a broken thumbnail. I already know why this is, having had some user-end experience with base64 (before either Outlook or Netscape knew how to decode it on the fly). My perception, phrased as a rule-of-thumb for the benefit of some who might argue its finer points, has always been the following:

Quote:

Originally Posted by Code Gods of the 1990s

Base64 encoding must be one continuous code stream or else it is invalid.

So what happened? Did someone find an application of this particular encoding where broken streams were more useful? Or even crucial?

At any rate, a sed or awk one-liner seems appropriate here. Anyone have a good one for this situation? One to remove newline characters?

BZT.

Last edited by SilversleevesX; 02-20-2010 at 03:40 PM.. Reason: Syntax (English, not code)

SilversleevesX

View Public Profile for SilversleevesX

Find all posts by SilversleevesX

7 More Discussions You Might Find Interesting

1. Programming

gunzip and base64 decode a string

I am writing a C program to get messages from a JMS queue into a string variable and then write them to a database. The messages are compressed (gzip) and encoded (base64), so I need to be able to perform gunzip and base64 decode inside the C. I don't want to write any of the messages to file so...

2. UNIX for Dummies Questions & Answers

I'm looking for someone who have Base64 binary

I need to install the base64 encryption method on a UNIX machine under AIX5.2. I've received a tar file but it is only C source , can you help me please. (sending me a binary base64 or to compile my source) Thanks by advance

3. UNIX for Dummies Questions & Answers

not able to run base64 exe

Hi, I have copied base64.exe under base64-1.3 folder and i am trying to run base64.exe from another folder called Request. But i am getting the following error message. mga.ksh: base64: not found Please let me know how to execute the base64.exe from a directory where it is not installed. ...

4. UNIX for Dummies Questions & Answers

mailx saved messages are unreadable (base64)

I am trying to parse emails sent from a blackberry. I am using fetchmail to download email through IMAP from my exchange server and then forward to local Linux mail. (This part works fine.) When viewing and saving messages sent as plain text from Outlook, everything works fine. However, when...

5. BSD

LFS-like thing, but with *BSD?

Hi, do you know, is there any thing like Linux From Scratch, but for a BSD operating system? A tutorial or guide to learn (and build) the system inside out? Would be pretty cool IMO. :D Blackbird

6. UNIX for Beginners Questions & Answers

Ldapsearch returning base64 encoded results

So my ldapsearch works great, except for some results I found today. My search is: /usr/lib64/mozldap/ldapsearch -T -h 10.1.1.1 -p 3891 -D "uid=datapower,ou=People,dc=blah,dc=com" -w xxxxxx -b "ou=Certs,dc=blah,dc=com"...

7. Shell Programming and Scripting

Base64 conversion in awk overlaps

hi, problem: output is not consistent as expected using external command in AWK description: I'm trying to convert $2 into a base64 string for later decoding, and for this when I use awk , I'm getting overlapped results , or say it results are not 100% correct. my code is: gawk...

LEARN ABOUT OSX

base64

base64(1)						    BSD General Commands Manual 						 base64(1)

NAME

     base64 -- Encode and decode using Base64 representation

SYNOPSIS

     base64 [-d | -h | -v | -D] [-b count] [-i input_file] [-o output_file]

DESCRIPTION

     base64 encodes and decodes Base64 data, as specified in RFC 4648. With no options, base64 reads raw data from stdin and writes encoded data
     as a continuous block to stdout.

OPTIONS

     The following options are available:
     -b count
     --break=count	  Insert line breaks every count characters. Default is 0, which generates an unbroken stream.

     -d
     --debug		  Print verbose log messages during processing.

     -D
     --decode		  Decode incoming Base64 stream into binary data.

     -h
     --help		  Print usage summary and exit.

     -i input_file
     --input=input_file   Read input from input_file.  Default is stdin; passing - also represents stdin.

     -o output_file
     --output=output_file
			  Write output to output_file.	Default is stdout; passing - also represents stdout.

     -v
     --version		  Print build version and exit.

SEE ALSO

     openssl(1), wikipedia page <http://en.wikipedia.org/wiki/Base64>, RFC 4648 <http://tools.ietf.org/html/rfc4648>

Mac OS X 10.7							 February 8, 2011						     Mac OS X 10.7