BaroPAM integration Guide(OpenVPN)

Application guide of BaroPAM solution, a 3-step authentication solution for user identification and authentication in OpenVPN environment

 

Index

 

1. What is OpenVPN?

2. OpenVPN installation and setup
2.1 Install OpenVPN
2.2 Linux client configuration

3. BaroPAM installation and setup
3.1 Preparation before installing BaroPAM
3.2 Download BaroPAM installation module
3.3 Create BaroPAM configuration file
3.4 NTP(Network Time Protocol) settings

4. OpenVPN server and BaroPAM configuration
4.1 OpenVPN server configuration
4.2 BaroPAM Configuration

5. OpenVPN connection test
5.1 Create new user
5.2 Create BaroPAM configuration file
5.3 OpenVPM connection test

6. About BaroPAM

 

 

1. What is OpenVPN?

 

A virtual private network (VPN) connects point to point using a tunneling protocol (communication protocol) based on encryption technology without a separate dedicated private network. This means a network solution that can build a wide area network (WAN) at low cost.

 

OpenVPN refers to an open source VPN protocol and its access program developed and distributed by OpenVPN Technologies, Inc.

 

As an open-source VPN protocol that can use both TCP and UDP protocols, it establishes a VPN connection using a TAP or TUN virtual network adapter.

 

Since packets are encrypted using SSL or TLS, a valid CA certificate is required. However, this is because there is no problem with the connection even if you do not use a trusted CA. In response, many individual users use programs such as OpenSSL to create VPN servers using self-authenticated certificates.

 

Even where L2TP or PPTP is blocked, OpenVPN is likely to connect.

 

However, if the firewall is an application firewall that intercepts all packets, there is no answer. In particular, in China and Egypt, which are active in Internet censorship, it was already blocked in 2013. To use OVPN in such an environment, it is necessary to set the cipher to AES-256-CFB, wrap it with an SSL or SSH tunnel (stunnel, etc.), use an XOR patch, or have a camouflage such as Obfsproxy.

 

Used when building an OpenVPN server or connecting to a server. It operates by reading the OpenVPN configuration file with the extension ovpn. The configuration file is different for the server and client, but the extension is the same, which can be confusing.

 

The client can read the certificate itself, so it works without installing a separate certificate.

 

There are two types of OpenVPN servers: OpenVPN Community Edition, which is free/open source (GPL), and paid OpenVPN Access Server, which provides additional features such as web GUI.

 

OpenVPN Community Edition basically does not provide a separate GUI for configuration, so you need to build a server using only command lines and text files. However, you can find any number of configuration methods on the Internet, and in some cases, a third-party wrapper is created, such as a router with custom firmware such as DD-WRT, so that you can build a server on the GUI.

 

Meanwhile, the OpenVPN client is available for Android (4.0 and above) and iOS, and supports most desktop operating systems. However, among modern mobile operating systems, Windows Phone (7, 8, and 10 all), Blackberry OS 10, and Tizen cannot be used. Sailfish OS supports it as a third-party app.

 

 

 

2. OpenVPN installation and setup

 

2.1 Install OpenVPN

 

Configuring OpenVPN on a CentOS 7/8 environment is surprisingly "easier than expected". First you need OpenVPN and easy-rsa.

 

1. Select the EPEL repository and then install the package

 

It comes with all the dependencies needed to install the OpenVPN package.

 

[root]# yum -y install epel-release

 

2. Find your server's public IP address

 

It is important to find out the server's public IP address, as it will come in handy when setting up an OpenVPN server.

 

[root]# curl ifconfig.me 173.82.115.6

 

3. Download the OpenVPN installation script and run the indicated commands.

 

[root]# wget https://raw.githubusercontent.com/Angristan/openvpn-install/master/openvpn-install.sh

 

4. Set execute permission to OpenVPN installation script

 

[root]# chmod +x openvpn-install.sh

 

5. Run the OpenVPN installation script

 

[root]# ./openvpn-install.sh

 

6. You will first be asked to provide the server's public IP address. After that, it is recommended to use the default options such as the default port number (1194) and the protocol to be used (UDP/TCP).

 

 

7. Next, select the default DNS resolver and select the no (n) option for both compression and encryption settings.

 

 

