Ahoi.
Ich habe mir auf meinem rPI einen kleinen apache-server installiert, der nur ownCloud (OC) beherbergen soll. Bisher habe ich nur über das lokale Netzwerk via abc.def.ghi.jkl/owncloud auf ihn zugegriffen was auch klappt.
Nun plane ich jedoch auch aus dem Internet Zugriff auf meine Sachen zu haben und nun wird es (etwas) knackiger: dyndns ist eingerichtet und funktioniert.
Um die Verbindung zu verschlüsseln und weil ich der einzige Nutzer bin habe ich mein eigenes Zertifikat erstellthttp://superuser.com/questions/73979/how-to-easily-create-a-ssl-certificate-and-configure-it-in-apache2-in-mac-os-x#74012
Soweit ja leicht alles Schritt für Schritt abzuarbeiten.
Nun habe ich (versucht?) apache mitzuteilen, dass ich ssl benutzen will:
a2enmod ssl
apache neu gestartet und bei Eingabe von https://myadress.mydyndns.com kommt die Fehlermeldung ssl_error_rx_record_too_long. Nach der Fehlerbeschreibung gegoogled und verschiedene Ansätze gefunden, die ich nicht nachvollziehen kann, weil ich nicht genau weiß welche Datei nun wo liegt/liegen soll?! Teilweise wird von httpd.conf gesprochen, doch die Datei existiert bei mir gar nicht.
Nun habe ich jedoch /etc/apache2/sites-available/default-ssl gefunden, welche ich folgendermaßen editiert habe:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 | <IfModule mod_ssl.c> <VirtualHost _default_:443> ServerAdmin webmaster@localhost DocumentRoot /var/www <Directory /> Options FollowSymLinks AllowOverride None </Directory> <Directory /var/www/> Options Indexes FollowSymLinks MultiViews AllowOverride None Order allow,deny allow from all </Directory> ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/ <Directory "/usr/lib/cgi-bin"> AllowOverride None Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch Order allow,deny Allow from all </Directory> ErrorLog ${APACHE_LOG_DIR}/error.log # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. LogLevel warn CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined # 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.2-common/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 #SSLCertificateFile /root/server.crt #SSLCertificateKeyFile /root/server.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 SSLCACertificatePath /root/ SSLCACertificateFile /root/server.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 # 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 mea$ # the standard Auth/DBMAuth methods can be used for access control$ # user name is the `one line' version of the client's X.509 certif$ # Note that no password is obtained from the user. Every entry in $ # file needs this password: `xxj31ZMTZzkVA'. # o ExportCertData: # This exports two additional environment variables: SSL_CLIENT_CE$ # SSL_SERVER_CERT. These contain the PEM-encoded certificates of t$ # server (always existing) and the client (only existing when clie$ # authentication is used). This can be used to import the certific$ # into CGI scripts. # o StdEnvVars: # This exports the standard SSL/TLS related `SSL_*' environment va$ # Per default this exportation is switched off for performance rea$ # because the extraction step is an expensive operation and is usu$ # 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 $ # under a "Satisfy any" situation, i.e. when it applies access is $ # and no other module can change it. # o OptRenegotiate: # This enables optimized SSL connection renegotiation handling whe$ # 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 $ # the close notify alert from client. When you need a different shut$ # approach you can use one of the following variables: # o ssl-unclean-shutdown: # This forces an unclean shutdown when the connection is closed, i$ # SSL close notify alert is send or allowed to received. This vio$ # the SSL/TLS standard but is needed for some brain-dead browsers.$ # this when you receive I/O errors because of the standard approac$ # mod_ssl sends the close notify alert. # o ssl-accurate-shutdown: # This forces an accurate shutdown when the connection is closed, $ # SSL close notify alert is send and mod_ssl waits for the close n$ # alert of the client. This is 100% SSL/TLS standard compliant, bu$ # practice often causes hanging connections with brain-dead browse$ # this only for browsers where you know that their SSL implementat$ # works correctly. # Notice: Most problems of broken clients are also related to the HT$ # keep-alive facility, so you usually additionally want to disable # keep-alive for those clients, too. Use variable "nokeepalive" for $ # Similarly, one has to force some clients to use HTTP/1.0 to workar$ # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0$ # "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> </IfModule> |
Was habe ich falsch gemacht bzw was habe ich vergessen?
Ich bin – was Server angeht – blutiger Anfänger.
Dank im Voraus. VG CM