Remove support for S/Key

Most people will 1) be using modern multi-factor authentication methods
like TOTP/OATH etc and 2) be getting support for multi-factor
authentication via PAM or BSD Auth.

1 files changed, 1 insertions, 13 deletions

diff --git a/auth2-chall.c b/auth2-chall.c
index 4fd18f467..2d5cff448 100644
--- a/auth2-chall.c
+++ b/auth2-chall.c
@@ -58,9 +58,6 @@ extern KbdintDevice bsdauth_device;
 #ifdef USE_PAM
 extern KbdintDevice sshpam_device;
 #endif
-#ifdef SKEY
-extern KbdintDevice skey_device;
-#endif
 #endif
 
 KbdintDevice *devices[] = {
@@ -70,9 +67,6 @@ KbdintDevice *devices[] = {
 #ifdef USE_PAM
         &sshpam_device,
 #endif
-#ifdef SKEY
-        &skey_device,
-#endif
 #endif
         NULL
 };
@@ -369,7 +363,7 @@ input_userauth_info_response(int type, u_int32_t seq, struct ssh *ssh)
 void
 privsep_challenge_enable(void)
 {
-#if defined(BSD_AUTH) || defined(USE_PAM) || defined(SKEY)
+#if defined(BSD_AUTH) || defined(USE_PAM)
         int n = 0;
 #endif
 #ifdef BSD_AUTH
@@ -378,9 +372,6 @@ privsep_challenge_enable(void)
 #ifdef USE_PAM
         extern KbdintDevice mm_sshpam_device;
 #endif
-#ifdef SKEY
-        extern KbdintDevice mm_skey_device;
-#endif
 
 #ifdef BSD_AUTH
         devices[n++] = &mm_bsdauth_device;
@@ -388,8 +379,5 @@ privsep_challenge_enable(void)
 #ifdef USE_PAM
         devices[n++] = &mm_sshpam_device;
 #endif
-#ifdef SKEY
-        devices[n++] = &mm_skey_device;
-#endif
 #endif
 }