Turns out that fix won't help with the PMA issues in MacOS CI

targets. /etc/pam.d is a protected directory and you need some
sort of user intervention to grant permission to allow the terminal
to make these changes. This is in addition to using sudo. As of now
we'll need to use self hosted runners to make this happen.

What's interesting is that it pam.d doesn't fail under the ubuntu
tests. For some reason it's either not actually testing pam or
it's using the sshd control file. It would be nice if the behaviour
was predictable

Author: rapier1

.github/setup_ci.sh

@@ -26,7 +26,7 @@ esac
 TARGETS=$@
 
 INSTALL_FIDO_PPA="no"
-COPY_PAM_MODULE="no"
+#COPY_PAM_MODULE="no"
 export DEBIAN_FRONTEND=noninteractive
 
 #echo "Setting up for '$TARGETS'"
@@ -86,7 +86,7 @@ for TARGET in $TARGETS; do
 	esac
         ;;
     *pam)
-	COPY_PAM_MODULE="yes"
+#	COPY_PAM_MODULE="yes"
         PACKAGES="$PACKAGES libpam0g-dev"
         ;;
     sk)
@@ -143,11 +143,11 @@ fi
 
 #need to copy the pam modules for sshd to hpnsshd on
 #macos with pam.
-if [ "yes" = "$COPY_PAM_MODULE" ]; then
-    if [ `uname` = "Darwin" }; then
-	sudo cp /etc/pam.d/sshd /etc/pam.d/hpnsshd
-    fi
-fi
+#if [ "yes" = "$COPY_PAM_MODULE" ]; then
+#    if [ `uname` = "Darwin" }; then
+#	sudo cp /etc/pam.d/sshd /etc/pam.d/hpnsshd
+#    fi
+#fi
 
 tries=3
 while [ ! -z "$PACKAGES" ] && [ "$tries" -gt "0" ]; do