Re: hiding source from view from customer

I know ultimately there are probably other ways to prevent this from

architecture concept... but just if it had to.. .is there a way?

I'm still not clear on why the source needs to be available, but assuming
it's an application dependency and knowing/acknowledging that this might be
a case of overkill, you could always encrypt the source in compiled objects
as Jon points out and then use various system APIs to access the debug
source within the debug session (to meet the application needs). This does
have the exposure, depending on how implemented, of having the encryption
key possibly on the system though there are ways to make key determination
a real challenge.

Bruce

On Thu, Feb 27, 2020 at 11:04 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

You've answered your own question I think Jay.

The whole point of encrypting the source in compiled objects is to allow
you to do just this.

When the program is created you specify the encryption key and protect
the source by the simple expedient of not supplying the key to the client.

Should you even need to debug the program in their production environment
your staff supply the key when firing up the debug session and the source
is visible during that debugging session and _only_ during that debugging
session.

On Feb 27, 2020, at 10:04 AM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx>

wrote:

so i know you can encrypt source from being debugged on on object...

but what if a source member is required to be shipped to the customer

BUT

it contains proprietary code? How can it be protected from view?

I know ultimately there are probably other ways to prevent this from

design

architecture concept... but just if it had to.. .is there a way?

tia

jay
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
Thanks and Regards,
Bruce
931-505-1915