openVPN設定 №5 – 自宅sambaサーバに接続

openvpn, VPS, レンタルサーバ(さくらインターネット)

自宅sambaに接続のことについて書きたいと思います。

【設定環境】
・sambaサーバ (centOS5.11)

1. “smb.conf” の編集
VPNサーバに割り振られているipアドレスを許可設定する。

[user@localhost] vi /etc/samba/smb.conf

[編集内容]

  :
  :
hosts allow = 127. 192.168.111. 192.168.222.
  :
  :

2. sambaサーバ内のファイアウォールにVPNネットワークの通信を許可する。

  :
  :
iptables -I FORWARD -i tun+ -s 192.168.222.0/24 -d 192.168.111.246 -j ACCEPT
  :
  :


3.sambaサーバに再起動を行う

/etc/init.d/smb restart
SMB サービスを停止中:                                      [  OK  ]
NMB サービスを停止中:                                      [  OK  ]
SMB サービスを起動中:                                      [  OK  ]
NMB サービスを起動中:                                      [  OK  ]

以上の設定を行ったことにより、”sambaサーバ” が接続できるようになる。

【参考文献】
CentOSで自宅サーバー構築さん – VPNサーバー構築(OpenVPN)

【素材】
フリー素材を使用させて頂きました。
Digipot さん – パソコン・サーバ・ルータ

記事を読む   openVPN設定 №5 – ...

openVPN設定 №5 – クライアント接続

openvpn, VPS, レンタルサーバ(さくらインターネット)

openvpn の構築が完了しましたので、VPNサーバに接続するためにクライアント接続について書きたいと思います。
接続方法は “Windows” 方法です。

1. “openvpn.net” より、クライアントファイルをダウンロードする。
http://openvpn.net/index.php/open-source/downloads.htmlより、”openvpn-2.3.6.zip” をダウンロードします。

2. ダウンロードしたファイルをインストールする。
インストールは規約に同意して頂き、保存先を指定をしてインストールを行います。

3. クライアントを接続するために、configファイル(ovpnファイル)を作成。
テキストエディターソフトを使って作ります。
文字コードは “utf-8” で設定を行う。

[ファイル名]

Client_pass.ovpn

[ファイル内容]

client
dev tun
proto udp
remote 【作成したVPNサーバのipアドレス】 1194
resolv-retry infinite

persist-key
persist-tun

ca ca.crt
cert Client_pass.crt
key Client_pass.key
askpass pass.cfg

key-direction 1
tls-auth ta.key 1

comp-lzo
verb 4

5. 必要な証明書、秘密鍵、共有鍵のパスワードを作成
easy-rsaで製作したファイルをFTPサーバなどを使ってダウンロードする。
また、共有鍵のパスワードをテキストファイルで入力をして保存する。
・ca.crt [サーバ証明書]
・ta.key [TLS-AUTH HMAC 共有鍵]
・Client_pass.crt [クライアント証明書]
・Client_pass.key [クライアント秘密鍵]

pass.cfg

[ファイル内容]

【パスワード入力】【ENTER】

“【】”はキーボードで入力していることを表しています。

6. 実行
・Client_pass.ovpn
・ca.crt
・ta.key
・Client_pass.crt
・Client_pass.key
の5つのファイルをPC内に保存する。
自分の場合は、”c:¥openvpn” 内に保存しました。

コマンドプロンプト 起動

cd c:¥ 【ENTER】
cd openvpn 【ENTER】
openvpn.exe --config Client_pass.ovpn 【ENTER】

以下の実行結果が確認がされた場合は、接続が
[実行結果]

Initialization Sequence Completed

【参考文献】
レンタルサーバ・自宅サーバの設定。構築のヒント さん – OpenVPN を使って仮想LAN接続してみる

記事を読む   openVPN設定 №5 & ...

openVPN設定 №4

openvpn, VPS, レンタルサーバ(さくらインターネット)

openVPN設定 №3からの続き

13. ipアドレス・ポートの設定
UDPポート1194解放とVPNサーバで使用されるipアドレスが通過できるようにフォワードの設定を行います。

   :
   :
iptables -A INPUT -p udp --dport 1194 -j ACCEPT_COUNTRY
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT
iptables -A FORWARD -m state --state NEW -o eth0 -j ACCEPT
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A OUTPUT -m state --state NEW -o eth0 -j ACCEPT
iptables -t nat -A POSTROUTING -s 192.168.222.0/24 -o eth0 -j MASQUERADE
   :
   :

14. iptablseの更新・openVPNの起動
iptablesの更新

