/dev/urandom

[realdreams]

after executing #more /dev/urandom the encoding in securecrt gets messed up, even the prompt turns into unreadable characters

$ more /dev/urandom 
w~R(Tq~-S}v
Q‘q=j.m+޻dW3QEn(3<S

                        XY8["8z!EV+dcR~R|eV,8{__Yg%iU
G*+ߘ+G|N/Ky(,-+[/ W1Ti++V+

                                   ¯kV[z3^_#4$'c&3yC6s#
vAzAvK65gkBׅ!ycL%|
%)        ͫ:Mن                                         Qޟ5.T
Ea^d8Ha'3eacinA[gXO".j6ߛs    *DpDE~t=6q    ri:`l./腨<S8)!_W]b҇)$
OceFZhŐh2mM%TTv4NI
    oLl
%^L:1mbl7m--More--(0%)
jvToC!d$r<`uq@x6L
-More--(0%)
JF;e 3$+8AXVwڬB
   --More--(0%)
                X!gJ[{ϧAyg+_D\-/~+81@좞K
+Vf`'.|S.9H=7'cQ^+
gIU-˟3h
 V}}MW~-J䘁e[Kz/
.2eѬ!W	+!AI
               XbZzi_)[+PB?,猊-P
                                +zM87,[[g

                                           ;]/S8^:•6_<A)_[6H,'hi&ZI*Cd(E-I)^+?
$;d
V#e

         <++^L+&|e+C! ;B++7 8(+D?E_D]*d^-
"A:2{+_
Dz70=n9"?VR@3
             vFVv-
                   #ZWx

                        tS5)DJǐ+|oA-y,Ըfe
^TX88?FedKZ${[tf٦	Nc"T5PI+6O;_+d++SgM,^

         =g\+c  6#
                   K9úD+]+c<;[)-'=+#Ac
L_-+V+>K=ez
                [+ENzcV++W:      HEM8|GYW15,y                               -iH>НCR9(=iǶ+(]

_Sb-Bc/QH+%-(<y|M4Q+9G]hXH~iא9DU!f[O|H

                                           +

                                             +e#gҹa-ҿ+56

                                                            0^bSL.Y{Cd[7+[ed+a_d-_+++edge]$ 
[ed+a_d-_+++edge]$

and
#openssl rand 128
the result can't be displayed properly, the command prompt rewrites the output on the same line.

[hostname]$  openssl rand 128
h(*ڇ

     b}'!z&LISG	U>[hostname]$

xterm, UTF-8 encoding for both

[rtb]

Hi realdreams,

The issue you are seeing is a result of non-printing characters that are in the data you are displaying in the SecureCRT terminal window.

The issue where your prompt is no longer legible is due to a character that tells SecureCRT to enter graphics mode. This can be resolved by selecting Reset from the Edit menu.

I have also created a feature request in our SecureCRT enhancement database to add an option to ignore the escape sequence to enter graphics mode. Should we add this feature in the future, we will post to this forum thread.

If you would like to be notified directly, please complete and submit the form at the following location:

Submit Feature Request

[SystemsJoe]

Originally Posted by realdreams

after executing #more /dev/urandom the encoding in securecrt gets messed up, even the prompt turns into unreadable characters

The exact same thing happens on a real VT100 and various emulators.

The problem is that one or both of the 7-bit character sets get changed to something other than US-ASCII, such as the VT100 line-drawing set. I use a csh alias to reset the terminal in case like these.

• Escape Open-Paren B = set GL to US-ASCII
• Escape Close-Paren B = set GR to US-ASCII
• reset = Unix/Linux command that sends other escape sequences

reset-vt100 printf "\033(B\033)B";reset

-Joe

[toloughlin]

Even easier:

Ctrl+v Ctrl-o <enter>