JJK, Thanks for the quick response, it is really appreciated. Can I ask where you picked up the syntax for this command line (familiar with the various shells and /dev/null but couldn't put this together)?
Thanks Again, Harold -----Original Message----- From: Jan Just Keijser via RT [mailto:r...@openssl.org] Sent: Monday, July 18, 2016 2:26 PM To: Lapprich, Harold (GE Aviation, US) Cc: openssl-dev@openssl.org Subject: EXT: Re: [openssl-dev] [openssl.org #4617] openssl Issue/Bug Hi, On 18/07/16 18:39, Lapprich, Harold via RT wrote: > To Whom It May Concern, > > openssl version -a: > > OpenSSL 1.0.2a 19 Mar 2015 > > built on: reproducible build, date unspecified > > platform: linux-ppc > > options: bn(64,32) rc4(ptr,char) des(idx,risc1,16,long) blowfish(idx) > > compiler: > /home/devadmin/buildserver/staging/build-output/c919/trunk-iop/host/us > r/bin/ccache > /home/devadmin/buildserver/staging/build-output/c919/trunk-iop/host/us > r/bin/powerpc-e500v2-linux-uclibc-gcc -I. -I.. -I../include -fPIC > -DOPENSSL_PIC -DZLIB_SHARED -DZLIB -DOPENSSL_THREADS -D_REENTRANT > -DDSO_DLFCN -DHAVE_DLFCN_H -DB_ENDIAN -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -mcpu=8540 -pipe -O2 > -Wall -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM > -DAES_ASM -DVPAES_ASM > > OPENSSLDIR: "/etc/ssl" > > > > OS Name, Version, Hardware platform: > > uname -a > > Linux ahmu-iop-devel 3.10.76 #1 SMP PREEMPT Fri Jul 8 11:18:12 EDT > 2016 ppc GNU/Linux > > > > > Using 'openssl' in a Linux design and since it is a command line application > it is always outputting content to the screen, for example: > > > openssl req -new -x509 -nodes -days 365 -subj > "/C=US/ST=Ohio/L=Cincinnati/O=www.ge.com/OU=AHMU-UNIT/CN=AHMU-UNIT" > -keyout start -out start > > Generating a 2048 bit RSA private key > > ...................................................................... > ...................+++ > > .............+++ > > writing new private key to 'start' > > ----- > > > Trying to find a way to prevent the output being output to 'stdout' but have > not found a parameter (can redirect to a file but the .....+ characters are > still written to the console). > > > There either has to be a missed parameter or bug exist? > This is not a bug or lacking feature. The ....+ characters are written to stderr, so if you use openssl ..... > stdout 2> stderr the characters disappear (into the file 'stderr'; use '2> /dev/null' to send then straight to bit-heaven). This depends slightly on the shell you use, BTW. The above syntax is for bash/zsh/ksh; for csh/tcsh a different syntax applies. HTH, JJK -- Ticket here: https://urldefense.proofpoint.com/v2/url?u=http-3A__rt.openssl.org_Ticket_Display.html-3Fid-3D4617&d=CwIDaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=i74Dd1YgazOdjUqZ7H6RwfJnspP534048ulHQI_l8Lg&m=hC-ePxGkl2IKC2iYTHYFk1qfc32xU_KzR5R3duyHaIM&s=G81nAuvPiu8kBUwgddPaVgh_UkoNVeOvf7Q4veAdNVo&e= Please log in as guest with password guest if prompted -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4617 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
