SSL mit Debian HowTo

FreeBSD, Gentoo, openSUSE, CentOS, Ubuntu, Debian
Post Reply
tommytom
Posts: 39
Joined: 2003-11-02 01:52
 

SSL mit Debian HowTo

Post by tommytom »

habe debian nun erfolgreich installiert..
ebenfalls confixx
was ich allerdings nicht zum laufen bekomme ist https://

Code: Select all

Port       State       Service
21/tcp     open        ftp
22/tcp     open        ssh
25/tcp     open        smtp
80/tcp     open        http
110/tcp    open        pop-3
443/tcp    open        https
obwohl dort https angezeigt wird bei nmap localhost bekomme ich immer eine fehler seite wenn ich meinen url mit https://name.tld aufrufe...

ich weiss nicht was ich falsch mache.. habe eigentlich auch alles in die httpd.conf eingetragen und einer zertifikat erstellt...

tom
[/quote]
wirsing
Posts: 604
Joined: 2002-11-20 21:32
Location: Vaihingen und Karlsruhe
 

Re: SSL mit Debian HowTo

Post by wirsing »

netstat -ntlp
tommytom
Posts: 39
Joined: 2003-11-02 01:52
 

Re: SSL mit Debian HowTo

Post by tommytom »

wirsing wrote:netstat -ntlp
bringt das ergebnis:

Code: Select all

netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:110             0.0.0.0:*               LISTEN      294/tcpserver
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1013/apache
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN      308/xinetd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      300/sshd
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      287/
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      1013/apache
genau so kommt es raus!

wirsing: was genau kann ich hier sehen?
wirsing
Posts: 604
Joined: 2002-11-20 21:32
Location: Vaihingen und Karlsruhe
 

Re: SSL mit Debian HowTo

Post by wirsing »

Zumindest, dass der Port 443 (https) von Apache belegt ist - jetzt wäre es sinnvoll, mal die Apache-Konfiguration und die Domain herauszurücken, damit wir uns das ansehen können. Die Apache-Konfiguration am Besten auf deinem Webspace mit Link dahin.
tommytom
Posts: 39
Joined: 2003-11-02 01:52
 

Re: SSL mit Debian HowTo

Post by tommytom »

ok:
http://web1.xxxx.de/myconf.txt

das düfte hoffentlich nicht zu insecure sein!?

tom
Last edited by tommytom on 2003-11-05 23:03, edited 1 time in total.
tommytom
Posts: 39
Joined: 2003-11-02 01:52
 

Re: SSL mit Debian HowTo

Post by tommytom »

also mit

Code: Select all

telnet xxxxxxx.de 443
passiert nichts...

und es kommt noch besser

jetzt (ohne änderung)

Code: Select all

netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:110             0.0.0.0:*               LISTEN      294/tcpserver
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1396/apache
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN      308/xinetd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      300/sshd
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      287/
port 443 ist weg!!!!!!!!!!!!! ich habe nichts geändert... oder vielleicht ein anderer von euch :wink:
Last edited by tommytom on 2003-11-05 23:03, edited 1 time in total.
wirsing
Posts: 604
Joined: 2002-11-20 21:32
Location: Vaihingen und Karlsruhe
 

Re: SSL mit Debian HowTo

Post by wirsing »

Das ist genau was ich meinte.
Also wenn ich versuche auf diesen Server mit SSL zuzugreifen, kommt Connection refused, d.h. da läuft gar nichts auf Port 443 - oder ist das ein anderer Server?
Interessant wären übrigens noch /etc/apache/conf/confixx_vhost.conf und ein Logauszug (sowohl acces_log als auch error_log) wenn jemand zugreift.
Wenn du nicht die ganze confixx_vhost.conf angeben willst, dann kannst du die vhosts weglassen, die mit "<VirtualHost 217.160.200.238:80>" beginnen.
tommytom
Posts: 39
Joined: 2003-11-02 01:52
 

Re: SSL mit Debian HowTo

Post by tommytom »

probiers noch mal.. ich hatte bevor ich euch die conf gab noch das hier dummerweise Ã?BER die loadmodules gemacht:

<IfModule mod_ssl.c>
Listen 80
Listen 443
</IfModule>


das steht jetzt drunter und nun läuft auch wieder der listen....

Code: Select all

nmap localhost

Starting nmap V. 2.54BETA31 ( www.insecure.org/nmap/ )
Interesting ports on localhost (127.0.0.1):
(The 1548 ports scanned but not shown below are in state: closed)
Port       State       Service
21/tcp     open        ftp
22/tcp     open        ssh
25/tcp     open        smtp
80/tcp     open        http
110/tcp    open        pop-3
443/tcp    open        https
wenn du immer noch files brauchst.. sag bescheid
wirsing
Posts: 604
Joined: 2002-11-20 21:32
Location: Vaihingen und Karlsruhe
 

Re: SSL mit Debian HowTo

Post by wirsing »

Immer noch dieselben.
tommytom
Posts: 39
Joined: 2003-11-02 01:52
 

Re: SSL mit Debian HowTo