iptables: チェインをポリシー ACCEPT へ設定中nat filter     [  OK  ]
iptables: ファイアウォールルールを消去中:                  [  OK  ]
iptables: モジュールを取り外し中:                          [  OK  ]
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
--2014-12-15 22:59:40--  http://nami.jp/ipv4bycc/cidr.txt.gz
nami.jp をDNSに問いあわせています... 133.242.178.137
nami.jp|133.242.178.137|:80 に接続しています... 接続しました。
HTTP による接続要求を送信しました、応答を待っています... 200 OK
長さ: 330986 (323K) [application/x-gzip]
`cidr.txt.gz' に保存中

100%[==========================================================================================================================================================================>] 330,986     --.-K/s 時間 0.04s

2014-12-15 22:59:40 (7.79 MB/s) - `cidr.txt.gz' へ保存完了 [330986/330986]

iptables: ファイアウォールのルールを /etc/sysconfig/iptable[  OK  ]中:
iptables: ファイアウォールルールを適用中:

openvpn起動

[user@localhost] /etc/init.d/openvpn start
openvpn を起動中:                                          [  OK  ]

以上でopenvpnサーバの構築が完了です。
今回のopenvpnサーバの構築については、レンタルサーバ・自宅サーバの設定。構築のヒント さん 、ecube lab+ さんの方から参考にさせて頂きました。
本当に感謝です。

【参考文献】
レンタルサーバ・自宅サーバの設定。構築のヒント さん – OpenVPN を使って仮想LAN接続してみる
ecube lab+ さん – さくらVPSで(クライアント→VPN→外部のための)VPNトンネルつくったよ

記事を読む   openVPN設定 №4

openVPN設定 №3

openvpn, VPS, レンタルサーバ(さくらインターネット)

openVPN設定 №2 の続きからです。

10. DHパラメータの作成

[user@localhost] ./build-dh

作成されたのか確認する場合は・・・

[user@localhost] ls keys/

[確認内容]

Generating DH parameters, 1024 bit long safe prime, generator 2
This is going to take a long time
..............................................................................................+.......................................+...............+......................................+............+......................+......+.............+.........................+...................................................................+........+..................+.................................................................................................................................................+......+.................+...........................................................................................+.....................................+...........................................................................................................+..............................................................................................................................................+......................+............................+....+...........................+.....................................................................................................................................................................................+...........................................................+.........+..........+..........................+........................................+...+............................................................+.......................................+......................+.........................+...........+...............+............+...................................................................+...+............+....+.+.................................................................+.............+.................................+......................................+................................+................+..............................................+................................................................................+..........................................................................+.........................................................+.......................................................+.......................................................+............................................................+...+..........+...................+....+.+....................................................................+....................................................+..........................................................................................................+..................................+...........................................................................................................................+..............................................................................................+..........................+..........................................................................+........................................+...+...+........+....................+...........................................................................................+...................................................................................+.....+.................................................................+....++*++*++*

作成されたのか確認する場合は・・・

[user@localhost] ls keys/

[確認内容]

dh1024.pem ・・・         

11. TLS-AUTH HMAC 共有鍵の作成

[user@localhost] openvpn --genkey --secret /etc/openvpn/easy-rsa/keys/ta.key

作成されたのか確認する場合は・・・

[user@localhost] ls keys/

[確認内容]

ta.key ・・・

12. OpenVPN のサーバー設定ファイルを編集
ハイライト(青っぽい)している部分はコメント化・追加した部分になります。

[user@localhost] vi /etc/openvpn/server.conf

[ファイル内容]

#################################################
# Sample OpenVPN 2.0 config file for            #
# multi-client server.                          #
#                                               #
# This file is for the server side              #
# of a many-clients <-> one-server              #
# OpenVPN configuration.                        #
#                                               #
# OpenVPN also supports                         #
# single-machine <-> single-machine             #
# configurations (See the Examples page         #
# on the web site for more info).               #
#                                               #
# This config should work on Windows            #
# or Linux/BSD systems.  Remember on            #
# Windows to quote pathnames and use            #
# double backslashes, e.g.:                     #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
#                                               #
# Comments are preceded with '#' or ';'         #
#################################################

# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one.  You will need to
# open up this port on your firewall.
port 1194

# TCP or UDP server?
;proto tcp
proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one.  On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key).  Each client
# and the server must have their own cert and
# key file.  The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys.  Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).

#---
#ca ca.crt
#cert server.crt
#key server.key  # This file should be kept secret
#---
ca easy-rsa/keys/ca.crt
cert easy-rsa/keys/server.crt
key easy-rsa/keys/server.key  # This file should be kept secret
#---