8. Upon completion, the script initializes the OpenVPN server's settings along with the installation of other software packages and dependencies.

 

 

9. Finally, create a client configuration file using the easy-RSA package, a command-line tool used for managing security certificates.

 

Just enter the client name and use the default selection. Client files are stored in your home directory with the .ovpn file extension.

 

 

10. When the script sets up the OpenVPN server and creates the client configuration file, the tunnel interface tun0 is created. This is a virtual interface through which all traffic from the client PC is tunneled to the server.

 

 

11. Start OpenVPN server and check status

 

 

 

 

2.2 Linux client configuration

 

1. Install EPEL repository and OpenVPN software package

 

$ sudo yum -y install epel-release $ sudo yum –y install openvpn

 

2. Once installed, use the scp command to test if it works

 

$ sudo scp -r tecmint@173.82.115.6:/home/tecmint/tecmint01.ovpn .

 

 

3. Once the client files are downloaded to your Linux machine, you can now initiate a connection to the VPN server using the following command.

 

$ sudo openvpn --config tecmint01.ovpn

 

You should get output similar to the one below.

 

 

4. A new routing table is created and a connection with the VPN server is established. Again, the virtual interface tunnel interface tun0 is created on the client machine.

 

As mentioned earlier, this is an interface that securely tunnels all traffic through an SSL tunnel to the OpenVPN server. The interface is dynamically assigned an IP address by the VPN server. As you can see, the OpenVPN server assigned an IP address of 10.8.0.2 to the client Linux system.

 

$ ifconfig

 

 

5. Check your public IP to see if you are connected to the OpenVPN server

 

$ curl ifconfig.me

 

 

I verified that the client machine was actually connecting to the OpenVPN server by selecting the VPN's public IP. Alternatively, you can fire up your browser and run a Google search "What's my IP" to see if your public IP has changed to the IP of your OpenVPN server.

 

 

Note) In OpenVPN, two methods of interworking with BaroPAM as secondary authentication support PAM authentication and Radius authentication. This document deals with PAM authentication, and for Radius authentication, refer to the "BaroPAM Guide (RADIUS-en).doc" document.

 

 

3. BaroPAM installation and setup

 

The BaroPAM solution is a zero trust security model based on the Pluggable Authentication Module (PAM) method that anyone can easily and immediately apply to various operating systems and applications that require secondary authentication (additional authentication) to enhance the security of information assets. It is a 3-step authentication solution with biometrics optimized for security.

 

 

 

3.1 Preparation before installing BaroPAM

 

To use the PAM module, the PAM package must be installed by default. To check the installation, run the following command. If it is not installed, use the command "dnf install pam" for Redhat series and "sudo apt-get install pam" for others.

 

[root]# rpm -qa | grep pam pam_smb-1.1.7-7.2.1 pam_passwdqc-1.0.2-1.2.2 pam-0.99.6.2-14.el5_11 pam_krb5-2.2.14-22.el5 pam-devel-0.99.6.2-14.el5_11 pam_ccreds-3-5 pam_smb-1.1.7-7.2.1 pam_pkcs11-0.5.3-26.el5 pam-devel-0.99.6.2-14.el5_11 pam_passwdqc-1.0.2-1.2.2 pam-0.99.6.2-14.el5_11 pam_ccreds-3-5 pam_krb5-2.2.14-22.el5 pam_pkcs11-0.5.3-26.el5

 

In the case of Redhat series, "Selinux" is an abbreviation of "Security Enhanced Linux" and provides a more excellent security policy than the basic Linux. If it is so outstanding that it is activated, a part where BaroPAM cannot be blocked due to security problems occurs (Failed to open tmp secret file "/usr/baropam/.baro_auth~" [Permission denied]). So, if possible, most of them are disabled (SELINUX=enforcing → disabled).

 

[root] /etc > vi /etc/sysconfig/selinux # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: #       enforcing - SELinux security policy is enforced. #       permissive - SELinux prints warnings instead of enforcing. #       disabled - SELinux is fully disabled. SELINUX=disabled # SELINUXTYPE= type of policy in use. Possible values are: #       targeted - Only targeted network daemons are protected. #       strict - Full SELinux protection. SELINUXTYPE=targeted   # SETLOCALDEFS= Check local definition changes SETLOCALDEFS=0

 

