SWAN之ikev2协议multi-level-ca配置测试

2023-12-19 09:58

本文主要是介绍SWAN之ikev2协议multi-level-ca配置测试,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

本测试主要验证多级CA证书验证的功能,远程用户carol,dave与网关moon建立连接时,分别使用中间CA证书所签发的实体证书,分配给carol的证书仅可访问moon网关之后的alice主机;dave的证书仅可访问venus主机。两个中间CA证书的名称CN分别为"Research CA"和"Sales CA"。本次测试拓扑如下:

在这里插入图片描述

carol主机配置

carol的配置文件:ikev2/multi-level-ca/hosts/carol/etc/ipsec.conf,内容如下。字段rightca的值为"C=CH, O=Linux strongSwan, CN=strongSwan Root CA",即要求对端的CA证书名称CN为:“strongSwan Root CA”。此外,定义了两个子连接alice和venus,字段rightsubnet分别对应主机alice(10.1.0.10)和主机venus(10.10.20)。

conn %defaultleft=PH_IP_CAROLleftcert=carolCert.pemleftsendcert=ifaskedright=PH_IP_MOONrightid=@moon.strongswan.orgrightca="C=CH, O=Linux strongSwan, CN=strongSwan Root CA"conn alicerightsubnet=PH_IP_ALICE/32auto=addconn venusrightsubnet=PH_IP_VENUS/32auto=add

carol主机的证书文件carolCert.pem内容如下,其签发者Issuer的信息为:C = CH, O = strongSwan Project, OU = Research, CN = Research CA。

$ openssl x509 -in ikev2/multi-level-ca/hosts/carol/etc/ipsec.d/certs/carolCert.pem -noout -text
Certificate:Data:Version: 3 (0x2)Serial Number: 1 (0x1)Signature Algorithm: sha256WithRSAEncryptionIssuer: C = CH, O = strongSwan Project, OU = Research, CN = Research CAValidityNot Before: Sep 14 08:37:52 2019 GMTNot After : Sep 14 08:37:52 2027 GMTSubject: C = CH, O = strongSwan Project, OU = Research, CN = carol@strongswan.org

dave主机配置

dave的配置文件:ikev2/multi-level-ca/hosts/dave/etc/ipsec.conf,内容如下。字段rightca的值为"C=CH, O=Linux strongSwan, CN=strongSwan Root CA",即要求对端的CA证书名称CN为:“strongSwan Root CA”。此外,定义了两个子连接alice和venus,字段rightsubnet分别对应主机alice(10.1.0.10)和主机venus(10.10.20)。

conn %defaultleft=PH_IP_DAVEleftcert=daveCert.pemleftsendcert=ifaskedright=PH_IP_MOONrightid=@moon.strongswan.orgrightca="C=CH, O=Linux strongSwan, CN=strongSwan Root CA"conn alicerightsubnet=PH_IP_ALICE/32auto=addconn venusrightsubnet=PH_IP_VENUS/32auto=add

dave主机的证书文件daveCert.pem内容如下,其签发者Issuer的信息为:C = CH, O = strongSwan Project, OU = Sales, CN = Sales CA。

$ openssl x509 -in ikev2/multi-level-ca/hosts/dave/etc/ipsec.d/certs/daveCert.pem -noout -text
Certificate:Data:Version: 3 (0x2)Serial Number: 1 (0x1)Signature Algorithm: sha256WithRSAEncryptionIssuer: C = CH, O = strongSwan Project, OU = Sales, CN = Sales CAValidityNot Before: Sep 14 08:37:52 2019 GMTNot After : Sep 14 08:37:52 2027 GMTSubject: C = CH, O = strongSwan Project, OU = Sales, CN = dave@strongswan.org

网关配置

moon网关的配置文件:ikev2/multi-level-ca/hosts/moon/etc/ipsec.conf,内容如下。连接alice配置中,rightca字段为"C=CH, O=strongSwan Project, OU=Research, CN=Research CA",要求对端的CA名称CN为:“Research CA”。远程客户carol使用的证书满足此要求。