# Diffie hellman parameters.
# Generate your own with:
#   openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys. 

#---
#dh dh1024.pem
#---
dh easy-rsa/keys/dh1024.pem
#---

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.

#---
#server 10.8.0.0 255.255.255.0
server 192.168.222.0 255.255.255.0
#---

# Maintain a record of client <-> virtual IP address
# associations in this file.  If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface.  Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0.  Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients.  Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses.  You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# Push routes to the client to allow it
# to reach other private subnets behind
# the server.  Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
#   iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN.  This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
#   ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients.  There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
#     group, and firewall the TUN/TAP interface
#     for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
#     modify the firewall in response to access
#     from different clients.  See man
#     page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push "redirect-gateway def1 bypass-dhcp"

#---
push "redirect-gateway def1"
#---

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses.  CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"

#---
push "dhcp-option DNS 【指定DNSサーバのIPアドレス】"
push "dhcp-option DNS 【指定DNSサーバのIPアドレス】"
#---

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.

#---
#;client-to-client
;client-to-client
#--

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names.  This is recommended
# only for testing purposes.  For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn


# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
#   openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.

#---
#;tls-auth ta.key 0 # This file is secret
#---
tls-auth easy-rsa/keys/ta.key 0 
#---

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.

#---
#;max-clients 100
max-clients 10
#---

# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.

#---
#;user nobody
#;group nobody
#---
user nobody
group nobody
#---

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.

#---
#status openvpn-status.log
status /var/log/openvpn/openvpn-status.log
#---

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it.  Use one
# or the other (but not both).

#---
#;log         openvpn.log
#;log-append  openvpn.log
log         /var/log/openvpn/openvpn.log
log-append /var/log/openvpn/openvpn.log
#---

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages.  At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

記事を読む   openVPN設定 №3

openVPN設定 №2

openvpn, VPS, レンタルサーバ(さくらインターネット)

openVPN設定 №1 の続きからです。

8.サーバ証明書とサーバ秘密鍵を作成。

[user@localhost] ./build-key-server server

[ファイル内容]