It doesn't take effect right away and requires a reboot to take effect.

 

If you want to apply the changes only to the currently connected terminal without rebooting, run the following command.

 

[root] /etc > /usr/sbin/setenforce 0

 

To download and install the BaroPAM authentication module, connect with the root account and create a directory (/usr/baropam) to download and install the module as follows.

 

[root]# mkdir /usr/baropam

 

Grant permissions (read, write, execute) of the directory to download and install the BaroPAM module as follows.

 

[root]# chmod -R 777 /usr/baropam

 

 

3.2 Download BaroPAM installation module

 

After accessing the BaroPAM authentication module with the root account, move to the directory (/usr/baropam) to download and install the module, and download the module as follows.

 

[root] /usr/baropam > wget http://nuriapp.com/download/libpam_baro_auth-x.x.tar

 

When the download of the BaroPAM authentication module is complete, the tar file is decompressed as follows.

 

[root] /usr/baropam > tar -xvf libpam_baro_auth-x.x.tar

 

When the BaroPAM authentication module is unzipped, the following BaroPAM related modules are created in the baropam directory.

 

[root] /usr/baropam > ls -al 합계 180 drwxrwxrwx  7 root   root   4096  8월 23 09:59 . drwxr-xr-x 17 root   root   4096  2월 10  2017 .. -r--r--r--  1 root   root      8  3월 24  2021 .baro_acl -r--r--r--  1 root   root    305  7월  2 14:41 .baro_auth -r--r--r--  1 root   root    290  6월 30 12:55 .baro_curl -rwxr-xr-x  1 root   root  69149  4월  6 19:12 baro_auth -rwxr-xr-x  1 root   root  65072  6월 29 16:36 baro_curl drwxr-xr-x  2 root   root   4096  7월 20  2021 jilee -rwxr-xr-x  1 root   root 152649  6월  9 08:19 pam_baro_auth.so -rwxr-xr-x  1 root   root 116158  6월 30 12:54 pam_baro_curl.so -rw-r--r--  1 root   root    150  6월 29 16:29 setcurl.sh -rw-r--r--  1 root   root    221  6월 27 15:59 setenv.sh

 

 

3.3 Create BaroPAM configuration file

 

The BaroPAM environment setting file must be created by executing the baro_auth program, and it must be located under /usr/baropam, the directory of the BaroPAM authentication module.

 

Format)

baro_auth -r rate_limit -R rate_time -t cycle_time –k key_method –e encrypt_flag -H hostname -A acl_type -a acl_filename -S secure_key -s filename

 

The configuration options of the BaroPAM configuration file are as follows.

 

Optino	Decumentation	Set value	Etc
-r	OTA key limited number of times (1~10)	3
-R	OTA key time limit (15~600 sec)	30
-t	OTA key authentication cycle (3~60 sec)	30
-k	OTA key authentication method (app1, app256, app384, app512)	app512
-e	Encryption of configuration files (yes or no)	no
-H	Server's hostname (uname -n)	nurit.co.kr
-A	Choose whether to allow or deny 2nd authentication	deny
-a	ACL file name for the account to allow or deny from 2nd authentication (file access permission is 444)	/usr/baropam/.baro_acl
-S	Secure key (license key) provided by the vendor	jIqIcHbVqdpj7b4PzBpM2DiIeBvmHFV/
-s	File name including the directory in which to create the BaroPAM configuration file	/usr/baropam/.baro_auth

 

Note) The filename of the -s option is the name of the file including the directory where the BaroPAM configuration file will be created (file access permission is 444). If the hostname of the set server does not match, BaroPAM may not operate normally. If the hostname is changed, it must be reflected in the relevant item of the environment setting.

 

Ex of use)

[root] /usr/baropam > ./baro_auth -r 3 -R 30 -t 30 –k app512 –e no -H nurit.co.kr -A deny -a /usr/baropam/.baro_acl -S jIqIcHbVqdpj7b4PzBpM2DiIeBvmHFV/ -s /usr/baropam/.baro_auth

 

If the BaroPAM environment setting file is set for each account, connect to the account and proceed with the work. (Not root)

 

