[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bash, echo or openssl bug?

From: tcadmin
Subject: bash, echo or openssl bug?
Date: Tue, 3 Jan 2012 14:33:27 +0100

Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL 
-DHAVE_CONFIG_H   -I.  -I../bash -I../bash/include -I../bash/lib   -g -O2 -Wall
uname output: Linux buildserver 2.6.27-11-server #1 SMP Wed Apr 1 21:34:13 UTC 
2009 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu

Bash Version: 3.2
Patch Level: 39
Release Status: release

        i dont know if the bug is a bash bug or openssl or echo, but when i 
echo a string and pipe it to openssl, the 
output comes on the same line as the prompt instead of a new line. it makes the 
output hard to read because it is prepended 
to the prompt text, e.g. address@hidden: ~$

        1. run the following code in bash terminal:
echo OHBjcWNLNGlQaVF5 | openssl base64 -d

        2. the output in the bash terminal looks like this:
address@hidden: ~$

        3. the output SHOULD look like this:
address@hidden: ~$

reply via email to

[Prev in Thread] Current Thread [Next in Thread]