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.236.13.105 with SMTP id a69mr25077862yha.16.1418635855254;
        Mon, 15 Dec 2014 01:30:55 -0800 (PST)
X-Received: by 10.140.84.11 with SMTP id k11mr60qgd.37.1418635855220; Mon, 15
 Dec 2014 01:30:55 -0800 (PST)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!w8no7921931qac.0!news-out.google.com!r1ni52qat.1!nntp.google.com!s7no7430763qap.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Mon, 15 Dec 2014 01:30:54 -0800 (PST)
In-Reply-To: <lyvble0ydo.fsf@pushface.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=5.80.153.30;
 posting-account=pmkN8QoAAAAtIhXRUfydb0SCISnwaeyg
NNTP-Posting-Host: 5.80.153.30
References: <1a2fea61-bcc1-43a9-b6e3-edf474308402@googlegroups.com>
 <lyvble0ydo.fsf@pushface.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <10b43460-09db-4fb1-9a68-4555ce57811b@googlegroups.com>
Subject: Re: Ada Connections to this Crypto.
From: Austin Obyrne <austin.obyrne@hotmail.com>
Injection-Date: Mon, 15 Dec 2014 09:30:55 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Xref: news.eternal-september.org comp.lang.ada:23994
Date: 2014-12-15T01:30:54-08:00
List-Id: <comp.lang.ada>

On Sunday, December 14, 2014 8:28:36 PM UTC, Simon Wright wrote:
> Austin Obyrne <austin.obyrne@hotmail.com> writes:
>=20
> > I have been harassed by some readers with claims that there are ways
> > by which 'any' data can be called (whatever that means)and encryption
> > will still work.  They seem to be saying that this is done by
> > user-defined enumeration types that can be used instead of ASCII or
> > Latin-1.
>=20
> I rather think I take offence at that. You imply that the program I
> wrote using your crypto to encrypt/decrypt a ZIP file (which is anything
> but Latin-1 text!) was bogus.
>=20
> :plonk:

Clearly, what I have suggested earlier is already being done indirectly by =
the other key-sets in every crypto scheme so it is not to be expected that =
using customized "Information Interchange" (Using the extract from ASCII) h=
as any erstwhile latent benefits.=20

I am more interested in your take on using Sequential_IO (being advocated t=
o me) instead of my preferred Text_IO which is totally adequate as it stand=
s.

What really puzzles me is the inference that using sequential_IO for which =
I would have to create crypto instances has extra *cryptographic properties=
 that will enable any data type to be be encrypted.  I don't think the peop=
le saying this realise that reading in data is very, very easy by many meth=
ods whereas encrypting it unbreakably after you have got it in is very, ver=
y difficult and changing the method of reading it in seems to be the undoin=
g of an already  very robust current system.

I would be grateful for your opinion on this because a number of people see=
m to be mixing up the CS with the Crypto. Nothing one does with the method =
of reading in data for encryption will make it easier to encrypt.

adacrypt