[root] /usr/baropam > ./baro_auth -r 3 -R 30 -t 30 –k app512 –e no -H nurit.co.kr -A deny -a ~/.baro_acl -S jIqIcHbVqdpj7b4PzBpM2DiIeBvmHFV/ -s ~/.baro_auth

 

1) Your emergency one-time authentication keys are:

The emergency OTA key is a super authentication key that can be used to access the SSH server again in case you lose it when the OTA key generator, the BaroPAM app, is unavailable, so it is good to write it down somewhere.

 

2) Enter "y" for all the questions that follow.

   Will it prevent man-in-the-middle attacks? y

 Will the same OTA key enable login to other accounts besides one account? y

   Shall we set the OTA key time limit to 30 seconds? y

 

The contents set in .baro_auth, the BaroPAM environment setting file, are as follows.

 

[root] /usr/baropam > cat .baro_auth " AUTH_KEY " RATE_LIMIT 3 30 " KEY_METHOD app512 " CYCLE_TIME 30 " SECURE_KEY jIqIcHbVqdpj7b4PzBpM2DiIeBvmHFV/ " ACL_NAME /usr/baropam/.baro_acl " ACL_TYPE deny " HOSTNAME nurit.co.kr " DISALLOW_REUSE 33458936 19035576 15364353 54649370 84342192

 

The setting items of .baro_auth, a BaroPAM configuration file, are as follows.

 

Item	Decumentation	Set value	Etc
AUTH_KEY	Authentication delimiter (fixed)
RATE_LIMIT	OTA key limit count (1~10), time limit (15~600 sec)	3 30
KEY_METHOD	OTA key authentication method (app1, app256, app384, app512: app, card1, card256, card384, card512: authentication card)	app512
LOGIN_TIM	last login time	0
CYCLE_TIME	OTA key authentication cycle (3~60 sec)	30
SECURE_KEY	Secure key (license key) provided by the vendor	jIqIcHbVqdpj7b4PzBpM2DiIeBvmHFV/
HOSTNAME	Server's hostname (uname -n)	nurit.co.kr
ACL_TYPE	Differentiate between allow and deny in 2nd authentication	deny
ACL_NAME	ACL Filename for the account to be allowed or excluded from 2nd authentication (file access permission is 444)	/usr/baropam/.baro_acl
DISALLOW_REUSE or ALLOW_REUSE	To prevent a man-in-the-middle attack, if "DISALLOW_REUSE" is set, other users cannot log in during the authentication cycle of the OTA key. If allowed, set "ALLOW_REUSE".	DISALLOW_REUSE

 

When using the BaroPAM module, if you need to exclude from the ACL for the account to be excluded from secondary authentication, create an ACL file in the directory set when setting up the BaroPAM environment, and enter the account to be excluded as follows. (The file access permission for .baro_acl must be set to 444.)

 

[root] /usr/baropam > vi .baro_acl barokey baropam

 

 

3.4 NTP(Network Time Protocol) settings

 

Since BaroPAM is a time synchronization method, if the server's time is different from the current time, login to the server may not be possible because the OTA keys do not match.

 

Recently, as a method of time synchronization (time server time synchronization) for information assets, the system time can be set to the current time in the root account using NTP (Network Time Protocol).

 

To use NTP, the NTP package must be installed by default. To check the installation, run the following command. If it is not installed, use the command "yum install ntp" for Redhat, CentOS 8 or lower, and "sudo apt-get install ntp" for others.

 

[root]# rpm -qa | grep ntp ntp-4.2.2p1-18.el5.centos chkfontpath-1.10.1-1.1

 

The following command can be used to register the ntpd service in the startup program when booting the server and to check whether ntp is activated.

 

[root]# chkconfig ntpd on [root]# chkconfig --list | grep ntp ntpd            0:off  1:off  2:on  3:on  4:on  5:on  6:off

 

Check whether the ntpd daemon is active when booting the server using chkconfig. If it is off in level 3 and 5, it is not activated automatically. To activate automatically, you must change 3 and 5 to on (active) with the following command.

 

[root]# chkconfig --level 3 ntpd on [root]# chkconfig --level 5 ntpd on

 

NTP servers operating in Korea are as follows.

 

server kr.pool.ntp.org server time.bora.net

 

Set the NTP server operating in Korea in "/etc/ntp.conf", the configuration file for the ntpd daemon configuration, as follows.

 

