Nginx国密化

原创 已于 2022-08-29 17:38:18 修改 · 3k 阅读 ·
本内容遵循CC 4.0 BY-SA版权协议
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
cknow-ai _全村的希望

cknow-ai 关注

标签
#nginx #运维 #linux
分类 开发工具
于 2022-08-29 17:36:30 首次发布
本文介绍了如何在Nginx中编译并使用GMSSL，详细讲述了在遇到make错误时如何解决，以及编译成功后的配置步骤和验证过程。

Nginx国密化记录

gmssl 相关

#下载gmssl2.5.4版本
wget https://github.com/guanzhi/GmSSL/archive/master.zip
# 解压
unzip master.zip
# 进入目录
cd GmSSL-master
# 配置config指定目录
./config --prefix=/usr/local/gmssl
make
make install
# 查看版本，验证是否安装成功
cd /usr/local/gmssl/
bin/gmssl version

# 报错了，这是由于openssl库的位置不正确造成的
bin/gmssl: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
# 现在基本都是建立软连接，但是可能都没说清楚就会比较懵。
# 1.首先确认gmssl的安装路径，我的是/usr/local/gmssl
# 2.应该将gmssl目录下的lib下的对应文件建立软连接
# 3.确认以上两点后，执行下面的命令
ln -s /usr/local/gmssl/lib/libssl.so.1.1 /usr/lib64/libssl.so.1.1
ln -s /usr/local/gmssl/lib/libcrypto.so.1.1 /usr/lib64/libcrypto.so.1.1
# 再执行bin/gmssl version，则正常返回版本信息

openssl nginx编译

此处使用的为nginx官网最新稳定无漏洞版

wget -c http://nginx.org/download/nginx-1.23.1.tar.gz

tar -zvxf nginx-1.23.1.tar.gz

cd nginx-1.23.1

./configure --prefix=/opt/nginx --with-http_stub_status_module --with-stream --with-http_ssl_module --with-http_gzip_static_module --with-stream_ssl_module --with-openssl="/usr/local/gmssl" --with-cc-opt="-I/usr/local/gmssl/include" --with-ld-opt="-lm"
#编译安装 Nginx
make && make install

如果编译执行过程中出现 make[1]: *** [/usr/local/wotrus_ssl2.0/.openssl/include/openssl/ssl.h] Error 127 错误。则需要进入 nginx-1.23.1/auto/lib/openssl 目录，编辑 conf 文件。需修改如下内容：

CORE_INCS="$CORE_INCS $OPENSSL/.openssl/include"
CORE_DEPS="$CORE_DEPS $OPENSSL/.openssl/include/openssl/ssl.h"
CORE_LIBS="$CORE_LIBS $OPENSSL/.openssl/lib/libssl.a"
CORE_LIBS="$CORE_LIBS $OPENSSL/.openssl/lib/libcrypto.a"

修改为：

CORE_INCS="$CORE_INCS $OPENSSL/include"
CORE_DEPS="$CORE_DEPS $OPENSSL/include/openssl/ssl.h"
CORE_LIBS="$CORE_LIBS $OPENSSL/lib/libssl.a"
CORE_LIBS="$CORE_LIBS $OPENSSL/lib/libcrypto.a"

保存文件后，需先执行 make clean 清除编译配置，再重新进入 nginx-1.23.1文件夹执行

./configure --prefix=/opt/nginx --with-http_stub_status_module --with-stream --with-http_ssl_module --with-http_gzip_static_module --with-stream_ssl_module --with-openssl="/usr/local/gmssl" --with-cc-opt="-I/usr/local/gmssl/include" --with-ld-opt="-lm"

#编译安装 Nginx
make && make install

编译成功后进入对应nginx目录

cd /opt/nginx/conf

mkdir sm2 

cd sm2

sh createGmKey.sh
# 1.以下命令在哪个目录执行的就会生成到哪个目录
# 2.openssl.cnf需要放在执行命令的目录下，主要修改了key usage，以便分别生成签名证书和加密证书,文件和脚本在最后
# 3.这里-extfile openssl.cnf -extensions v3_ca既是为了区分前面和加密证书也是为了生成v3版本的证书，如果不加生成的是V1版本的

验证

pwd 

#查看当前目录路径，确保目录在/opt/nginx/conf/sm2下

/usr/local/gmssl/bin/gmssl s_server -port 4430 -key ./server.key -cert ./server.crt  -dkey ./server_en.key -dcert ./server_en.crt -CAfile ./root.crt
#执行gmssl验证证书 端口4430或者443都可

配置nginx配置文件