连接venus配置中,rightca字段为"C=CH, O=strongSwan Project, OU=Sales, CN=Sales CA",要求对端的CA名称CN为:“Sales CA”。远程客户dave使用的证书满足此要求。

conn %defaultleft=PH_IP_MOONleftcert=moonCert.pemleftsendcert=ifaskedleftid=@moon.strongswan.orgconn aliceleftsubnet=PH_IP_ALICE/32right=%anyrightca="C=CH, O=strongSwan Project, OU=Research, CN=Research CA"auto=addconn venusleftsubnet=PH_IP_VENUS/32right=%anyrightca="C=CH, O=strongSwan Project, OU=Sales, CN=Sales CA"auto=add

moon网关的CA证书researchCert.pem,由根CA:strongSwan Root CA所签发,签发给Research部门(OU),名称(CN)为:Research CA。

$ openssl x509 -in ikev2/multi-level-ca/hosts/moon/etc/ipsec.d/cacerts/researchCert.pem -noout -text
Certificate:Data:Version: 3 (0x2)Serial Number: 11 (0xb)Signature Algorithm: sha256WithRSAEncryptionIssuer: C = CH, O = strongSwan Project, CN = strongSwan Root CAValidityNot Before: Sep 14 08:37:52 2019 GMTNot After : Sep 14 08:37:52 2028 GMTSubject: C = CH, O = strongSwan Project, OU = Research, CN = Research CA

moon网关的CA证书salesCert.pem,由根CA:strongSwan Root CA所签发,签发给Sales部门(OU),名称(CN)为:Sales CA。

$ openssl x509 -in ikev2/multi-level-ca/hosts/moon/etc/ipsec.d/cacerts/salesCert.pem -noout -text
Certificate:Data:Version: 3 (0x2)Serial Number: 12 (0xc)Signature Algorithm: sha256WithRSAEncryptionIssuer: C = CH, O = strongSwan Project, CN = strongSwan Root CAValidityNot Before: Sep 14 08:37:52 2019 GMTNot After : Sep 14 08:37:52 2028 GMTSubject: C = CH, O = strongSwan Project, OU = Sales, CN = Sales CA

测试准备阶段

配置文件:ikev2/multi-level-ca/pretest.dat,内容为通常的ipsec连接的启动语句。本次测试中,在carol和dave主机上都会启动名称为alice和venus的两个连接。不过,在carol主机上首先启动alice连接,在dave主机上首先启动venus连接,这两个连接都可成功。相反,carol上的子连接venus和dave上的子连接alice,都会失败,放后执行。

moon::ipsec start
carol::ipsec start
dave::ipsec start
moon::expect-connection alice
moon::expect-connection venus
carol::expect-connection alice
carol::expect-connection venus
carol::ipsec up alice
carol::ipsec up venus
dave::expect-connection alice
dave::expect-connection venus
dave::ipsec up venus
dave::ipsec up alice

测试阶段

配置文件:ikev2/multi-level-ca/evaltest.dat内容如下。在moon网关的strongswan日志文件中,确认carol和dave证书的验证,以及中间CA证书的验证。

moon:: cat /var/log/daemon.log::fetching crl from.*http.*research.crl::YES
moon:: cat /var/log/daemon.log::crl correctly signed by.*Research CA::YES
moon:: cat /var/log/daemon.log::fetching crl from.*http.*sales.crl::YES
moon:: cat /var/log/daemon.log::crl correctly signed by.*Sales CA::YES
moon:: cat /var/log/daemon.log::fetching crl from.*http.*strongswan.crl::YES
moon:: cat /var/log/daemon.log::crl correctly signed by.*strongSwan Root CA::YES

以下为moon网关上strongswan进程验证证书的日志信息。在IKE_SA_INIT响应消息中,CERTREQ载荷中包含三个证书请求,CN分别为:“Research CA”、“Sales CA"和"strongSwan Root CA”,其中前两个为中间证书,第三个为根证书。