[root]# vi /etc/ntp.conf # Use public servers from the pool.ntp.org project. # Please consider joining the pool (http://www.pool.ntp.org/join.html). #server 0.centos.pool.ntp.org #server 1.centos.pool.ntp.org #server 2.centos.pool.ntp.org #server 3.centos.pool.ntp.org server kr.pool.ntp.org iburst server time.bora.net   iburst

 

The iburst option is a kind of option setting that shortens the time required for synchronization.

 

After the setup for the ntpd daemon setup is complete, it is absolutely necessary to restart the NTP daemon after confirming that the NTP setup has been properly added.

 

[root]# /etc/init.d/ntpd restart Stopping ntpd: [  OK  ] Starting ntpd: [  OK  ]

 

You can check the ntpd time with the following command.

 

[root]# ntpq -p      remote           refid      st t when poll reach   delay   offset  jitter ============================================================================== *121.174.142.82  220.73.142.66    3 u  791 1024  377    9.333   -4.250   0.428 +time.bora.net   58.224.35.2      3 u  654 1024  367    2.926  -27.295  24.481  183.110.225.61  .INIT.          16 u    - 1024    0    0.000    0.000   0.000  LOCAL(0)        .LOCL.          10 l   39   64  377    0.000    0.000   0.001

* The displayed ip is the ntp server getting the current time

 

To use NTP, the NTP package must be installed by default. To check the installation, run the following command. If it is not installed, use the "dnf install chrony" command to install Redhat, CentOS 8 or later versions.

 

[root@baropam ~]# rpm -qa | grep chrony chrony-3.5-1.el8.x86_64

 

NTP servers operating in Korea are as follows.

 

server kr.pool.ntp.org server time.bora.net

 

Set the NTP server operating in Korea in "/etc/chrony.conf", the configuration file for the ntpd daemon configuration, as follows.

 

[root@baropam ~]# vi /etc/chrony.conf   # Use public servers from the pool.ntp.org project. # Please consider joining the pool (http://www.pool.ntp.org/join.html). #pool 2.centos.pool.ntp.org iburst server kr.pool.ntp.org iburst server time.bora.net   iburst   # Record the rate at which the system clock gains/losses time. driftfile /var/lib/chrony/drift   # Allow the system clock to be stepped in the first three updates # if its offset is larger than 1 second. makestep 1.0 3   # Enable kernel synchronization of the real-time clock (RTC). rtcsync   # Enable hardware timestamping on all interfaces that support it. #hwtimestamp *   # Increase the minimum number of selectable sources required to adjust # the system clock. #minsources 2   # Allow NTP client access from local network. allow 192.168.0.0/16   # Serve time even if not synchronized to a time source. #local stratum 10   # Specify file containing keys for NTP authentication. keyfile /etc/chrony.keys   # Get TAI-UTC offset and leap seconds from the system tz database. leapsectz right/UTC   # Specify directory for log files. logdir /var/log/chrony   # Select which information is logged. #log measurements statistics tracking

 

After the setup for the ntpd daemon setup is complete, it is absolutely necessary to restart the NTP daemon after confirming that the NTP setup has been properly added. (Starting chrony service and registering drive when booting)

 

[root@baropam ~]# sudo systemctl enable chronyd [root@baropam ~]# sudo systemctl restart chronyd

 

You can check the ntpd time with the following command.

 

List of servers receiving time / list of servers registered in chrony.conf file)

 

[root@baropam ~]# chronyc sources 210 Number of sources = 2 MS Name/IP address         Stratum Poll Reach LastRx Last sample               =============================================================================== ^* ec2-54-180-134-81.ap-nor>     2   6   377    43   -349us[-1059us] +/-   24ms ^- time.bora.net                 2   6   377    42  +1398us[+1398us] +/-   90ms

 

Server information receiving time)

 

[root@baropam ~]# chronyc tracking Reference ID    : 36B48651 (ec2-54-180-134-81.ap-northeast-2.compute.amazonaw) Stratum         : 3 Ref time (UTC)  : Sun Mar 22 07:07:43 2020 System time     : 0.000130027 seconds slow of NTP time Last offset     : -0.000710122 seconds RMS offset      : 0.000583203 seconds Frequency       : 19.980 ppm fast Residual freq   : +0.142 ppm Skew            : 3.235 ppm Root delay      : 0.013462566 seconds Root dispersion : 0.017946836 seconds Update interval : 65.0 seconds Leap status     : Normal

 

