monokal/Shellshock

Prints nothing at times

Closed this issue · 15 comments

Hi,

I came to know of your script from https://plus.google.com/+CybercitiBiz/posts/2oKJUj56SXk

It's pretty cool! Thanks!

Just that at times, when I execute the script, it prints nothing as shown in the screenshot.

clipboard01

Hi! Thanks for your kind words.

That's an odd one. Could you please check the messages folder for any files
with blank contents please? This shouldn't be the case but would explain
why you're getting random blank output.

Thanks,
Daniel.

On 26 July 2014 17:41, kaushalmodi notifications@github.com wrote:

Hi,

I came to know of your script from
https://plus.google.com/+CybercitiBiz/posts/2oKJUj56SXk

It's pretty cool! Thanks!

Just that at times, when I execute the script, it prints nothing as shown
in the screenshot.

[image: clipboard01]
https://cloud.githubusercontent.com/assets/3578197/3711662/90995f66-14e3-11e4-80a5-a89defa4faf5.png


Reply to this email directly or view it on GitHub
#1.

Well, none of the messages are blank, but I think it prints blank when trying to print Freedom. I have never coded in Ruby.. what debug statement should I add so that it also prints the file it is reading out?

Thanks. The simplest way of determining if that's the case it to simply add
a string at the top of the file in "freedom.txt" and run
"ruby shellshock.rb" until you hit it.

On 26 July 2014 17:46, kaushalmodi notifications@github.com wrote:

Well, none of the messages are blank, but I think it prints blank when
trying to print Freedom. I have never coded in Ruby.. what debug statement
should I add so that it also prints the file it is reading out?


Reply to this email directly or view it on GitHub
#1 (comment)
.

Looks like my terminal is unable to print certain types of ascii characters.. like the block asciis in Freedom. I'll close this issue as it's not related to your script. By the way, would you have an idea why my terminal wouldn't be printing those asciis? (I will google in parallel.) I am using xterm with 256 colors and tmux.

Thanks. I'd like to get this sorted though as I'd like computability across all terminals. Could you give it a try outside of tmux please?

Yes, I did try it outside tmux and still I don't see the output. Even a simple cat of that message.txt doesn't output anything. I am using tcsh shell in xterm. What shell/terminal are you using? Strangely, haven't yet come across an issue like this on google yet..

Looks like it has to do with printing unicode chars. http://stackoverflow.com/questions/12649896/why-doesnt-my-terminal-output-unicode-characters-properly

Well.. my terminal apparently supports UTF-8 as I see that being set when I type locale.

Hmm I'm not familiar with tcsh but I'll look in to what might be causing
the issue. Thanks for your input. As a temporary fix you can simply delete
freedom.txt and Shellshock will continue to work as normal.

On 26 July 2014 18:01, kaushalmodi notifications@github.com wrote:

Yes, I did try it outside tmux and still I don't see the output. Even a
simple cat of that message.txt doesn't output anything. I am using tcsh
shell in xterm.


Reply to this email directly or view it on GitHub
#1 (comment)
.

Yeah, that's what I did, can live without those asciis :)

Cool. Be sure to contribute back if you generate any cool graphics! :) The
current selection is a very small starter sample but I'd really like a
large selection.

On 26 July 2014 18:07, kaushalmodi notifications@github.com wrote:

Yeah, that's what I did, can live without those asciis :)


Reply to this email directly or view it on GitHub
#1 (comment)
.

Found the culprit! It's the terminal fonts! I have Inconsolata font as default and it doesn't have enough glyphs to show those characters. I like the font too much to change it, but I am curious.. what's your terminal font?

Ah, well done pal. I'm personally using "14pt Inconsolata for Powerline" on
iTerm (the screenshot on README). I've also tested it on Ubuntu 14.04 with default Terminal config.

On 26 July 2014 18:16, kaushalmodi notifications@github.com wrote:

Found the culprit! It's the terminal fonts! I have Inconsolata font as
default and it doesn't have enough glyphs to show those characters. I like
the font too much to change it, but I am curious.. what's your terminal
font?


Reply to this email directly or view it on GitHub
#1 (comment)
.

Finally!

Tip from here helped.. to use uxterm instead of xterm and I switched to Source Code Pro for Powerline.

clipboard01

Ahhhh! Good work. I'm glad you like my little weekend script hehe

It's funny; I never needed to have unicode support in my terminal. And doubt I still need unicode support. But still I desperately needed to figure out how to show unicode correctly (just for knowledge, just in the case I need it in future :) )