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.182.121.170 with SMTP id ll10mr53558905obb.12.1417367261285;
        Sun, 30 Nov 2014 09:07:41 -0800 (PST)
X-Received: by 10.140.33.229 with SMTP id j92mr5242qgj.7.1417367261260; Sun,
 30 Nov 2014 09:07:41 -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!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!h15no10816845igd.0!news-out.google.com!m4ni576qag.1!nntp.google.com!w8no3648116qac.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sun, 30 Nov 2014 09:07:41 -0800 (PST)
In-Reply-To: <m5ffcl$hvq$1@dont-email.me>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=104.169.161.149;
 posting-account=Ies7ywoAAACcdHZMiIRy0M84lcJvfxwg
NNTP-Posting-Host: 104.169.161.149
References: <8f7e0b44-14a7-4e39-8910-d8f6e553b904@googlegroups.com>
 <lywq6cn997.fsf@pushface.org>
 <2a3a193b-9ae3-421e-8017-972b926c5489@googlegroups.com>
 <m5ffcl$hvq$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f99e6781-f877-47cb-93bd-0036791be090@googlegroups.com>
Subject: Re: A matter of interest.
From: brbarkstrom@gmail.com
Injection-Date: Sun, 30 Nov 2014 17:07:41 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2109
X-Received-Body-CRC: 2914624325
Xref: news.eternal-september.org comp.lang.ada:23803
Date: 2014-11-30T09:07:41-08:00
List-Id: <comp.lang.ada>

On Sunday, November 30, 2014 11:08:06 AM UTC-5, bj=F6rn lundin wrote:
> On 2014-11-30 14:24, Austin Obyrne wrote:
>=20
> >=20
> > But surely the compiler does a bit-by-bit job ?
>=20
> no
>=20
>  Year : Integer :=3D 2014;
>=20
> will compile just as
>=20
>  YEAR : INTEGER :=3D 2014;
>=20
> and
>=20
>  YEAR           : INTEGER               :=3D 2014;
>=20
> but they are of course different when represented
> as files.
>=20
>=20
> --
> Bj=F6rn

I do not believe that a new cryptographic algorithm can be trusted
until it has been published and attacked by competent cryptanalysts.
The classic text is

Schneier, B., 1996: Applied Cryptography: Protocols, Algorithms,
and Source Code in C, John Wiley & Sons, New York, NY

If the algorithm hasn't been published, the usual term would be
"security by obscurity."  It doesn't work.

Bruce B.