Hi Guys,
I have FTP problems, just run an EtreCheck to see if there are any problems. Could someone help?
Yes, Malwarebytes installed since it is the "only antivirus we need"
And yes, the Malware bytes VPN is not active, so why would it mess up my internet since I'm not paying for the extra to have it working? Doesn't make sense to me ...
That Samsung Drive is for my FCPX work 4K files storage library
(have to delete some files on that), and was formatted on my old Imac.
The Mac Studio is brand new, using it for 2 months now, no back-up as for now.
Attached a EtreCheck Full Disk Access scan.
I use FTP in Adobe Dreamweaver to upload files to my websites. The problems started some weeks ago, sometimes de FTP access works and sometimes not. I have a dedicated server where I host my websites, but the company off course say that it has to be some problem on my side ...
That's why the EtreCheck to see if there are any problems with my machine.
Just remember something that could explain the configuration profile thing. I recently switched from an old 2017 Imac to my new Studio. On that old Imac I was booting from a T7 2Tb SSD.
When I did set up the studio for scratch I quickly connected that T7 2TB SSD on to my studio to get some things that I forgot to copy into the new Studio. Maybe that could explain why there is a registration of profiles but since it is not connected anymore the configuration profiles in blank and not to be found?
That still doesn't explain the problems with the FTP ...
MrHoffman wrote:
It is quite literally older than IP, having gotten started on NCP, and then being adapted to the exceedingly permissive networks of early-times IP.
I remember once I was foolhardy enough to release an app with FTP support. Right away, I had someone trying to use it with an OpenVMS server. 😄
etresoft wrote:
MrHoffman wrote:
It is quite literally older than IP, having gotten started on NCP, and then being adapted to the exceedingly permissive networks of early-times IP.
I remember once I was foolhardy enough to release an app with FTP support. Right away, I had someone trying to use it with an OpenVMS server. 😄
How weird. That combination is still possible to encounter too, and the vendor is still creating and selling new x86-64 versions, and a second vendor also offering their own IP stack for the platform. One of the very few (only?) servers with IP networking as a separately-installed kit. With FTP. And FTP and modern networking still causes issues, same as everywhere.
So, deleting Malwarebytes will resolve all my FTP problems magicly?
Anything else that you could have seen in that report that you would like to enlighten us?
Yes, the FTP problems where there before I installed it.
I have the banks App on my iPhone but for some money transfers I have to use my desktop with web access.
Sorry, my bad.
Warsaw is part of a security check for the Bank of Brazil that has to be installed to be able to access my account.
Uninstalled the Malwarebytes with the Uninstaller, emptied trash, restarted, run a new EtreCheck and yes the Configuration profile warning is still there ... but I have none installed. FTP still not working.
<< Configuration profile warning is still there >>
Please change
Settings > Pprivacy & Security > Full Disk access...
...to allow Etrecheck to have "Full Disk Access" to uncover what that might be.
tomniama wrote:
Warsaw is part of a security check for the Bank of Brazil that has to be installed to be able to access my account.
I am not familiar with Warsaw either, did you experience the same trouble before 11/27 when it was installed. The reoccurring crashes of that process is not a good sign where it has now crashed 6 times including today. From the little bit of research I did find it is a bank installed process that would likely be identified as a Configuration Profile. Do you have an iPhone where you can access your account with their app? I suspect on the Mac you are using web access where they feel the need to provide some kind of internet protections.
etresoft wrote:
What kind of FTP problems are you having?
FTP is not included in the operating system any more. So by default, any FTP problems are 3rd party software problems.
Furthermore, FTP is crazy complicated. There are many different versions. FTP was designed many, many years ago.
It is quite literally older than IP, having gotten started on NCP, and then being adapted to the exceedingly permissive networks of early-times IP.
It is completely unsuitable for the modern internet. And I'm not just talking about potential security problems. It's very design and how it makes connections is unique.
The first of the two connections (from a local ephemeral port to remote TCP port 21) provides control functions.
The second connection (from TCP port 20 to an ephemeral port) is used for data transfer and that second and new TCP connection then either inherently slams into one of the local firewalls (in active mode), or inherently slams into one of the remote firewalls (in passive mode), depending on the FTP data transfer mode selected (active or passive).
The only way this second connection doesn’t get blocked in a modern network with firewalls at network perimeters is if the source network firewalls decode the control traffic and pre-open the second local port (active) or if the target network firewalls decode the control traffic and pre-open the second port (passive).
This FTP protocol connection design is nearly purpose-built to get blocked by firewalls, and to require deep packet inspection.
This same FTP packet inspection can incidentally also show the cleartext user and cleartext password, also directly visible to any intervening hosts and firewalls and routers involved in the connection.
Contrast with sftp, which works with one port (TCP 22) and one network connection, doesn’t use a second connection, and doesn’t inherently meet a firewall again after the initial connection. It is also end-to-end encrypted, protecting the connection credentials. And it is supported by Adobe Dreamweaver.
It's really not surprising that FTP isn't working. It far more surprising that you had it working at any time in the past 20 years. Any kind of system update from your computer, your ISP modem, your Internet connection, your ISP's internet connection, your server, your server's connection could easily break FTP. And when you call all of those people up to complain, not a single one of them will care. They will all tell you to stop using FTP.
This is simply a non-starter. You must find another way.
Apple removed FTP (and telnet) support in macOS 10.13 some eight years ago, specifically because these protocols are insecure.
Why not still use FTP? Well, I’d rather not have my file server and web server surprise breached.
EtreCheck Report - FTP problems
