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.21.1 with SMTP id h1mr2350491qab.3.1378241902358; Tue, 03 Sep 2013 13:58:22 -0700 (PDT) X-Received: by 10.49.70.138 with SMTP id m10mr100941qeu.9.1378241902329; Tue, 03 Sep 2013 13:58:22 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!j7no174372qai.0!news-out.google.com!p7ni567qas.0!nntp.google.com!j7no174366qai.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 3 Sep 2013 13:58:22 -0700 (PDT) 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 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Formatting Re-opened Ciphertext Problem. From: Austin Obyrne Injection-Date: Tue, 03 Sep 2013 20:58:22 +0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 3254 Xref: news.eternal-september.org comp.lang.ada:17091 Date: 2013-09-03T13:58:22-07:00 List-Id: Alice and Bob are the entities of a secure communications loop =96 they use= identical programs such that anything Alice encrypts in her Ada-95 program= Bob should be able to decrypt in his identical program software. This involves Alice sending her file of ciphertext after encryption of some= plaintexts as an attachment to an open email to Bob. *Alice=92s file of ciphertext is copy =91n pasted as a Word document file i= n Microsoft Word for calling later to go as the attachment to the email. Problem. When Alice encrypts something like say the word =91milestone=92 her ciphert= ext as integers is stored as a file of some 27 integers of ciphertext =96 t= hat=92s ok =96 but when she re-opens the file if ciphertext again in her gn= at 311.p editor (AdaGIDE editor) so as to make it into a Word document for = sending to Bob (which she can do ok) she finds that the spacing 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 volume of cipher= text to be copy 'n pasted as a Word document considerably which she does no= t want. The upshot is that the eventual file of ciphertext in the case of a large f= ile (of 30000 characters actually to hand) being sent to Bob as a word docu= ment is so large now because of the enlarged spacing that his editor can=92= t take it and he can only decrypt a portion of the full message (which he c= an do ok =96 but stops at 992 characters instead of 30000). All of this be= cause of the spacing in the ciphertext being 4 spaces instead of 1. Question: Can Alice control the spacing of the ciphertext by any means when= it is reopened after encrypting it initially in her AdaGIDE editor. (I hav= e 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 ciphertext reopens in the A= daGIDE editor =96 i.e. can I regulate the spacing to be just 1 space and no= t 4 spaces. Your help would be greatly appreciated. This scheme depends on being able= to solve this problem. It is a good scheme otherwise. Thanks in anticipation. Adacrypt