Check information such as time status and synchronization)

 

[root@baropam ~]# timedatectl status                Local time: Sun 2020-03-22 16:08:45 KST            Universal time: Sun 2020-03-22 07:08:45 UTC                  RTC time: Sun 2020-03-22 07:08:44                 Time zone: Asia/Seoul (KST, +0900) System clock synchronized: yes               NTP service: active           RTC in local TZ: no

 

 

4. OpenVPN server and BaroPAM configuration

 

4.1 OpenVPN server configuration

 

This is a standard OpenVPN server configuration, except that it uses the OpenVPN Auth plugin, which calls the OpenVPN PAM module. Then we provide the PAM module with the username, password and OTP token (2FA token).

 

[root]# vi /etc/openvpn/server.conf port 1194 proto tcp dev tun user nobody group nobody persist-key persist-tun keepalive 10 120 topology subnet server 10.8.0.0 255.255.255.0 ifconfig-pool-persist ipp.txt push "dhcp-option DNS 94.140.14.14" push "dhcp-option DNS 94.140.15.15" push "redirect-gateway def1 bypass-dhcp" dh none ecdh-curve prime256v1 tls-crypt tls-crypt.key crl-verify crl.pem ca ca.crt cert server_AxnoivMgFAdSlI4f.crt key server_AxnoivMgFAdSlI4f.key auth SHA256 cipher AES-128-GCM ncp-ciphers AES-128-GCM tls-server tls-version-min 1.2 tls-cipher TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256 client-config-dir /etc/openvpn/ccd status /var/log/openvpn/status.log verb 3   # 2FA plugin /usr/lib64/openvpn/plugins/openvpn-plugin-auth-pam.so "openvpn login USERNAME password PASSWORD pin OTP"

 

This configuration creates an openvpn server on TCP port 1194. The default is to use UDP, but I've found that TCP works better on unreliable networks.

 

 

4.2 BaroPAM Configuration

 

Due to the nature of OpenVPN, in order to set BaroPAM environment configuration files for each user account, a directory dedicated to BaroPAM environment configuration files (/usr/baropam/openvpn) is created as follows.

 

[root]# mkdir /usr/baropam/openvpn

 

Grant permissions (read, write) to the directory dedicated to the BaroPAM environment configuration file (/usr/baropam/openvpn) as follows.

 

[root]# chmod -R 755 /usr/baropam/openvpn

 

Due to the nature of OpenVPN, if BaroPAM configuration files are set for each user account, the BaroPAM module is set in the openvpn file at the top as follows.

 

# BaroPAM auth      required  /usr/baropam/pam_baro_auth.so nullok secret=/etc/baropam/openvpn/.${USER}_auth encrypt=no authtok_prompt=pin   account   required   pam_unix.so auth      required   pam_unix.so auth      substack   password-auth auth      include    postlogin account   required   pam_sepermit.so account   required   pam_nologin.so account   include    password-auth password  include    password-auth

 

For reference, the secret parameter sets the name of the BaroPAM configuration file, and the encrypt parameter sets the encryption/decryption flag (yes or no) of the BaroPAM configuration file.

 

"authtok_prompt=pin" checks the OTA key, which is the OTP token generated and entered by the user's BaroPAM app.

 

 

5. OpenVPN connection test

 

5.1 Create new user

 

To create a new OpenVPN user, run the OpenVPN installation script to create a new user.

 

[root]# ./openvpn-install.sh Welcome to OpenVPN-install! The git repository is available at: https://github.com/angristan/openvpn-install   It looks like OpenVPN is already installed.   What do you want to do?    1) Add a new user    2) Revoke existing user    3) Remove OpenVPN    4) Exit Select an option [1-4]: 1   ………

 

When a new user is created, the "Client name.ovpn" file, which is a profile necessary for connection using Openvpn client connect, is created in the user's home directory.

 

 

5.2 Create BaroPAM configuration file

 

Create a new user by running the installation script that creates the file that sets the BaroPAM environment for the OpenVPN new user.

 

