注册
登录
关注:
官网首页
阿里云8折
论坛
wdCDN系统
智能DNS软件
搜索
私人消息 (0)
公共消息 (0)
论坛任务 (0)
系统消息 (0)
好友消息 (0)
帖子消息 (0)
WDlinux官方论坛
»
lamp|lnmp|lnamp|一键安装包
» 老大求解啊,还是昨天那个ssl问题
无标题文档
wdCP系统
(
介绍
,
功能特性
,
运行环境
,
安装说明
,
演示
,
常见问题
,
使用教程
)
wdCDN系统
(
介绍
,
功能特性
,
运行环境
,
安装说明
,
演示
,
常见问题
,
使用手册
)
wdOS系统
(
介绍
,
功能特性
,
运行环境
,
安装说明
,
演示
,
常见问题
,
使用教程
)
wdDNS系统
(
介绍
,
功能特性
,
运行环境
,
安装说明
,
演示
,
常见问题
,
使用手册
)
注册 发贴 提问 回复-必看必看
wddns免费智能 DNS
开通
本地或虚拟机使 用wdcp
一键包在mysql编 译时"卡住"
【300G高防】双线 无视攻击
wdcp官方技术支持/服务
阿里云8折优惠券
无敌云
腾讯云优惠中,现注册更有260代金额券赠送
返回列表
发帖
zhxuri
发短消息
加为好友
zhxuri
当前离线
UID
7162
帖子
23
精华
0
积分
104
阅读权限
20
在线时间
32 小时
注册时间
2012-6-12
最后登录
2018-5-7
注册会员
1
#
跳转到
»
倒序看帖
打印
字体大小:
t
T
发表于 2012-6-13 09:32
|
只看该作者
提问三步曲:
提问先看教程/FAQ索引(
wdcp
,
wdcp_v3
,
一键包
)及搜索,会让你更快解决问题
1 提供详细,如系统版本,wdcp版本,软件版本等及错误的详细信息,贴上论坛或截图发论坛
2 做过哪些操作或改动设置等
温馨提示:信息不详,很可能会没人理你!论坛有教程说明的,也可能没人理!因为,你懂的
[求助]
老大求解啊,还是昨天那个ssl问题
我昨天照着老大发的链接配置ssl出现了报错httpd无法启动
提示是/www/wdlinux/httpd-2.2.22/conf/extra/httpd-ssl.conf里有错误
我根据报错的位置一个一个注释下去,报错的问题就一个一个的出来
SSLPassPhraseDialog 第一次报错是提示这个
SSLSessionCache 第二次
SSLMutex 第三次
SSLEngine 的四次
第五次我崩溃了,我又来发帖求助了,ssl很有用,目前也很棘手,老大
收藏
分享
zhxuri
发短消息
加为好友
zhxuri
当前离线
UID
7162
帖子
23
精华
0
积分
104
阅读权限
20
在线时间
32 小时
注册时间
2012-6-12
最后登录
2018-5-7
注册会员
2
#
发表于 2012-6-13 09:41
|
只看该作者
这个问题是给httpd.conf下的Include conf/extra/httpd-ssl.conf去掉注释后出现的
然后问题就出在httpd-ssl.conf里了
下面是我的httpd-ssl.conf大家帮忙看看是哪里出了问题啊,我的是最新的lanmp包啊是阿里云的vps
TOP
zhxuri
发短消息
加为好友
zhxuri
当前离线
UID
7162
帖子
23
精华
0
积分
104
阅读权限
20
在线时间
32 小时
注册时间
2012-6-12
最后登录
2018-5-7
注册会员
3
#
发表于 2012-6-13 09:42
|
只看该作者
#
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailing information about these
# directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
#
# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the SSL library.
# The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.
#
#SSLRandomSeed startup file:/dev/random 512
#SSLRandomSeed startup file:/dev/urandom 512
#SSLRandomSeed connect file:/dev/random 512
#SSLRandomSeed connect file:/dev/urandom 512
#
# When we also provide SSL we have to listen to the
# standard HTTP port (see above) and to the HTTPS port
#
# Note: Configurations that use IPv6 but not IPv4-mapped addresses need two
# Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443"
#
Listen 443
##
## SSL Global Context
##
## All SSL configuration in this context applies both to
## the main server and all SSL-enabled virtual hosts.
##
#
# Some MIME-types for downloading Certificates and CRLs
#
AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl .crl
# Pass Phrase Dialog:
# Configure the pass phrase gathering process.
# The filtering dialog program (`builtin' is a internal
# terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog builtin
# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds).
#SSLSessionCache "dbm:/www/wdlinux/httpd-2.2.22/logs/ssl_scache"
SSLSessionCache "shmcb:/www/wdlinux/httpd-2.2.22/logs/ssl_scache(512000)"
SSLSessionCacheTimeout 300
# Semaphore:
# Configure the path to the mutual exclusion semaphore the
# SSL engine uses internally for inter-process synchronization.
SSLMutex "file:/www/wdlinux/httpd-2.2.22/logs/ssl_mutex"
##
## SSL Virtual Host Context
##
复制代码
TOP
zhxuri
发短消息
加为好友
zhxuri
当前离线
UID
7162
帖子
23
精华
0
积分
104
阅读权限
20
在线时间
32 小时
注册时间
2012-6-12
最后登录
2018-5-7
注册会员
4
#
发表于 2012-6-13 09:43
|
只看该作者
<VirtualHost _default_:443>
# General setup for the virtual host
DocumentRoot "/www/wdlinux/httpd-2.2.22/htdocs"
ServerName www.example.com:443
ServerAdmin fjsh@fjsh.com
ErrorLog "/www/wdlinux/httpd-2.2.22/logs/error_log"
TransferLog "/www/wdlinux/httpd-2.2.22/logs/access_log"
# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
SSLEngine on
# SSL Protocol support:
# List the protocol versions which clients are allowed to
# connect with. Disable SSLv2 by default (cf. RFC 6176).
SSLProtocol all -SSLv2
# SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite HIGH:MEDIUM:!aNULL:!MD5
# Speed-optimized SSL Cipher configuration:
# If speed is your main concern (on busy HTTPS servers e.g.),
# you might want to force clients to specific, performance
# optimized ciphers. In this case, prepend those ciphers
# to the SSLCipherSuite list, and enable SSLHonorCipherOrder.
# Caveat: by giving precedence to RC4-SHA and AES128-SHA
# (as in the example below), most connections will no longer
# have perfect forward secrecy - if the server's key is
# compromised, captures of past or future traffic must be
# considered compromised, too.
#SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5
#SSLHonorCipherOrder on
# Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate. If
# the certificate is encrypted, then you will be prompted for a
# pass phrase. Note that a kill -HUP will prompt again. Keep
# in mind that if you have both an RSA and a DSA certificate you
# can configure both in parallel (to also allow the use of DSA
# ciphers, etc.)
SSLCertificateFile "/www/wdlinux/httpd-2.2.22/conf/server.crt"
#SSLCertificateFile "/www/wdlinux/httpd-2.2.22/conf/server-dsa.crt"
# Server Private Key:
# If the key is not combined with the certificate, use this
# directive to point at the key file. Keep in mind that if
# you've both a RSA and a DSA private key you can configure
# both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile "/www/wdlinux/httpd-2.2.22/conf/server.key"
#SSLCertificateKeyFile "/www/wdlinux/httpd-2.2.22/conf/server-dsa.key"
# Server Certificate Chain:
# Point SSLCertificateChainFile at a file containing the
# concatenation of PEM encoded CA certificates which form the
# certificate chain for the server certificate. Alternatively
# the referenced file can be the same as SSLCertificateFile
# when the CA certificates are directly appended to the server
# certificate for convinience.
#SSLCertificateChainFile "/www/wdlinux/httpd-2.2.22/conf/server-ca.crt"
# Certificate Authority (CA):
# Set the CA certificate verification path where to find CA
# certificates for client authentication or alternatively one
# huge file containing all of them (file must be PEM encoded)
# Note: Inside SSLCACertificatePath you need hash symlinks
# to point to the certificate files. Use the provided
# Makefile to update the hash symlinks after changes.
#SSLCACertificatePath "/www/wdlinux/httpd-2.2.22/conf/ssl.crt"
#SSLCACertificateFile "/www/wdlinux/httpd-2.2.22/conf/ssl.crt/ca-bundle.crt"
# Certificate Revocation Lists (CRL):
# Set the CA revocation path where to find CA CRLs for client
# authentication or alternatively one huge file containing all
# of them (file must be PEM encoded)
# Note: Inside SSLCARevocationPath you need hash symlinks
# to point to the certificate files. Use the provided
# Makefile to update the hash symlinks after changes.
#SSLCARevocationPath "/www/wdlinux/httpd-2.2.22/conf/ssl.crl"
#SSLCARevocationFile "/www/wdlinux/httpd-2.2.22/conf/ssl.crl/ca-bundle.crl"
# Client Authentication (Type):
# Client certificate verification type and depth. Types are
# none, optional, require and optional_no_ca. Depth is a
# number which specifies how deeply to verify the certificate
# issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth 10
# Access Control:
# With SSLRequire you can do per-directory access control based
# on arbitrary complex boolean expressions containing server
# variable checks and other lookup directives. The syntax is a
# mixture between C and Perl. See the mod_ssl documentation
# for more details.
#<Location />
#SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
# and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
# and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
# and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
# and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
# or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#</Location>
# SSL Engine Options:
# Set various options for the SSL engine.
# o FakeBasicAuth:
# Translate the client X.509 into a Basic Authorisation. This means that
# the standard Auth/DBMAuth methods can be used for access control. The
# user name is the `one line' version of the client's X.509 certificate.
# Note that no password is obtained from the user. Every entry in the user
# file needs this password: `xxj31ZMTZzkVA'.
# o ExportCertData:
# This exports two additional environment variables: SSL_CLIENT_CERT and
# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
# server (always existing) and the client (only existing when client
# authentication is used). This can be used to import the certificates
# into CGI scripts.
# o StdEnvVars:
# This exports the standard SSL/TLS related `SSL_*' environment variables.
# Per default this exportation is switched off for performance reasons,
# because the extraction step is an expensive operation and is usually
# useless for serving static content. So one usually enables the
# exportation for CGI and SSI requests only.
# o StrictRequire:
# This denies access when "SSLRequireSSL" or "SSLRequire" applied even
# under a "Satisfy any" situation, i.e. when it applies access is denied
# and no other module can change it.
# o OptRenegotiate:
# This enables optimized SSL connection renegotiation handling when SSL
# directives are used in per-directory context.
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<FilesMatch "\.(cgi|shtml|phtml|php)$">
SSLOptions +StdEnvVars
</FilesMatch>
<Directory "/www/wdlinux/httpd-2.2.22/cgi-bin">
SSLOptions +StdEnvVars
</Directory>
# SSL Protocol Adjustments:
# The safe and default but still SSL/TLS standard compliant shutdown
# approach is that mod_ssl sends the close notify alert but doesn't wait for
# the close notify alert from client. When you need a different shutdown
# approach you can use one of the following variables:
# o ssl-unclean-shutdown:
# This forces an unclean shutdown when the connection is closed, i.e. no
# SSL close notify alert is send or allowed to received. This violates
# the SSL/TLS standard but is needed for some brain-dead browsers. Use
# this when you receive I/O errors because of the standard approach where
# mod_ssl sends the close notify alert.
# o ssl-accurate-shutdown:
# This forces an accurate shutdown when the connection is closed, i.e. a
# SSL close notify alert is send and mod_ssl waits for the close notify
# alert of the client. This is 100% SSL/TLS standard compliant, but in
# practice often causes hanging connections with brain-dead browsers. Use
# this only for browsers where you know that their SSL implementation
# works correctly.
# Notice: Most problems of broken clients are also related to the HTTP
# keep-alive facility, so you usually additionally want to disable
# keep-alive for those clients, too. Use variable "nokeepalive" for this.
# Similarly, one has to force some clients to use HTTP/1.0 to workaround
# their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
# "force-response-1.0" for this.
BrowserMatch "MSIE [2-5]" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
# Per-Server Logging:
# The home of a custom SSL log file. Use this when you want a
# compact non-error SSL logfile on a virtual host basis.
CustomLog "/www/wdlinux/httpd-2.2.22/logs/ssl_request_log" \
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
</VirtualHost>
复制代码
TOP
zhxuri
发短消息
加为好友
zhxuri
当前离线
UID
7162
帖子
23
精华
0
积分
104
阅读权限
20
在线时间
32 小时
注册时间
2012-6-12
最后登录
2018-5-7
注册会员
5
#
发表于 2012-6-13 09:45
|
只看该作者
老大昨天发的那个链接我在lamp包里测试没啥问题 但是到了我的这个lnamp就悲剧了。这个事怎么回事呢。
怎么弄都是在报错
TOP
admin
发短消息
加为好友
admin
当前离线
UID
1
帖子
9587
精华
3
积分
29636
阅读权限
200
在线时间
17618 小时
注册时间
2011-11-15
最后登录
2024-8-30
管理员
6
#
发表于 2012-6-13 10:01
|
只看该作者
用到lnamp后,apache成了后端的服务,前端是nginx
你在nginx里,加上对SSL的转发试试
看清提问三步曲及多看教程/FAQ索引(
wdcp
,
v3
,
一键包
,
wdOS
),益处多多.
wdcp工具集
阿里云主机8折优惠码
TOP
zhxuri
发短消息
加为好友
zhxuri
当前离线
UID
7162
帖子
23
精华
0
积分
104
阅读权限
20
在线时间
32 小时
注册时间
2012-6-12
最后登录
2018-5-7
注册会员
7
#
发表于 2012-6-13 11:38
|
只看该作者
我去试试看 拿nginx做ssl看下行不行
TOP
zhxuri
发短消息
加为好友
zhxuri
当前离线
UID
7162
帖子
23
精华
0
积分
104
阅读权限
20
在线时间
32 小时
注册时间
2012-6-12
最后登录
2018-5-7
注册会员
8
#
发表于 2012-6-13 15:36
|
只看该作者
感谢老大!成功了就是nginx。lanmp里面还有个nginx我竟然忘了,好惭愧啊!
现在去申请一个免费证书玩下,哈哈哈哈哈哈
TOP
admin
发短消息
加为好友
admin
当前离线
UID
1
帖子
9587
精华
3
积分
29636
阅读权限
200
在线时间
17618 小时
注册时间
2011-11-15
最后登录
2024-8-30
管理员
9
#
发表于 2012-6-13 18:50
|
只看该作者
把具体的操作也说明下,方便后来人参考
看清提问三步曲及多看教程/FAQ索引(
wdcp
,
v3
,
一键包
,
wdOS
),益处多多.
wdcp工具集
阿里云主机8折优惠码
TOP
374399415
发短消息
加为好友
374399415
当前离线
UID
16057
帖子
20
精华
0
积分
101
阅读权限
20
在线时间
60 小时
注册时间
2013-1-25
最后登录
2014-3-11
注册会员
10
#
发表于 2013-10-24 08:27
|
只看该作者
老大把lanmp ssl设置说明写一下么。。。
TOP
返回列表
我的Linux|wdlinux
ai|大模型|大数据
开源精选
wdCP V3|Linux服务器/云主机/虚拟主机管理系统
wddns|智能DNS系统|免费智能DNS解析
lamp|lnmp|lnamp|一键安装包
wdCP V2|linux下免费的服务器/虚拟主机管理系统
wdcdn系统|CDN缓存加速管理系统
wdOS|CentOS精简版|CentOS定制版
区块链技术|智能合约|区块链开发
wdlinux学堂|wdOS知识库|linux知识库|教程|文档
站务管理
站务管理
[收藏此主题]
[关注此主题的新回复]
[通过 QQ、MSN 分享给朋友]