# vi /opt/nginx/conf/nginx.conf

#在配置文件server配置项中新增/修改如下配置项

ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
#必须配置上标准算法（兼容性原因）

ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH::AES128-SHA:DES-CBC3-SHA:ECC-SM4-CBC-SM3:ECC-SM4-GCM-SM3:ECDHE-SM2-WITH-SMS4-GCM-SM3:ECDHE-SM2-WITH-SMS4-SHA256:ECDHE-SM2-WITH-SMS4-SM3:SM2-WITH-SMS4-SM3:SM2DHE-WITH-SMS4-SM3!NULL:!aNULL:!MD5:!ADH:!RC4:!3DES;
ssl_prefer_server_ciphers on;

#需要先配置国密签名证书/私钥，再配置国密加密证书/私钥
#证书及其私钥需要连续配置

ssl_certificate      "/opt/nginx/conf/sm2/server.crt";
ssl_certificate_key  "/opt/nginx/conf/sm2/server.key";
ssl_certificate      "/opt/nginx/conf/sm2/server_en.crt";
ssl_certificate_key  "/opt/nginx/conf/sm2/server_en.key";

# nginx/sbin检查配置文件
./nginx -t    
# 无误后启动
./nginx

使用密信浏览器或360企业版即可验证

openssl.cnf文件

#
# OpenSSL example configuration file.
# This is mostly being used for generation of certificate requests.
#

# This definition stops the following lines choking if HOME isn't
# defined.
HOME			= .
RANDFILE		= $ENV::HOME/.rnd

# Extra OBJECT IDENTIFIER info:
#oid_file		= $ENV::HOME/.oid
oid_section		= new_oids

# To use this configuration file with the "-extfile" option of the
# "openssl x509" utility, name here the section containing the
# X.509v3 extensions to use:
# extensions		=
# (Alternatively, use a configuration file that has only
# X.509v3 extensions in its main [= default] section.)

[ new_oids ]

# We can add new OIDs in here for use by 'ca', 'req' and 'ts'.
# Add a simple OID like this:
# testoid1=1.2.3.4
# Or use config file substitution like this:
# testoid2=${testoid1}.5.6

# Policies used by the TSA examples.
tsa_policy1 = 1.2.3.4.1
tsa_policy2 = 1.2.3.4.5.6
tsa_policy3 = 1.2.3.4.5.7

####################################################################
[ ca ]
default_ca	= CA_default		# The default ca section

####################################################################
[ CA_default ]

dir		= /usr/local/gmzs2		# Where everything is kept
certs		= $dir/certs		# Where the issued certs are kept
crl_dir		= $dir/crl		# Where the issued crl are kept
database	= $dir/index.txt	# database index file.
#unique_subject	= no			# Set to 'no' to allow creation of
					# several certs with same subject.
new_certs_dir	= $dir/newcerts		# default place for new certs.

certificate	= $dir/cacert.pem 	# The CA certificate
serial		= $dir/serial 		# The current serial number
crlnumber	= $dir/crlnumber	# the current crl number
					# must be commented out to leave a V1 CRL
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem # The private key
RANDFILE	= $dir/private/.rand	# private random number file

x509_extensions	= usr_cert		# The extensions to add to the cert

# Comment out the following two lines for the "traditional"
# (and highly broken) format.
name_opt 	= ca_default		# Subject Name options
cert_opt 	= ca_default		# Certificate field options

# Extension copying option: use with caution.
# copy_extensions = copy

# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs
# so this is commented out by default to leave a V1 CRL.
# crlnumber must also be commented out to leave a V1 CRL.
# crl_extensions	= crl_ext

default_days	= 365			# how long to certify for
default_crl_days= 30			# how long before next CRL
default_md	= default		# use public key default MD
preserve	= no			# keep passed DN ordering

# A few difference way of specifying how similar the request should look
# For type CA, the listed attributes must be the same, and the optional
# and supplied fields are just that :-)
policy		= policy_match

# For the CA policy
[ policy_match ]
countryName		= match
stateOrProvinceName	= match
organizationName	= match
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional

# For the 'anything' policy
# At this point in time, you must list all acceptable 'object'
# types.
[ policy_anything ]
countryName		= optional
stateOrProvinceName	= optional
localityName		= optional
organizationName	= optional
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional

####################################################################
[ req ]
default_bits		= 2048
default_keyfile 	= privkey.pem
distinguished_name	= req_distinguished_name
attributes		= req_attributes
x509_extensions	= v3_ca	# The extensions to add to the self signed cert

# Passwords for private keys if not present they will be prompted for
# input_password = secret
# output_password = secret