Post by tommytom »

habe gerade was interessantes festgestellt:

in einem backup von meinem suse httpd.conf file ist folgende passage drin:

Code: Select all

##
##  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
#
<IfDefine SSL>
AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl    .crl
</IfDefine>

<IfModule mod_ssl.c>

#   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        none
#SSLSessionCache        shmht:/var/run/ssl_scache(512000)
#SSLSessionCache        shmcb:/var/run/ssl_scache(512000)
SSLSessionCache         dbm:/var/run/ssl_scache
SSLSessionCacheTimeout  300

#   Semaphore:
#   Configure the path to the mutual exclusion semaphore the
#   SSL engine uses internally for inter-process synchronization. 
SSLMutex  file:/var/run/ssl_mutex

#   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 builtin
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random  512
#SSLRandomSeed startup file:/dev/urandom 512
#SSLRandomSeed connect file:/dev/random  512
#SSLRandomSeed connect file:/dev/urandom 512

#   Logging:
#   The home of the dedicated SSL protocol logfile. Errors are
#   additionally duplicated in the general error log file.  Put
#   this somewhere where it cannot be used for symlink attacks on
#   a real server (i.e. somewhere where only root can write).
#   Log levels are (ascending order: higher ones include lower ones):
#   none, error, warn, info, trace, debug.
SSLLog      /var/log/httpd/ssl_engine_log
SSLLogLevel info

</IfModule>

<IfDefine SSL>

##
## SSL Virtual Host Context
##

# SSL-confixx:
NameVirtualHost 217.160.xxx.xxx:443
<VirtualHost 217.160.xxx.xxx:443>
  ServerName confixx.xxxxkxxxx.de
  #User confixx
  #Group users
  DocumentRoot /home/www/confixx/html
  php_admin_value safe_mode_exec_dir /home/www/confixx/bin
  php_admin_value upload_tmp_dir /home/www/confixx/tmp
  ScriptAlias /cgi-bin/ /home/www/confixx/html/cgi-bin/
  #CustomLog /var/log/httpd/xxxxxxxx.de_access.log "%h %l %u %t "%r" %s %b "%{Referer}i" "%{User-agent}i""
  #ErrorLog /var/log/httpd/xxxxxxxxx.de_error.log

  ServerAdmin webmaster@xxxxxxxxx.de
  ErrorLog /var/log/httpd/ssl-error_log
  TransferLog /var/log/httpd/ssl-access_log

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

  #   SSL Cipher Suite:
  #   List the ciphers that the client is permitted to negotiate.
  #   See the mod_ssl documentation for a complete list.
  SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL

  #   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. A test
  #   certificate can be generated with `make certificate' under
  #   built time. Keep in mind that if you've both a RSA and a DSA
  #   certificate you can configure both in parallel (to also allow
  #   the use of DSA ciphers, etc.)
  SSLCertificateFile /etc/httpd/ssl.crt/server.crt
  #SSLCertificateFile /etc/httpd/ssl.crt/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 /etc/httpd/ssl.key/server.key
  #SSLCertificateKeyFile /etc/httpd/ssl.key/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 /etc/httpd/ssl.crt/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/httpd/ssl.crt
  #SSLCACertificateFile /etc/httpd/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/httpd/ssl.crl
  #SSLCARevocationFile /etc/httpd/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 CompatEnvVars:
  #     This exports obsolete environment variables for backward compatibility
  #     to Apache-SSL 1.x, mod_ssl 2.0.x, Sioux 1.0 and Stronghold 2.x. Use this
  #     to provide compatibility to existing CGI scripts.
  #   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 +CompatEnvVars +StrictRequire
  <Files ~ ".(cgi|shtml|phtml|php3?)$">
      SSLOptions +StdEnvVars
  </Files>
  <Directory "/srv/www/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.
  SetEnvIf User-Agent ".*MSIE.*" 
           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 /var/log/httpd/ssl_request_log 
            "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x "%r" %b"
  
</VirtualHost>                                  

</IfDefine>
warum hat das die neuste confixx version vom update server nicht mitinstalliert?
wirsing
Posts: 604
Joined: 2002-11-20 21:32
Location: Vaihingen und Karlsruhe
 

Re: SSL mit Debian HowTo

Post by wirsing »

Eine Frage: Warum willst du eigentlich nicht mehr, dass man dir hilft?
tommytom
Posts: 39
Joined: 2003-11-02 01:52
 

Re: SSL mit Debian HowTo

Post by tommytom »

das problem liegt definitiv an meiner confixx installation. es fehlt "lediglich" die konfiguration von sll.

ich weiss nicht warum es dort nicht drin ist und ob das alles von confixx allein kommt. ich habe aber auch keine .bakup files von den installern der tools - sodas man nicht unbedingt ausgehen kann das ich vergessen habe soetwas "zusammenzufügen" ..

übrigens mit

Code: Select all

telnet xxxxxxxx.de 443
spricht sehr wohl der server an... ich sage mal der schlüssel liegt hier in der httpd.conf
Post Reply