[root]# vi baro_auth.sh DIR_BARO_AUTH=/usr/baropam/openvpn   # run the BaroPAM authenticator as the local user and save the code cp ${DIR_BARO_AUTH}/.baro_auth ${DIR_BARO_AUTH}/.$1_auth   # Change phone number sed -i "s/01012341234/$2/g" ${DIR_BARO_AUTH}/.$1_auth   # Change file ownership chown $1:$1 ${DIR_BARO_AUTH}/.$1_auth

 

If the newly created user ID is "baropam" and the phone number is "01027714076", execute the shell script as follows to create it.

 

[root]# sh baro_auth.sh baropam 01027714076

 

5.3 OpenVPM connection test

 

The OpenVPN client configuration asks for a user, password, and verification code. The user is "baropam" and the password is an authentication token that can be generated by adding the BaroPAM authentication code to the password and verification code generated randomly above and sent to the user. So, if the password is "baropam" and the authentication code generated by the BaroPAM app is "183436", enter the openvpn prompt.

 

If everything works correctly, you should see something like this.

 

1) In case of Linux environment

 

[root]# openvpn --config /home/baropam/baropam.ovpn Sat Aug 12 12:15:52 2023 Unrecognized option or missing or extra parameter(s) in /home/baropam/baropam.ovpn:22: block-outside-dns (2.4.12) Sat Aug 12 12:15:52 2023 OpenVPN 2.4.12 x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 17 2022 Sat Aug 12 12:15:52 2023 library versions: OpenSSL 1.1.1k  FIPS 25 Mar 2021, LZO 2.08 Enter Auth Username: baropam Enter Auth Password: ******* CHALLENGE: Enter Verfication code: 183436 Sat Aug 12 12:16:06 2023 Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key Sat Aug 12 12:16:06 2023 Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication Sat Aug 12 12:16:06 2023 Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key Sat Aug 12 12:16:06 2023 Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication Sat Aug 12 12:16:06 2023 TCP/UDP: Preserving recently used remote address: [AF_INET6]fe80::a00:27ff:fe88:d454%enp0s3:1194 Sat Aug 12 12:16:06 2023 Socket Buffers: R=[87380->87380] S=[16384->16384] Sat Aug 12 12:16:06 2023 Attempting to establish TCP connection with [AF_INET6]fe80::a00:27ff:fe88:d454%enp0s3:1194 [nonblock] Sat Aug 12 12:16:06 2023 TCP: connect to [AF_INET6]fe80::a00:27ff:fe88:d454%enp0s3:1194 failed: Connection refused Sat Aug 12 12:16:06 2023 SIGUSR1[connection failed(soft),init_instance] received, process restarting Sat Aug 12 12:16:06 2023 Restart pause, 5 second(s) Sat Aug 12 12:16:11 2023 TCP/UDP: Preserving recently used remote address: [AF_INET6]fe80::5b49:1861:5bb3:125d%tun0:1194 Sat Aug 12 12:16:11 2023 Socket Buffers: R=[87380->87380] S=[16384->16384] Sat Aug 12 12:16:11 2023 Attempting to establish TCP connection with [AF_INET6]fe80::5b49:1861:5bb3:125d%tun0:1194 [nonblock] Sat Aug 12 12:16:11 2023 TCP: connect to [AF_INET6]fe80::5b49:1861:5bb3:125d%tun0:1194 failed: Connection refused Sat Aug 12 12:16:11 2023 SIGUSR1[connection failed(soft),init_instance] received, process restarting Sat Aug 12 12:16:11 2023 Restart pause, 5 second(s) Sat Aug 12 12:16:16 2023 TCP/UDP: Preserving recently used remote address: [AF_INET]10.0.2.15:1194 Sat Aug 12 12:16:16 2023 Socket Buffers: R=[87380->87380] S=[16384->16384] Sat Aug 12 12:16:16 2023 Attempting to establish TCP connection with [AF_INET]10.0.2.15:1194 [nonblock] Sat Aug 12 12:16:16 2023 TCP connection established with [AF_INET]10.0.2.15:1194 Sat Aug 12 12:16:16 2023 TCP_CLIENT link local: (not bound) Sat Aug 12 12:16:16 2023 TCP_CLIENT link remote: [AF_INET]10.0.2.15:1194 Sat Aug 12 12:16:16 2023 TLS: Initial packet from [AF_INET]10.0.2.15:1194, sid=02dac0ef c3b2db35 Sat Aug 12 12:16:16 2023 VERIFY OK: depth=1, CN=cn_wMUVcNxNlTWtMkZA Sat Aug 12 12:16:16 2023 VERIFY KU OK Sat Aug 12 12:16:16 2023 Validating certificate extended key usage Sat Aug 12 12:16:16 2023 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sat Aug 12 12:16:16 2023 VERIFY EKU OK Sat Aug 12 12:16:16 2023 VERIFY X509NAME OK: CN=server_AxnoivMgFAdSlI4f Sat Aug 12 12:16:16 2023 VERIFY OK: depth=0, CN=server_AxnoivMgFAdSlI4f Sat Aug 12 12:16:16 2023 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 256 bit EC, curve: prime256v1 Sat Aug 12 12:16:16 2023 [server_AxnoivMgFAdSlI4f] Peer Connection Initiated with [AF_INET]10.0.2.15:1194 Sat Aug 12 12:16:17 2023 SENT CONTROL [server_AxnoivMgFAdSlI4f]: 'PUSH_REQUEST' (status=1) Sat Aug 12 12:16:17 2023 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 94.140.14.14,dhcp-option DNS 94.140.15.15,redirect-gateway def1 bypass-dhcp,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.8.0.2 255.255.255.0,peer-id 0,cipher AES-128-GCM' Sat Aug 12 12:16:17 2023 OPTIONS IMPORT: timers and/or timeouts modified Sat Aug 12 12:16:17 2023 OPTIONS IMPORT: --ifconfig/up options modified Sat Aug 12 12:16:17 2023 OPTIONS IMPORT: route options modified Sat Aug 12 12:16:17 2023 OPTIONS IMPORT: route-related options modified Sat Aug 12 12:16:17 2023 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Sat Aug 12 12:16:17 2023 OPTIONS IMPORT: peer-id set Sat Aug 12 12:16:17 2023 OPTIONS IMPORT: adjusting link_mtu to 1626 Sat Aug 12 12:16:17 2023 OPTIONS IMPORT: data channel crypto options modified Sat Aug 12 12:16:17 2023 Outgoing Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key Sat Aug 12 12:16:17 2023 Incoming Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key Sat Aug 12 12:16:17 2023 ROUTE_GATEWAY 10.0.2.2/255.255.255.0 IFACE=enp0s3 HWADDR=08:00:27:88:d4:54 Sat Aug 12 12:16:17 2023 TUN/TAP device tun1 opened Sat Aug 12 12:16:17 2023 TUN/TAP TX queue length set to 100 Sat Aug 12 12:16:17 2023 /sbin/ip link set dev tun1 up mtu 1500 Sat Aug 12 12:16:17 2023 /sbin/ip addr add dev tun1 10.8.0.2/24 broadcast 10.8.0.255 Sat Aug 12 12:16:17 2023 /sbin/ip route add 10.0.2.15/32 dev enp0s3 Sat Aug 12 12:16:17 2023 /sbin/ip route add 0.0.0.0/1 via 10.8.0.1 Sat Aug 12 12:16:17 2023 /sbin/ip route add 128.0.0.0/1 via 10.8.0.1 Sat Aug 12 12:16:17 2023 Initialization Sequence Completed

 

2) In case of Windows environment

 

In the case of Windows environment, after installing OpenVPN, import the "Client name.ovpn" file, which is a profile required for connection, to the OpenVPN GUI using the Openvpn client connect created when creating a new user, and then proceed with the login test.

 

 

 

6. About BaroPAM

 

 

Version 1.0 - Official Release - 2016.12.1

Copyright ⓒ Nurit corp. All rights reserved.

http://www.nurit.co.kr

 

Company: Nurit Co., Ltd.

Registration Number: 258-87-00901

CEO: Jongil Lee

Tel: +8210-2771-4076(Technical support, sales inquiry)

email: mc529@nurit.co.kr

Address: #913, 15, Magokjungang 2-ro, Gangseo-gu, Seoul (Magok-dong, Magok Techno Tower 2)