# This sets a mask for permitted string types. There are several options.
# default: PrintableString, T61String, BMPString.
# pkix	 : PrintableString, BMPString (PKIX recommendation before 2004)
# utf8only: only UTF8Strings (PKIX recommendation after 2004).
# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).
# MASK:XXXX a literal mask value.
# WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings.
string_mask = utf8only

# req_extensions = v3_req # The extensions to add to a certificate request

[ req_distinguished_name ]
countryName			= Country Name (2 letter code)
countryName_default		= CN
countryName_min			= 2
countryName_max			= 2

stateOrProvinceName		= State or Province Name (full name)
stateOrProvinceName_default	= Some-State

localityName			= Locality Name (eg, city)

0.organizationName		= Organization Name (eg, company)
0.organizationName_default	= Internet Widgits Pty Ltd

# we can do this but it is not needed normally :-)
#1.organizationName		= Second Organization Name (eg, company)
#1.organizationName_default	= World Wide Web Pty Ltd

organizationalUnitName		= Organizational Unit Name (eg, section)
#organizationalUnitName_default	=

commonName			= Common Name (e.g. server FQDN or YOUR name)
commonName_max			= 64

emailAddress			= Email Address
emailAddress_max		= 64

# SET-ex3			= SET extension number 3

[ req_attributes ]
challengePassword		= A challenge password
challengePassword_min		= 4
challengePassword_max		= 20

unstructuredName		= An optional company name

[ usr_cert ]

# These extensions are added when 'ca' signs a request.

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

basicConstraints=CA:FALSE

# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.

# This is OK for an SSL server.
# nsCertType			= server

# For an object signing certificate this would be used.
# nsCertType = objsign

# For normal client use this is typical
# nsCertType = client, email

# and for everything including object signing:
# nsCertType = client, email, objsign

# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment
# keyUsage = digitalSignature
keyUsage = keyEncipherment

# This will be displayed in Netscape's comment listbox.
nsComment			= "OpenSSL Generated Certificate"

# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer

# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren't
# deprecated according to PKIX.
# subjectAltName=email:move

# Copy subject details
# issuerAltName=issuer:copy

#nsCaRevocationUrl		= http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName

# This is required for TSA certificates.
# extendedKeyUsage = critical,timeStamping

[ v3_req ]

# Extensions to add to a certificate request

basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature


[ v3enc_req ]

# Extensions to add to a certificate request

basicConstraints = CA:FALSE
keyUsage = keyAgreement, keyEncipherment, dataEncipherment




[ v3_ca ]


# Extensions for a typical CA


# PKIX recommendation.

subjectKeyIdentifier=hash

authorityKeyIdentifier=keyid:always,issuer

basicConstraints = critical,CA:true

# Key usage: this is typical for a CA certificate. However since it will
# prevent it being used as an test self-signed certificate it is best
# left out by default.
keyUsage = cRLSign, keyCertSign

# Some might want this also
# nsCertType = sslCA, emailCA

# Include email address in subject alt name: another PKIX recommendation
# subjectAltName=email:copy
# Copy issuer details
# issuerAltName=issuer:copy

# DER hex encoding of an extension: beware experts only!
# obj=DER:02:03
# Where 'obj' is a standard or added object
# You can even override a supported extension:
# basicConstraints= critical, DER:30:03:01:01:FF

[ crl_ext ]

# CRL extensions.
# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.

# issuerAltName=issuer:copy
authorityKeyIdentifier=keyid:always

[ proxy_cert_ext ]
# These extensions should be added when creating a proxy certificate

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

basicConstraints=CA:FALSE

# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.

# This is OK for an SSL server.
# nsCertType			= server

# For an object signing certificate this would be used.
# nsCertType = objsign

# For normal client use this is typical
# nsCertType = client, email

# and for everything including object signing:
# nsCertType = client, email, objsign

# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

# This will be displayed in Netscape's comment listbox.
nsComment			= "OpenSSL Generated Certificate"

# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer

# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren't
# deprecated according to PKIX.
# subjectAltName=email:move

# Copy subject details
# issuerAltName=issuer:copy

#nsCaRevocationUrl		= http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName

# This really needs to be in place for it to be a proxy certificate.
proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo

####################################################################
[ tsa ]

default_tsa = tsa_config1	# the default TSA section

[ tsa_config1 ]

# These are used by the TSA reply generation only.
dir		= ./demoCA		# TSA root directory
serial		= $dir/tsaserial	# The current serial number (mandatory)
crypto_device	= builtin		# OpenSSL engine to use for signing
signer_cert	= $dir/tsacert.pem 	# The TSA signing certificate
					# (optional)
