× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. November 2004

RE: security hole in interactive sql call statement?

>Oh, well, we would just have to take strsql away from programmer for
now.

How will you do that? I assume from your statements that you have two
machines (or at least 2 lpars) one for dev and one for production. On
your dev box do a WRKRDBDIRE command and define a remote database for
production, call it, say, "PRODUCTION" for lack of a better name. 

Then, ON THE DEV BOX, start sql. In STRSQL issue the following:

CONNECT TO PRODUCTION
CALL QCMDEXC("AnyCommandWithOutAScreen", 0000000999.00000)

And see what happens. I would _guess_ that this is cought as a remote
database request, same as ODBC, but I don't know, since it's iSeries to
iSeries. 

Locking down production isn't always as easy as it appears.

-Walden

------------
Walden H Leverich III
President & CEO
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.