在随后carol的报文IKE_AUTH中,提供了一个end entity证书:“C=CH, O=strongSwan Project, OU=Research, CN=carol@strongswan.org”,据此在moon网关的配置中匹配到名称为alice的连接,以及对应的中间CA文件:moon/etc/ipsec.d/cacerts/researchCert.pem。接下来获取CRL文件:research.crl,验证carol证书的状态,先使用中间CA证书ResearchCert.pem验证crl文件的有效性,在根据CRL验证carol证书有效性。

之后,获取strongswan.crl证书,以验证中间CA证书:"C=CH, O=strongSwan Project, OU=Research, CN=Research CA"的有效性。整个证书链验证完成之后,认证成功。

moon charon: 13[IKE] sending cert request for "C=CH, O=strongSwan Project, OU=Research, CN=Research CA"
moon charon: 13[IKE] sending cert request for "C=CH, O=strongSwan Project, OU=Sales, CN=Sales CA"
moon charon: 13[IKE] sending cert request for "C=CH, O=strongSwan Project, CN=strongSwan Root CA"
moon charon: 13[ENC] generating IKE_SA_INIT response 0 [ SA KE No N(NATD_S_IP) N(NATD_D_IP) CERTREQ N(FRAG_SUP) N(HASH_ALG) N(CHDLESS_SUP) N(MULT_AUTH) ]
moon charon: 14[NET] received packet: from 192.168.0.100[4500] to 192.168.0.1[4500] (1236 bytes)
moon charon: 15[ENC] parsed IKE_AUTH request 1 [ IDi CERT N(INIT_CONTACT) CERTREQ IDr AUTH SA TSi TSr N(MOBIKE_SUP) N(ADD_6_ADDR) N(MULT_AUTH) N(EAP_ONLY) N(MSG_ID_SYN_SUP) ]
moon charon: 15[IKE] received cert request for "C=CH, O=strongSwan Project, CN=strongSwan Root CA"
moon charon: 15[IKE] received end entity cert "C=CH, O=strongSwan Project, OU=Research, CN=carol@strongswan.org"
moon charon: 15[CFG] looking for peer configs matching 192.168.0.1[moon.strongswan.org]...192.168.0.100[C=CH, O=strongSwan Project, OU=Research, CN=carol@strongswan.org]
moon charon: 15[CFG] selected peer config 'alice'
moon charon: 15[CFG]   using certificate "C=CH, O=strongSwan Project, OU=Research, CN=carol@strongswan.org"
moon charon: 15[CFG]   using trusted intermediate ca certificate "C=CH, O=strongSwan Project, OU=Research, CN=Research CA"
moon charon: 15[CFG] checking certificate status of "C=CH, O=strongSwan Project, OU=Research, CN=carol@strongswan.org"
moon charon: 15[CFG]   fetching crl from 'http://crl.strongswan.org/research.crl' ...
moon charon: 15[CFG]   using trusted ca certificate "C=CH, O=strongSwan Project, CN=strongSwan Root CA"
moon charon: 15[CFG]   reached self-signed root ca with a path length of 0
moon charon: 15[CFG]   using trusted certificate "C=CH, O=strongSwan Project, OU=Research, CN=Research CA"
moon charon: 15[CFG]   crl correctly signed by "C=CH, O=strongSwan Project, OU=Research, CN=Research CA"
moon charon: 15[CFG]   crl is valid: until Nov 15 03:32:58 2019
moon charon: 15[CFG] certificate status is good
moon charon: 15[CFG]   using trusted ca certificate "C=CH, O=strongSwan Project, CN=strongSwan Root CA"
moon charon: 15[CFG] checking certificate status of "C=CH, O=strongSwan Project, OU=Research, CN=Research CA"
moon charon: 15[CFG]   fetching crl from 'http://crl.strongswan.org/strongswan.crl' ...
moon charon: 15[CFG]   using trusted certificate "C=CH, O=strongSwan Project, CN=strongSwan Root CA"
moon charon: 15[CFG]   crl correctly signed by "C=CH, O=strongSwan Project, CN=strongSwan Root CA"
moon charon: 15[CFG]   crl is valid: until Nov 15 03:32:58 2019
moon charon: 15[CFG] certificate status is good
moon charon: 15[CFG]   reached self-signed root ca with a path length of 1
moon charon: 15[IKE] authentication of 'C=CH, O=strongSwan Project, OU=Research, CN=carol@strongswan.org' with RSA_EMSA_PKCS1_SHA2_256 successful

