새로 고침 실패 - 우분투 15.04 - 내 로그 아파치에 오류가 발생했습니다

Question

SSL 암호 초기화를 입력 할 때 :
/etc/init.d/apache2 reload

[(화) 년 2 월 14 15 : 53 : 2017 59.437078] [SSL : emerg가] [PID를 15072] AH02580 : 초기화 : 키 www.XXX.com:443에 대한 패스 문구가 잘못되었습니다.
[Tue Feb 14 15 : 53 : 59.437128 2017] [ssl : emerg] [pid 15072] SSL 라이브러리 오류 : 오류 : 0D0680A8 : asn1 인코딩 루틴 : ASN1_CHECK_TLEN : 잘못된 태그
[2 월 14 일 15 : 53 : 59.437137 2017] SSL 라이브러리 오류 : 0D08303A : asn1 인코딩 루틴 : ASN1_TEMPLATE_NOEXP_D2I : 중첩 된 asn1 오류
[(화) 년 2 월 14 15 : 53 : 59.437143 2017] [SSL : emerg가] [PID 15072] SSL 라이브러리 오류 : 오류 : 0D0680A8 : ASN1 인코딩 루틴 : ASN1_CHECK_TLEN : 잘못된 태그
[(화) 년 2 월 14 15 : 53 : 59.437150 2017] SSL 라이브러리 오류 : 0D07803A : asn1 인코딩 루틴 : ASN1_ITEM_EX_D2I : 중첩 된 asn1 오류 (유형 = RSA)
[Tue Feb 14 15 : 53 : 59.437157 2017] [ssl : emerg] [SSL : pid 15072] SSL 라이브러리 오류 : 04093004 : rsa 루틴 : OLD_RSA_PRIV_DECODE : RSA 라이브러리
[2 월 14 일 15 : 53 : 59.437163 2017] [ssl : emerg] [pid 15072] SSL 라이브러리 오류 : 0D0680A8 : asn1 인코딩 SSL 라이브러리 오류 : 0D07803A : asn1 인코딩 루틴 : ASN1_ITEM_EX_D2I : 중첩 asn1 오류 (유형 = PKCS8_PRIV_KEY_INFO)
[Tue Feb 14 15 : 53 : 59.437174 2017] [ssl : emerg] [pid 15072] AH02311 : mod_ssl을 초기화하는 중 오류가 발생했습니다. 자세한 내용은 /var/log/apache2/error.log를 참조하십시오.
[Tue Feb 14 15 : 53 : 59.437177 2017] [ssl : emerg] [pid 15072] AH02564 : 암호화 된 (?) 개인 키 www.XXX를 구성하지 못했습니다. .COM : 443 : 0, AH00016 /root/www.XXXX.com.key
을 확인하십시오 구성

이 아니라 그 /etc/init.d/apache2 restart 작품을 유의하시기 바랍니다 못했습니다.
genrsa -des3 -out www.XXXX.com 2048 + 비밀번호가 있습니다 사용하여 CSR을 생성

:
req -new -key la_cle -out the_file

기본 사이트 구성은 000-default.conf 및 기본

나는 사용하여 서버에 내 키를 생성 -ssl.conf 파일 :

,

<Directory /var/www/html/> 
    Order allow,deny 
    Deny from all 
    Require all granted 
</Directory> 

# The ServerName directive sets the request scheme, hostname and port that 
# the server uses to identify itself. This is used when creating 
# redirection URLs. In the context of virtual hosts, the ServerName 
# specifies what hostname must appear in the request's Host: header to 
# match this virtual host. For the default virtual host (this file) this 
# value is not decisive as it is used as a last resort host regardless. 
# However, you must set it for any further virtual host explicitly. 
#ServerName www.example.com 

ServerAdmin webmaster@localhost 
DocumentRoot /var/www/html 

# Available loglevels: trace8, ..., trace1, debug, info, notice, warn, 
# error, crit, alert, emerg. 
# It is also possible to configure the loglevel for particular 
# modules, e.g. 
#LogLevel info ssl:warn 

ErrorLog ${APACHE_LOG_DIR}/error.log 
CustomLog ${APACHE_LOG_DIR}/access.log combined 

# For most configuration files from conf-available/, which are 
# enabled or disabled at a global level, it is possible to 
# include a line for only one particular virtual host. For example the 
# following line enables the CGI configuration for this host only 
# after it has been globally disabled with "a2disconf". 
#Include conf-available/serve-cgi-bin.conf 

# VIM : 구문 = 아파치 TS = 4 SW = 4 STS = 4 SR noet

ServerAdmin webmaster@localhost 

    DocumentRoot /var/www/html 
    ServerName www.XXXX.com 
    SSLEngine on 
    SSLCertificateFile /root/www.XXXX.com.crt 
    SSLCertificateKeyFile /root/www.XXXX.com.key 
    SSLCertificateChainFile /root/inter.www.XXXX.com.crt 
    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, 
    # error, crit, alert, emerg. 
    # It is also possible to configure the loglevel for particular 
    # modules, e.g. 
    #LogLevel info ssl:warn 

    ErrorLog ${APACHE_LOG_DIR}/error.log 
    CustomLog ${APACHE_LOG_DIR}/access.log combined 

    # For most configuration files from conf-available/, which are 
    # enabled or disabled at a global level, it is possible to 
    # include a line for only one particular virtual host. For example the 
    # following line enables the CGI configuration for this host only 
    # after it has been globally disabled with "a2disconf". 
    #Include conf-available/serve-cgi-bin.conf 

    # SSL Engine Switch: 
    # Enable/Disable SSL for this virtual host. 
    SSLEngine on 

    # A self-signed (snakeoil) certificate can be created by installing 
    # the ssl-cert package. See 
    # /usr/share/doc/apache2/README.Debian.gz for more info. 
    # If both key and certificate are stored in the same file, only the 
    # SSLCertificateFile directive is needed. 
    SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem 
    SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.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 /etc/apache2/ssl.crt/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 /etc/ssl/certs/ 
    #SSLCACertificateFile /etc/apache2/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 /etc/apache2/ssl.crl/ 
    #SSLCARevocationFile /etc/apache2/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 

    # 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 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 /usr/lib/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-6]" \ 
      nokeepalive ssl-unclean-shutdown \ 
      downgrade-1.0 force-response-1.0 
    # MSIE 7 and newer should be able to use keepalive 
    BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown 

</VirtualHost> 

# VIM : 구문 = 아파치의 TS = 4 SW = 4 sts = 4 sr noet

apache2.conf 파일 암호로 SSLPassPhraseDialog exec:/root/key-pem으로 스크립트를 만들었습니다.

왜 작동하지 않는지 알 수 없습니다.

Answer 1

불어 부분에 대해 죄송합니다. 문제가 스크립트에서 발생한다고 생각하지 않습니다. sslpassdialogphrase로 전달합니다. 암호를 손으로 쓴다면 여전히 작동하지 않기 때문입니다. 또한 같은 서버를 사용하는 다른 서버에서도 구성 할 수 있습니다. 문제는 항상 동일합니다. www.xxxx.com.key에 불일치 값이 있는데 그 이유를 알 수 없습니다. 자체 인증서를 만들려고했는데 제대로 작동합니다. 내 자체 서명 인증서에서 동일한 문제가 발생했다면 암호문을 잘못 입력했을 수도 있지만 그렇지 않은 것처럼 보입니다.