Re: bash displays strange characters after base64 decoding

Path	csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!usenet.stanford.edu!not-for-mail
From	Dennis Williamson <dennistwilliamson@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: bash displays strange characters after base64 decoding
Date	Thu, 6 Aug 2015 16:38:42 -0500
Lines	116
Approved	bug-bash@gnu.org
Message-ID	<mailman.7904.1438897127.904.bug-bash@gnu.org> (permalink)
References	<55C39D51.6010401@posteo.org>
NNTP-Posting-Host	lists.gnu.org
Mime-Version	1.0
Content-Type	multipart/alternative; boundary=047d7bd6c488db845d051cab5735
X-Trace	usenet.stanford.edu 1438897128 7354 208.118.235.17 (6 Aug 2015 21:38:48 GMT)
X-Complaints-To	action@cs.stanford.edu
Cc	"bug-bash@gnu.org" <bug-bash@gnu.org>, bash <bash@packages.debian.org>
To	Valentin Schmidt <vsch@posteo.org>
Envelope-to	bug-bash@gnu.org
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ne2jASSoj/q/+gnpiyE8QL9fVWQIsvgkpBccHECSKe4=; b=b++Dp5BpXbP1h9zqkVxSUOVehm8k8MhhEyv3bubPsCJZZRv4oCr860NW0JEKy3oogL hkvzBkoF2YHOsZZchoX0PDLJ6qvbXklPU+nh0gt4Wj/fiOxM7x+oczQiEgkXP5GhL0EH NeXKQU+IWFoDmAqNqYxEdcoyDsbfEuNrCtzI4XLtW3nIZmpBoQFqbsZkrN1FZLfZtJMe IMEI/Ug1OWWgFAjQMO7lw9gSlt2WspgwB5BXSSh/39ZiJHk4SlutmX9k5UQf8eSBF9IQ H9mBQo1pNqf2jmoG7tqSUCKlu1EQl1tybz02Vss4aQH5la0+Rzkpgd7a9XG1NvVpddNS 9voA==
X-Received	by 10.60.159.196 with SMTP id xe4mr3578935oeb.23.1438897122540; Thu, 06 Aug 2015 14:38:42 -0700 (PDT)
In-Reply-To	<55C39D51.6010401@posteo.org>
X-detected-operating-system	by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value).
X-Received-From	2607:f8b0:4003:c01::231
X-BeenThere	bug-bash@gnu.org
X-Mailman-Version	2.1.14
Precedence	list
List-Id	Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe	<https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive	<http://lists.gnu.org/archive/html/bug-bash>
List-Post	<mailto:bug-bash@gnu.org>
List-Help	<mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe	<https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref	csiph.com gnu.bash.bug:11297

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

On Thu, Aug 6, 2015 at 12:45 PM, Valentin Schmidt <vsch@posteo.org> wrote:

> From: vsch@posteo.org
> To: bug-bash@gnu.org,bash@packages.debian.org
> Subject: bash displays strange characters after base64 decoding
>
> Configuration Information:
> 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../. -I.././include -I.././lib -D_FORTIFY_SOURCE=2
> -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
> -Werror=format-security -Wall
> uname output: Linux ongakui 3.13.0-24-generic #47-Ubuntu SMP Fri May 2
> 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> Machine Type: x86_64-pc-linux-gnu
>
> Bash Version: 4.3
> Patch Level: 11
> Release Status: release
>
> Description:
> Bash displays strange characters (including command prompt) (see attached
> png file) after the execution of the base64 (GNU coreutils 8.21) command
> like described as follows:
> base64 -d base64.txt
> The aim was actually to direct the output of the base64 command into a
> file (would have been a .jpg file) but the ">decoded.jpg" was forgotten.
> Accordingly the output was directed to stdout instead. This resulted in
> the command prompt consisting of strange characters after decoding.
> Also any command entered via the keyboard resulted in strange characters
> being displayed instead of the typed characters.
> Also the output of the ls (which seems to be executed) command (as an
> example) is displayed as strange characters.
>
> Repeat-By:
> As described above.
>
>
Not a bug. Also not Bash related. You have sent control characters to your
terminal which causes it to display alternate characters.

Try entering the reset command (you'll have to do it more or less blindly).

-- 
Visit serverfault.com to get your system administration questions answered.

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: bash displays strange characters after base64 decoding Dennis Williamson <dennistwilliamson@gmail.com> - 2015-08-06 16:38 -0500

csiph-web