Installing Apache, PHP, and MySQL on Mac OS X Sierra This is an update for Mac OS X Sierra of a previous post on installing Apache, PHP, and MySQL for Mac OS X. Posted in Main Thread on September 29, 2016.
Apparently, Apple has removed /usr/bin/ftp, and left secure ftp at /usr/bin/sftp. However, some sites still do not support secure ftp, so Apple has removed ftp without regard for that issue. Another heads up. For the first time in High Sierra, Apple has changed the default PATH element order (i.e. /etc/paths) to make /usr/local/bin have the highest precedence over /usr/bin, instead of previously, the last (lowest) position in these PATH elements.
This means if you have two commands installed in both locations with the same exact name, but different builds — the version in /usr/local/bin will run when you type the command name, instead of the system installed command in /usr/bin. Now, where it has never been needed before, one must explicitly preface the system command with /usr/bin/command. This is nuts. As VikingOSX states it, the default PATH has been modified. This is unfair, as it wasn't mentioned anywhere. Even as root, I couldn't make an 'cp -p sftp ftp' nor 'ln -s sftp ftp' in the /usr/bin directory.
So what I made to recover an ftp command is (with sudo or being root): cp -p /usr/bin/sftp /usr/local/bin/ftp This works, and the copied sftp (named ftp) behaves correctly (this kind of executable behaves differently according to their name, such as vi and view). HTH to have ftp back. However, this doesn't solve my Cyberduck.app not working anymore, I thoughty is was realated to ftp missing. It probably is, but they must have explicitly specified /usr/bin/ftp, which I can't fix.
Maybe some advanced access rights (like setfacl and getfacl commands)? This is a good one! You made my day! You should probalbly read this: ? Actually, OSx is a horrible OS in regards of security, because the user has very limited access and authority over major parts of the system.
Considering, that every line of code is a possible one to exploit, the major goal should be to reduce complexity to gain security. While with other UNIX like OS as BSD or Linux the users have the possibility to reduce attack surface pretty effective, with OSx this is difficult or impossible at all for the OS itself. Who, for example, needs the bloated standard kernel? In this thing nearly everything is included even if 95% of the users only need 30% of the included functions.
Do I need to compile all filesystem drivers, when I only need ext4? Or why do I need 20 different bluetooth drivers compliled, when my PC does not even have bluetooth hardware? I could go on and on and on. With Linux one can build a kernal from scratch exactly with the features required and can even only compile them as modules (or even utilize security features as grsecurity and PaX). Even better, one can sandbox every application using seccomp to filter system calls (as Google does with Chrome btw).
Not sure why so many people guess, that Apple OS is safe, but I'm really interested if anyone has a good argument, because none comes to my mind. Cheers, sizeof(void). In terms of security, removing clients like 'telnet' and 'ftp' does not make an operating system any more or less secure. You probably lock your car when its in a public car park in town, but you might choose to leave it open when its in your locked garage at home. In the same vein, is true that a security dead-lock door is probably harder for people to get through, but do you really need it on your internal toilet door? The point here is that tools are just tools, and deploying security needs to be done sensibly. As a networking guy for 20+ years, I'll use telnet locally to test stuff, but ssh to servers on the internet.
(at the very least, we should have vendor supported ways to get them back - forcing people to get 3rd party stuff is surely the worse security outcome!!). Apple Footer. This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums.
Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.