comp.lang.ada
 help / color / mirror / Atom feed
From: Austin Obyrne <austin.obyrne@hotmail.com>
Subject: Re: Outrageous Thoughts on Ada Compilers.
Date: Thu, 25 Feb 2016 08:37:18 -0800 (PST)
Date: 2016-02-25T08:37:18-08:00	[thread overview]
Message-ID: <c67795ee-f64f-4591-af52-ea3e062d7f28@googlegroups.com> (raw)
In-Reply-To: <ly1t81m8vp.fsf@pushface.org>

On Thursday, February 25, 2016 at 9:34:04 AM UTC, Simon Wright wrote:
> Austin Obyrne <austin.obyrne@hotmail.com> writes:
> 
> > A point I want to establish is that - reference the compiler - no
> > matter how it is done and no matter what langauges are used to
> > complete it all of these languages use 'ASCII' as their encryption
> > domain - if I can then somehow access the compiler sourcecode I can
> > customise a unique compiler for my own exclusive use by encrypting a
> > private version that I can ahare with another entity having made a
> > secure delivery to that person of the modified compiler.
> 
> Months ago I provided you with source code demonstrating that your
> woefully inefficient encryption could be used on any input, including
> binary; so ASCII is irrelevant.
> 
> You could certainly produce a compiler for your exclusive use; it might
> be a copyright violation (not in the case of GNAT), but you'd be very
> unlikely to be found out. You could encrypt the source, and/or the built
> compiler, and distribute the result; in the case of GNAT, the licensing
> terms would oblige you to provide the other entity with the source as
> well as the compiler. For other compilers, the legality would depend on
> the copyright/licensing status of the source material.
> 
> > Do you know how to access the compiler sourcecode?
> 
> For GNAT, yes; otherwise, no.

Hi Simon,

I realise I am opening a massive can of worms here and I cannot even think of defending any thing that experienced Ada designers such as yourself bring up. 

But there is no need to do anything just yet.

I have a powerful encryption program called "ShuttlePads" that can encrypt anything that emanates from ASCII.

*Claim.
(In the present context)

Every compiler uses ASCII as its eventual output domain i.e. the eventual compiler source code is some combination of the 95 elements of ASCII.

*I can encrypt these to form a customised version of the parent compiler.

I can then manage this with another entity to create a unique loop for our sole use.

There is no need to go back to machine code??


<Do you know how to access the compiler sourcecode?
<For GNAT, yes; otherwise, no.

That alone may be sufficient to disable the compil;er in question.??

AOB 

 

  reply	other threads:[~2016-02-25 16:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 16:54 Outrageous Thoughts on Ada Compilers Austin Obyrne
2016-02-23 17:03 ` Pascal Obry
2016-02-23 18:52   ` Nasser M. Abbasi
2016-02-23 19:10   ` Austin Obyrne
2016-02-23 22:10   ` Niklas Holsti
2016-02-24  8:36     ` Austin Obyrne
2016-02-24  8:41       ` MM
2016-02-25  9:34       ` Simon Wright
2016-02-25 16:37         ` Austin Obyrne [this message]
2016-02-25 18:50           ` MM
2016-02-25 18:13         ` Austin Obyrne
2016-02-25 18:29           ` MM
2016-02-28  2:20 ` Luke A. Guest
2016-02-28  8:55   ` MM
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox