1、準備一個空白的CentOS

檢視系統版本

$ su

# cat /etc/redhat-release

CentOS Linux release 7.4.1708 (Core) 

2、安裝RoR環境

參照《CentOS 7 快速安裝RoR環境 》

安裝結果：

$ ruby -v
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]

$ rails -v

Rails 5.1.5

3、安裝Nginx和Passenger

參照《Passenger + Nginx 部署Rails》

4、建立RoR工程

rails new test_https

建立一個controller，測試get/post

cd test_https/

rails g controller test_params

修改./config/routes.rb

Rails.application.routes.draw do
  # For details on the DSL available within this file, see http://guides.rubyonrails.org/routing.html
	get  'test_params/do_get_test'
	post 'test_params/do_post_test'
end

修改./app/controllers/test_params_controller.rb

class TestParamsController < ApplicationController
	skip_before_action :verify_authenticity_token
	def do_get_test
		render :json => "hello this is get_test-->" + request.GET["key"]
		return
	end
	def do_post_test
		render :json => "hello this is get_post-->" + request.POST["key"]
		return
	end
end
 

用開發模式部署

rails s -b 0.0.0.0 -p 3333

get測試

post測試（使用火狐瀏覽器）

按下F12，點選“Network”選項卡

重新整理一下介面，點選剛剛完成的GET網路請求，點選“Edit and Resent”

修改：1-請求型別改為POST；2-請求路徑；3-增加請求內容描述”Content-Type:"application/json;chatset=UTF-8"“；4-增加請求引數；5-點選重發

檢視結果

5、用Passenger + Nginx部署RoR工程

參照《Passenger + Nginx 部署Rails》

6、自創CA

6.1 建立CA的加密私鑰

openssl genrsa -des3 -out ca.key 2048 #建立RSA 2048位私鑰，並用des3加密演算法對這把私鑰加密，然後輸出到ca.key

6.2 用私鑰生成CA證書

openssl req -new -x509 -days 356 -key ca.key -out ca.crt #根據ca.key裡面包含的私鑰生成對應的自簽名證書。證書=公鑰+有效期+附加資訊。-x509表示輸出證書，-days 365 為有效期

7、用自創CA為網站頒發證書

7.1 建立伺服器端加密私鑰

openssl genrsa -des3 -out com.thinking.test.pem 2048

7.2 將加密私鑰解密，生成非加密私鑰，此非加密私鑰將用於伺服器端解密資料

openssl rsa -in com.thinking.test.pem -out com.thinking.test.key

7.3 用服務端私鑰建立服務端證書

openssl req -new -key com.thinking.test.pem -out com.thinking.test.csr

7.4 用CA的私鑰簽名7.3服務端證書（公鑰）。簽名之後生成的這個證書將會被客戶端下載，作為公鑰加密客戶端資料。

openssl ca -policy policy_anything -days 365 -cert ca.crt -keyfile ca.key -in com.thinking.test.csr -out com.thinking.test.crt

* 附上CA公鑰（ca.crt）的目的是為了告訴校驗方（客戶端）這個證書（com.thinking.test.crt）是由誰簽發的。這樣的話，校驗方拿到這個加密證書（com.thinking.test.crt）就在自己的公鑰列表（預裝證書列表）裡面查詢，如果查到了這個公鑰就說明這個CA是受信的，否則不受信。即使不受信，校驗方還是可以用這個附加的CA公鑰解密出服務端證書（com.thinking.test.csr，即公鑰）從而完成與不受信服務端的通訊，只是此時大多數瀏覽器會報警。

出現錯誤：

Using configuration from /etc/pki/tls/openssl.cnf
Enter pass phrase for ca.key:
I am unable to access the /etc/pki/CA/newcerts directory
/etc/pki/CA/newcerts: Permission denied

解決：

用sudo執行這個命令

sudo openssl ca -policy policy_anything -days 365 -cert ca.crt -keyfile ca.key -in com.thinking.test.csr -out com.thinking.test.crt

出現錯誤：

Using configuration from /etc/pki/tls/openssl.cnf
Enter pass phrase for ca.key:
/etc/pki/CA/index.txt: No such file or directory
unable to open '/etc/pki/CA/index.txt'
140396375230368:error:02001002:system library:fopen:No such file or directory:bss_file.c:402:fopen('/etc/pki/CA/index.txt','r')
140396375230368:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:404:

解決：

執行sudo touch /etc/pki/CA/index.txt

出現錯誤：

Using configuration from /etc/pki/tls/openssl.cnf
Enter pass phrase for ca.key:
/etc/pki/CA/serial: No such file or directory
error while loading serial number
140459065653152:error:02001002:system library:fopen:No such file or directory:bss_file.c:402:fopen('/etc/pki/CA/serial','r')
140459065653152:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:404:

解決：

執行# echo 01 > /etc/pki/CA/serial

完成之後配置nginx

    server {
        listen       4444 ssl;
        server_name  127.0.0.1;
        root         /home/thinking/Desktop/test-proj/test_https/public;
        passenger_enabled on;
        rails_env production; 


        ssl_certificate      /home/thinking/Desktop/test-proj/https/com.thinking.test.crt;
        ssl_certificate_key  /home/thinking/Desktop/test-proj/https/com.thinking.test.key;


        ssl_session_cache    shared:SSL:1m;
        ssl_session_timeout  5m;


        ssl_ciphers  HIGH:!aNULL:!MD5;
        ssl_prefer_server_ciphers  on;


    }

完整的nginx.conf

#user  nobody;
worker_processes  1;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid        logs/nginx.pid;


events {
    worker_connections  1024;
}


http {
    passenger_root /home/thinking/.rvm/gems/ruby-2.4.1/gems/passenger-5.2.1;
    passenger_ruby /home/thinking/.rvm/gems/ruby-2.4.1/wrappers/ruby;

    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    #                  '$status $body_bytes_sent "$http_referer" '
    #                  '"$http_user_agent" "$http_x_forwarded_for"';

    #access_log  logs/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;

    #gzip  on;

    server {
        listen       3333;
        server_name  127.0.0.1;
        root         /home/thinking/Desktop/test-proj/test_https/public;
        passenger_enabled on;
        rails_env production; 
    }

    server {
        listen       80;
        server_name  localhost;

        #charset koi8-r;

        #access_log  logs/host.access.log  main;

        location / {
            root   html;
            index  index.html index.htm;
        }

        #error_page  404              /404.html;

        # redirect server error pages to the static page /50x.html
        #
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   html;
        }

        # proxy the PHP scripts to Apache listening on 127.0.0.1:80
        #
        #location ~ \.php$ {
        #    proxy_pass   http://127.0.0.1;
        #}

        # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
        #
        #location ~ \.php$ {
        #    root           html;
        #    fastcgi_pass   127.0.0.1:9000;
        #    fastcgi_index  index.php;
        #    fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;
        #    include        fastcgi_params;
        #}

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        #location ~ /\.ht {
        #    deny  all;
        #}
    }


    # another virtual host using mix of IP-, name-, and port-based configuration
    #
    #server {
    #    listen       8000;
    #    listen       somename:8080;
    #    server_name  somename  alias  another.alias;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}

    server {
        listen       4444 ssl;
        server_name  127.0.0.1;
        root         /home/thinking/Desktop/test-proj/test_https/public;
        passenger_enabled on;
        rails_env production; 


        ssl_certificate      /home/thinking/Desktop/test-proj/https/com.thinking.test.crt;
        ssl_certificate_key  /home/thinking/Desktop/test-proj/https/com.thinking.test.key;


        ssl_session_cache    shared:SSL:1m;
        ssl_session_timeout  5m;


        ssl_ciphers  HIGH:!aNULL:!MD5;
        ssl_prefer_server_ciphers  on;


    }

    # HTTPS server
    #
    #server {
    #    listen       443 ssl;
    #    server_name  localhost;

    #    ssl_certificate      cert.pem;
    #    ssl_certificate_key  cert.key;

    #    ssl_session_cache    shared:SSL:1m;
    #    ssl_session_timeout  5m;

    #    ssl_ciphers  HIGH:!aNULL:!MD5;
    #    ssl_prefer_server_ciphers  on;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}

}

重啟nginx使之生效

8、測試GET/POST

用火狐瀏覽器打開出現如下警告

新增信任

點選Advanced-->Add Exception-->Confirm Security Exception，再開啟：

用另一臺windows主機上面的chrome測試

說明SSL加密已經生效了，只是連線不受信任。

看清楚證書資訊“View certificate”，發現CA也不受信

9、在Windows系統上使連線受信

這其實分兩個步驟：

1、使CA可信

2、CA證明站點可信

9.1 在windows系統上安裝CA證書，使CA可信

把6.2生成的CA證書ca.crt拷貝到windows系統，雙擊安裝。注意，必須安裝到“受信任的根證書頒發機構”儲存區。

（後續如果需要解除安裝，控制面板裡面搜尋“證書”即可找到證書管理工具，然後進去移除即可）

這樣之後，

檢視證書資訊“View certificate”

9.2 使站點受信

可以看到證書是頒發給yong的，不是192.168.0.64，所以要做host

以管理員身份執行notepad++，開啟檔案C:\Windows\System32\drivers\etc\hosts

新增192.168.0.64 yong

然後重試

完美！