Why do these base64 encoding outputs differ, given the same input string?

Question

When getting a bas64 encoded string from the same input string I find that JavaScript, Groovy, and Go have the same result, but GNU base64 is slightly different. Why is that?

JavaScript (nodejs v0.10.33):

new Buffer('Laurence Tureaud is Mr. T').toString('base64');
TGF1cmVuY2UgVHVyZWF1ZCBpcyBNci4gVA==

Groovy (2.3.7 on Java 8):

'Laurence Tureaud is Mr. T'.bytes.encodeBase64().toString()
TGF1cmVuY2UgVHVyZWF1ZCBpcyBNci4gVA==

Go (1.4):

b64.StdEncoding.EncodeToString([]byte("Laurence Tureaud is Mr. T"))
TGF1cmVuY2UgVHVyZWF1ZCBpcyBNci4gVA==

GNU base64 (GNU coreutils 8.12.197-032bb with UTF-8 term charset):

echo 'Laurence Tureaud is Mr. T' | base64
TGF1cmVuY2UgVHVyZWF1ZCBpcyBNci4gVAo=

If you decode the results you'll see that the GNU base64 has a new line character at the end. (You get 'Laurence Tureaud is Mr. T\n' where \n is a new line. — Daniel Tung, May 07 '15 at 13:32

score 7 · Accepted Answer · edited May 07 '15 at 13:40

7

echo 'Laurence Tureaud is Mr. T'

Echo adds a newline after the string.

Try the following to remove the newline:

echo -n 'Laurence Tureaud is Mr. T' | base64

And you get TGF1cmVuY2UgVHVyZWF1ZCBpcyBNci4gVA==

edited May 07 '15 at 13:40

Daniel Tung

427
2
14

answered May 07 '15 at 13:31

Roger Gustavsson

1,689
10
20

1

Ah, yes, that was it indeed. The following matches: printf 'Laurence Tureaud is Mr. T' | base64 – user605331 May 07 '15 at 13:37
@user605331 If this worked for you, please mark this as the correct solution. Thanks! :) – Daniel Tung May 07 '15 at 13:39
1

SO won't allow until 5 minutes has passed. I tried. – user605331 May 07 '15 at 13:40
@user605331 Sorry, didn't mean to rush you. Just wanted to put a little reminder. I added a little more to this answer for future reference! – Daniel Tung May 07 '15 at 13:41

score 4 · Answer 2 · answered May 07 '15 at 13:32

4

All output is the same.

The only difference is that bash appends a newline (\n) to the end when using echo. Therefore the is an additional character appended to the output (the character = is only a padding in base64).

answered May 07 '15 at 13:32

Uwe Plonus

9,803
4
41
48

Why do these base64 encoding outputs differ, given the same input string?

2 Answers2