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

[Openvpn-users] Static IP assignment and authorization


  • Subject: [Openvpn-users] Static IP assignment and authorization
  • From: Ralf Hildebrandt <Ralf.Hildebrandt@xxxxxxxxxx>
  • Date: Wed, 4 Jan 2006 17:17:02 +0100

By creating individual SSL Certificates and per-User settings in
/etc7openvpn/ccd/<cn_of_the_certificate> we're able to assign static
IP addresses to our VPN clients. So far, so good.

We also use "auth-user-pass" and the user needs to specify his/her
email passwort to gain VPN access to our net. So far so good.

But can I prevent a user from using HIS SSL certificate but somebody
else's credentials?

E.g. he/she uses the cert with the cn hildeb.vpn.charite.de, but uses
the username "someotheruser" and the appropriate password?

I wonder if it's possible to tie the use of the username hildeb to the
certificate with the cn hildeb.vpn.charite.de, e.g. using a map that
specifies:

hildeb	    hildeb.vpn.charite.de
otheruser   otheruser.vpn.charite.de

-- 
Ralf Hildebrandt (i.A. des IT-Zentrums)         Ralf.Hildebrandt@xxxxxxxxxx
Charite - Universitätsmedizin Berlin            Tel.  +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin    Fax.  +49 (0)30-450 570-962
IT-Zentrum Standort CBF                 send no mail to spamtrap@xxxxxxxxxx

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


Warning: require_once(../../../archive_common.php) [function.require-once]: failed to open stream: No such file or directory in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-01/msg00067.html on line 198

Fatal error: require_once() [function.require]: Failed opening required '../../../archive_common.php' (include_path='/usr/local/lib/php') in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-01/msg00067.html on line 198