From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.224.13.136 with SMTP id c8mr1919691qaa.0.1378282840904; Wed, 04 Sep 2013 01:20:40 -0700 (PDT) X-Received: by 10.49.104.83 with SMTP id gc19mr25899qeb.12.1378282840880; Wed, 04 Sep 2013 01:20:40 -0700 (PDT) Path: border1.nntp.dca3.giganews.com!border2.nntp.dca3.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!j7no230716qai.0!news-out.google.com!p7ni567qas.0!nntp.google.com!j7no230714qai.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 4 Sep 2013 01:20:40 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=86.173.125.168; posting-account=pmkN8QoAAAAtIhXRUfydb0SCISnwaeyg NNTP-Posting-Host: 86.173.125.168 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <4b7a89a5-43c1-40f7-a7b6-0c57d0c58785@googlegroups.com> Subject: Re: Formatting Re-opened Ciphertext Problem. From: Austin Obyrne Injection-Date: Wed, 04 Sep 2013 08:20:40 +0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Original-Bytes: 5740 Xref: number.nntp.dca.giganews.com comp.lang.ada:183275 Date: 2013-09-04T01:20:40-07:00 List-Id: On Wednesday, September 4, 2013 3:36:09 AM UTC+1, Dennis Lee Bieber wrote: > On Tue, 3 Sep 2013 13:58:22 -0700 (PDT), Austin Obyrne declaimed the following: > >*Alice=92s file of ciphertext is copy= =91n pasted as a Word document file in Microsoft Word for calling later to= go as the attachment to the email. > Why? I presume it is a text file... W= hy not just attach the text file to the email... Who knows what Word might = do to the contents -- not to mention having to extract the cipher text at t= he other end before reversing the process. (Especially as "Word document fi= le" encompasses some four or five variants: Word 6 [I think even Word 2010 = has stopped supporting that format], Word between v6 and 2007 [proprietary = binary format], RTF, and the ZIPped XML format used since Word 2007). Word = expects to operate on paragraphs, not plain text. >Problem. > >When Alice e= ncrypts something like say the word =91milestone=92 her ciphertext as integ= ers is stored as a file of some 27 integers of ciphertext =96 that=92s ok = =96 but when she re-opens the file if ciphertext again in her gnat 311.p ed= itor (AdaGIDE editor) so as to make it into a Word document for sending to = Bob (which AdaGIDE is an Ada IDE developed for educational usage (Air Force= Academy). It is optimized to display formatted Ada source files of (relati= vely) small size (since GNAT works with separate spec/body files -- source = files from compilers that allow multiple spec/body/packages in one file hav= e to be "chopped" to work in the GNAT world -- so an editor doesn't have to= work with significant sized files) >she can do ok) she finds that the spac= ing between the integers is now four spaces between each integer instead of= what she would like to be just 1 conventional space. This increases the vo= lume of ciphertext to be copy 'n pasted as a Word document considerably whi= ch she does not want. So... What character was being used in the program to= separate these integers? If the program is separating each integer with a = TAB character, then seeing four spaces is quite likely the correct behavior= . Or could these integers be written using a formatted write specifying a f= ixed width, which is wider than that needed for the integer. > >The upshot = is that the eventual file of ciphertext in the case of a large file (of 300= 00 characters actually to hand) being sent to Bob as a word document is so = large now because of the enlarged spacing that his editor can=92t take it a= nd he can only decrypt a portion of the full message (which he can do ok = =96 but stops at 992 characters instead of 30000). All of this because of t= he spacing in the ciphertext being 4 spaces instead of 1. > I'm pretty sure= even W9x Notepad could handle a 30kB file -- so just what type of expansio= n is this "ciphertext" inflicting... Even a 10:1 expansion is only 300kB, w= hich is in the noise. But again, this shouldn't matter... Just send to ciph= ertext file itself as the attachment, and feed that to the decipher process= directly -- don't try loading into a text editor just to be copied into a = Word document for sending, only to reverse that on the other end. >Question= : Can Alice control the spacing of the ciphertext by any means when it is r= eopened after encrypting it initially in her AdaGIDE editor. (I have looked= at the tools options in AdaGIDE =96 =91interval=92 setting? Change it to 1= But no effect) > >In other words can I somehow format the way the cipherte= xt reopens in the AdaGIDE editor =96 i.e. can I regulate the spacing to be = just 1 space and not 4 spaces. > >Your help would be greatly appreciated. T= his scheme depends on being able to solve this problem. It is a good scheme= otherwise. > >Thanks in anticipation. > >Adacrypt -- Wulfraed Dennis Lee B= ieber AF6VN wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/ Hi again Dennis, Tried that with two small files - works beautifully - many,many thanks. Don't know where I got the idea that Ada Language file are incompatible wit= h ordinary things like 'Send' and 'Save' directly to them and instead need = to go through the AdaGIDE editor. Anyway its problem solved so far - going to try some large 'mega' files nex= t to see if the same magic is ok. Many thanks again. Regards - Austin