× 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.

Thanks Jim,

I am not following how your customers are using internal addresses ?

Your customers are using AWS servers and connecting using sftp ?

If you are using internal addressing do you have vpn's or site to site
tunnels or how are you using internal addresses ?

Just curious



From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
Cc: "Don Brown" <DBrown@xxxxxxxxxx>
Date: 23/01/2023 12:08 PM
Subject: Re: Disabled profile

Should be but it depends on how that connection is set up. We have
customers doing this all the time but they are all internal addresses.

On Sun, Jan 22, 2023 at 7:53 PM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
Thanks Rob,

Ok I can now see many PW entries in the audit journal.

This is obviously a brute force attach trying to identify a log on.

The system has ssh (port 22) open to allow sftp from an application
running on AWS

SFTP is using user name and password as that is what the provider wanted.
Yes it could be better, maybe this will provide some reasons to change.

Need to get the firewall guys to lock this down to the AWS address,
presuming that the application running on AWS would have a single outgoing

IP address ?



From: "Rob Berendt" <robertowenberendt@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"
Date: 23/01/2023 09:08 AM
Subject: Re: Disabled profile
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>

Can you look at the audit journals again but instead of security look for
changes to the user profile object. We had a recent thread on this. The
person was able to nail down the job, program, and IP address.

On Sun, Jan 22, 2023 at 5:44 PM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I am trying to investigate how a profile became disabled.

This is a 7.3 system and the audit journal does not include *SECURITY

In the history log I can see the profile became disabled at 00:16:58 on
Saturday morning.

Thee were no log entries for invalid password (CPF2234).

There is noting related in the system operator message queue.

This is the first time this has happened.

The profile that was disabled is only used for database access from a
Linux system running PHP and accessing the IBMi database

The system is using the iACS ODBC driver to connect. Would there be logs
on the Linux box ?

Any suggestions appreciated.



This email has been scanned for computer viruses. Although MSD has taken
reasonable precautions to ensure no viruses are present in this email,
cannot accept responsibility for any loss or damage arising from the use

this email or attachments..
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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@xxxxxxxxxxxxxxxxxxxx for any subscription related

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-2023 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.