I believe they are VPN tunnels.
Jim Oberholtzer
Agile Technology Architects
On Jan 23, 2023, at 3:39 PM, Don Brown <DBrown@xxxxxxxxxx> wrote:
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
Thanks
Don
From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
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
<[1]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 ?
Thanks
Don
From: "Rob Berendt" <[2]robertowenberendt@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<[3]midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 23/01/2023 09:08 AM
Subject: Re: Disabled profile
Sent by: "MIDRANGE-L" <[4]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 <
[5]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.
>
> Thanks
>
> Don
>
>
>
>
> --
> This email has been scanned for computer viruses. Although MSD has
taken
> reasonable precautions to ensure no viruses are present in this email,
MSD
> cannot accept responsibility for any loss or damage arising from the
use
of
> this email or attachments..
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: [6]MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: [7]
https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: [8]MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at [9]
https://archive.midrange.com/midrange-l.
>
> Please contact [10]support@xxxxxxxxxxxxxxxxxxxx for any subscription
related
> questions.
>
>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: [11]MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [12]
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: [13]MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [14]
https://archive.midrange.com/midrange-l.
Please contact [15]support@xxxxxxxxxxxxxxxxxxxx for any subscription
related
questions.
--
This email has been scanned for computer viruses. Although MSD has taken
reasonable precautions to ensure no viruses are present in this email,
MSD cannot accept responsibility for any loss or damage arising from the
use of this email or attachments..
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: [16]MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [17]
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: [18]MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [19]
https://archive.midrange.com/midrange-l.
Please contact [20]support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.
--
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
References
Visible links
1. mailto:midrange-l@xxxxxxxxxxxxxxxxxx
2. mailto:robertowenberendt@xxxxxxxxx
3. mailto:midrange-l@xxxxxxxxxxxxxxxxxx
4. mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx
5. mailto:midrange-l@xxxxxxxxxxxxxxxxxx
6. mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
7.
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.com_mailman_listinfo_midrange-2Dl&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=x3rBwxMTlO3UcnVchBJYlkqPD8BpO91HbuZYQ_ZepUs&m=B2J2tVT4mJbc50oIcOux7O2GHy1uXiFgwxtkAtLX-aQ&s=AnOqNaPbdb9AxwrKEaxkS1FWcPUAWtmiJhuYABcXbpg&e=
8. mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
9.
https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.midrange.com_midrange-2Dl&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=x3rBwxMTlO3UcnVchBJYlkqPD8BpO91HbuZYQ_ZepUs&m=B2J2tVT4mJbc50oIcOux7O2GHy1uXiFgwxtkAtLX-aQ&s=2meXJ_iqpY5aLbbVkMsa9JaWAHG2PwtooMsBuB8r0U8&e=
10. mailto:support@xxxxxxxxxxxxxxxxxxxx
11. mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
12.
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.com_mailman_listinfo_midrange-2Dl&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=x3rBwxMTlO3UcnVchBJYlkqPD8BpO91HbuZYQ_ZepUs&m=B2J2tVT4mJbc50oIcOux7O2GHy1uXiFgwxtkAtLX-aQ&s=AnOqNaPbdb9AxwrKEaxkS1FWcPUAWtmiJhuYABcXbpg&e=
13. mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
14.
https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.midrange.com_midrange-2Dl&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=x3rBwxMTlO3UcnVchBJYlkqPD8BpO91HbuZYQ_ZepUs&m=B2J2tVT4mJbc50oIcOux7O2GHy1uXiFgwxtkAtLX-aQ&s=2meXJ_iqpY5aLbbVkMsa9JaWAHG2PwtooMsBuB8r0U8&e=
15. mailto:support@xxxxxxxxxxxxxxxxxxxx
16. mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
17.
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.com_mailman_listinfo_midrange-2Dl&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=x3rBwxMTlO3UcnVchBJYlkqPD8BpO91HbuZYQ_ZepUs&m=B2J2tVT4mJbc50oIcOux7O2GHy1uXiFgwxtkAtLX-aQ&s=AnOqNaPbdb9AxwrKEaxkS1FWcPUAWtmiJhuYABcXbpg&e=
18. mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
19.
https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.midrange.com_midrange-2Dl&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=x3rBwxMTlO3UcnVchBJYlkqPD8BpO91HbuZYQ_ZepUs&m=B2J2tVT4mJbc50oIcOux7O2GHy1uXiFgwxtkAtLX-aQ&s=2meXJ_iqpY5aLbbVkMsa9JaWAHG2PwtooMsBuB8r0U8&e=
20. mailto:support@xxxxxxxxxxxxxxxxxxxx
midrange.com