以下测试语句,在carol和moon上确认名称为alice的连接的建立,并且在carol主机的strongswan进程日志中将检查到TS_UNACCEPTABLE的通知,这是由于在carol上建立子连接venus失败所导致的。

carol::ipsec status 2> /dev/null::alice.*INSTALLED, TUNNEL::YES
moon:: ipsec status 2> /dev/null::alice.*ESTABLISHED.*carol@strongswan.org::YES
carol::cat /var/log/daemon.log::received TS_UNACCEPTABLE notify, no CHILD_SA built::YES
carol::ipsec status 2> /dev/null::venus.*INSTALLED::NO

看一下carol主机上strongswan进程的日志,子连接venus未能创建成功,在报文CREATE_CHILD_SA request 2中,载荷TSr的值为:10.1.0.20(venus主机),但是在moon网关上定义到venus的连接需要具有"Sales CA"签发的证书,carol的证书为"Research CA"所签发。

carol charon: 05[CFG] received stroke: initiate 'venus'
carol charon: 09[IKE] establishing CHILD_SA venus{2}
carol charon: 09[ENC] generating CREATE_CHILD_SA request 2 [ SA No TSi TSr ]
carol charon: 09[NET] sending packet: from 192.168.0.100[4500] to 192.168.0.1[4500] (256 bytes)
carol charon: 12[NET] received packet: from 192.168.0.1[4500] to 192.168.0.100[4500] (80 bytes)
carol charon: 12[ENC] parsed CREATE_CHILD_SA response 2 [ N(TS_UNACCEPT) ]
carol charon: 12[IKE] received TS_UNACCEPTABLE notify, no CHILD_SA built
carol charon: 12[IKE] failed to establish CHILD_SA, keeping IKE_SA

moon网关上strongwan进程的日志中,显示了拒绝carol主机此TSr的信息。

moon charon: 16[ENC] parsed CREATE_CHILD_SA request 2 [ SA No TSi TSr ]
moon charon: 16[IKE] traffic selectors 10.1.0.20/32 === 192.168.0.100/32 unacceptable
moon charon: 16[IKE] failed to establish CHILD_SA, keeping IKE_SA
moon charon: 16[ENC] generating CREATE_CHILD_SA response 2 [ N(TS_UNACCEPT) ]

对于主机dave的认证过程与以上carol相似,以下为moon网关上strongswan进程日志中与dave相关的部分信息。由于在moon网关上,名称为alice连接排在前面,dave的连接首先匹配alice,在相关的证书验证完成之后,将会产生:constraint check failed错误,因为alice连接要求"Research CA"签发的证书,而dave的证书由"Sales CA"签发。此时将匹配moon网关上的配置venus。

moon charon: 07[IKE] authentication of 'C=CH, O=strongSwan Project, OU=Sales, CN=dave@strongswan.org' with RSA_EMSA_PKCS1_SHA2_256 successful
moon charon: 07[CFG] constraint check failed: peer not authenticated by CA 'C=CH, O=strongSwan Project, OU=Research, CN=Research CA'
moon charon: 07[CFG] selected peer config 'alice' unacceptable: non-matching authentication done
moon charon: 07[CFG] switching to peer config 'venus'
moon charon: 07[IKE] peer supports MOBIKE
moon charon: 07[IKE] authentication of 'moon.strongswan.org' (myself) with RSA_EMSA_PKCS1_SHA2_256 successful
moon charon: 07[IKE] IKE_SA venus[2] established between 192.168.0.1[moon.strongswan.org]...192.168.0.200[C=CH, O=strongSwan Project, OU=Sales, CN=dave@strongswan.org]

