Journal : IPv6 en amateur en France, comment faire ?
Posté par Grumbl (page perso, ) le 05 juin 2007
Qui parmi vous pourrait donner son avis sur les bonnes et mauvaises solutions à pacher pour faire de l'IPv6 sur internet en France, quand, à priori, on est dans une zone à peu près couverte par tous les opérateurs ?
> Lire le journal (19 commentaires, moyenne: 2,7).
Vous avez demandé le commentaire #838876.
Run by 
Cette page a été générée par Templeet en 0.0585s (dont 0.0061 de SQL).
Cette page est peut-être conforme xhtml 1.0.
Information sur le site.
Nerim
Il y a de ça 3 ans, Nerim fournissait de un bloc (/32 ou /48) d'adresses IPv6 nativement, càd sans passer par du tunnel broker, c'était, si je dis pas de bétises, la passerelle PPP qui envoyait directement le bloc d'IPv6 en même temps que l'IPv4.
C'était bien plus confortable !
Pour eux ça leur permettait de tester en production des routeurs IPv6 (ils avaient de mémoire un accord avec le constructeur des routeurs), et pour toi, ça te permettait d'avoir 42 serveurs web qui écoutaient tous sur le 80, avec les 42 vhosts qui vont bien.
IPv6, c'est fun !
[^]Re: Nerim
euh chez moi j'ai pas besoin de 42 serveurs pour faire 42 vhosts :-)
[^]Re: Nerim
C'est dommage alors tu es peu regardant de la securite ;-)
Essaie de mettre ssl sur tes 42 vhosts... Avec un certificat valide un seul de tes vhosts ne generera pas de popup de securite sur le navigateur de ton visiteur.
Bref ipv6 \o/
Les fans de Ubuntu et leurs CD, c'est comme les Mormons avec leur évangile, ils en ont toujours sur eux à donner, au cas où.
Zorro.
[^]Re: Nerim
Faux. http://wiki.cacert.org/wiki/VhostTaskForce
Chezmoiçamarchebien (certificats auto-signés, avec un subjectAltName).
[^]Re: Nerim
Oh, je connaissais pas ... Interesant.
C'est pas parfait mais ca a le merite d'exister ...
http://wiki.cacert.org/wiki/VhostTaskForce#head-7236c4e2c993(...)
Les fans de Ubuntu et leurs CD, c'est comme les Mormons avec leur évangile, ils en ont toujours sur eux à donner, au cas où.
Zorro.
[^]Besoin d'aide
Ca a l'air interessant votre truc, ca m'embete depuis un moment ce pb de SSL.
Mais : j'ai rien compris (sur le comment faire).
Si quelqu'un peut m'expliquer pas a pas coment faire (pour un newbie de base!), en ayant :
- Apache 2 configuré avec 2 sites (que je passerai en SSL du coup, ca je sais faire) a.example.com et b.example.com
- Un certificat auto-signé avec apache2-ssl-certificate, c'est la seule methode que je connaisse...
Je lui en serai très reconnaissant!
[^]Re: Besoin d'aide
Tu télé-charge ce script :
http://guillaume.romagny.free.fr/evaldo/csr.sh
Ensuite tu ajoutes un a un tes domaines pour la demande de certificat :
example.com
example.example.com
www.example.com
etc.example.com
Ça va te sortir un .csr et un .pem (ta clef privée).
Tu t'inscrit sur cacert.org, tu ajoutes ton domaine.
Ensuite tu copie colle ta demande de certificat et tu recevra ton certificat final utilisable.
Bon pour un vrai certificat qui dégage pas 100% de info a part les common name et autres domaines faut te faire enregistrer correctement auprès de cacert ou acheter un vrai certificat auprès de cacert.
Chezmoiçamarche, mon pseudo + .eu et vous avez un example.
Après tu auras besoin d'un mod_rewrite et des règles qui vont bien dans ton virtualhost ssl.
Petit example :
# This is a VirtualHosts configuration.
<IfModule mod_ssl.c>
<VirtualHost _default_:443>
# Rewrite url depending on requested domain name
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteOptions inherit
# etc domain
RewriteCond %{HTTP_HOST} ^etc\.
RewriteCond %{REQUEST_URI} !^/icons.*
RewriteCond %{REQUEST_URI} !^/error.*
RewriteRule ^/(.*) /var/www/etc/$1 [L]
# phpmyadmin domain
RewriteCond %{HTTP_HOST} ^phpmyadmin\.
RewriteRule ^/(.*) /var/www/phpMyAdmin/$1 [L]
# example domain
RewriteCond %{HTTP_HOST} ^example\.
RewriteCond %{HTTP_HOST} !^example\.com$
RewriteRule ^/(.*) /var/www/example/$1 [L]
</IfModule>
# Document root
DocumentRoot "/var/www/yaorte2"
# Error log
ErrorLog logs/ssl_error_log
<IfModule mod_log_config.c>
TransferLog logs/ssl_access_log
</IfModule>
# 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:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW
# SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect. Disable SSLv2 access by default:
SSLProtocol all -SSLv2
# 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 /etc/pki/tls/certs/localhost.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/pki/tls/private/localhost.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/pki/tls/certs/server-chain.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.
#SSLCACertificateFile /etc/pki/tls/certs/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/pki/tls/certs/ssl.crl
#SSLCARevocationFile /etc/pki/tls/certs/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 "/var/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.
<IfModule mod_setenvif.c>
BrowserMatch ".*MSIE.*" nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
</IfModule>
# 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.
<IfModule mod_log_config.c>
CustomLog logs/ssl_request_log \
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
</IfModule>
</VirtualHost>
</IfModule>
site perso : http://rapsys.free.fr/
[^]Re: Nerim
Avec des vhosts basés sur le nom. Par contre, avec des vhosts basés sur l'ip, cela est possible.
[^]Re: Nerim
En réalité on peut mettre un certificat par vhost avec une seule ipv4, voir : http://wiki.cacert.org/wiki/VhostTaskForce