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 autolearn=unavailable autolearn_force=no version=3.4.4 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!gegeweb.org!usenet-fr.net!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Wed, 11 Dec 2013 15:53:58 +0100 From: "G.B." User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Binary versus text and compiler versions, was: Re: Will Ada-95 Programs Written in MS Windows Run in MacOS and Linux Without Some Tweaking. References: <1d445f04-b670-444f-9858-55da271fe17a@googlegroups.com> <2b6dc37f-4aa6-4c18-be59-8c09f6f37f01@googlegroups.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <52a87c86$0$6659$9b4e6d93@newsspool2.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 11 Dec 2013 15:53:59 CET NNTP-Posting-Host: d73a8607.newsspool2.arcor-online.net X-Trace: DXC=gDj=X3JW\4oEB;5>eE0T7mA9EHlD;3Ycb4Fo<]lROoRa8kFjLh>_cHTX3jmVCA87V7MT5a X-Complaints-To: usenet-abuse@arcor.de Xref: news.eternal-september.org comp.lang.ada:17959 Date: 2013-12-11T15:53:59+01:00 List-Id: On 11.12.13 09:35, Dmitry A. Kazakov wrote: > On Tue, 10 Dec 2013 23:08:40 +0000 (UTC), Simon Clubley wrote: > >> On 2013-12-10, Randy Brukardt wrote: >>> >>> But if I was writing this sort of code, I wouldn't worry about line endings >>> at all, and simply encrypt the file as binary data, using Stream_IO to read >>> it in and out. >> >> Thank you. That's one of a number of things I don't understand about this. >> >> A serious encryption tool is going to treat the input as a opaque stream of >> bytes not as text. I'd think encryption will be processing a stream of bits, no? What's a byte and why or how should the dissection of the stream into bytes be fine whereas a textual representation should not? Units of 2**(n*8) may be a good choice for some algorithms written for n*8-bit hardware, if it's not using signs. Anyway, a serious attempt at encryption requires, I guess, a SINA box or some such. > That depends. I remember porting early versions of PGP to SysV and VMS, > back in early 90's. It was all about text files which must have been > converted, recoded etc in order to be readable. Indeed, pieces of data and pieces of text are isomorphic, e.g. by way of Base64 : Bits -> Text. The issue if binary vs text thus seems one of practicality, not one of encryption? Text is sometimes seen as more robust in the presence of old software that has char caused MSB problems. So, given PGP has ascii armored coding, in support of stone aged transport layers, why not just require that encryption start at 7bit data units? (This restriction helps keeping faulty produces in place, and it allows continuing the ASCII caused destruction of well educated text processing. ;-)