strongswan测试版本: 5.8.1

END

这篇关于SWAN之ikev2协议multi-level-ca配置测试的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/511774

相关文章

mybatis映射器配置小结

《mybatis映射器配置小结》本文详解MyBatis映射器配置,重点讲解字段映射的三种解决方案(别名、自动驼峰映射、resultMap),文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定... 目录select中字段的映射问题使用SQL语句中的别名功能使用mapUnderscoreToCame

Linux下MySQL数据库定时备份脚本与Crontab配置教学

《Linux下MySQL数据库定时备份脚本与Crontab配置教学》在生产环境中,数据库是核心资产之一,定期备份数据库可以有效防止意外数据丢失,本文将分享一份MySQL定时备份脚本,并讲解如何通过cr... 目录备份脚本详解脚本功能说明授权与可执行权限使用 Crontab 定时执行编辑 Crontab添加定

Java使用jar命令配置服务器端口的完整指南

《Java使用jar命令配置服务器端口的完整指南》本文将详细介绍如何使用java-jar命令启动应用,并重点讲解如何配置服务器端口,同时提供一个实用的Web工具来简化这一过程,希望对大家有所帮助... 目录1. Java Jar文件简介1.1 什么是Jar文件1.2 创建可执行Jar文件2. 使用java

SpringBoot 多环境开发实战(从配置、管理与控制)

《SpringBoot多环境开发实战(从配置、管理与控制)》本文详解SpringBoot多环境配置,涵盖单文件YAML、多文件模式、MavenProfile分组及激活策略,通过优先级控制灵活切换环境... 目录一、多环境开发基础(单文件 YAML 版)(一)配置原理与优势(二)实操示例二、多环境开发多文件版

Vite 打包目录结构自定义配置小结

《Vite打包目录结构自定义配置小结》在Vite工程开发中,默认打包后的dist目录资源常集中在asset目录下,不利于资源管理,本文基于Rollup配置原理,本文就来介绍一下通过Vite配置自定义... 目录一、实现原理二、具体配置步骤1. 基础配置文件2. 配置说明(1)js 资源分离(2)非 JS 资

MySQL8 密码强度评估与配置详解

《MySQL8密码强度评估与配置详解》MySQL8默认启用密码强度插件,实施MEDIUM策略(长度8、含数字/字母/特殊字符),支持动态调整与配置文件设置,推荐使用STRONG策略并定期更新密码以提... 目录一、mysql 8 密码强度评估机制1.核心插件:validate_password2.密码策略级

ShardingProxy读写分离之原理、配置与实践过程

《ShardingProxy读写分离之原理、配置与实践过程》ShardingProxy是ApacheShardingSphere的数据库中间件,通过三层架构实现读写分离,解决高并发场景下数据库性能瓶... 目录一、ShardingProxy技术定位与读写分离核心价值1.1 技术定位1.2 读写分离核心价值二

HTTP 与 SpringBoot 参数提交与接收协议方式

《HTTP与SpringBoot参数提交与接收协议方式》HTTP参数提交方式包括URL查询、表单、JSON/XML、路径变量、头部、Cookie、GraphQL、WebSocket和SSE,依据... 目录HTTP 协议支持多种参数提交方式,主要取决于请求方法(Method)和内容类型(Content-Ty

QT Creator配置Kit的实现示例

《QTCreator配置Kit的实现示例》本文主要介绍了使用Qt5.12.12与VS2022时,因MSVC编译器版本不匹配及WindowsSDK缺失导致配置错误的问题解决,感兴趣的可以了解一下... 目录0、背景:qt5.12.12+vs2022一、症状:二、原因:(可以跳过,直奔后面的解决方法)三、解决方

SpringBoot路径映射配置的实现步骤

《SpringBoot路径映射配置的实现步骤》本文介绍了如何在SpringBoot项目中配置路径映射,使得除static目录外的资源可被访问,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一... 目录SpringBoot路径映射补:springboot 配置虚拟路径映射 @RequestMapp