Generating a 1024 bit RSA private key
............................................................++++++
.....++++++
writing new private key to 'server.key'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [JP]:【ENTER】
State or Province Name (full name) [Tokyo]:【ENTER】
Locality Name (eg, city) [Hachiouzi]:【ENTER】
Organization Name (eg, company) [tmyinsight.net]:【ENTER】
Organizational Unit Name (eg, section) [changeme]:【ENTER】
Common Name (eg, your name or your server's hostname) [server]:【ENTER】
Name [changeme]:【ENTER】
Email Address [postmaster@tmyinsight.net]:【ENTER】

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:【ENTER】
An optional company name []:【ENTER】
Using configuration from /etc/openvpn/easy-rsa/openssl-1.0.0.cnf
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
countryName           :PRINTABLE:'JP'
stateOrProvinceName   :PRINTABLE:'Tokyo'
localityName          :PRINTABLE:'Hachiouzi'
organizationName      :PRINTABLE:'tmyinsight.net'
organizationalUnitName:PRINTABLE:'changeme'
commonName            :PRINTABLE:'server'
name                  :PRINTABLE:'changeme'
emailAddress          :IA5STRING:'postmaster@tmyinsight.net'
Certificate is to be certified until Dec 10 12:56:12 2024 GMT (3650 days)
Sign the certificate? [y/n]:【y】【ENTER】


1 out of 1 certificate requests certified, commit? [y/n]【y】【ENTER】
Write out database with 1 new entries
Data Base Updated

※”【】”はキーボードで入力していることを表しています。
作成されたのか確認する場合は・・・

[user@localhost] ls keys/
server.crt server.csr server.key ・・・

9. クライアント証明書・クライアントの秘密鍵を作成。
クライアントの数が決まっている場合は、その分だけ繰り返し作成を行ってください。
また、パスフレーズの有無の設定が出来ますので、そのことも書きたいと思います。

[パスフレーズが必要な場合]

[user@localhost] ./build-key-pass Client_pass

[確認内容]

Generating a 1024 bit RSA private key
..................++++++
..................++++++
writing new private key to 'Client_pass.key'
Enter PEM pass phrase:【パスフレーズを入力】【ENTER】
Verifying - Enter PEM pass phrase:【パスフレーズを再入力】【ENTER】
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [JP]:【ENTER】
State or Province Name (full name) [Tokyo]:【ENTER】
Locality Name (eg, city) [Hachiouzi]:【ENTER】
Organization Name (eg, company) [tmyinsight.net]:【ENTER】
Organizational Unit Name (eg, section) [changeme]:【ENTER】
Common Name (eg, your name or your server's hostname) [Client_pass]:
Name [changeme]:【ENTER】
Email Address [postmaster@tmyinsight.net]:【ENTER】

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:【ENTER】
An optional company name []:【ENTER】
Using configuration from /etc/openvpn/easy-rsa/openssl-1.0.0.cnf
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
countryName           :PRINTABLE:'JP'
stateOrProvinceName   :PRINTABLE:'Tokyo'
localityName          :PRINTABLE:'Hachiouzi'
organizationName      :PRINTABLE:'tmyinsight.net'
organizationalUnitName:PRINTABLE:'changeme'
commonName            :T61STRING:'Client_pass'
name                  :PRINTABLE:'changeme'
emailAddress          :IA5STRING:'postmaster@tmyinsight.net'
Certificate is to be certified until Dec 10 13:09:34 2024 GMT (3650 days)
Sign the certificate? [y/n]:【y】【ENTER】


1 out of 1 certificate requests certified, commit? [y/n]【y】【ENTER】
Write out database with 1 new entries
Data Base Updated

[パスフレーズが不必要な場合]

[user@localhost] ./build-key Client_nopass

[確認内容]

Generating a 1024 bit RSA private key
.............................................................++++++
...................................................++++++
writing new private key to 'Client_nopass.key'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [JP]:【ENTER】
State or Province Name (full name) [Tokyo]:【ENTER】
Locality Name (eg, city) [Hachiouzi]:【ENTER】
Organization Name (eg, company) [tmyinsight.net]:【ENTER】
Organizational Unit Name (eg, section) [changeme]:【ENTER】
Common Name (eg, your name or your server's hostname) [Client_nopass]:
Name [changeme]:【ENTER】
Email Address [postmaster@tmyinsight.net]:【ENTER】

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:【ENTER】
An optional company name []:【ENTER】
Using configuration from /etc/openvpn/easy-rsa/openssl-1.0.0.cnf
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
countryName           :PRINTABLE:'JP'
stateOrProvinceName   :PRINTABLE:'Tokyo'
localityName          :PRINTABLE:'Hachiouzi'
organizationName      :PRINTABLE:'tmyinsight.net'
organizationalUnitName:PRINTABLE:'changeme'
commonName            :T61STRING:'Client_nopass'
name                  :PRINTABLE:'changeme'
emailAddress          :IA5STRING:'postmaster@tmyinsight.net'
Certificate is to be certified until Dec 10 13:22:33 2024 GMT (3650 days)
Sign the certificate? [y/n]:【y】【ENTER】

1 out of 1 certificate requests certified, commit? [y/n]【y】【ENTER】
Write out database with 1 new entries
Data Base Updated

※”【】”はキーボードで入力していることを表しています。

作成されたのか確認する場合は・・・

[user@localhost] ls keys/

[確認内容]

Client_nopass.csr  Client_pass.crt  Client_pass.key  Client_nopass.crt  Client_nopass.key  Client_pass.csr ・・・         

記事を読む   openVPN設定 №2

openVPN設定 №1

openvpn, VPS, レンタルサーバ(さくらインターネット)

今回はopenVPNについて書きたいと思います。
書く内容が多いので、何回か区切りさせて頂きます。

自宅内のネットワークに接続が出来たらと思って構築してみました。
VPNサーバを構築することにあたり “Sakura Ineternet VPS” で使用します。
また、今回は自宅内にあるSambaサーバに接続ができるように設定を行っていきます。

【最初に】
今回の設定は、インターネット上で調べてから構築を行い実行を行っています。
参考させて頂いた文献については、最後の”参考文献”としてご紹介させて頂きます。
構築が出来たことに本当に感謝です。

【設定環境】
・VPNサーバ[SakuraVPS]OS:centOS 6.4

【設定方法】
※1 root権限で作業作業をしていきます。
※2 “rpmforge” リポジトリ を追加していることを前提にしています。

1. “openvpn” をインストールする。

[user@localhost] yum install --enablerepo=rpmforge -y install openvpn

2. SSL/TSLの認証手続きを行うため、”easy-rsa” を使用します。
“openvpn” のサイトよりファイルをダウンロードします。
自分が解りやすい指定のディレクトリ先に保存を行ってください。

[user@localhost] wget http://swupdate.openvpn.org/community/releases/openvpn-2.3.6.tar.gz

3. “openvpn-2.3.6.tar.gz” を解凍し、解凍したディレクトリ内にある”easy-rsa” を “/etc/openvpn/” にコピーします。

[user@localhost] tar -zxvf openvpn-2.3.6.tar.gz
   :
   :
解凍中
   :
   :
[user@localhost]
[user@localhost] cp -fr openvpn-2.3.6/easy-rsa/2.0 /etc/openvpn/easy-rsa

4. 認証局(CA) を基本情報を編集して保存する。

[user@localhost] vi /etc/openvpn/easy-rsa/vars

[ファイル内容]

# easy-rsa parameter settings

# NOTE: If you installed from an RPM,
# don't edit this file in place in
# /usr/share/openvpn/easy-rsa --
# instead, you should copy the whole
# easy-rsa directory to another location
# (such as /etc/openvpn) so that your
# edits will not be wiped out by a future
# OpenVPN package upgrade.

# This variable should point to
# the top level of the easy-rsa
# tree.
export EASY_RSA="`pwd`"

#
# This variable should point to
# the requested executables
#
export OPENSSL="openssl"
export PKCS11TOOL="pkcs11-tool"
export GREP="grep"


# This variable should point to
# the openssl.cnf file included
# with easy-rsa.
export KEY_CONFIG=`$EASY_RSA/whichopensslcnf $EASY_RSA`

# Edit this variable to point to
# your soon-to-be-created key
# directory.
#
# WARNING: clean-all will do
# a rm -rf on this directory
# so make sure you define
# it correctly!
export KEY_DIR="$EASY_RSA/keys"

# Issue rm -rf warning
echo NOTE: If you run ./clean-all, I will be doing a rm -rf on $KEY_DIR

# PKCS11 fixes
export PKCS11_MODULE_PATH="dummy"
export PKCS11_PIN="dummy"

# Increase this to 2048 if you
# are paranoid.  This will slow
# down TLS negotiation performance
# as well as the one-time DH parms
# generation process.
export KEY_SIZE=1024

# In how many days should the root CA key expire?
export CA_EXPIRE=3650

# In how many days should certificates expire?
export KEY_EXPIRE=3650

# These are the default values for fields
# which will be placed in the certificate.
# Don't leave any of these fields blank.

#---[↓↓コメント化↓↓]---
#export KEY_COUNTRY="US"
#export KEY_PROVINCE="CA"
#export KEY_CITY="SanFrancisco"
#export KEY_ORG="Fort-Funston"
#export KEY_EMAIL="me@myhost.mydomain"
#export KEY_EMAIL=mail@host.domain
#---[↑↑コメント化↑↑]---

#---[↓↓追加↓↓]---
export KEY_COUNTRY="JP"                       # 国:日本
export KEY_PROVINCE="Tokyo"                   # 都道府県:東京
export KEY_CITY="Hachiouzi"                   # 地町村区:八王子
export KEY_ORG="tmyinsight.net"               # サイト情報:ドメイン
export KEY_EMAIL="postmaster@tmyinsight.net"  # メールアドレス:管理者メールアドレス
#---[↑↑追加↑↑]---

export KEY_CN=changeme
export KEY_NAME=changeme
export KEY_OU=changeme
export PKCS11_MODULE_PATH=changeme
export PKCS11_PIN=1234

5. “vars” をスクリプト実行する

[user@localhost] source vars

6. “vars” と “./clean-all” を実行する。

[user@localhost] ./vars
[user@localhost] ./clean-all

7. プライベートCA構築[CA証明書・CA秘密鍵 作成]

[user@localhost] ./build-ca

[ファイル内容]

Generating a 1024 bit RSA private key
.............................................................++++++
.............................................................................................................++++++
writing new private key to 'ca.key'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [JP]: 【ENTER】
State or Province Name (full name) [Tokyo]:【ENTER】
Locality Name (eg, city) [Hachiouzi]:【ENTER】
Organization Name (eg, company) [tmyinsight.net]:【ENTER】
Organizational Unit Name (eg, section) [changeme]:【ENTER】
Common Name (eg, your name or your server's hostname) [changeme]:【ENTER】
Name [changeme]:【ENTER】
Email Address [postmaster@tmyinsight.net]:【ENTER】

※”【ENTER】” はエンターキーを押していることを表しています。

作成されたのか確認する場合は・・・

[user@localhost] ls keys/

[確認内容]

ca.crt  ca.key  ・・・

【素材】
フリー素材を使用させて頂きました。
Digipot さん – パソコン・サーバ・ルータ

記事を読む   openVPN設定 №1

PAGE TOP