certs		= $dir/cacert.pem	# Certificate chain to include in reply
					# (optional)
signer_key	= $dir/private/tsakey.pem # The TSA private key (optional)
signer_digest	= sm3			# Signing digest to use. (Optional)
default_policy	= tsa_policy1		# Policy if request did not specify it
					# (optional)
other_policies	= tsa_policy2, tsa_policy3		# acceptable policies (optional)
digests		= sm3, sha256, sha384, sha512		# Acceptable message digests (mandatory)
accuracy	= secs:1, millisecs:500, microsecs:100	# (optional)
clock_precision_digits  = 0	# number of digits after dot. (optional)
ordering		= yes	# Is ordering defined for timestamps?
				# (optional, default: no)
tsa_name		= yes	# Must the TSA name be included in the reply?
				# (optional, default: no)
ess_cert_id_chain	= no	# Must the ESS cert id chain be included?
				# (optional, default: no)

createGmKey.sh

    # 生成CA证书
	/usr/local/gmssl/bin/gmssl ecparam -genkey -name sm2p256v1 -noout -out root.key
	/usr/local/gmssl/bin/gmssl req -new -key root.key -out root.req -subj "/C=CN/ST=BeiJing/L=BeiJing/O=WYW/CN=LLL"
	/usr/local/gmssl/bin/gmssl x509 -req -days 3650 -sm3 -in root.req -extfile openssl.cnf -extensions v3_ca -signkey root.key -out root.crt

	# Server签名证书
	/usr/local/gmssl/bin/gmssl ecparam -name sm2p256v1 -genkey -noout -out server.key
	/usr/local/gmssl/bin/gmssl req -new -SM3 -key server.key -out server.csr -subj /C=CN/ST=BeiJing/L=BeiJing/O=WYW/CN="LLL"
	/usr/local/gmssl/bin/gmssl x509 -req -SM3 -days 3650 -in server.csr -extfile openssl.cnf -extensions v3_req -CA root.crt -CAkey root.key -set_serial 1000000001 -out server.crt

	# Server加密证书
	/usr/local/gmssl/bin/gmssl ecparam -name sm2p256v1 -genkey -noout -out server_en.key
	/usr/local/gmssl/bin/gmssl req -new -SM3 -key server_en.key -out server1.csr -subj /C=CN/ST=BeiJing/L=BeiJing/O=WYW/CN="LLL"
	/usr/local/gmssl/bin/gmssl x509 -req -SM3 -days 3650 -in server1.csr -extfile openssl.cnf -extensions v3enc_req -CA root.crt -CAkey root.key -set_serial 1000002001 -out server_en.crt
