Re: Change debug encryption on a program? -- MIDRANGE-L

Subject: Re: Change debug encryption on a program?
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Wed, 7 Mar 2018 18:05:02 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 2018-03-07 1:32 PM, Mark S Waterbury wrote:

Also, if you ship code compiled with DBGVIEW(*ALL) or DBGVIEW(*LISTING) and a DBGENCPWD("password"), any user with *ALLOBJ can apparently issue STRDBG for that object, and they can "see" the source views without having to enter the password ...

When compiled with DBGVIEW(*LIST) and DBGENCKEY(password), my experience is that even with *ALLOBJ, I can't see the listing view without specifying the password.

I agree that with DBGVIEW(*ALL), if the source is on the system, anyone with authority to the source can see the source debug view.

Follow-Ups:

Re: Change debug encryption on a program? , David Gibbs
Re: Change debug encryption on a program? , Mark S Waterbury

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.