[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

[Openvpn-devel] Server not using tty as it's passing auth to pam_access.so


  • Subject: [Openvpn-devel] Server not using tty as it's passing auth to pam_access.so
  • From: David <linuxman1973@xxxxxxxxx>
  • Date: Mon, 22 Aug 2005 03:11:46 +0000 (UTC)

Apologize for putting this problem on the developer list.  Just not getting to
many hits else where.  When I log into my server and manually restart the
server, all is well with my VPN connections.  After a short time, login attempts
result in failures.  The passwords come back as auth failed or critical errors
(in the openvpn.log file).  

Did some research and it appears the login attempts that are passed to PAM and
pam_access.so (via login module) are not showing an originating tty.  The
/var/log/auth.log shows:
Aug 21 18:31:11 nssab2-ada-jenkins pam_access[6060]: couldn't get the tty name
Aug 21 19:28:09 nssab2-ada-jenkins pam_access[6060]: couldn't get the tty name
Aug 21 19:32:03 nssab2-ada-jenkins pam_access[6060]: couldn't get the tty name
Aug 21 19:33:50 nssab2-ada-jenkins pam_access[6060]: couldn't get the tty name
Aug 21 19:45:53 nssab2-ada-jenkins pam_access[6060]: couldn't get the tty name

The requesting tty that pam_access expects is not there, NULL value.  It then
kills the login process and OpenVPN will not work till manually stopped and
restarted from a SSH session.

Using PAM .78 and openvpn-2.0_rc17




____________________________________________
Openvpn-devel mailing list
Openvpn-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-devel