点赞 点赞 0
评论 0
书签 书签 10
国密GmSSL安装包+国密Nginx安装包+搭建国密应用服务器
10-30
资源含国密GmSSL安装包和国密Nginx安装包，这些安装包适合用于搭建国密应用服务器 GmSSL-master.zip nginx-1.21.6.zip
nginx gmcurl gmssl
05-16
nginx in linux 32 with gmtls support 国密gmssl gmtls 支持的 nginx 在 linux 32 中可以用 gmcurl 与 360国密浏览器 都可以 支持
nginx国密证书(gmssl)安装
qq_44877496的博客
04-25 4463
本文档基于此安装包安装若目标机无法上网，无法执行yum，可通过手动下载安装包，rpm执行安装，部分rpm安装包如下。
centos使用nginx部署国密SSL证书
dong123aaa的博客
11-03 1568
6) 编辑auto/lib/openssl/conf，将全部$OPENSSL/.openssl/修改为$OPENSSL/并保存。2) 解压 tar xzfm gmssl_openssl_1.1_bxx.tar.gz -C /usr/local。1) 下载gmssl_openssl_1.1_bxx.tar.gz到/root/下。9) /usr/local/nginx即为生成的nginx目录。5) 进入目录 cd /root/nginx-1.24.0。（1）采用RPM包安装（源码包没有gcc环境无法编译）
Nginx 1.25.3 下 SM2 国密证书配置全流程（含OpenSSL 3.0生成CSR避坑指南）
weixin_30296405的博客
03-30 358
本文详细介绍了在Nginx 1.25.3环境下配置SM2国密证书的全流程，包括OpenSSL 3.0生成CSR的避坑指南。从环境准备、密钥对生成到Nginx专属配置，提供了一套经过生产验证的完整方案，帮助开发者高效部署国密加密证书，确保HTTPS服务的安全性和兼容性。
nginx 同一端口同时支持国密和标密功能
Big_Bristlegass的博客
08-01 1903
nginx支持同一端口，支持国密和标密
Nginx国密改造
qq_49081692的博客
05-31 4952
国密web服务器，国密nginx，nginx国密，国密改造
构建网络信息安全的中国方案 - 国密SSL/TLCP协议介绍以及国密Nginx服务器部署
热门推荐
new9232的博客
01-07 1万+
国密SSL协议指的是采用国密算法，符合国密标准的安全传输协议。简而言之，国密SSL就是SSL/TLS协议的国密版本。
从协议到实践：国密TLCP协议深度解析与Nginx国密化改造实战
weixin_42567752的博客
05-16 285
本文深度解析国密TLCP协议的设计原理与优势，并提供Nginx国密化改造的实战指南。通过对比国密SSL与TLCP的特性差异，详细讲解TLCP协议栈及双证书机制，并给出从环境准备到编译安装、关键配置的完整部署流程，帮助开发者快速实现国密算法在传输层的标准化应用。
国密TLS实战：在Nginx/OpenSSL中启用ECDHE-SM4-SM3套件背后的SM2密钥交换
最新发布
weixin_33727510的博客
05-17 486
本文详细介绍了在Nginx/OpenSSL中启用国密TLS套件ECDHE-SM4-SM3的实践方法，重点解析了SM2密钥交换的技术原理与实现步骤。通过编译支持SM2的OpenSSL、生成SM2证书以及优化Nginx配置，帮助开发者在金融、政务等关键领域部署高安全性的国密TLS通信方案。
SM2证书验签实战：从‘Unknown named curve‘报错到完整HTTPS国密通信的调试过程
k6l7m8n9的博客
02-26 616
本文详细记录了在Java项目中解决SM2证书加载时遇到的'Unknown named curve'报错的完整过程。通过深入分析报错根源，并正确集成BouncyCastle加密提供者，文章提供了从证书加载、构建国密HTTPS客户端到服务端（Tomcat/Nginx）配置的实战指南，最终实现完整的国密HTTPS双向认证通信。
国密Nginx容器化实战：从零构建支持TLCP协议的Docker镜像
weixin_29210759的博客
02-02 370
本文详细介绍了如何从零构建支持TLCP协议的国密Nginx Docker镜像，涵盖国密SSL与TLCP协议基础、容器化部署优势、镜像构建步骤及性能优化技巧。通过实战案例展示国密算法在金融级场景中的应用，帮助开发者快速实现安全高效的服务器部署。
基于GmSSL搭建Nginx国密反向代理服务器
weixin_45548465的博客
05-22 7000
环境：centos7 1810 安装编译依赖包 yum install -y vim lrzsz tree screen psmisc lsof tcpdump wget ntpdate gcc gcc-c++ glibc glibc-devel pcre pcre-devel openssl openssl-devel systemd-devel net-tools iotop bc zip unzip zlib-devel bash-completion nfs-utils automake libxm
搭建支持国密GmSSL的Nginx环境
m0_46665077的博客
10-30 3560
搭建基于国密Nginx的应用服务，国密GmSSL、国密Nginx
国密 SM2 SSL 证书 Nginx 安装指南 linux版
wwwwestcn的博客
10-25 2907
1) 下载 wget http://download.myhostadmin.net/gmssl/gmssl_openssl_1.1_b8.tar.gz到/root/下。3) 下载wget http://download.myhostadmin.net/gmssl/nginx-1.18.0.zip 到/root/下。*.***.com_encryptKeyData.txt：内容为已加密的加密证书私钥片段。*.***.com_encrypt.crt：加密证书。
国密版 Nginx服务器安装
啊渊的专栏
11-01 5788
一、简介 GMSSL提供一个国密版OpenSSL和国密版Nginx，支持单向/双向认证，支持标准SSL/国密SSL自适应。 其中国密版OpenSSL基于OpenSSL1.1.1d实现，且已经修正了CVE-2020-1967。 证书申请 https://gmssl.cn/gmssl/index.jsp 二、运行环境 Centos7 x86_64 三、下载 yum install wget -y 国密OpenSSL与国密Nginxgmssl_openssl_1.1_bxx.tar.gz...
国密NGINX（tengine）部署web测试
Youdef
06-21 1495
因没有国密SSL浏览器，打开了rsa证书验证可访问。1、安装tengine+tongsuo。4、国密浏览器或命令行验证。2、配置conf证书。
Nginx国密支持问题记录
zhangdm的博客
03-03 2258
NGINX 增加国密支持
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值