# AUTHOR , YEAR. # Raphael Hertzog , 2015. msgid "" msgstr "" "Project-Id-Version: 0\n" "POT-Creation-Date: 2022-08-10 10:50+0200\n" "PO-Revision-Date: 2022-07-30 18:42+0200\n" "Last-Translator: Galina Anikina \n" "Language-Team: French \n" "Language: fr-FR\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n > 1;\n" "X-Generator: Weblate 2.18-dev\n" msgid "Network" msgstr "Réseau" msgid "Gateway" msgstr "Passerelle" msgid "TCP/IP" msgstr "TCP/IP" msgid "IPv6" msgstr "IPv6" msgid "DNS" msgstr "DNS" msgid "Bind" msgstr "Bind" msgid "DHCP" msgstr "DHCP" msgid "QoS" msgstr "QoS" msgid "Network Infrastructure" msgstr "Infrastructure réseau" msgid "Linux sports the whole Unix heritage for networking, and Debian provides a full set of tools to create and manage them. This chapter reviews these tools." msgstr "Linux profite du considérable héritage d'Unix dans le domaine des réseaux et Debian dispose de toute la panoplie des outils existants pour les créer et les gérer. Ce chapitre les passe en revue." msgid "gateway" msgstr "passerelle" msgid "networkgateway" msgstr "réseaupasserelle" msgid "router" msgstr "routeur" msgid "A gateway is a system linking several networks. This term often refers to a local network's “exit point” on the mandatory path to all external IP addresses. The gateway is connected to each of the networks it links together, and acts as a router to convey IP packets between its various interfaces." msgstr "Une passerelle relie plusieurs réseaux entre eux. Ce terme désigne souvent la « porte de sortie » d'un réseau local, point de passage obligé pour atteindre toutes les adresses IP externes. La passerelle est connectée à chacun des réseaux qu'elle relie et agit en tant que routeur pour faire transiter les paquets IP entre ses différentes interfaces." msgid "BACK TO BASICS IP packet" msgstr "B.A.-BA Paquet IP" msgid "packetIP" msgstr "paquetIP" #, fuzzy #| msgid "DNSautomated updates" msgid "IPInternet Protocol" msgstr "DNSmise à jour automatique" #, fuzzy #| msgid "AH, protocol" msgid "Internet Protocol" msgstr "AH, protocole" msgid "Most networks nowadays use the IP protocol (Internet Protocol). This protocol segments the transmitted data into limited-size packets. Each packet contains, in addition to its payload data, a number of details required for its proper routing." msgstr "Les réseaux employant le protocole Internet (IP — Internet Protocol) pour échanger des informations fonctionnent par paquets : les données y circulent de manière intermittente dans des blocs de taille limitée. Chaque paquet contient, en plus des données, les informations nécessaires à son acheminement (ou routage)." msgid "BACK TO BASICS TCP/UDP" msgstr "B.A.-BA TCP/UDP" #, fuzzy #| msgid "protocolESP" msgid "protocolTCP" msgstr "protocoleESP" #, fuzzy #| msgid "protocolESP" msgid "protocolUDP" msgstr "protocoleESP" msgid "portTCP" msgstr "portTCP" msgid "portUDP" msgstr "portUDP" #, fuzzy #| msgid "DNSzone" msgid "TCPport" msgstr "DNSzone" #, fuzzy #| msgid "DNSzone" msgid "UDPport" msgstr "DNSzone" #, fuzzy #| msgid "Dynamic Host Configuration Protocol" msgid "Transmission Control Protocol" msgstr "Dynamic Host Configuration Protocol" #, fuzzy #| msgid "protocolESP" msgid "User Datagram ProtocolUDP" msgstr "protocoleESP" msgid "Many programs do not handle the individual packets themselves, even though the data they transmit does travel over IP; they often use TCP (Transmission Control Protocol). TCP is a layer over IP allowing the establishment of connections dedicated to data streams between two points. The programs then only see an entry point into which data can be fed with the guarantee that the same data exits without loss (and in the same sequence) at the exit point at the other end of the connection. Although many kinds of errors can happen in the lower layers, they are compensated by TCP: lost packets are retransmitted, and packets arriving out of order (for example, if they used different paths) are re-ordered appropriately." msgstr "TCP est un protocole permettant d'établir un flux de données continues entre deux points. Il repose sur IP, mais il permet aux programmes qui l'utilisent de faire abstraction des paquets eux-mêmes. Ces programmes ne voient qu'un point d'entrée dans lequel ils envoient des octets, ces octets ressortant sans perte (et dans l'ordre) au point de sortie. TCP compense en effet diverses erreurs qui peuvent apparaître au niveau réseau inférieur : les pertes de paquets déclenchent une retransmission et les données sont remises dans l'ordre le cas échéant (par exemple si tous les paquets n'empruntent pas le même itinéraire)." msgid "Another protocol relying on IP is UDP (User Datagram Protocol). In contrast to TCP, it is packet-oriented. Its goals are different: the purpose of UDP is only to transmit one packet from an application to another. The protocol does not try to compensate for possible packet loss on the way, nor does it ensure that packets are received in the same order as were sent. The main advantage to this protocol is that the latency is greatly improved, since the loss of a single packet does not delay the receiving of all following packets until the lost one is retransmitted." msgstr "UDP est également un protocole qui repose sur IP mais, à la différence de TCP, il reste orienté paquet. Il n'a pas les mêmes buts non plus : il ne s'agit ici que de faire passer un paquet d'une application à une autre. Le protocole ne cherche pas à corriger les éventuelles pertes de paquets sur le réseau, pas plus qu'il ne va s'assurer que les paquets sont remis à l'application destinataire dans l'ordre où ils ont été émis. On y gagne généralement en temps de latence, puisque la perte d'un paquet ne bloque pas la réception des paquets suivants jusqu'à la retransmission du paquet perdu." msgid "TCP and UDP both involve ports, which are “extension numbers” for establishing communication with a given application on a machine. This concept allows keeping several different communications in parallel with the same correspondent, since these communications can be distinguished by the port number." msgstr "TCP et UDP fonctionnent avec des ports, qui sont des points d'attache pour établir une connexion avec une application sur une machine. Ce concept permet d'avoir plusieurs communications différenciées avec le même interlocuteur, le numéro de port étant le critère distinctif." msgid "Internet Assigned Numbers AuthorityIANA" msgstr "" #, fuzzy #| msgid "NAT" msgid "IANA" msgstr "NAT" #, fuzzy #| msgid "qualityof service" msgid "/etc/etc/services" msgstr "qualitéde service" #, fuzzy #| msgid "Some of these port numbers — standardized by the IANA (Internet Assigned Numbers Authority) — are “well-known” for being associated with network services. For instance, TCP port 25 is generally used by the email server. " msgid "Some of these port numbers — standardized by the IANA (Internet Assigned Numbers Authority) — are “well-known” for being associated with network services. For instance, TCP port 25 is generally used by the email server. The list of services associated with port numbers can be found in the /etc/services file, also explained in services 5, as well as in: " msgstr "Certains de ces numéros — standardisés par l'IANA (Internet Assigned Numbers Authority, ou autorité Internet d'attribution des numéros) — sont associés à des services réseau. Par exemple, le port 25 est généralement employé par le serveur de courrier électronique. " #, fuzzy #| msgid "servicequality" msgid "IPmasquerading" msgstr "servicequalité" #, fuzzy #| msgid "networkgateway" msgid "networkmasquerading" msgstr "réseaupasserelle" msgid "When a local network uses a private address range (not routable on the Internet), the gateway needs to implement address masquerading so that the machines on the network can communicate with the outside world. The masquerading operation is a kind of proxy operating on the network level: each outgoing connection from an internal machine is replaced with a connection from the gateway itself (since the gateway does have an external, routable address), the data going through the masqueraded connection is sent to the new one, and the data coming back in reply is sent through to the masqueraded connection to the internal machine. The gateway uses a range of dedicated TCP ports for this purpose, usually with very high numbers (over 60000). Each connection coming from an internal machine then appears to the outside world as a connection coming from one of these reserved ports." msgstr "Lorsqu'un réseau local utilise une plage d'adresses privées (non routables sur Internet), la passerelle doit effectuer du masquerading (masquage d'adresses IP) pour que ses machines puissent communiquer avec l'extérieur. L'opération consiste à remplacer chaque connexion sortante par une connexion provenant de la passerelle elle-même (disposant d'une adresse valable sur le réseau externe) puis à faire suivre les données reçues en réponse à la machine ayant initiée la connexion. Pour mener à bien cette tâche, la passerelle dispose d'une plage de ports TCP dédiés au masquerading (il s'agit souvent de numéros de port très élevés, supérieurs à 60 000). Chaque nouvelle connexion issue d'une machine interne apparaîtra à l'extérieur comme provenant de l'un de ces ports réservés. Lorsque la passerelle reçoit une réponse sur l'un d'entre eux, elle sait à quelle machine la faire suivre." msgid "masquerading" msgstr "masquerading" msgid "CULTURE Private address range" msgstr "CULTURE Plages d'adresses privées" #, fuzzy #| msgid "IP addressprivate" msgid "IPprivate address" msgstr "adresse IPprivée" msgid "private IP address" msgstr "privée, adresse IP" msgid "RFC 1918 defines three ranges of IPv4 addresses not meant to be routed on the Internet but only used in local networks. The first one, 10.0.0.0/8 (see sidebar ), is a class-A range (with 224 IP addresses). The second one, 172.16.0.0/12, gathers 16 class-B ranges (172.16.0.0/16 to 172.31.0.0/16), each containing 216 IP addresses. Finally, 192.168.0.0/16 is a class-B range (grouping 256 class-C ranges, 192.168.0.0/24 to 192.168.255.0/24, with 256 IP addresses each). " msgstr "La RFC 1918 définit trois plages d'adresses IPv4 à ne pas router sur Internet, prévues pour un usage dans des réseaux locaux. La première, 10.0.0.0/8 (voir encadré ), est une plage de classe A (contenant 224 adresses IP). La deuxième, 172.16.0.0/12, rassemble 16 plages de classe B (172.16.0.0/16 à 172.31.0.0/16) pouvant contenir chacune 216 adresses IP. La dernière, 192.168.0.0/16, est une plage de classe B (regroupant les 256 plages de classe C 192.168.0.0/24 à 192.168.255.0/24, de 256 adresses IP chacune). " msgid "The gateway can also perform two kinds of network address translation (or NAT for short). The first kind, Destination NAT (DNAT) is a technique to alter the destination IP address (and/or the TCP or UDP port) for a (generally) incoming connection. The connection tracking mechanism also alters the following packets in the same connection to ensure continuity in the communication. The second kind of NAT is Source NAT (SNAT), of which masquerading is a particular case; SNAT alters the source IP address (and/or the TCP or UDP port) of a (generally) outgoing connection. As for DNAT, all the packets in the connection are appropriately handled by the connection tracking mechanism. Note that NAT is only relevant for IPv4 and its limited address space; in IPv6, the wide availability of addresses greatly reduces the usefulness of NAT by allowing all “internal” addresses to be directly routable on the Internet (this does not imply that internal machines are accessible, since intermediary firewalls can filter traffic)." msgstr "La passerelle peut également effectuer une traduction d'adresses réseau (NAT, ou Network Address Translation). Il en existe de deux types. Le Destination NAT (DNAT) est une technique pour altérer l'adresse IP (et/ou le port TCP ou UDP) destinataire d'une nouvelle connexion (généralement entrante). Le mécanisme de « suivi des connexions » (connection tracking) altérera aussi les autres paquets de la même connexion pour assurer la continuité de la communication. Son pendant, le Source NAT (SNAT), dont le masquerading est un cas particulier, altère l'adresse IP (et/ou le port TCP ou UDP) source d'une nouvelle connexion (généralement sortante). Comme pour le DNAT, le suivi des connexions gère de manière adéquate les paquets suivants. Il est à noter que ce mécanisme de NAT n'est pertinent que dans le cas d'IPv4 ; l'abondance d'adresses fait que le NAT n'est pas requis sur les réseaux IPv6, ce qui simplifie les configurations puisque chaque adresse est routée directement (ce qui ne veut pas dire qu'elle soit accessible, des coupe-feu pouvant filtrer le trafic en chemin)." #, fuzzy #| msgid "NetworkAddress Translation" msgid "NATNetwork Address Translation" msgstr "NetworkAddress Translation" #, fuzzy #| msgid "NetworkAddress Translation" msgid "Network Address TranslationNAT" msgstr "NetworkAddress Translation" #, fuzzy #| msgid "NetworkAddress Translation" msgid "networkaddress translationNAT" msgstr "NetworkAddress Translation" #, fuzzy #| msgid "networkgateway" msgid "networkNAT" msgstr "réseaupasserelle" #, fuzzy #| msgid "DNSautomated updates" msgid "SNATSource NAT" msgstr "DNSmise à jour automatique" #, fuzzy #| msgid "Source NAT" msgid "Source NATSNAT" msgstr "Source NAT" #, fuzzy #| msgid "DNSautomated updates" msgid "DNATDestination NAT" msgstr "DNSmise à jour automatique" #, fuzzy #| msgid "Destination NAT" msgid "Destination NATDNAT" msgstr "Destination NAT" msgid "BACK TO BASICS Port forwarding" msgstr "B.A.-BA Port forwarding" msgid "port forwarding" msgstr "port forwarding" #, fuzzy #| msgid "networkgateway" msgid "networkport forwarding" msgstr "réseaupasserelle" #, fuzzy #| msgid "ripd" msgid "redir" msgstr "ripd" msgid "A concrete application of DNAT is port forwarding. Incoming connections to a given port of a machine are forwarded to a port on another machine. Other solutions may exist for achieving a similar effect, though, especially at the application level with ssh (see ) or redir." msgstr "Le port forwarding, dont le principe est de rediriger (« faire suivre ») une connexion entrant sur un port donné vers un port d'une autre machine, se réalise facilement à partir d'une technique de DNAT. D'autres solutions techniques existent cependant pour obtenir un résultat similaire, notamment avec des redirections au niveau applicatif grâce à ssh (voir ) ou redir." msgid "filesystemvirtual/proc/" msgstr "" msgid "Enough theory, let's get practical. Turning a Debian system into a gateway is a simple matter of enabling the appropriate option in the Linux kernel, by way of the /proc/ virtual filesystem:" msgstr "Après la théorie, place à la pratique. Il est très facile de transformer un système Debian en passerelle : il suffit d'activer l'option adéquate du noyau Linux. On peut pour cela procéder par l'intermédiaire du système de fichiers virtuels /proc :" msgid "" "\n" "# echo 1 > /proc/sys/net/ipv4/conf/default/forwarding" msgstr "" "\n" "# echo 1 > /proc/sys/net/ipv4/conf/default/forwarding" #, fuzzy #| msgid "/etc/bind/named.conf" msgid "/etc/etc/sysctl.conf" msgstr "/etc/bind/named.conf" #, fuzzy #| msgid "trafficlimitation" msgid "/etc/etc/sysctl.d/" msgstr "traficlimitation" #, fuzzy #| msgid "This option can also be automatically enabled on boot if /etc/sysctl.conf sets the net.ipv4.conf.default.forwarding option to 1." msgid "This option can also be automatically enabled on boot if /etc/sysctl.conf or a configuration file in /etc/sysctl.d/ sets the net.ipv4.conf.default.forwarding option to 1." msgstr "Pour activer cette option automatiquement à chaque démarrage, on positionnera dans le fichier /etc/sysctl.conf l'option net.ipv4.conf.default.forwarding à 1." msgid "The /etc/sysctl.conf file" msgstr "Fichier /etc/sysctl.conf" msgid "" "\n" "net.ipv4.conf.default.forwarding = 1\n" "net.ipv4.conf.default.rp_filter = 1\n" "net.ipv4.tcp_syncookies = 1" msgstr "" "\n" "net.ipv4.conf.default.forwarding = 1\n" "net.ipv4.conf.default.rp_filter = 1\n" "net.ipv4.tcp_syncookies = 1" msgid "The same effect can be obtained for IPv6 by simply replacing ipv4 with ipv6 in the manual command and using the net.ipv6.conf.all.forwarding line in /etc/sysctl.conf." msgstr "Pour IPv6, on remplacera simplement ipv4 par ipv6 dans la commande et on modifiera la ligne net.ipv6.conf.all.forwarding dans /etc/sysctl.conf." msgid "Enabling IPv4 masquerading is a slightly more complex operation that involves configuring the netfilter firewall." msgstr "Activer le masquerading IPv4 est une opération plus complexe, nécessitant de configurer le pare-feu netfilter." msgid "Similarly, using NAT (for IPv4) requires configuring netfilter. Since the primary purpose of this component is packet filtering, the details are listed in (see )." msgstr "L'emploi du NAT (en IPv4) nécessite lui aussi de configurer netfilter. Comme il s'agit d'un élément logiciel dont la vocation première est de servir de filtre de paquets, il sera abordé dans le chapitre « Sécurité » (voir )." #, fuzzy #| msgid "X.509, certificate" msgid "X.509 certificates" msgstr "X.509, certificat" msgid "certificateX.509" msgstr "certificat X.509" msgid "SSL" msgstr "SSL" #, fuzzy #| msgid "recordDNS" msgid "Secure Socket LayerSSL" msgstr "enregistrementDNS" msgid "TLS" msgstr "TLS" #, fuzzy #| msgid "portTCP" msgid "Transport Layer SecurityTLS" msgstr "portTCP" msgid "X.509certificates" msgstr "X.509certificats" #, fuzzy #| msgid "DNSautomated updates" msgid "CACertificate Authority" msgstr "DNSmise à jour automatique" #, fuzzy #| msgid "X.509, certificate" msgid "Certificate Authority" msgstr "X.509, certificat" msgid "Certificates are an important building block of many network services built on cryptographic protocols, when they need some sort of central authentication." msgstr "" #, fuzzy #| msgid "IKE" msgid "IETF" msgstr "IKE" #, fuzzy #| msgid "The SSL protocol (Secure Socket Layer) was invented by Netscape to secure connections to web servers. It was later standardized by IETF under the acronym TLS (Transport Layer Security). Since then TLS continued to evolve and nowadays SSL is deprecated due to multiple design flaws that have been discovered." msgid "Among those protocols, SSL (Secure Socket Layer) was invented by Netscape to secure connections to web servers. It was later standardized by IETF under the acronym TLS (Transport Layer Security). Since then TLS continued to evolve, and nowadays SSL is deprecated due to multiple design flaws that have been discovered." msgstr "SSL (Secure Socket Layer) est un protocole inventé par Netscape pour sécuriser les connexions aux serveurs web. Plus tard, il a été standardisé par l'IETF sous le nom de TLS (Transport Layer Security). Depuis lors, TLS a continué d'évoluer et de nos jours SSL est obsolète à cause de multiples problèmes de conception récemment découverts." msgid "The TLS protocol aims primarily to provide privacy and data integrity between two or more communicating computer applications. The most common case on the Internet is the communication between a client (e.g. a web browser) and a server." msgstr "" #, fuzzy #| msgid "zonereverse" msgid "certificateroot certificate" msgstr "zoneinverse" #, fuzzy #| msgid "However, anyone can create a key pair, store any identity on it, and pretend to be the identity of their choice. One solution involves the concept of a Certification Authority (CA), formalized by the X.509 standard. This term covers an entity that holds a trusted key pair known as a root certificate. This certificate is only used to sign other certificates (key pairs), after proper steps have been undertaken to check the identity stored on the key pair. Applications using X.509 can then check the certificates presented to them, if they know about the trusted root certificates." msgid "A key pair is needed for the exchange of information, which involves a public key that includes information about the identity of the owner and matches a private key. The private key must be kept secret, otherwise the security is compromised. However, anyone can create a key pair, store any identity on it, and pretend to be the identity of their choice. One solution involves the concept of a Certification Authority (CA), formalized by the X.509 standard. This term covers an entity that holds a trusted key pair known as a root certificate. This certificate is only used to sign other certificates (key pairs), after proper steps have been undertaken to check the identity stored on the key pair. Applications using X.509 can then check the certificates presented to them, if they know about the trusted root certificates." msgstr "Toutefois, n'importe qui peut créer une biclé et s'attribuer l'identité de son choix. Pour régler ce problème, le concept d'autorité de certification (CA, Certificate Authority) a été créé par le standard X.509. Il s'agit d'une entité disposant d'une biclé de confiance que l'on nomme « certificat racine ». Ce certificat va seulement être employé pour signer d'autres certificats après avoir vérifié l'identité qui y est inscrite. Toute application exploitant des certificats X.509 doit disposer d'un ou plusieurs certificats racines de confiance pour valider l'authenticité des certificats qui lui sont présentés." msgid "You can implement a CA (as described in ), but if you intend to use the certificate for a website, you need to rely on a trusted CA. The prices vary significantly, but it is possible to implement great security spending little to no money." msgstr "" msgid "Creating gratis trusted certificates" msgstr "" #, fuzzy #| msgid "zonereverse" msgid "certificatetrusted certificate" msgstr "zoneinverse" #, fuzzy #| msgid "zonereverse" msgid "certificatesnakeoil certificate" msgstr "zoneinverse" #, fuzzy #| msgid "zonereverse" msgid "certificateletsencryptcertbot" msgstr "zoneinverse" msgid "Many programs create and use snakeoil certificates by default (see sidebar ). Fortunately the certbot package brings everything we need to create our own trusted certificates, provided by the \"Lets Encrypt\" initiative (see sidebar ), which can also be used for mail transport agents (Postfix), mail delivery agents (Dovecot, Cyrus, etc.), and other network services." msgstr "" msgid "The Falcot administrators just want to create a certificate for their website, which runs on Apache. There is a convenient Apache plugin for certbot that automatically edits the Apache configuration to serve the obtained certificate, so they make use of it:" msgstr "" #, fuzzy #| msgid "bind9" msgid "certbot" msgstr "bind9" #, fuzzy #| msgid "iputils-tracepath" msgid "python3-certbot-apache" msgstr "iputils-tracepath" #, fuzzy #| msgid "zonereverse" msgid "Apachecertbot" msgstr "zoneinverse" #, fuzzy #| msgid "zonereverse" msgid "Apachepython3-certbot-apache" msgstr "zoneinverse" #, fuzzy #| msgid "zonereverse" msgid "Apachetrusted certificates" msgstr "zoneinverse" msgid "" "\n" "# apt install python3-certbot-apache\n" "[...]\n" "# certbot --apache\n" "aving debug log to /var/log/letsencrypt/letsencrypt.log\n" "Plugins selected: Authenticator apache, Installer apache\n" "Enter email address (used for urgent renewal and security notices)\n" " (Enter 'c' to cancel): admin@falcot.com\n" "\n" "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" "Please read the Terms of Service at\n" "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must\n" "agree in order to register with the ACME server. Do you agree?\n" "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" "(Y)es/(N)o: Y\n" "\n" "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" "Would you be willing, once your first certificate is successfully issued, to\n" "share your email address with the Electronic Frontier Foundation, a founding\n" "partner of the Let's Encrypt project and the non-profit organization that\n" "develops Certbot? We'd like to send you email about our work encrypting the web,\n" "EFF news, campaigns, and ways to support digital freedom.\n" "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" "(Y)es/(N)o: N\n" "\n" "Account registered.\n" "\n" "No names were found in your configuration files. Please enter in your domain\n" "name(s) (comma and/or space separated) (Enter 'c' to cancel): falcot.com\n" "\n" "Requesting a certificate for falcot.com\n" "Performing the following challenges:\n" "http-01 challenge for falcot.com\n" "Enabled Apache rewrite module\n" "Waiting for verification...\n" "Cleaning up challenges\n" "Created an SSL vhost at /etc/apache2/sites-available/000-default-le-ssl.conf\n" "Enabled Apache socache_shmcb module\n" "Enabled Apache ssl module\n" "Deploying Certificate to VirtualHost /etc/apache2/sites-available/000-default-le-ssl.conf\n" "Enabling available site: /etc/apache2/sites-available/000-default-le-ssl.conf\n" "\n" "Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.\n" "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" "1: No redirect - Make no further changes to the webserver configuration.\n" "2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for\n" "new sites, or if you're confident your site works on HTTPS. You can undo this\n" "change by editing your web server's configuration.\n" "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" "Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2\n" "\n" "Enabled Apache rewrite module\n" "Redirecting vhost in /etc/apache2/sites-enabled/000-default.conf to ssl vhost in /etc/apache2/sites-available/000-default-le-ssl.conf\n" "\n" "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" "Congratulations! You have successfully enabled https://falcot.com\n" "\n" "You should test your configuration at:\n" "https://www.ssllabs.com/ssltest/analyze.html?d=falcot.com\n" "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n" "\n" "IMPORTANT NOTES:\n" " - Congratulations! Your certificate and chain have been saved at:\n" " /etc/letsencrypt/live/falcot.com/fullchain.pem\n" " Your key file has been saved at:\n" " /etc/letsencrypt/live/falcot.com/privkey.pem\n" " Your cert will expire on 2022-06-04. To obtain a new or tweaked\n" " version of this certificate in the future, simply run certbot again\n" " with the \"certonly\" option. To non-interactively renew *all* of\n" " your certificates, run \"certbot renew\"\n" " - Your account credentials have been saved in your Certbot\n" " configuration directory at /etc/letsencrypt. You should make a\n" " secure backup of this folder now. This configuration directory will\n" " also contain certificates and private keys obtained by Certbot so\n" " making regular backups of this folder is ideal.\n" " - If you like Certbot, please consider supporting our work by:\n" "\n" " Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate\n" " Donating to EFF: https://eff.org/donate-le\n" "" msgstr "" #, fuzzy #| msgid "CULTURE Private address range" msgid "CULTURE The Let's Encrypt Initiative" msgstr "CULTURE Plages d'adresses privées" #, fuzzy #| msgid "IPsec" msgid "Let's Encrypt" msgstr "IPsec" msgid "The Let's Encrypt initiative is a joint effort to create a free, automated, and open certificate authority (CA), run for the public's benefit. It is supported by the EFF and the Linux Foundation. The initiative provides an automated tool for acquiring and renewing certificates. This reduces the amount of manual effort involved, especially if multiple sites and domains must be managed. The certificates can also be used for SIP, XMPP, WebSockets and TURN servers. Usage of the service requires control over the DNS information of the domain in question (domain validation). " msgstr "" msgid "If you would rather keep the server running during the certificate creation, you can use the webroot plugin to get the certificate with the arguments certonly and --webroot. You would have to specify a --webroot-path (abbreviated -w), which should contain the files served. The command looks as follows:" msgstr "" msgid "# certbot certonly --webroot -w /var/www/html -d www.DOMAIN.com -d DOMAIN.com" msgstr "" msgid "You need to restart all services using the certificates that you have created." msgstr "" #, fuzzy #| msgid "zonereverse" msgid "/etc/etc/cron.d/certbot" msgstr "zoneinverse" #, fuzzy #| msgid "route" msgid "certbot" msgstr "route" msgid "The certificates created are so called short-life certificates, which are valid for 90 days and must therefor be renewed every once in three months using the certbot renew command. However, we shouldn't renew every certificate manually, but automatically. A basic cron job is included by certbot in /etc/cron.d/certbot. To ensure that certificates can be automatically renewed, you can execute certbot renew --dry-run." msgstr "" msgid "Public Key Infrastructure: easy-rsa" msgstr "Infrastructure de clés publiques easy-rsa" #, fuzzy #| msgid "PKI (Public Key Infrastructure)" msgid "PKIPublic Key Infrastructure" msgstr "PKI (Public Key Infrastructure)" msgid "Public Key Infrastructure" msgstr "infrastructure de clés publiques" #, fuzzy #| msgid "NAT" msgid "X.509" msgstr "NAT" msgid "easy-rsa" msgstr "easy-rsa" msgid "RSA (algorithm)" msgstr "RSA (algorithme)" #, fuzzy #| msgid "portTCP" msgid "algorithmRSA" msgstr "portTCP" msgid "key pair" msgstr "biclé" #, fuzzy #| msgid "The RSA algorithm is widely used in public-key cryptography. It involves a “key pair”, comprised of a private and a public key. The two keys are closely linked to each other, and their mathematical properties are such that a message encrypted with the public key can only be decrypted by someone knowing the private key, which ensures confidentiality. In the opposite direction, a message encrypted with the private key can be decrypted by anyone knowing the public key, which allows authenticating the origin of a message since only someone with access to the private key could generate it. When associated with a digital hash function (MD5, SHA1, or a more recent variant), this leads to a signature mechanism that can be applied to any message." msgid "It is also possible to create our own CA, for that we will use the RSA algorithm, widely used in public-key cryptography. It involves a “key pair”, comprised of a private and a public key. The two keys are closely linked to each other, and their mathematical properties are such that a message encrypted with the public key can only be decrypted by someone knowing the private key, which ensures confidentiality. In the opposite direction, a message encrypted with the private key can be decrypted by anyone knowing the public key, which allows authenticating the origin of a message since only someone with access to the private key could generate it. When associated with a digital hash function (MD5, SHA1, or a more recent variant), this leads to a signature mechanism that can be applied to any message." msgstr "L'algorithme RSA est très employé en cryptographie à clé publique. Il permet de générer deux clés (une privée et une publique) étroitement liées dont les propriétés mathématiques sont telles qu'un message chiffré avec la clé publique ne peut être déchiffré que par le détenteur de la clé privée (on assure ainsi la confidentialité). Inversement, un message chiffré avec la clé privée peut être déchiffré par tout possesseur de la clé publique. Cela permet d'authentifier la provenance d'un message, on sait alors que ce dernier a été expédié par le propriétaire de la clé privée. Associé à une empreinte (MD5, SHA1 ou une variante plus récente), on obtient un mécanisme de signature d'un message quelconque. Une paire de clés (une privée et la publique correspondante) est appelée « biclé »." #, fuzzy #| msgid "OpenVPN follows this rule. Since public CAs only emit certificates in exchange for a (hefty) fee, it is also possible to create a private certification authority within the company. The easy-rsa package provides tools to serve as an X.509 certification infrastructure, implemented as a set of scripts using the openssl command." msgid "Since public CAs only emit certificates in exchange for a (hefty) fee, it is also possible to create a private certification authority within the company. The easy-rsa package provides tools to serve as an X.509 certification infrastructure, implemented as a set of scripts using the openssl command." msgstr "OpenVPN ne fait pas exception à la règle. Pour éviter de payer (cher) les services d'une autorité de certification, il est possible de créer sa propre autorité de certification, interne à l'entreprise. Le paquet easy-rsa peut être employé comme infrastructure de gestion de certificats X.509, il s'appuie sur un ensemble de scripts utilisant la commande openssl." #, fuzzy #| msgid "CULTURE SSL and TLS" msgid "ALTERNATIVE GnuTLS" msgstr "CULTURE SSL et TLS" msgid "DTLS" msgstr "DTLS" msgid "GnuTLS" msgstr "GnuTLS" msgid "GnuTLS can also be used to generate a CA, and deal with other technologies around the TLS, DTLS and SSL protocols." msgstr "" msgid "The package gnutls-bin contains the command-line utilities. It is also useful to install the gnutls-doc package, which includes extensive documentation." msgstr "" msgid "The Falcot Corp administrators use this tool to create the required certificates, both for the server and the clients. This allows the configuration of all clients to be similar since they will only have to be set up so as to trust certificates coming from Falcot's local CA. This CA is the first certificate to create; to this end, the administrators set up a directory with the files required for the CA in an appropriate location, preferably on a machine not connected to the network in order to mitigate the risk of the CA's private key being stolen." msgstr "Les administrateurs de Falcot décident de l'employer pour créer les certificats nécessaires, à la fois pour le serveur et pour les clients. La configuration de tous les clients sera ainsi a priori identique puisqu'il suffira de préciser à chacun qu'il ne doit faire confiance qu'aux certificats signés par l'autorité de certification locale, celle de Falcot. Ils commencent par créer cette dernière ; pour cela, ils mettent en place un répertoire contenant les fichiers nécessaires à l'autorité de certification à un emplacement qu'ils contrôlent, et de préférence sur une machine non connectée au réseau afin de limiter les risques de vol de la clé privée de l'autorité de certification." msgid "" "\n" "$ make-cadir pki-falcot\n" "$ cd pki-falcot" msgstr "" "\n" "$ make-cadir pki-falcot\n" "$ cd pki-falcot" #, fuzzy #| msgid "They then store the required parameters into the vars file, especially those named with a KEY_ prefix; these variables are then integrated into the environment:" msgid "They then store the required parameters into the vars file, which can be uncommented and edited:" msgstr "Ils placent les paramètres nécessaires dans le fichier vars et notamment ceux débutant par KEY_, puis ils les intègrent dans l'environnement :" msgid "" "\n" "$ grep EASYRSA vars\n" "$ vim vars\n" "$ " msgstr "" msgid "Now we prepare the public key infrastructure directory with the following command:" msgstr "" #, fuzzy #| msgid "" #| "\n" #| "$ make-cadir pki-falcot\n" #| "$ cd pki-falcot" msgid "" "\n" "$ ./easyrsa init-pki\n" "\n" "\n" "init-pki complete; you may now create a CA or requests.\n" "Your newly created PKI dir is: /home/debian/pki-falcot/pki\n" "\n" "" msgstr "" "\n" "$ make-cadir pki-falcot\n" "$ cd pki-falcot" #, fuzzy #| msgid "The next step is the creation of the CA's key pair itself (the two parts of the key pair will be stored under keys/ca.crt and keys/ca.key during this step):" msgid "The next step is the creation of the CA's key pair itself (the two parts of the key pair will be stored under pki/ca.crt and pki/private/ca.key during this step). We can add the option nopass to avoid entering a password each time the private key is used:" msgstr "Ils créent alors la biclé de l'autorité de certification (les fichiers keys/ca.crt et keys/ca.key sont créés au cours de cette opération) :" #, fuzzy #| msgid "" #| "\n" #| "$ ./build-ca\n" #| "Generating a 2048 bit RSA private key\n" #| "...................................................................+++\n" #| "...+++\n" #| "writing new private key to 'ca.key'\n" #| "-----\n" #| "You are about to be asked to enter information that will be incorporated\n" #| "into your certificate request.\n" #| "What you are about to enter is what is called a Distinguished Name or a DN.\n" #| "There are quite a few fields but you can leave some blank\n" #| "For some fields there will be a default value,\n" #| "If you enter '.', the field will be left blank.\n" #| "-----\n" #| "Country Name (2 letter code) [FR]:\n" #| "State or Province Name (full name) [Loire]:\n" #| "Locality Name (eg, city) [Saint-Étienne]:\n" #| "Organization Name (eg, company) [Falcot Corp]:\n" #| "Organizational Unit Name (eg, section) [Certificate authority]:\n" #| "Common Name (eg, your name or your server's hostname) [Falcot Corp CA]:\n" #| "Name [Certificate authority for Falcot Corp]:\n" #| "Email Address [admin@falcot.com]:\n" #| "" msgid "" "\n" "$ ./easyrsa build-ca nopass\n" "\n" "Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n" "Generating RSA private key, 2048 bit long modulus (2 primes)\n" "..................+++++\n" "...............................+++++\n" "e is 65537 (0x010001)\n" "You are about to be asked to enter information that will be incorporated\n" "into your certificate request.\n" "What you are about to enter is what is called a Distinguished Name or a DN.\n" "There are quite a few fields but you can leave some blank\n" "For some fields there will be a default value,\n" "If you enter '.', the field will be left blank.\n" "-----\n" "Common Name (eg: your user, host, or server name) [Easy-RSA CA]:\n" "\n" "CA creation complete and you may now import and sign cert requests.\n" "Your new CA certificate file for publishing is at:\n" "/home/debian/pki-falcot/pki/ca.crt\n" "\n" "" msgstr "" "\n" "$ ./build-ca\n" "Generating a 2048 bit RSA private key\n" "...................................................................+++\n" "...+++\n" "writing new private key to 'ca.key'\n" "-----\n" "You are about to be asked to enter information that will be incorporated\n" "into your certificate request.\n" "What you are about to enter is what is called a Distinguished Name or a DN.\n" "There are quite a few fields but you can leave some blank\n" "For some fields there will be a default value,\n" "If you enter '.', the field will be left blank.\n" "-----\n" "Country Name (2 letter code) [FR]:\n" "State or Province Name (full name) [Loire]:\n" "Locality Name (eg, city) [Saint-Étienne]:\n" "Organization Name (eg, company) [Falcot Corp]:\n" "Organizational Unit Name (eg, section) [Certificate authority]:\n" "Common Name (eg, your name or your server's hostname) [Falcot Corp CA]:\n" "Name [Certificate authority for Falcot Corp]:\n" "Email Address [admin@falcot.com]:\n" "" #, fuzzy #| msgid "named.conf" msgid "dh.pem" msgstr "named.conf" #, fuzzy #| msgid "The certificate for the VPN server can now be created, as well as the Diffie-Hellman parameters required for the server side of an SSL/TLS connection. The VPN server is identified by its DNS name vpn.falcot.com; this name is re-used for the generated key files (keys/vpn.falcot.com.crt for the public certificate, keys/vpn.falcot.com.key for the private key):" msgid "The certificate can now be created, as well as the Diffie-Hellman parameters required for the server side of an SSL/TLS connection. They want to use it for a VPN server (see section ) that is identified by the DNS name vpn.falcot.com; this name is re-used for the generated key files (keys/vpn.falcot.com.crt for the public certificate, keys/vpn.falcot.com.key for the private key):" msgstr "On peut alors créer un certificat pour le serveur VPN ainsi que les paramètres Diffie-Hellman nécessaires pour le côté serveur d'une connexion SSL/TLS. Le serveur VPN est identifié par son nom DNS vpn.falcot.com ; ce nom est employé dans les fichiers de clés générés (keys/vpn.falcot.com.crt pour le certificat public et keys/vpn.falcot.com.key pour la clé privée) :" msgid "" "\n" "$ ./easyrsa gen-req vpn.falcot.com nopass\n" "\n" "Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n" "Generating a RSA private key\n" "......................................+++++\n" "..........................................................................+++++\n" "writing new private key to '/home/debian/pki-falcot/pki/easy-rsa-5515.0PwyXl/tmp.g1c6u6'\n" "-----\n" "You are about to be asked to enter information that will be incorporated\n" "into your certificate request.\n" "What you are about to enter is what is called a Distinguished Name or a DN.\n" "There are quite a few fields but you can leave some blank\n" "For some fields there will be a default value,\n" "If you enter '.', the field will be left blank.\n" "-----\n" "Common Name (eg: your user, host, or server name) [vpn.falcot.com]:\n" "\n" "Keypair and certificate request completed. Your files are:\n" "req: /home/debian/pki-falcot/pki/reqs/vpn.falcot.com.req\n" "key: /home/debian/pki-falcot/pki/private/vpn.falcot.com.key\n" "\n" "\n" "$ ./easyrsa sign-req server vpn.falcot.com\n" "\n" "Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n" "\n" "\n" "You are about to sign the following certificate.\n" "Please check over the details shown below for accuracy. Note that this request\n" "has not been cryptographically verified. Please be sure it came from a trusted\n" "source or that you have verified the request checksum with the sender.\n" "\n" "Request subject, to be signed as a server certificate for 825 days:\n" "\n" "subject=\n" " commonName = vpn.falcot.com\n" "\n" "\n" "Type the word 'yes' to continue, or any other input to abort.\n" " Confirm request details: yes\n" "Using configuration from /home/debian/pki-falcot/pki/easy-rsa-5603.87iCIa/tmp.u8r8Fj\n" "Check that the request matches the signature\n" "Signature ok\n" "The Subject's Distinguished Name is as follows\n" "commonName :ASN.1 12:'vpn.falcot.com'\n" "Certificate is to be certified until May 27 15:26:29 2024 GMT (825 days)\n" "\n" "Write out database with 1 new entries\n" "Data Base Updated\n" "\n" "Certificate created at: /home/debian/pki-falcot/pki/issued/vpn.falcot.com.crt\n" "\n" "\n" "$ ./easyrsa gen-dh\n" "\n" "Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n" "Generating DH parameters, 2048 bit long safe prime, generator 2\n" "This is going to take a long time\n" "[…]\n" "\n" "DH parameters of size 2048 created at /home/debian/pki-falcot/pki/dh.pem\n" "\n" "" msgstr "" msgid "The following step creates certificates for the VPN clients; one certificate is required for each computer or person allowed to use the VPN:" msgstr "Il ne reste plus qu'à créer les certificats pour les clients du VPN, un par ordinateur ou personne autorisée à s'y connecter :" msgid "" "\n" "$ ./easyrsa build-client-full JoeSmith nopass\n" "\n" "Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n" "Generating a RSA private key\n" "...................................+++++\n" ".........................................................................................+++++\n" "writing new private key to '/home/debian/pki-falcot/pki/easy-rsa-5694.DOYwSn/tmp.RKlbOE'\n" "-----\n" "Using configuration from /home/debian/pki-falcot/pki/easy-rsa-5694.DOYwSn/tmp.d5QHAC\n" "Check that the request matches the signature\n" "Signature ok\n" "The Subject's Distinguished Name is as follows\n" "commonName :ASN.1 12:'JoeSmith'\n" "Certificate is to be certified until May 27 15:29:25 2024 GMT (825 days)\n" "\n" "Write out database with 1 new entries\n" "Data Base Updated\n" "\n" "" msgstr "" msgid "Virtual Private Network" msgstr "Réseau privé virtuel" msgid "networkvirtual private" msgstr "réseauprivé virtuel" msgid "VPN" msgstr "VPN" #, fuzzy #| msgid "virtual private network" msgid "virtual private networkVPN" msgstr "Virtual Private Network" #, fuzzy #| msgid "packetIP" msgid "IPIPsec" msgstr "paquetIP" msgid "A Virtual Private Network (VPN for short) is a way to link two different local networks through the Internet by way of a tunnel; the tunnel is usually encrypted for confidentiality. VPNs are often used to integrate a remote machine within a company's local network." msgstr "Un réseau privé virtuel (Virtual Private Network, ou VPN) est un moyen de relier par Internet deux réseaux locaux distants via un tunnel (généralement chiffré pour des raisons de confidentialité). Souvent, cette technique sert simplement à intégrer une machine distante au sein du réseau local de l'entreprise." #, fuzzy #| msgid "Several tools provide this. OpenVPN is an efficient solution, easy to deploy and maintain, based on SSL/TLS. Another possibility is using IPsec to encrypt IP traffic between two machines; this encryption is transparent, which means that applications running on these hosts need not be modified to take the VPN into account. SSH can also be used to provide a VPN, in addition to its more conventional features. Finally, a VPN can be established using Microsoft's PPTP protocol. Other solutions exist, but are beyond the focus of this book." msgid "Several tools provide this functionality. OpenVPN is an efficient solution, easy to deploy and maintain, based on SSL/TLS. Another possibility is using IPsec to encrypt IP traffic between two machines; this encryption is transparent, which means that applications running on these hosts need not be modified to take the VPN into account. SSH can also be used to provide a VPN, in addition to its more conventional features. Finally, a VPN can be established using Microsoft's PPTP protocol. Other solutions exist, but are beyond the focus of this book." msgstr "Il y a plusieurs manières d'obtenir ce résultat. OpenVPN est une solution efficace et facile à déployer et maintenir, s'appuyant sur SSL/TLS. On peut également employer IPsec qui permet de chiffrer les communications IP entre deux hôtes, de manière transparente — c'est-à-dire que les applications fonctionnant sur ces hôtes n'ont pas besoin d'être modifiées pour tenir compte de l'existence du réseau privé virtuel. SSH offre également une fonctionnalité de VPN bien que cela ne soit pas son rôle premier. Enfin, il est possible de recourir au protocole PPTP de Microsoft. Ce livre négligera les autres solutions." msgid "OpenVPN" msgstr "OpenVPN" msgid "OpenVPN" msgstr "OpenVPN" #, fuzzy #| msgid "DNSzone" msgid "VPNOpenVPN" msgstr "DNSzone" #, fuzzy #| msgid "networkvirtual private" msgid "networktun interface" msgstr "réseauprivé virtuel" #, fuzzy #| msgid "networkvirtual private" msgid "networktap interface" msgstr "réseauprivé virtuel" msgid "OpenVPN is a piece of software dedicated to creating virtual private networks. Its setup involves creating virtual network interfaces on the VPN server and on the client(s); both tun (for IP-level tunnels) and tap (for Ethernet-level tunnels) interfaces are supported. In practice, tun interfaces will most often be used except when the VPN clients are meant to be integrated into the server's local network by way of an Ethernet bridge." msgstr "Logiciel dédié à la création de réseaux privés virtuels, sa mise en œuvre implique la création d'interfaces réseau virtuelles à la fois sur le serveur VPN et sur le (ou les) client(s). Il gère aussi bien les interfaces tun (tunnel de niveau IP) que tap (tunnel de niveau Ethernet). Concrètement, on emploiera des interfaces tun sauf lorsque l'on souhaite intégrer les clients VPN dans le réseau local du serveur par le biais d'un pont Ethernet (bridge)." msgid "OpenVPN relies on OpenSSL for all the SSL/TLS cryptography and associated features (confidentiality, authentication, integrity, non-repudiation). It can be configured either with a shared private key or using X.509 certificates based on a public key infrastructure. The latter configuration is strongly preferred since it allows greater flexibility when faced with a growing number of roaming users accessing the VPN." msgstr "OpenVPN s'appuie sur OpenSSL pour gérer toute la cryptographie SSL/TLS et assurer les fonctions associées (confidentialité, authentification, intégrité, non-répudiation). Il peut être configuré pour employer une clé secrète partagée ou pour exploiter des certificats X509 d'une infrastructure de clés publiques. Cette dernière configuration sera toujours privilégiée car plus souple pour gérer une population croissante d'utilisateurs nomades disposant d'un accès au VPN." msgid "Configuring the OpenVPN Server" msgstr "Configuration du serveur OpenVPN" #, fuzzy #| msgid "zonereverse" msgid "OpenVPNserver" msgstr "zoneinverse" #, fuzzy #| msgid "Now all certificates have been created, they need to be copied where appropriate: the root certificate's public key (keys/ca.crt) will be stored on all machines (both server and clients) as /etc/ssl/certs/Falcot_CA.crt. The server's certificate is installed only on the server (keys/vpn.falcot.com.crt goes to /etc/ssl/vpn.falcot.com.crt, and keys/vpn.falcot.com.key goes to /etc/ssl/private/vpn.falcot.com.key with restricted permissions so that only the administrator can read it), with the corresponding Diffie-Hellman parameters (keys/dh2048.pem) installed to /etc/openvpn/dh2048.pem. Client certificates are installed on the corresponding VPN client in a similar fashion." msgid "After all certificates have been created (follow the instructions from ), they need to be copied where appropriate: the root certificate's public key (pki/ca.crt) will be stored on all machines (both server and clients) as /etc/ssl/certs/Falcot_CA.crt. The server's certificate is installed only on the server (pki/issued/vpn.falcot.com.crt goes to /etc/ssl/certs/vpn.falcot.com.crt, and pki/private/vpn.falcot.com.key goes to /etc/ssl/private/vpn.falcot.com.key with restricted permissions so that only the administrator can read it), with the corresponding Diffie-Hellman parameters (pki/dh.pem) installed to /etc/openvpn/dh.pem. Client certificates are installed on the corresponding VPN client in a similar fashion." msgstr "Maintenant que tous les certificats ont été créés, il reste à les copier là où ils sont nécessaires : la clé publique du certificat racine (keys/ca.crt) se trouvera sur toutes les machines (serveur et clients), en /etc/ssl/certs/Falcot_CA.crt. Le certificat serveur s'installe uniquement sur le serveur (keys/vpn.falcot.com.crt en /etc/ssl/vpn.falcot.com.crt et keys/vpn.falcot.com.key en /etc/ssl/private/vpn.falcot.com.key avec des droits restreints pour que seul l'administrateur puisse le lire) accompagné des paramètres Diffie-Hellman (keys/dh2048.pem) que l'on peut installer en /etc/openvpn/dh2048.pem. Chaque certificat client s'installe de manière similaire sur le client VPN correspondant." #, fuzzy #| msgid "firewallIPv6" msgid "/etc/etc/ssl/" msgstr "IPv6pare-feu" #, fuzzy #| msgid "firewallIPv6" msgid "/etc/etc/openvpn/dh.pem" msgstr "IPv6pare-feu" #, fuzzy #| msgid "trafficcontrol" msgid "/etc/etc/openvpn/*.conf" msgstr "traficcontrôle" #, fuzzy #| msgid "By default, the OpenVPN initialization script tries starting all virtual private networks defined in /etc/openvpn/*.conf. Setting up a VPN server is therefore a matter of storing a corresponding configuration file in this directory. A good starting point is /usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz, which leads to a rather standard server. Of course, some parameters need to be adapted: ca, cert, key and dh need to describe the selected locations (respectively, /etc/ssl/certs/Falcot_CA.crt, /etc/ssl/vpn.falcot.com.crt, /etc/ssl/private/vpn.falcot.com.key and /etc/openvpn/dh2048.pem). The server 10.8.0.0 255.255.255.0 directive defines the subnet to be used by the VPN; the server uses the first IP address in that range (10.8.0.1) and the rest of the addresses are allocated to clients." msgid "By default, the OpenVPN initialization script tries starting all virtual private networks defined in /etc/openvpn/*.conf. Setting up a VPN server is therefore a matter of storing a corresponding configuration file in this directory. A good starting point is /usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz, which leads to a rather standard server. Of course, some parameters need to be adapted: ca, cert, key and dh need to describe the selected locations (respectively, /etc/ssl/certs/Falcot_CA.crt, /etc/ssl/vpn.falcot.com.crt, /etc/ssl/private/vpn.falcot.com.key and /etc/openvpn/dh.pem). The server 10.8.0.0 255.255.255.0 directive defines the subnet to be used by the VPN; the server uses the first IP address in that range (10.8.0.1) and the rest of the addresses are allocated to clients." msgstr "Par défaut, le script d'initialisation d'OpenVPN tente de démarrer tous les réseaux privés virtuels définis dans /etc/openvpn/*.conf. Pour mettre en place un serveur VPN, il suffit donc de déposer le fichier de configuration correspondant dans ce répertoire. On peut s'inspirer de /usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz, une configuration serveur relativement standard. Il faut évidemment éditer les paramètres ca, cert, key et dh pour indiquer les emplacements retenus (/etc/ssl/certs/Falcot_CA.crt, /etc/ssl/vpn.falcot.com.crt, /etc/ssl/private/vpn.falcot.com.key et /etc/openvpn/dh2048.pem respectivement). La directive server 10.8.0.0 255.255.255.0 indique le sous-réseau employé par le VPN : le serveur dispose de la première IP (10.8.0.1) et les clients se voient attribuer le reste des adresses." #, fuzzy #| msgid "trafficcontrol" msgid "/etc/etc/network/interfaces" msgstr "traficcontrôle" #, fuzzy #| msgid "networkvirtual private" msgid "networkvirtual interface" msgstr "réseauprivé virtuel" #, fuzzy #| msgid "DNSzone" msgid "OpenVPNnetwork interface" msgstr "DNSzone" #, fuzzy #| msgid "With this configuration, starting OpenVPN creates the virtual network interface, usually under the tun0 name. However, firewalls are often configured at the same time as the real network interfaces, which happens before OpenVPN starts. Good practice therefore recommends creating a persistent virtual network interface, and configuring OpenVPN to use this pre-existing interface. This further allows choosing the name for this interface. To this end, openvpn --mktun --dev vpn --dev-type tun creates a virtual network interface named vpn with type tun; this command can easily be integrated in the firewall configuration script, or in an up directive of the /etc/network/interfaces file. The OpenVPN configuration file must also be updated accordingly, with the dev vpn and dev-type tun directives." msgid "With this configuration, starting OpenVPN creates the virtual network interface, usually under the tun0 name. However, firewalls are often configured at the same time as the real network interfaces, which happens before OpenVPN starts. Good practice therefore recommends creating a persistent virtual network interface, and configuring OpenVPN to use this pre-existing interface. This further allows choosing the name for this interface. To this end, openvpn --mktun --dev vpn --dev-type tun creates a virtual network interface named vpn with type tun; this command can easily be integrated in the firewall configuration script, or in an up directive of the /etc/network/interfaces file, or a udev rule can be added to that end. The OpenVPN configuration file must also be updated accordingly, with the dev vpn and dev-type tun directives." msgstr "Dans cette configuration, l'interface réseau virtuelle n'est créée que lorsque OpenVPN est démarré et sera généralement nommée tun0. Comme le pare-feu est généralement configuré en même temps que les interfaces réseau réelles, et que cela se déroule avant le démarrage d'OpenVPN, il est souhaitable de créer une interface réseau virtuelle persistente à ce moment-là et de configurer OpenVPN pour faire usage de cette interface pré-existante. Cela permet en outre de choisir le nom donné à l'interface réseau. La commande openvpn --mktun --dev vpn --dev-type tun crée une interface réseau virtuelle nommée vpn et de type tun ; elle peut facilement s'intégrer au début du script de configuration du pare-feu ou dans une directive up de /etc/network/interfaces. Le fichier de configuration d'OpenVPN doit être mis à jour en conséquence avec les directives dev vpn et dev-type tun." #, fuzzy #| msgid "DNSzone" msgid "OpenVPNpush route" msgstr "DNSzone" msgid "Barring further action, VPN clients can only access the VPN server itself by way of the 10.8.0.1 address. Granting the clients access to the local network (192.168.0.0/24), requires adding a push route 192.168.0.0 255.255.255.0 directive to the OpenVPN configuration so that VPN clients automatically get a network route telling them that this network is reachable by way of the VPN. Furthermore, machines on the local network also need to be informed that the route to the VPN goes through the VPN server (this automatically works when the VPN server is installed on the gateway). Alternatively, the VPN server can be configured to perform IP masquerading so that connections coming from VPN clients appear as if they are coming from the VPN server instead (see )." msgstr "Sans mesures supplémentaires, les clients VPN n'ont accès qu'au serveur VPN, par l'intermédiaire de l'adresse IP 10.8.0.1. Pour donner accès au réseau local (192.168.0.0/24), il faut ajouter une directive push route 192.168.0.0 255.255.255.0 à la configuration d'OpenVPN afin que les clients VPN obtiennent automatiquement une route indiquant que le réseau en question est joignable par l'intermédiaire du VPN. En outre, il faut s'assurer que toutes les machines du réseau local aient une route indiquant que le réseau privé virtuel est accessible par l'intermédiaire du serveur VPN (c'est automatiquement le cas si le serveur VPN est installé sur la passerelle du réseau local). Alternativement, il faut configurer le masquerading sur le serveur afin que les connexions initiées par les clients apparaissent comme provenant du serveur VPN (voir )." msgid "Configuring the OpenVPN Client" msgstr "Configuration du client OpenVPN" #, fuzzy #| msgid "DNSzone" msgid "OpenVPNclient" msgstr "DNSzone" msgid "Setting up an OpenVPN client also requires creating a configuration file in /etc/openvpn/. A standard configuration can be obtained by using /usr/share/doc/openvpn/examples/sample-config-files/client.conf as a starting point. The remote vpn.falcot.com 1194 directive describes the address and port of the OpenVPN server; the ca, cert and key also need to be adapted to describe the locations of the key files." msgstr "Pour mettre en place un client OpenVPN, il faut également déposer un fichier de configuration dans /etc/openvpn/. On pourra s'inspirer de /usr/share/doc/openvpn/examples/sample-config-files/client.conf pour une configuration standard. La directive remote vpn.falcot.com 1194 indique l'adresse et le port du serveur OpenVPN. Les directives ca, cert et key doivent aussi être modifiées pour indiquer l'emplacement des différentes clés." #, fuzzy #| msgid "networkvirtual private" msgid "OpenVPNAUTOSTART" msgstr "réseauprivé virtuel" #, fuzzy #| msgid "trafficlimitation" msgid "/etc/etc/default/openvpn" msgstr "traficlimitation" #, fuzzy #| msgid "servername" msgid "serviceopenvpn@.service" msgstr "serveurde noms" #, fuzzy #| msgid "If the VPN should not be started automatically on boot, set the AUTOSTART directive to none in the /etc/default/openvpn file. Starting or stopping a given VPN connection is always possible with the commands service openvpn@name start and service openvpn@name stop (where the connection name matches the one defined in /etc/openvpn/name.conf)." msgid "If the VPN should not be started automatically on boot, set the AUTOSTART directive to none in the /etc/default/openvpn file. Starting or stopping a given VPN connection is always possible with the commands systemctl start openvpn@name and systemctl stop openvpn@name (where the connection name matches the one defined in /etc/openvpn/name.conf)." msgstr "Si l'on ne veut pas que la connexion au VPN soit automatiquement mise en place au démarrage, on peut positionner AUTOSTART à none dans /etc/default/openvpn. On peut toujours démarrer/stopper une connexion VPN spécifique avec service openvpn@nom start et service openvpn@nom stop (la connexion nom correspond à celle définie dans /etc/openvpn/nom.conf)." #, fuzzy #| msgid "zonereverse" msgid "OpenVPNnetwork-manager-openvpn-gnome" msgstr "zoneinverse" #, fuzzy #| msgid "The network-manager-openvpn-gnome package contains an extension to Network Manager (see ) that allows managing OpenVPN virtual private networks. This allows every user to configure OpenVPN connections graphically and to control them from the network management icon. network-manager-openvpn-gnome" msgid "The network-manager-openvpn-gnome package contains an extension to Network Manager (see ) that allows managing OpenVPN virtual private networks. This allows every user to configure OpenVPN connections graphically and to control them from the network management icon." msgstr "Le paquet network-manager-openvpn-gnome est une extension de Network Manager (voir ) lui permettant de gérer des réseaux privés virtuels OpenVPN. Chaque utilisateur peut ainsi configurer graphiquement une connexion à un VPN OpenVPN et la contrôler depuis l'icône de gestion du réseau. network-manager-openvpn-gnome" #, fuzzy #| msgid "iputils-ping" msgid "network-manager-openvpn-gnome" msgstr "iputils-ping" msgid "Virtual Private Network with SSH" msgstr "Réseau privé virtuel avec SSH" #, fuzzy #| msgid "portTCP" msgid "SSHVPN" msgstr "portTCP" msgid "PPP" msgstr "PPP" #, fuzzy #| msgid "There are actually two ways of creating a virtual private network with SSH. The historic one involves establishing a PPP layer over the SSH link. This method is described in a HOWTO document: " msgid "There are actually two ways of creating a virtual private network with SSH. The historic one involves establishing a PPP layer over the SSH link. This method is described in a HOWTO document: " msgstr "Il existe en réalité deux méthodes pour établir un réseau privé virtuel à l'aide de SSH. La première, historique, consiste à établir une couche PPP au-dessus du lien SSH. Elle est documentée dans un HOWTO : " #, fuzzy #| msgid "DNSzone" msgid "SSHPermitTunnel" msgstr "DNSzone" #, fuzzy #| msgid "/etc/bind/named.conf" msgid "/etc/etc/ssh/sshd_config" msgstr "/etc/bind/named.conf" msgid "The second method is more recent, and was introduced with OpenSSH 4.3; it is now possible for OpenSSH to create virtual network interfaces (tun*) on both sides of an SSH connection, and these virtual interfaces can be configured exactly as if they were physical interfaces. The tunneling system must first be enabled by setting PermitTunnel to “yes” in the SSH server configuration file (/etc/ssh/sshd_config). When establishing the SSH connection, the creation of a tunnel must be explicitly requested with the -w any:any option (any can be replaced with the desired tun device number). This requires the user to have administrator privilege on both sides, so as to be able to create the network device (in other words, the connection must be established as root)." msgstr "La seconde méthode est plus récente. OpenSSH permet en effet, depuis sa version 4.3, d'établir des interfaces réseau virtuelles (tun*) de part et d'autre d'une connexion SSH. Ces interfaces réseau peuvent alors être configurées exactement comme s'il s'agissait d'interfaces réseau locales. Il faut autoriser la création de tunnels en positionnant PermitTunnel à « yes » dans la configuration du serveur SSH (/etc/ssh/sshd_config). Lors de l'établissement de la connexion, il faut explicitement demander la création d'un tunnel en passant l'option -w any:any (on peut remplacer any par le numéro de périphérique tun désiré). Des deux côtés, l'utilisateur doit avoir les droits administrateur pour créer le périphérique réseau nécessaire (autrement dit, il faut se connecter en tant que root)." msgid "Both methods for creating a virtual private network over SSH are quite straightforward. However, the VPN they provide is not the most efficient available; in particular, it does not handle high levels of traffic very well." msgstr "Quelle que soit la méthode choisie, l'établissement d'un réseau privé virtuel sur SSH est très simple à mettre en œuvre. En revanche, ce n'est pas le fonctionnement le plus efficace : il n'est pas adapté aux gros débits sur le réseau privé virtuel." #, fuzzy #| msgid "The explanation is that when a TCP/IP stack is encapsulated within a TCP/IP connection (for SSH), the TCP protocol is used twice, once for the SSH connection and once within the tunnel. This leads to problems, especially due to the way TCP adapts to network conditions by altering timeout delays. The following site describes the problem in more detail: VPNs over SSH should therefore be restricted to one-off tunnels with no performance constraints." msgid "The explanation is that when a TCP/IP stack is encapsulated within a TCP/IP connection (for SSH), the TCP protocol is used twice, once for the SSH connection and once within the tunnel. This leads to problems, especially due to the way TCP adapts to network conditions by altering timeout delays. The following site describes the problem in more detail: " msgstr "Concrètement, en encapsulant une pile de protocole TCP/IP dans une connexion TCP/IP (SSH), on emploie deux fois le protocole TCP (une fois pour le SSH proprement dit et une fois à l'intérieur du tunnel). Cela pose quelques problèmes, notamment à cause de la capacité de TCP à s'adapter aux conditions du réseau en variant les délais de timeout (délai maximal d'attente). Le site suivant détaille ces problèmes : On réservera donc l'utilisation de cette méthode aux tunnels établis ponctuellement et qui n'ont pas de fortes contraintes de performance." msgid "VPNs over SSH should therefore be restricted to one-off tunnels with no performance constraints." msgstr "" msgid "IPsec" msgstr "IPsec" msgid "IPsec" msgstr "IPsec" #, fuzzy #| msgid "protocolESP" msgid "Internet Protocol SecurityIPsec" msgstr "protocoleESP" msgid "libreswan" msgstr "libreswan" msgid "strongswan" msgstr "strongswan" msgid "IPsec, despite being the standard in IP VPNs, is rather more involved in its implementation. The IPsec engine itself is integrated in the Linux kernel; the required user-space parts, the control and configuration tools, are provided by the libreswan package or the strongswan package. Here we describe briefly the first of these options." msgstr "" #, fuzzy #| msgid "/etc/bind/named.conf" msgid "/etc/etc/ipsec.conf" msgstr "/etc/bind/named.conf" #, fuzzy #| msgid "servername" msgid "IPsectunnel" msgstr "serveurde noms" msgid "First, we install the libreswan package. In concrete terms, each host's /etc/ipsec.conf contains the parameters for IPsec tunnels (or Security Associations, in the IPsec terminology) that the host is concerned with. There are many configuration examples in /usr/share/doc/libreswan/, but Libreswan's online documentation has more examples with explanations: " msgstr "" #, fuzzy #| msgid "servername" msgid "serviceipsec.service" msgstr "serveurde noms" msgid "The IPsec service can be controlled with systemctl; for example, systemctl start ipsec will start the IPsec service." msgstr "" msgid "IKE" msgstr "IKE" #, fuzzy #| msgid "IPsec" msgid "IPsec Key ExchangeIKE" msgstr "IPsec" #, fuzzy #| msgid "IPsecIPsec Key Exchange" msgid "IPsecIPsec Key ExchangeIKE" msgstr "IPsecéchange de clefs IPsec" msgid "setkey" msgstr "setkey" msgid "In spite of its status as the reference, the complexity of setting up IPsec restricts its usage in practice. OpenVPN-based solutions will generally be preferred when the required tunnels are neither too many nor too dynamic." msgstr "Malgré son statut de référence, sa complexité de mise en œuvre restreint considérablement l'usage d'IPsec dans la pratique. On préférera généralement une solution à base d'OpenVPN lorsque les tunnels VPN nécessaires sont peu nombreux et n'évoluent pas régulièrement." msgid "CAUTION IPsec and NAT" msgstr "ATTENTION IPsec et NAT" msgid "NAT" msgstr "NAT" msgid "NAT-T" msgstr "NAT-T" #, fuzzy #| msgid "NAT Traversal" msgid "NAT TraversalNAT-T" msgstr "Nat Traversal" msgid "NATing firewalls and IPsec do not work well together: since IPsec signs the packets, any change on these packets that the firewall might perform will void the signature, and the packets will be rejected at their destination. Various IPsec implementations now include the NAT-T technique (for NAT Traversal), which basically encapsulates the IPsec packet within a standard UDP packet." msgstr "IPsec cohabite difficilement avec NAT sur un pare-feu. En effet, IPsec signant les paquets, toute modification de ceux-ci à la volée invalidera leur signature et les fera refuser. Les différentes implémentations d'IPsec proposent désormais la technique NAT-T (NAT Traversal, ou traversée de NAT), qui consiste à encapsuler le paquet IPsec dans un paquet UDP." msgid "SECURITY IPsec and firewalls" msgstr "SÉCURITÉ IPsec et pare-feu" msgid "ESP, protocol" msgstr "ESP, protocole" msgid "AH, protocol" msgstr "AH, protocole" msgid "protocolAH" msgstr "protocoleAH" msgid "protocolESP" msgstr "protocoleESP" msgid "The standard mode of operation of IPsec involves data exchanges on UDP port 500 for key exchanges (also on UDP port 4500 in the case that NAT-T is in use). Moreover, IPsec packets use two dedicated IP protocols that the firewall must let through; reception of these packets is based on their protocol numbers, 50 (ESP) and 51 (AH)." msgstr "Le fonctionnement d'IPsec induit des échanges de données sur le port UDP 500 pour les échanges de clés (et aussi sur le port UDP 4 500 si NAT-T est employé). De plus, les paquets IPsec utilisent deux protocoles IP dédiés que le pare-feu doit aussi laisser passer : les protocoles numérotés 50 (ESP) et 51 (AH)." msgid "PPTP" msgstr "PPTP" msgid "PPTP" msgstr "PPTP" msgid "GRE, protocol" msgstr "GRE, protocole" msgid "protocolGRE" msgstr "protocoleGRE" msgid "PPTP (for Point-to-Point Tunneling Protocol) uses two communication channels, one for control data and one for payload data; the latter uses the GRE protocol (Generic Routing Encapsulation). A standard PPP link is then set up over the data exchange channel." msgstr "PPTP (Point-to-Point Tunneling Protocol, ou protocole de tunnel en point à point) emploie deux canaux de communication, pour échanger respectivement des informations de contrôle et des données (ces dernières emploient le protocole GRE — Generic Routing Encapsulation, ou encapsulation de routage générique). Une connexion PPP standard s'établit sur le canal d'échange de données." msgid "Configuring the Client" msgstr "Configuration du client" #, fuzzy #| msgid "portTCP" msgid "PPTPClient" msgstr "portTCP" msgid "pptp-linux" msgstr "pptp-linux" msgid "The pptp-linux package contains an easily-configured PPTP client for Linux. The following instructions take their inspiration from the official documentation: " msgstr "Le paquet pptp-linux est facile à configurer. Les instructions suivantes sont inspirées de sa documentation officielle : " #, fuzzy #| msgid "servername" msgid "/etc/etc/ppp/" msgstr "serveurde noms" msgid "The Falcot administrators created several files: /etc/ppp/options.pptp, /etc/ppp/peers/falcot, /etc/ppp/ip-up.d/falcot, and /etc/ppp/ip-down.d/falcot." msgstr "Les administrateurs de Falcot ont créé plusieurs fichiers : /etc/ppp/options.pptp, /etc/ppp/peers/falcot, /etc/ppp/ip-up.d/falcot et /etc/ppp/ip-down.d/falcot." msgid "The /etc/ppp/options.pptp file" msgstr "Fichier /etc/ppp/options.pptp" msgid "" "\n" "# PPP options used for a PPTP connection\n" "lock\n" "noauth\n" "nobsdcomp\n" "nodeflate" msgstr "" "\n" "# Options PPP employées pour une connexion PPTP\n" "lock\n" "noauth\n" "nobsdcomp\n" "nodeflate" msgid "The /etc/ppp/peers/falcot file" msgstr "Fichier /etc/ppp/peers/falcot" msgid "" "\n" "# vpn.falcot.com is the PPTP server\n" "pty \"pptp vpn.falcot.com --nolaunchpppd\"\n" "# the connection will identify as the \"vpn\" user\n" "user vpn\n" "remotename pptp\n" "# encryption is needed\n" "require-mppe-128\n" "file /etc/ppp/options.pptp\n" "ipparam falcot" msgstr "" "\n" "# vpn.falcot.com est le serveur PPTP\n" "pty \"pptp vpn.falcot.com --nolaunchpppd\"\n" "# la connexion s'identifiera comme utilisateur « vpn »\n" "user vpn\n" "remotename pptp\n" "# la prise en charge du chiffrement est nécessaire\n" "require-mppe-128\n" "file /etc/ppp/options.pptp\n" "ipparam falcot" msgid "The /etc/ppp/ip-up.d/falcot file" msgstr "Fichier /etc/ppp/ip-up.d/falcot" #, fuzzy #| msgid "" #| "\n" #| "# Create the route to the Falcot network\n" #| "if [ \"$6\" = \"falcot\" ]; then\n" #| " # 192.168.0.0/24 is the (remote) Falcot network\n" #| " route add -net 192.168.0.0 netmask 255.255.255.0 dev $1\n" #| "fi" msgid "" "\n" "# Create the route to the Falcot network\n" "if [ \"$6\" = \"falcot\" ]; then\n" " # 192.168.0.0/24 is the (remote) Falcot network\n" " ip route add 192.168.0.0/24 dev $1\n" "fi" msgstr "" "\n" "# Créer la route vers le réseau local de Falcot\n" "if [ \"$6\" = \"falcot\" ]; then\n" " # 192.168.0.0/24 est le réseau distant chez Falcot\n" " route add -net 192.168.0.0 netmask 255.255.255.0 dev $1\n" "fi" msgid "The /etc/ppp/ip-down.d/falcot file" msgstr "Fichier /etc/ppp/ip-down.d/falcot" #, fuzzy #| msgid "" #| "\n" #| "# Delete the route to the Falcot network\n" #| "if [ \"$6\" = \"falcot\" ]; then\n" #| " # 192.168.0.0/24 is the (remote) Falcot network\n" #| " route del -net 192.168.0.0 netmask 255.255.255.0 dev $1\n" #| "fi" msgid "" "\n" "# Delete the route to the Falcot network\n" "if [ \"$6\" = \"falcot\" ]; then\n" " # 192.168.0.0/24 is the (remote) Falcot network\n" " ip route del 192.168.0.0/24 dev $1\n" "fi" msgstr "" "\n" "# Supprimer la route vers le réseau local de Falcot\n" "if [ \"$6\" = \"falcot\" ]; then\n" " # 192.168.0.0/24 est le réseau distant chez Falcot\n" " route del -net 192.168.0.0 netmask 255.255.255.0 dev $1\n" "fi" msgid "SECURITY MPPE" msgstr "SÉCURITÉ MPPE" msgid "MPPE" msgstr "MPPE" #, fuzzy #| msgid "MicrosoftPoint-to-Point Encryption" msgid "MicrosoftPoint-to-Point EncryptionMPPE" msgstr "MicrosoftPoint-to-Point Encryption" msgid "Securing PPTP involves using the MPPE feature (Microsoft Point-to-Point Encryption), which is available in official Debian kernels as a module." msgstr "La sécurisation de PPTP recourt à MPPE (Microsoft Point-to-Point Encryption, ou chiffrement point à point de Microsoft), fonctionnalité intégrée sous forme de module dans les noyaux Debian officiels." msgid "Configuring the Server" msgstr "Configuration du serveur" #, fuzzy #| msgid "bgpd" msgid "pptpd" msgstr "bgpd" msgid "CAUTION PPTP and firewalls" msgstr "ATTENTION PPTP et pare-feu" msgid "Intermediate firewalls need to be configured to let through IP packets using protocol 47 (GRE). Moreover, the PPTP server's port 1723 needs to be open so that the communication channel can happen." msgstr "Les pare-feu intermédiaires doivent autoriser les paquets IP employant le protocole 47 (GRE). De plus, le port 1 723 du serveur PPTP doit être ouvert pour qu'une communication puisse prendre place." #, fuzzy #| msgid "/etc/bind/named.conf" msgid "/etc/etc/pptpd.conf" msgstr "/etc/bind/named.conf" msgid "pptpd is the PPTP server for Linux. Its main configuration file, /etc/pptpd.conf, requires very few changes: localip (local IP address) and remoteip (remote IP address). In the example below, the PPTP server always uses the 192.168.0.199 address, and PPTP clients receive IP addresses from 192.168.0.200 to 192.168.0.250." msgstr "pptpd est le serveur PPTP pour Linux. Son fichier de configuration principal /etc/pptpd.conf n'a presque pas besoin de modifications ; il faut juste y renseigner localip (adresse IP locale) et remoteip (adresse IP distante). Dans le fichier suivant, le serveur PPTP a toujours l'adresse IP 192.168.0.199 et les clients PPTP reçoivent des adresses IP comprises entre 192.168.0.200 et 192.168.0.250." msgid "The /etc/pptpd.conf file" msgstr "Fichier /etc/pptpd.conf" #, fuzzy #| msgid "" #| "\n" #| "# TAG: speed\n" #| "#\n" #| "# Specifies the speed for the PPP daemon to talk at.\n" #| "#\n" #| "speed 115200\n" #| "\n" #| "# TAG: option\n" #| "#\n" #| "# Specifies the location of the PPP options file.\n" #| "# By default PPP looks in '/etc/ppp/options'\n" #| "#\n" #| "option /etc/ppp/pptpd-options\n" #| "\n" #| "# TAG: debug\n" #| "#\n" #| "# Turns on (more) debugging to syslog\n" #| "#\n" #| "# debug\n" #| "\n" #| "# TAG: localip\n" #| "# TAG: remoteip\n" #| "#\n" #| "# Specifies the local and remote IP address ranges.\n" #| "#\n" #| "# You can specify single IP addresses separated by commas or you can\n" #| "# specify ranges, or both. For example:\n" #| "#\n" #| "# 192.168.0.234,192.168.0.245-249,192.168.0.254\n" #| "#\n" #| "# IMPORTANT RESTRICTIONS:\n" #| "#\n" #| "# 1. No spaces are permitted between commas or within addresses.\n" #| "#\n" #| "# 2. If you give more IP addresses than MAX_CONNECTIONS, it will\n" #| "# start at the beginning of the list and go until it gets\n" #| "# MAX_CONNECTIONS IPs. Others will be ignored.\n" #| "#\n" #| "# 3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,\n" #| "# you must type 234-238 if you mean this.\n" #| "#\n" #| "# 4. If you give a single localIP, that's ok - all local IPs will\n" #| "# be set to the given one. You MUST still give at least one remote\n" #| "# IP for each simultaneous client.\n" #| "#\n" #| "#localip 192.168.0.234-238,192.168.0.245\n" #| "#remoteip 192.168.1.234-238,192.168.1.245\n" #| "#localip 10.0.1.1\n" #| "#remoteip 10.0.1.2-100\n" #| "localip 192.168.0.199\n" #| "remoteip 192.168.0.200-250" msgid "" "\n" "[..]\n" "# TAG: localip\n" "# TAG: remoteip\n" "# Specifies the local and remote IP address ranges.\n" "#\n" "# These options are ignored if delegate option is set.\n" "#\n" "# Any addresses work as long as the local machine takes care of the\n" "# routing. But if you want to use MS-Windows networking, you should\n" "# use IP addresses out of the LAN address space and use the proxyarp\n" "# option in the pppd options file, or run bcrelay.\n" "#\n" "# You can specify single IP addresses seperated by commas or you can\n" "# specify ranges, or both. For example:\n" "#\n" "# 192.168.0.234,192.168.0.245-249,192.168.0.254\n" "#\n" "# IMPORTANT RESTRICTIONS:\n" "#\n" "# 1. No spaces are permitted between commas or within addresses.\n" "#\n" "# 2. If you give more IP addresses than the value of connections,\n" "# it will start at the beginning of the list and go until it\n" "# gets connections IPs. Others will be ignored.\n" "#\n" "# 3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,\n" "# you must type 234-238 if you mean this.\n" "#\n" "# 4. If you give a single localIP, that's ok - all local IPs will\n" "# be set to the given one. You MUST still give at least one remote\n" "# IP for each simultaneous client.\n" "#\n" "# (Recommended)\n" "#localip 192.168.0.1\n" "#remoteip 192.168.0.234-238,192.168.0.245\n" "# or\n" "#localip 192.168.0.234-238,192.168.0.245\n" "#remoteip 192.168.1.234-238,192.168.1.245\n" "localip 192.168.0.199\n" "remoteip 192.168.0.200-250" msgstr "" "\n" "# TAG: speed\n" "#\n" "# Specifies the speed for the PPP daemon to talk at.\n" "#\n" "speed 115200\n" "\n" "# TAG: option\n" "#\n" "# Specifies the location of the PPP options file.\n" "# By default PPP looks in '/etc/ppp/options'\n" "#\n" "option /etc/ppp/pptpd-options\n" "\n" "# TAG: debug\n" "#\n" "# Turns on (more) debugging to syslog\n" "#\n" "# debug\n" "\n" "# TAG: localip\n" "# TAG: remoteip\n" "#\n" "# Specifies the local and remote IP address ranges.\n" "#\n" "# You can specify single IP addresses separated by commas or you can\n" "# specify ranges, or both. For example:\n" "#\n" "# 192.168.0.234,192.168.0.245-249,192.168.0.254\n" "#\n" "# IMPORTANT RESTRICTIONS:\n" "#\n" "# 1. No spaces are permitted between commas or within addresses.\n" "#\n" "# 2. If you give more IP addresses than MAX_CONNECTIONS, it will\n" "# start at the beginning of the list and go until it gets\n" "# MAX_CONNECTIONS IPs. Others will be ignored.\n" "#\n" "# 3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,\n" "# you must type 234-238 if you mean this.\n" "#\n" "# 4. If you give a single localIP, that's ok - all local IPs will\n" "# be set to the given one. You MUST still give at least one remote\n" "# IP for each simultaneous client.\n" "#\n" "#localip 192.168.0.234-238,192.168.0.245\n" "#remoteip 192.168.1.234-238,192.168.1.245\n" "#localip 10.0.1.1\n" "#remoteip 10.0.1.2-100\n" "localip 192.168.0.199\n" "remoteip 192.168.0.200-250" #, fuzzy #| msgid "trafficlimitation" msgid "/etc/etc/ppp/pptpd-options" msgstr "traficlimitation" msgid "The PPP configuration used by the PPTP server also requires a few changes in /etc/ppp/pptpd-options. The important parameters are the server name (pptp), the domain name (falcot.com), and the IP addresses for DNS and WINS servers." msgstr "Il faut aussi modifier la configuration PPP employée par le serveur PPTP, consignée dans le fichier /etc/ppp/pptpd-options. Les paramètres importants à changer sont les noms du serveur (pptp) et du domaine (falcot.com) ainsi que les adresses IP des serveurs DNS et Wins." msgid "The /etc/ppp/pptpd-options file" msgstr "Fichier /etc/ppp/pptpd-options" #, fuzzy #| msgid "" #| "\n" #| "## turn pppd syslog debugging on\n" #| "#debug\n" #| "\n" #| "## change 'servername' to whatever you specify as your server name in chap-secrets\n" #| "name pptp\n" #| "## change the domainname to your local domain\n" #| "domain falcot.com\n" #| "\n" #| "## these are reasonable defaults for WinXXXX clients\n" #| "## for the security related settings\n" #| "# The Debian pppd package now supports both MSCHAP and MPPE, so enable them\n" #| "# here. Please note that the kernel support for MPPE must also be present!\n" #| "auth\n" #| "require-chap\n" #| "require-mschap\n" #| "require-mschap-v2\n" #| "require-mppe-128\n" #| "\n" #| "## Fill in your addresses\n" #| "ms-dns 192.168.0.1\n" #| "ms-wins 192.168.0.1\n" #| "\n" #| "## Fill in your netmask\n" #| "netmask 255.255.255.0\n" #| "\n" #| "## some defaults\n" #| "nodefaultroute\n" #| "proxyarp\n" #| "lock" msgid "" "\n" "# Enable connection debugging facilities.\n" "# (see your syslog configuration for where pppd sends to)\n" "#debug\n" "\n" "# Name of the local system for authentication purposes\n" "# (must match the second field in /etc/ppp/chap-secrets entries)\n" "name pptpd\n" "\n" "# Optional: domain name to use for authentication\n" "## change the domainname to your local domain\n" "domain falcot.com\n" "\n" "# Authentication\n" "## these are reasonable defaults for WinXXXX clients\n" "## for the security related settings\n" "auth\n" "refuse-pap\n" "refuse-chap\n" "refuse-mschap\n" "# Require the peer to authenticate itself using MS-CHAPv2 [Microsoft\n" "# Challenge Handshake Authentication Protocol, Version 2] authentication.\n" "require-mschap-v2\n" "# Require MPPE 128-bit encryption\n" "# (note that MPPE requires the use of MSCHAP-V2 during authentication)\n" "require-mppe-128\n" "\n" "# Network and Routing\n" "## Fill in your addresses\n" "ms-dns 192.168.0.1\n" "ms-wins 192.168.0.1\n" "\n" "## Fill in your netmask\n" "netmask 255.255.255.0\n" "\n" "## some defaults\n" "nodefaultroute\n" "proxyarp\n" "lock" msgstr "" "\n" "## turn pppd syslog debugging on\n" "#debug\n" "\n" "## change 'servername' to whatever you specify as your server name in chap-secrets\n" "name pptp\n" "## change the domainname to your local domain\n" "domain falcot.com\n" "\n" "## these are reasonable defaults for WinXXXX clients\n" "## for the security related settings\n" "# The Debian pppd package now supports both MSCHAP and MPPE, so enable them\n" "# here. Please note that the kernel support for MPPE must also be present!\n" "auth\n" "require-chap\n" "require-mschap\n" "require-mschap-v2\n" "require-mppe-128\n" "\n" "## Fill in your addresses\n" "ms-dns 192.168.0.1\n" "ms-wins 192.168.0.1\n" "\n" "## Fill in your netmask\n" "netmask 255.255.255.0\n" "\n" "## some defaults\n" "nodefaultroute\n" "proxyarp\n" "lock" #, fuzzy #| msgid "zonereverse" msgid "/etc/etc/ppp/chap-secrets" msgstr "zoneinverse" msgid "The last step involves registering the vpn user (and the associated password) in the /etc/ppp/chap-secrets file. Contrary to other instances where an asterisk (*) would work, the server name must be filled explicitly here. Furthermore, Windows PPTP clients identify themselves under the DOMAIN\\\\USER form, instead of only providing a user name. This explains why the file also mentions the FALCOT\\\\vpn user. It is also possible to specify individual IP addresses for users; an asterisk in this field specifies that dynamic addressing should be used." msgstr "La dernière étape est d'enregistrer l'utilisateur vpn et le mot de passe associé dans le fichier /etc/ppp/chap-secrets. Le nom du serveur doit y être renseigné explicitement, l'astérisque (*) habituel ne fonctionnant pas. Par ailleurs, il faut savoir que les clients PPTP sous Windows s'identifient sous la forme DOMAINE\\\\UTILISATEUR au lieu de se contenter du nom d'utilisateur. C'est pourquoi on trouve aussi dans ce fichier l'utilisateur FALCOT\\\\vpn. On peut encore y spécifier individuellement les adresses IP des utilisateurs, ou indiquer un astérisque dans ce champ si l'on ne souhaite pas d'adresses fixes." msgid "The /etc/ppp/chap-secrets file" msgstr "Fichier /etc/ppp/chap-secrets" msgid "" "\n" "# Secrets for authentication using CHAP\n" "# client server secret IP addresses\n" "vpn pptp f@Lc3au *\n" "FALCOT\\\\vpn pptp f@Lc3au *" msgstr "" "\n" "# Secrets for authentication using CHAP\n" "# client server secret IP addresses\n" "vpn pptp f@Lc3au *\n" "FALCOT\\\\vpn pptp f@Lc3au *" msgid "SECURITY PPTP vulnerabilities" msgstr "SÉCURITÉ Failles de PPTP" #, fuzzy #| msgid "zonereverse" msgid "PPTPvulnerabilities" msgstr "zoneinverse" msgid "Microsoft's first PPTP implementation drew severe criticism because it had many security vulnerabilities; most have since then been fixed in more recent versions. The configuration documented in this section uses the latest version of the protocol. Be aware though that removing some options (such as require-mppe-128 and require-mschap-v2) would make the service vulnerable again." msgstr "La première implémentation par Microsoft de PPTP fut sévèrement critiquée car elle souffrait de nombreuses failles de sécurité, pour la plupart corrigées dans la dernière version du protocole. C'est cette dernière version qui est employée par la configuration documentée dans cette section. Attention cependant, car la suppression de certaines options (notamment require-mppe-128 et require-mschap-v2) rendrait le service à nouveau vulnérable." msgid "Quality of Service" msgstr "Qualité de service" msgid "Principle and Mechanism" msgstr "Principe et fonctionnement" #, fuzzy #| msgid "networkgateway" msgid "networkQoS" msgstr "réseaupasserelle" msgid "QoS" msgstr "QoS" #, fuzzy #| msgid "quality of service" msgid "Quality of ServiceQoS" msgstr "quality of service" #, fuzzy #| msgid "qualityof service" msgid "qualityof serviceQoS" msgstr "qualitéde service" #, fuzzy #| msgid "servicequality" msgid "servicequalityQoS" msgstr "servicequalité" msgid "Quality of Service (or QoS for short) refers to a set of techniques that guarantee or improve the quality of the service provided to applications. The most popular such technique involves classifying the network traffic into categories, and differentiating the handling of traffic according to which category it belongs to. The main application of this differentiated services concept is traffic shaping, which limits the data transmission rates for connections related to some services and/or hosts so as not to saturate the available bandwidth and starve important other services. Traffic shaping is a particularly good fit for TCP traffic, since this protocol automatically adapts to available bandwidth." msgstr "Le terme QoS (Quality of Service) désigne l'ensemble des techniques permettant de garantir ou d'améliorer sensiblement la qualité de service apportée à des applications. La plus populaire consiste à traiter différemment chaque type de trafic réseau ; son application principale est le shaping. Cela permet de limiter les débits attribués à certains services et/ou à certaines machines, notamment pour ne pas saturer la bande passante. Cette technique s'adapte bien au flux TCP car ce protocole s'adapte automatiquement au débit disponible." #, fuzzy #| msgid "CULTURE SSL and TLS" msgid "CULTURE Net neutrality and QoS" msgstr "CULTURE SSL et TLS" #, fuzzy #| msgid "networkgateway" msgid "networkneutrality" msgstr "réseaupasserelle" msgid "Network neutrality is achieved when Internet service providers treat all Internet communications equally, that is, without any access limitation based on content, user, website, destination address, etc." msgstr "" msgid "Quality of service can be implemented in a net neutral Internet, but only if Internet service providers can't charge a special fee for a higher-quality service." msgstr "" msgid "It is also possible to alter the priorities on traffic, which allows prioritizing packets related to interactive services (such as ssh and telnet) or to services that only deal with small blocks of data." msgstr "On peut encore modifier les priorités du trafic, ce qui permet généralement de traiter d'abord les paquets relatifs à des services interactifs (ssh, telnet) ou à des services échangeant de petits blocs de données." msgid "The Debian kernels include the features required for QoS along with their associated modules. These modules are many, and each of them provides a different service, most notably by way of special schedulers for the queues of IP packets; the wide range of available scheduler behaviors spans the whole range of possible requirements." msgstr "Les noyaux Debian intègrent le QoS et toute la panoplie des modules associés. Ils sont nombreux, et chacun offre un service différent — notamment par le biais de files d'attente pour les paquets IP (scheduler, ou ordonnanceur), dont les mécanismes variés couvrent tout le spectre des besoins possibles." msgid "CULTURE LARTC — Linux Advanced Routing & Traffic Control" msgstr "CULTURE LARTC — Linux Advanced Routing & Trafic Control" #, fuzzy #| msgid "networkvirtual private" msgid "networkadvanced routingrouting" msgstr "réseauprivé virtuel" msgid "routingadvanced" msgstr "routageavancé" msgid "trafficcontrol" msgstr "traficcontrôle" msgid "control of traffic" msgstr "contrôle du trafic" #, fuzzy #| msgid "The Linux Advanced Routing & Traffic Control HOWTO is the reference document covering everything there is to know about network quality of service. " msgid "The Linux Advanced Routing & Traffic Control HOWTO is the reference document covering everything there is to know about network quality of service. " msgstr "Le HOWTO du routage avancé et du contrôle de trafic sous Linux est un document de référence qui couvre de manière assez exhaustive tout ce qui concerne la qualité de service. " msgid "Configuring and Implementing" msgstr "Configuration et mise en œuvre" msgid "iproute" msgstr "iproute" msgid "tc" msgstr "tc" msgid "QoS parameters are set through the tc command (provided by the iproute package). Since its interface is quite complex, using higher-level tools is recommended." msgstr "Le QoS se paramètre avec le logiciel tc, du paquet Debian iproute. Son interface étant extrêmement complexe, il est préférable d'employer des outils de plus haut niveau." msgid "Reducing Latencies: wondershaper" msgstr "Minimiser le temps de latence : wondershaper" msgid "wondershaper" msgstr "wondershaper" msgid "limitation of traffic" msgstr "limitation de trafic" msgid "trafficlimitation" msgstr "traficlimitation" msgid "The main purpose of wondershaper (in the similarly-named package) is to minimize latencies independent of network load. This is achieved by limiting total traffic to a value that falls just short of the link saturation value." msgstr "L'objectif de wondershaper (du paquet Debian éponyme) est de minimiser les temps de latence quelle que soit la charge réseau. Il l'atteint en limitant le trafic total juste en deçà de la valeur de saturation de la ligne." #, fuzzy #| msgid "Once a network interface is configured, setting up this traffic limitation is achieved by running wondershaper interface download_rate upload_rate. The interface can be eth0 or ppp0 for example, and both rates are expressed in kilobits per second. The wondershaper remove interface command disables traffic control on the specified interface." msgid "Once a network interface is configured, setting up this traffic limitation is achieved by running wondershaper interface download_rate upload_rate. The interface can be enp1s0, eth0 or ppp0 for example, and both rates are expressed in kilobits per second. The wondershaper remove interface command disables traffic control on the specified interface." msgstr "Après la configuration d'une interface réseau, il est possible de mettre en place ce contrôle du trafic par la commande wondershaper interface débit_descendant débit_montant. L'interface sera par exemple eth0 ou ppp0 et les deux débits (descendant et montant) s'expriment en kilobits par seconde. La commande wondershaper remove interface désactive le contrôle du trafic sur l'interface indiquée." #, fuzzy #| msgid "zonereverse" msgid "/etc/etc/network/interfaces" msgstr "zoneinverse" #, fuzzy #| msgid "For an Ethernet connection, this script is best called right after the interface is configured. This is done by adding up and down directives to the /etc/network/interfaces file allowing declared commands to be run, respectively, after the interface is configured and before it is deconfigured. For example:" msgid "For an Ethernet connection, historically this script would be called right after the interface is configured. This is done by adding up and down directives to the /etc/network/interfaces file allowing declared commands to be run, respectively, after the interface is configured and before it is deconfigured. Or in the PPP case, creating a script that calls wondershaper in /etc/ppp/ip-up.d/ will enable traffic control as soon as the connection is up. Below is an example using this first method:" msgstr "Pour une connexion Ethernet, le plus simple est d'appeler automatiquement ce script après la configuration de l'interface en modifiant le fichier /etc/network/interfaces pour y ajouter des directives up (indiquant une commande à exécuter après configuration de l'interface) et down (indiquant une commande à exécuter après déconfiguration de l'interface) comme suit :" msgid "Changes in the /etc/network/interfaces file" msgstr "Modification du fichier /etc/network/interfaces" msgid "" "\n" "iface eth0 inet dhcp\n" " up /sbin/wondershaper eth0 500 100\n" " down /sbin/wondershaper remove eth0" msgstr "" "\n" "iface eth0 inet dhcp\n" " up /sbin/wondershaper eth0 500 100\n" " down /sbin/wondershaper remove eth0" msgid "GOING FURTHER Optimal configuration" msgstr "POUR ALLER PLUS LOIN Configuration optimale" msgid "The /usr/share/doc/wondershaper/README.Debian.gz file describes, in some detail, the configuration method recommended by the package maintainer. In particular, it advises measuring the download and upload speeds so as to best evaluate real limits." msgstr "Le fichier /usr/share/doc/wondershaper/README.Debian.gz détaille la méthode de configuration recommandée par le mainteneur du paquet. Il conseille d'effectuer des mesures de vitesses de téléchargement pour mieux évaluer les limites réelles." msgid "Standard Configuration" msgstr "Configuration standard" msgid "DSCP" msgstr "DSCP" #, fuzzy #| msgid "reverse zone" msgid "Differentiated Services Code PointDSCP" msgstr "inverse, zone" #, fuzzy #| msgid "Barring a specific QoS configuration, the Linux kernel uses the pfifo_fast queue scheduler, which provides a few interesting features by itself. The priority of each processed IP packet is based on the ToS field (Type of Service) of this packet; modifying this field is enough to take advantage of the scheduling features. There are five possible values:" msgid "Barring a specific QoS configuration, the Linux kernel uses the pfifo_fast queue scheduler, which provides a few interesting features by itself. The priority of each processed IP packet is based on the DSCP field (Differentiated Services Code Point) of this packet; modifying this 6-bit field is enough to take advantage of the scheduling features. Refer to for more information." msgstr "En l'absence d'une configuration particulière de QoS, le noyau Linux emploie la file d'attente pfifo_fast, qui propose déjà quelques fonctionnalités intéressantes. Pour établir les priorités des paquets IP, elle utilise leur champ ToS (Type of Service, ou type de service) — qu'il suffira donc de modifier pour bénéficier de cette file. Ce champ peut recevoir cinq valeurs :" #, fuzzy #| msgid "DNSzone" msgid "IPnetfilter" msgstr "DNSzone" #, fuzzy #| msgid "The ToS field can be set by applications that generate IP packets, or modified on the fly by netfilter. The following rules are sufficient to increase responsiveness for a server's SSH service:" msgid "The DSCP field can be set by applications that generate IP packets, or modified on the fly by netfilter. The following rules are sufficient to increase responsiveness for a server's SSH service, note that the DSCP field must be set in hexadecimal:" msgstr "Le champ ToS peut être positionné par les applications qui génèrent des paquets IP ou modifié à la volée par netfilter. Avec la règle ci-dessous, il est ainsi possible d'améliorer l'interactivité du service SSH d'un serveur :" msgid "" "\n" "nft add table ip mangle\n" "nft add rule ip mangle PREROUTING tcp sport 22 counter ip dscp set 0x04\n" "nft add rule ip mangle PREROUTING tcp dport 22 counter ip dscp set 0x04" msgstr "" msgid "Dynamic Routing" msgstr "Routage dynamique" #, fuzzy #| msgid "routingdynamic" msgid "routingdynamicfrr" msgstr "routagedynamique" #, fuzzy #| msgid "ripd" msgid "frr" msgstr "ripd" #, fuzzy #| msgid "quagga" msgid "quaggafrr" msgstr "quagga" #, fuzzy #| msgid "zebra" msgid "zebrafrr" msgstr "zebra" #, fuzzy #| msgid "The reference tool for dynamic routing is currently quagga, from the similarly-named package; it used to be zebra until development of the latter stopped. However, quagga kept the names of the programs for compatibility reasons which explains the zebra commands below." msgid "The reference tool for dynamic routing is currently frr from the similarly-named package; it used to be quagga, and before that zebra until development of these stopped. However, frr kept the names of the programs for compatibility reasons which explains the zebra commands below." msgstr "Le logiciel quagga (du paquet Debian éponyme) est désormais la référence en matière de routage dynamique (il a supplanté zebra, dont le développement s'est arrêté). Cependant, pour des raisons de compatibilité, le projet quagga a conservé les noms des exécutables : c'est pourquoi on retrouve le programme zebra plus loin." msgid "BACK TO BASICS Dynamic routing" msgstr "B.A.-BA Routage dynamique" msgid "Dynamic routing allows routers to adjust, in real time, the paths used for transmitting IP packets. Each protocol involves its own method of defining routes (shortest path, use routes advertised by peers, and so on)." msgstr "Le routage dynamique permet aux routeurs d'ajuster en temps réel les chemins employés pour faire circuler les paquets IP. Chaque protocole a sa propre méthode de définition des routes (calcul du chemin le plus court, récupération des routes annoncées par les partenaires, etc.)." #, fuzzy #| msgid "trafficlimitation" msgid "iproute" msgstr "traficlimitation" msgid "route" msgstr "route" #, fuzzy #| msgid "In the Linux kernel, a route links a network device to a set of machines that can be reached through this device. The route command defines new routes and displays existing ones." msgid "In the Linux kernel, a route links a network device to a set of machines that can be reached through this device. The ip command, when route is used as the first argument, defines new routes and displays existing ones. The route command was used for that purpose, but it is deprecated in favor of ip." msgstr "Pour le noyau Linux, une route associe un périphérique réseau à un ensemble de machines qu'il peut atteindre. La commande route permet de les définir et de les consulter." #, fuzzy #| msgid "Quagga is a set of daemons cooperating to define the routing tables to be used by the Linux kernel; each routing protocol (most notably BGP, OSPF and RIP) provides its own daemon. The zebra daemon collects information from other daemons and handles static routing tables accordingly. The other daemons are known as bgpd, ospfd, ospf6d, ripd, ripngd, isisd, and babeld." msgid "FRR (FRRouting) is a set of daemons cooperating to define the routing tables to be used by the Linux kernel; each routing protocol (most notably BGP, OSPF and RIP) provides its own daemon(s). The zebra and staticd daemons, which are always started, collect information from other daemons and handle static routing tables accordingly. The other daemons are known as bgpd, ospfd, ospf6d, ripd, ripngd, isisd, etc." msgstr "C'est un ensemble de démons qui coopèrent pour définir les tables de routage employées par le noyau Linux, chaque protocole de routage (notamment BGP, OSPF, RIP) disposant de son propre démon. Le démon zebra centralise les informations reçues des autres démons (bgpd, ospfd, ospf6d, ripd, ripngd et babeld) et gère les tables de routage statiques." msgid "OSPF" msgstr "OSPF" msgid "BGP" msgstr "BGP" msgid "RIP" msgstr "RIP" msgid "IS-IS" msgstr "IS-IS" msgid "bgpd" msgstr "bgpd" msgid "ospfd" msgstr "ospfd" msgid "ospf6d" msgstr "ospf6d" msgid "ripd" msgstr "ripd" msgid "ripngd" msgstr "ripngd" msgid "isisd" msgstr "isisd" #, fuzzy #| msgid "servername" msgid "servicefrr.service" msgstr "serveurde noms" msgid "Daemons are enabled by creating the /etc/frr/daemon.conf config file, daemon being the name of the daemon to use, and editing the /etc/frr/daemon configuration file. The daemon config file must belong to the frr user and group with permissions of 0640 in order for the /etc/init.d/frr script or the frr.service systemd service file to invoke the daemon. The package frr provides configuration examples under /usr/share/doc/frr/examples/." msgstr "" #, fuzzy #| msgid "The configuration of each of these daemons requires knowledge of the routing protocol in question. These protocols cannot be described in detail here, but the quagga-doc provides ample explanation in the form of an info file. The same contents may be more easily browsed as HTML on the Quagga website: " msgid "The configuration of each of these daemons requires knowledge of the routing protocol in question. These protocols cannot be described in detail here, but frr-doc provides ample explanation in the form of both info and HTML files. The same contents may be more browsed on the project's website: " msgstr "La configuration de chacun de ces démons impose de connaître le fonctionnement du protocole de routage concerné. Il n'est pas possible de tous les détailler ici, mais sachez que le manuel au format info du paquet quagga-doc n'est pas avare d'explications. Par souci d'ergonomie, il est aussi possible de consulter ce manuel au format HTML à l'adresse suivante : " #, fuzzy #| msgid "In addition, the syntax is very close to a standard router's configuration interface, and network administrators will adapt quickly to quagga." msgid "In addition, the syntax is very close to a standard router's configuration interface, and network administrators will adapt quickly to frr." msgstr "Par ailleurs, la syntaxe est très similaire à l'interface de configuration d'un routeur traditionnel et un administrateur réseau s'adaptera rapidement à quagga." msgid "IN PRACTICE OSPF, BGP or RIP?" msgstr "EN PRATIQUE OSPF, BGP ou RIP ?" #, fuzzy #| msgid "protocolESP" msgid "protocolBGP" msgstr "protocoleESP" #, fuzzy #| msgid "protocolESP" msgid "protocolRIP" msgstr "protocoleESP" #, fuzzy #| msgid "OSPF is generally the best protocol to use for dynamic routing on private networks, but BGP is more common for Internet-wide routing. RIP is rather ancient, and hardly used anymore." msgid "OSPF (Open Shortest Path First) is generally the best protocol to use for dynamic routing on private networks, but BGP (Border Gateway Protocol) is more common for Internet-wide routing. RIP (Routing Information Protocol) is rather ancient, and hardly used anymore." msgstr "OSPF est probablement le protocole à privilégier pour du routage dynamique sur des réseaux privés, mais c'est BGP qu'on trouve majoritairement sur Internet. RIP est un ancêtre désormais assez peu utilisé." #, fuzzy #| msgid "portTCP" msgid "IPv4IPv4" msgstr "portTCP" #, fuzzy #| msgid "firewallIPv6" msgid "IPv6IPv6" msgstr "IPv6pare-feu" #, fuzzy #| msgid "IPv6" msgid "IPv4" msgstr "IPv6" msgid "IPv6" msgstr "IPv6" msgid "iputils-ping" msgstr "iputils-ping" msgid "iputils-tracepath" msgstr "iputils-tracepath" #, fuzzy #| msgid "IPv6, successor to IPv4, is a new version of the IP protocol designed to fix its flaws, most notably the scarcity of available IP addresses. This protocol handles the network layer; its purpose is to provide a way to address machines, to convey data to their intended destination, and to handle data fragmentation if needed (in other words, to split packets into chunks with a size that depends on the network links to be used on the path and to reassemble the chunks in their proper order on arrival)." msgid "IPv6, successor to IPv4, is a newer version of the IP protocol designed to fix its flaws, most notably the scarcity of available IP addresses. This protocol handles the network layer; its purpose is to provide a way to address machines, to convey data to their intended destination, and to handle data fragmentation if needed (in other words, to split packets into chunks with a size that depends on the network links to be used on the path and to reassemble the chunks in their proper order on arrival)." msgstr "IPv6 — successeur d'IPv4 — est une nouvelle version du protocole IP, qui doit en corriger les défauts et notamment le nombre trop faible d'adresses IP existantes. Ce protocole gère la couche réseau, il offre ainsi la possibilité d'adresser les machines (c'est-à-dire de faire parvenir les données à leur destination connue par une adresse) et de fragmenter les données (à savoir de les découper en tronçons dépendants de la taille des différents liens empruntés en chemin, et de les réassembler à l'arrivée)." msgid "Debian kernels include IPv6 handling in the core kernel (with the exception of some architectures that have it compiled as a module named ipv6). Basic tools such as ping and traceroute have their IPv6 equivalents in ping6 and traceroute6, available respectively in the iputils-ping and iputils-tracepath packages." msgstr "Les noyaux Debian prennent systématiquement IPv6 en charge, le code correspondant étant intégré à l'image de base (à part pour certaines architectures, qui ne le proposent que dans un module ipv6 optionnel). Les outils de base comme ping et traceroute ont pour équivalents IPv6 ping6 et traceroute6, respectivement disponibles dans les paquets Debian iputils-ping et iputils-tracepath." msgid "The IPv6 network is configured similarly to IPv4, in /etc/network/interfaces. But if you want that network to be globally available, you must ensure that you have an IPv6-capable router relaying traffic to the global IPv6 network." msgstr "On peut configurer le réseau IPv6 comme un réseau IPv4, à travers le fichier /etc/network/interfaces. Pour ne pas se contenter d'un réseau IPv6 privé, il faut cependant disposer d'un routeur capable de relayer le trafic sur le réseau IPv6 global." msgid "Example of IPv6 configuration" msgstr "Exemple de configuration IPv6" #, fuzzy #| msgid "" #| "\n" #| "iface eth0 inet6 static\n" #| " address 2001:db8:1234:5::1:1\n" #| " netmask 64\n" #| " # Disabling auto-configuration\n" #| " # autoconf 0\n" #| " # The router is auto-configured and has no fixed address\n" #| " # (accept_ra 1). If it had:\n" #| " # gateway 2001:db8:1234:5::1" msgid "" "\n" "iface enp7s0 inet6 static\n" " address 2001:db8:1234:5::1:1/64\n" " # Disabling auto-configuration\n" " # autoconf 0\n" " # The router is auto-configured and has no fixed address\n" " # (accept_ra 1). If it had:\n" " # gateway 2001:db8:1234:5::1" msgstr "" "\n" "iface eth0 inet6 static\n" " address 2001:db8:1234:5::1:1\n" " netmask 64\n" " # Pour désactiver l'auto-configuration:\n" " # autoconf 0\n" " # Le routeur est auto-configuré et n'a pas d'adresse fixe.\n" " # (/proc/sys/net/ipv6/conf/all/accept_ra). Sinon pour le forcer:\n" " # gateway 2001:db8:1234:5::1" #, fuzzy #| msgid "SSL" msgid "SLAAC" msgstr "SSL" msgid "Stateless Address AutoconfigurationSLAAC" msgstr "" msgid "IPv6 subnets usually have a netmask of 64 bits. This means that 264 distinct addresses exist within the subnet. This allows Stateless Address Autoconfiguration (SLAAC) to pick an address based on the network interface's MAC address. By default, if SLAAC is activated in your network and IPv6 on your computer, the kernel will automatically find IPv6 routers and configure the network interfaces." msgstr "Les sous-réseaux IPv6 ont généralement un masque de 64 bits, ce qui autorise 264 adresses dans le sous-réseau. Cela permet l'autoconfiguration d'adresses sans état (Stateless Address Autoconfiguration ou SLAAC), qui choisit une adresse IPv6 à partir de l'adresse MAC de l'interface. Par défaut, si SLAAC est actif sur le réseau et IPv6 actif sur un ordinateur, le noyau va automatiquement trouver les routeurs IPv6 et configurer les interfaces." #, fuzzy #| msgid "ISC" msgid "MAC" msgstr "ISC" #, fuzzy #| msgid "IP addressprivate" msgid "IPv6privacy extensions" msgstr "adresse IPprivée" #, fuzzy #| msgid "This behavior may have privacy implications. If you switch networks frequently, e.g. with a laptop, you might not want your MAC address being a part of your public IPv6 address. This makes it easy to identify the same device across networks. A solution to this are IPv6 privacy extensions (which Debian enables by default if IPv6 connectivity is detected during initial installation), which will assign an additional randomly generated address to the interface, periodically change them and prefer them for outgoing connections. Incoming connections can still use the address generated by SLAAC. The following example, for use in /etc/network/interfaces, activates these privacy extensions." msgid "This behavior may have privacy implications. If you switch networks frequently, e.g. with a laptop, you might not want your MAC address being a part of your public IPv6 address. This makes it easy to identify the same device across networks. A solution to this are IPv6 privacy extensions (which Debian enables by default if IPv6 connectivity is detected during initial installation), which will assign an additional randomly generated address to the interface, periodically change them and prefer them for outgoing connections. Incoming connections can still use the address generated by SLAAC. The following example, for use in /etc/network/interfaces, activates these privacy extensions for the interface enp7s0." msgstr "Ce comportement a des implications en termes de fuites d'information. Lorsqu'on change fréquemment de réseau, par exemple avec un ordinateur portable, on ne souhaite pas forcément que l'adresse MAC fasse partie de l'adresse IPv6 publique, puisque cela permet d'identifier aisément le même ordinateur sur des réseaux différents. Ce problème se résout grâce à une extension d'IPv6 (que Debian active par défaut si une connexion IPv6 fonctionnelle est détectée à l'installation initiale), qui remplace cette adresse MAC par un composant aléatoire, qui renouvelle ce composant de manière régulière et qui utilise l'adresse résultante pour les connexions sortantes. Les connexions entrantes peuvent continuer d'utiliser les adresses générées par SLAAC. L'exemple qui suit, à insérer dans /etc/network/interfaces, active cette extension." msgid "IPv6 privacy extensions" msgstr "Extension d'IPv6 pour la protection des données personnelles" #, fuzzy #| msgid "" #| "\n" #| "iface eth0 inet6 auto\n" #| " # Prefer the randomly assigned addresses for outgoing connections.\n" #| " privext 2" msgid "" "\n" "iface enp7s0 inet6 auto\n" " # Prefer the randomly assigned addresses for outgoing connections.\n" " privext 2" msgstr "" "\n" "iface eth0 inet6 auto\n" " # Préférer l'adresse générée aléatoirement pour les connexions sortantes\n" " privext 2" msgid "TIP Programs built with IPv6" msgstr "ASTUCE Programmes compilés avec IPv6" #, fuzzy #| msgid "zonereverse" msgid "mailing listsdebian-ipv6@lists.debian.org" msgstr "zoneinverse" #, fuzzy #| msgid "Many pieces of software need to be adapted to handle IPv6. Most of the packages in Debian have been adapted already, but not all. If your favorite package does not work with IPv6 yet, you can ask for help on the debian-ipv6 mailing-list. They might know about an IPv6-aware replacement and could file a bug to get the issue properly tracked. " msgid "Many pieces of software need to be adapted to handle IPv6. Most of the packages in Debian have been adapted already, but not all. If your favorite package does not work with IPv6 yet, you can ask for help on the debian-ipv6 mailing-list. They might know about an IPv6-aware replacement and could file a bug to get the issue properly tracked. " msgstr "De nombreux logiciels ont besoin d'être adaptés à IPv6. La plupart des paquets de Debian l'ont déjà été, mais il reste des exceptions. Si votre paquet favori ne fonctionne pas encore avec IPv6, vous pouvez demander de l'aide sur la liste de diffusion debian-ipv6. Les abonnés de cette liste pourront selon les cas vous suggérer un substitut qui prend en charge IPv6 ou vous aider à soumettre un rapport de bogue pour que le problème soit correctement référencé. " #, fuzzy #| msgid "DNSzone" msgid "IPv6firewall" msgstr "DNSzone" msgid "firewallIPv6" msgstr "IPv6pare-feu" msgid "ip6tables" msgstr "ip6tables" msgid "IPv6 connections can be restricted, in the same fashion as for IPv4. nft can be used to create firewall rules for IPv4 and IPv6 (see )." msgstr "" msgid "Tunneling" msgstr "Tunnel" #, fuzzy #| msgid "DNSzone" msgid "IPv6tunneling" msgstr "DNSzone" msgid "CAUTION IPv6 tunneling and firewalls" msgstr "ATTENTION Tunnels IPv6 et pare-feu" #, fuzzy #| msgid "DNSzone" msgid "IPv6tunnel broker" msgstr "DNSzone" msgid "IPv6 tunneling over IPv4 (as opposed to native IPv6) requires the firewall to accept the traffic, which uses IPv4 protocol number 41." msgstr "Le transport d'IPv6 dans un tunnel IPv4 (par opposition à l'IPv6 natif) a besoin que le pare-feu laisse passer le trafic utilisant le protocole IPv4 numéro 41." #, fuzzy #| msgid "If a native IPv6 connection is not available, the fallback method is to use a tunnel over IPv4. Gogo6 is one (free) provider of such tunnels: " msgid "If a native IPv6 connection is not available, the fallback method is to use a tunnel over IPv4. Hurricane Electric is one (free) provider of such tunnels: " msgstr "En l'absence d'une connexion native en IPv6, on peut toujours s'y connecter via un tunnel sur IPv4. Gogo6 est un fournisseur gratuit de tels tunnels : " #, fuzzy #| msgid "Source NAT" msgid "Hurricane Electric" msgstr "Source NAT" #, fuzzy #| msgid "router" msgid "tunnel broker" msgstr "routeur" msgid "To use a Hurricane Electric tunnel, you need to register an account, login, select a free tunnel and edit the file /etc/network/interfaces with the generated code." msgstr "" msgid "radvd" msgstr "radvd" #, fuzzy #| msgid "/etc/bind/named.conf" msgid "/etc/etc/radvd.conf" msgstr "/etc/bind/named.conf" #, fuzzy #| msgid "servername" msgid "serviceradvd.service" msgstr "serveurde noms" #, fuzzy #| msgid "The machine then becomes the access router for a subnet with a 56-bit prefix. Once the tunnel is aware of this change, the local network must be told about it; this implies installing the radvd daemon (from the similarly-named package). This IPv6 configuration daemon has a role similar to dhcpd in the IPv4 world." msgid "You can install and configure the radvd daemon (from the similarly-named package) if you want to use the configured computer as a router for a local network. This IPv6 configuration daemon has a role similar to dhcpd in the IPv4 world." msgstr "La machine est alors le routeur d'accès à un sous-réseau dont le préfixe fait 56 bits. Le tunnel désormais averti, il faut encore informer le réseau local de cette caractéristique en installant le démon radvd (du paquet éponyme). C'est un démon de configuration IPv6 jouant le même rôle que dhcpd pour le monde IPv4." #, fuzzy #| msgid "networkvirtual private" msgid "ipaddress" msgstr "réseauprivé virtuel" #, fuzzy #| msgid "The /etc/radvd.conf configuration file must then be created (see /usr/share/doc/radvd/examples/simple-radvd.conf as a starting point). In our case, the only required change is the prefix, which needs to be replaced with the one provided by Freenet6; it can be found in the output of the ifconfig command, in the block concerning the tun interface." msgid "The /etc/radvd.conf configuration file must then be created (see /usr/share/doc/radvd/examples/simple-radvd.conf as a starting point). In our case, the only required change is the prefix, which needs to be replaced with the one provided by Hurricane Electric; it can be found in the output of the ip a command, in the block concerning the he-ipv6 interface." msgstr "Il faut ensuite créer son fichier de configuration /etc/radvd.conf (par exemple en adaptant le fichier /usr/share/doc/radvd/examples/simple-radvd.conf). En l'occurrence, le seul changement nécessaire est le préfixe, qu'il faut remplacer par celui fourni par Freenet6 (que l'on retrouvera dans la sortie de la commande ifconfig dans le bloc relatif à l'interface tun)." #, fuzzy #| msgid "Then run service gogoc restart and service radvd start, and the IPv6 network should work." msgid "Then run systemctl start radvd. The IPv6 network should now work." msgstr "Après les commandes service gogoc restart et service radvd start, le réseau IPv6 sera enfin fonctionnel." msgid "Domain Name Servers (DNS)" msgstr "Serveur de noms (DNS)" msgid "DNS" msgstr "DNS" #, fuzzy #| msgid "zoneDNS" msgid "Domain Name ServiceDNS" msgstr "zoneDNS" msgid "servername" msgstr "serveurde noms" #, fuzzy #| msgid "NetworkAddress Translation" msgid "IPaddress mapping" msgstr "NetworkAddress Translation" #, fuzzy #| msgid "The Domain Name Service (DNS) is a fundamental component of the Internet: it maps host names to IP addresses (and vice-versa), which allows the use of www.debian.org instead of 5.153.231.4 or 2001:41c8:1000:21::21:4." msgid "The Domain Name Service (DNS) is a fundamental component of the Internet: it maps host names to IP addresses (and vice-versa), which allows the use of www.debian.org instead of 130.89.148.77 or 2001:67c:2564:a119::77." msgstr "Le service de gestion des noms (Domain Name Service) est fondamental sur Internet : il associe des noms à des adresses IP (et vice versa), ce qui permet de saisir france.debian.net en lieu et place de 92.243.16.27." msgid "DNS records are organized in zones; each zone matches either a domain (or a subdomain) or an IP address range (since IP addresses are generally allocated in consecutive ranges). A primary server is authoritative on the contents of a zone; secondary servers, usually hosted on separate machines, provide regularly refreshed copies of the primary zone." msgstr "Les informations DNS sont regroupées par zones, correspondant chacune à un domaine ou à une plage d'adresses IP (les adresses IP sont généralement allouées par blocs d'adresses consécutives). Un serveur primaire fait autorité sur le contenu d'une zone ; un serveur secondaire, normalement hébergé sur une autre machine, se contente de proposer une copie de la zone primaire, qu'il met à jour régulièrement." msgid "zoneDNS" msgstr "zoneDNS" msgid "DNSzone" msgstr "DNSzone" #, fuzzy #| msgid "DNSzone" msgid "DNSresource record" msgstr "DNSzone" #, fuzzy #| msgid "Each zone can contain records of various kinds (Resource Records):" msgid "Each zone can contain records of various kinds (Resource Records), these are some of the most common:" msgstr "Chaque zone peut contenir différents types d'enregistrements (Resource Records):" msgid "A (address record): IPv4 address. This is the most common form to point a domain to an IPv4 address." msgstr "" #, fuzzy #| msgid "DNSzone" msgid "DNSresource recordA" msgstr "DNSzone" #, fuzzy #| msgid "CNAME: alias (canonical name). CNAME, DNS record" msgid "CNAME (canonical name record): alias" msgstr "CNAME : définition d'un alias. CNAME, enregistrement DNS" #, fuzzy #| msgid "DNSzone" msgid "DNSresource recordCNAME" msgstr "DNSzone" #, fuzzy #| msgid "MX: mail exchange, an email server. This information is used by other email servers to find where to send email addressed to a given address. Each MX record has a priority. The highest-priority server (with the lowest number) is tried first (see sidebar ); other servers are contacted in order of decreasing priority if the first one does not reply. MXDNS record" msgid "MX (mail exchange): an email server. This information is used by other email servers to find where to send email addressed to a given address. Each MX record has a priority. The highest-priority server (with the lowest number) is tried first (see sidebar ); other servers are contacted in order of decreasing priority if the first one does not reply." msgstr "MX : définition d'un serveur de courrier électronique, information exploitée par les serveurs de messagerie pour retrouver le serveur correspondant à l'adresse de destination d'un courrier électronique. Chaque enregistrement MX a une priorité associée. Le serveur de plus haute priorité (portant le nombre le plus petit) recevra les connexions SMTP (voir encadré ). S'il ne répond pas, le deuxième serveur sera contacté, etc. MXenregistrement DNS" #, fuzzy #| msgid "DNSzone" msgid "DNSresource recordMX" msgstr "DNSzone" #, fuzzy #| msgid "PTR: mapping of an IP address to a name. Such a record is stored in a “reverse DNS” zone named after the IP address range. For example, 1.168.192.in-addr.arpa is the zone containing the reverse mapping for all addresses in the 192.168.1.0/24 range. PTR, DNS record" msgid "PTR (pointer): mapping of an IP address to a name. Such a record is stored in a “reverse DNS” zone named after the IP address range. For example, 1.168.192.in-addr.arpa is the zone containing the reverse mapping for all addresses in the 192.168.1.0/24 range." msgstr "PTR : correspondance adresse IP vers nom. Elle est stockée dans une zone dédiée à la résolution inverse, nommée en fonction de la plage d'adresses IP : par exemple 1.168.192.in-addr.arpa pour toutes les adresses du réseau 192.168.1.0/24. PTR, enregistrement DNS" #, fuzzy #| msgid "DNSzone" msgid "DNSresource recordPTR" msgstr "DNSzone" msgid "AAAA (IPv6 address record): IPv6 address." msgstr "" #, fuzzy #| msgid "DNSzone" msgid "DNSresource recordAAAA" msgstr "DNSzone" #, fuzzy #| msgid "NS: maps a name to a name server. Each domain must have at least one NS record. These records point at a DNS server that can answer queries concerning this domain; they usually point at the primary and secondary servers for the domain. These records also allow DNS delegation; for instance, the falcot.com zone can include an NS record for internal.falcot.com, which means that the internal.falcot.com zone is handled by another server. Of course, this server must declare an internal.falcot.com zone. NS, DNS record" msgid "NS (name server): maps a name to a name server. Each domain must have at least one NS record. These records point at a DNS server that can answer queries concerning this domain; they usually point at the primary and secondary servers for the domain. These records also allow DNS delegation; for instance, the falcot.com zone can include an NS record for internal.falcot.com, which means that the internal.falcot.com zone is handled by another server. Of course, this server must declare an internal.falcot.com zone." msgstr "NS : correspondance nom vers serveur de noms. Chaque domaine doit compter au moins un enregistrement NS. Tous ces enregistrements pointent sur un serveur DNS capable de répondre aux requêtes portant sur ce domaine ; ils signaleront les serveurs primaires et secondaires du domaine concerné. Ces enregistrements permettent aussi de mettre en place une délégation DNS. On pourra ainsi indiquer que le domaine interne.falcot.com est géré par un autre serveur de noms et déléguer ainsi une partie du service. Évidemment, le serveur concerné devra déclarer une zone interne.falcot.com. NS, enregistrement DNS" #, fuzzy #| msgid "DNSzone" msgid "DNSresource recordNS" msgstr "DNSzone" msgid "DNS software" msgstr "" msgid "ISC" msgstr "ISC" #, fuzzy #| msgid "Internet Software Consortium" msgid "Internet Software ConsortiumISC" msgstr "Internet Software Consortium" msgid "bind9" msgstr "bind9" #, fuzzy #| msgid "zonereverse" msgid "DNSbind9bind" msgstr "zoneinverse" #, fuzzy #| msgid "The reference name server, Bind, was developed and is maintained by ISC (Internet Software Consortium). It is provided in Debian by the bind9 package. Version 9 brings two major changes compared to previous versions. First, the DNS server can now run under an unprivileged user, so that a security vulnerability in the server does not grant root privileges to the attacker (as was seen repeatedly with versions 8.x)." msgid "The reference name server, Bind, was developed and is maintained by ISC (the Internet Software Consortium). It is provided in Debian by the bind9 package. Version 9 brings two major changes compared to previous versions. First, the DNS server can now run under an unprivileged user, so that a security vulnerability in the server does not grant root privileges to the attacker (as was seen repeatedly with versions 8.x)." msgstr "Le logiciel serveur de noms de référence, Bind, est développé par l'ISC (Internet Software Consortium, ou consortium du logiciel Internet). Debian le fournit dans le paquet bind9. La version 9 apporte deux nouveautés majeures. Il est désormais possible d'employer le serveur DNS sous une identité utilisateur non privilégié de sorte qu'une faille de sécurité ne donne pas systématiquement les droits de root à l'attaquant, comme cela a souvent été le cas avec la version 8.x." msgid "Furthermore, Bind supports the DNSSEC standard for signing (and therefore authenticating) DNS records, which allows blocking any spoofing of this data during man-in-the-middle attacks." msgstr "Par ailleurs, elle prend en charge DNSSEC, norme qui permet de signer et donc d'authentifier les enregistrements DNS, interdisant ainsi toute falsification de ces données, par exemple par des intermédiaires malintentionnés." msgid "CULTURE DNSSEC" msgstr "CULTURE DNSSEC" msgid "DNSSEC" msgstr "DNSSEC" msgid "Domain Name System Security ExtensionsDNSSEC" msgstr "" #, fuzzy #| msgid "DNSzone" msgid "DNSsecurity extensionsDNSSEC" msgstr "DNSzone" #, fuzzy #| msgid "The DNSSEC norm is quite complex; this partly explains why it is not in widespread usage yet (even if it perfectly coexists with DNS servers unaware of DNSSEC). To understand all the ins and outs, you should check the following article. " msgid "The DNSSEC norm is quite complex; this partly explains why it is not in widespread usage yet (even if it perfectly coexists with DNS servers unaware of DNSSEC). To understand all the ins and outs, you should check the following article. " msgstr "La norme DNSSEC est assez complexe ; pour en comprendre tous les tenants et aboutissants, nous vous suggérons de consulter les informations disponibles sur le site du NIC France (organisme gérant l'attribution des domaines en .fr), et particulièrement les supports de cours. Il faut savoir que cette norme, encore relativement expérimentale, n'est pas systématiquement employée (même si elle coexiste parfaitement avec des serveurs DNS qui ne la connaissent pas). " #, fuzzy #| msgid "Configuring" msgid "Configuring bind" msgstr "Configuration" #, fuzzy #| msgid "zoneDNS" msgid "daemonbind" msgstr "zoneDNS" #, fuzzy #| msgid "recordDNS" msgid "serverDNS" msgstr "enregistrementDNS" #, fuzzy #| msgid "networkDHCP configuration" msgid "bindconfiguration" msgstr "réseauconfiguration DHCP" msgid "Configuration files for bind, irrespective of version, have the same structure." msgstr "Quelle que soit la version de bind employée, les fichiers de configuration ont la même structure." msgid "The Falcot administrators created a primary falcot.com zone to store information related to this domain, and a 168.192.in-addr.arpa zone for reverse mapping of IP addresses in the local networks." msgstr "Les administrateurs de Falcot ont créé une zone primaire falcot.com pour stocker les informations relatives à ce domaine et une zone 168.192.in-addr.arpa pour les résolutions inverses des adresses IP des différents réseaux locaux." msgid "CAUTION Names of reverse zones" msgstr "ATTENTION Noms des zones inverses" msgid "zonereverse" msgstr "zoneinverse" msgid "reverse zone" msgstr "inverse, zone" #, fuzzy #| msgid "DNSzone" msgid "DNSreverse zone" msgstr "DNSzone" msgid "in-addr.arpa" msgstr "in-addr.arpa" msgid "ip6.arpa" msgstr "ip6.arpa" msgid "nibble format" msgstr "nibble, format" msgid "Reverse zones have a particular name. The zone covering the 192.168.0.0/16 network needs to be named 168.192.in-addr.arpa: the IP address components are reversed, and followed by the in-addr.arpa suffix." msgstr "Une zone inverse porte un nom particulier. La zone couvrant le réseau 192.168.0.0/16 s'appellera ainsi 168.192.in-addr.arpa : les composants de l'adresse IP sont inversés et suivis du suffixe in-addr.arpa." msgid "For IPv6 networks, the suffix is ip6.arpa and the IP address components which are reversed are each character in the full hexadecimal representation of the IP address. As such, the 2001:0bc8:31a0::/48 network would use a zone named 0.a.1.3.8.c.b.0.1.0.0.2.ip6.arpa." msgstr "Pour les réseaux IPv6, le suffixe est ip6.arpa et les composants de l'adresse IP (qui sont listés dans l'ordre inverse) sont les caractères de la représentation hexadécimale complète de l'adresse. Ainsi, le réseau 2001:0bc8:31a0::/48 utilise une zone nommée 0.a.1.3.8.c.b.0.1.0.0.2.ip6.arpa." msgid "TIP Testing the DNS server" msgstr "ASTUCE Tester le serveur DNS" msgid "host" msgstr "host" msgid "The host command (in the bind9-host package) queries a DNS server, and can be used to test the server configuration. For example, host machine.falcot.com localhost checks the local server's reply for the machine.falcot.com query. host ipaddress localhost tests the reverse resolution." msgstr "La commande host (du paquet bind9-host) interroge un serveur DNS, par exemple celui qu'on vient de configurer. La commande host machine.falcot.com localhost contrôlera donc la réponse du serveur DNS local pour la requête machine.falcot.com. La commande host adresseip localhost testera la résolution inverse." #, fuzzy #| msgid "/etc/bind/named.conf" msgid "/etc/etc/bind/named.conf" msgstr "/etc/bind/named.conf" msgid "The following configuration excerpts, taken from the Falcot files, can serve as starting points to configure a DNS server:" msgstr "On pourra configurer un serveur DNS en s'inspirant des extraits suivants, issus des fichiers de configuration de la société Falcot:" msgid "Excerpt of /etc/bind/named.conf.local" msgstr "Extrait du fichier /etc/bind/named.conf.local" msgid "" "\n" "zone \"falcot.com\" {\n" " type master;\n" " file \"/etc/bind/db.falcot.com\";\n" " allow-query { any; };\n" " allow-transfer {\n" " 195.20.105.149/32 ; // ns0.xname.org\n" " 193.23.158.13/32 ; // ns1.xname.org\n" " };\n" "};\n" "\n" "zone \"internal.falcot.com\" {\n" " type master;\n" " file \"/etc/bind/db.internal.falcot.com\";\n" " allow-query { 192.168.0.0/16; };\n" "};\n" "\n" "zone \"168.192.in-addr.arpa\" {\n" " type master;\n" " file \"/etc/bind/db.192.168\";\n" " allow-query { 192.168.0.0/16; };\n" "};" msgstr "" "\n" "zone \"falcot.com\" {\n" " type master;\n" " file \"/etc/bind/db.falcot.com\";\n" " allow-query { any; };\n" " allow-transfer {\n" " 195.20.105.149/32 ; // ns0.xname.org\n" " 193.23.158.13/32 ; // ns1.xname.org\n" " };\n" "};\n" "\n" "zone \"interne.falcot.com\" {\n" " type master;\n" " file \"/etc/bind/db.interne.falcot.com\";\n" " allow-query { 192.168.0.0/16; };\n" "};\n" "\n" "zone \"168.192.in-addr.arpa\" {\n" " type master;\n" " file \"/etc/bind/db.192.168\";\n" " allow-query { 192.168.0.0/16; };\n" "};" msgid "Excerpt of /etc/bind/db.falcot.com" msgstr "Extrait du fichier /etc/bind/db.falcot.com" msgid "" "; falcot.com Zone \n" "; admin.falcot.com. => zone contact: admin@falcot.com\n" "$TTL 604800\n" "@ IN SOA falcot.com. admin.falcot.com. (\n" " 20040121 ; Serial\n" " 604800 ; Refresh\n" " 86400 ; Retry\n" " 2419200 ; Expire\n" " 604800 ) ; Negative Cache TTL\n" ";\n" "; The @ refers to the zone name (\"falcot.com\" here)\n" "; or to $ORIGIN if that directive has been used\n" ";\n" "@ IN NS ns\n" "@ IN NS ns0.xname.org.\n" "\n" "internal IN NS 192.168.0.2\n" "\n" "@ IN A 212.94.201.10\n" "@ IN MX 5 mail\n" "@ IN MX 10 mail2\n" "\n" "ns IN A 212.94.201.10\n" "mail IN A 212.94.201.10\n" "mail2 IN A 212.94.201.11\n" "www IN A 212.94.201.11\n" "\n" "dns IN CNAME ns" msgstr "" "; Zone falcot.com\n" "; admin.falcot.com. => contact pour la zone: admin@falcot.com\n" "$TTL 604800\n" "@ IN SOA falcot.com. admin.falcot.com. (\n" " 20040121 ; Serial\n" " 604800 ; Refresh\n" " 86400 ; Retry\n" " 2419200 ; Expire\n" " 604800 ) ; Negative Cache TTL\n" ";\n" "; Le @ fait référence au nom de la zone («falcot.com.» en l'occurrence)\n" "; ou à $ORIGIN si cette directive a été employée\n" ";\n" "@ IN NS ns\n" "@ IN NS ns0.xname.org.\n" "\n" "interne IN NS 192.168.0.2\n" "\n" "@ IN A 212.94.201.10\n" "@ IN MX 5 mail\n" "@ IN MX 10 mail2\n" "\n" "ns IN A 212.94.201.10\n" "mail IN A 212.94.201.10\n" "mail2 IN A 212.94.201.11\n" "www IN A 212.94.201.11\n" "\n" "dns IN CNAME ns" msgid "CAUTION Syntax of a name" msgstr "ATTENTION Syntaxe d'un nom" msgid "The syntax of machine names follows strict rules. For instance, machine implies machine.domain. If the domain name should not be appended to a name, said name must be written as machine. (with a dot as suffix). Indicating a DNS name outside the current domain therefore requires a syntax such as machine.otherdomain.com. (with the final dot)." msgstr "La syntaxe désignant les noms de machines est particulière. machine sous-entend ainsi machine.domaine. S'il ne faut pas ajouter automatiquement le nom du domaine, il convient d'écrire machine. (en suffixant ce nom d'un point). Pour indiquer un nom DNS extérieur au domaine géré, on écrira donc machine.autredomaine.com. avec un point." msgid "Excerpt of /etc/bind/db.192.168" msgstr "Extrait du fichier /etc/bind/db.192.168" msgid "" "; Reverse zone for 192.168.0.0/16\n" "; admin.falcot.com. => zone contact: admin@falcot.com\n" "$TTL 604800\n" "@ IN SOA ns.internal.falcot.com. admin.falcot.com. (\n" " 20040121 ; Serial\n" " 604800 ; Refresh\n" " 86400 ; Retry\n" " 2419200 ; Expire\n" " 604800 ) ; Negative Cache TTL\n" "\n" " IN NS ns.internal.falcot.com.\n" "\n" "; 192.168.0.1 -> arrakis\n" "1.0 IN PTR arrakis.internal.falcot.com.\n" "; 192.168.0.2 -> neptune\n" "2.0 IN PTR neptune.internal.falcot.com.\n" "\n" "; 192.168.3.1 -> pau\n" "1.3 IN PTR pau.internal.falcot.com." msgstr "" "; Zone inverse pour 192.168.0.0/16\n" "; admin.falcot.com. => contact pour la zone: admin@falcot.com\n" "$TTL 604800\n" "@ IN SOA ns.interne.falcot.com. admin.falcot.com. (\n" " 20040121 ; Serial\n" " 604800 ; Refresh\n" " 86400 ; Retry\n" " 2419200 ; Expire\n" " 604800 ) ; Negative Cache TTL\n" "\n" " IN NS ns.interne.falcot.com.\n" "\n" "; 192.168.0.1 -> arrakis\n" "1.0 IN PTR arrakis.interne.falcot.com.\n" "; 192.168.0.2 -> neptune\n" "2.0 IN PTR neptune.interne.falcot.com.\n" "\n" "; 192.168.3.1 -> pau\n" "1.3 IN PTR pau.interne.falcot.com." #, fuzzy #| msgid "Dynamic Host Configuration Protocol" msgid "DHCPDynamic Host Configuration Protocol" msgstr "Dynamic Host Configuration Protocol" #, fuzzy #| msgid "Dynamic Host Configuration Protocol" msgid "Dynamic Host Configuration ProtocolDHCP" msgstr "Dynamic Host Configuration Protocol" msgid "networkDHCP configuration" msgstr "réseauconfiguration DHCP" #, fuzzy #| msgid "bind9" msgid "isc-dhcp-server" msgstr "bind9" msgid "DHCP (for Dynamic Host Configuration Protocol) is a protocol by which a machine can automatically get its network configuration when it boots. This allows centralizing the management of network configurations, and ensuring that all desktop machines get similar settings." msgstr "DHCP (Dynamic Host Configuration Protocol, ou protocole de configuration dynamique des hôtes) est un moyen de rapatrier automatiquement sa configuration pour une machine qui vient de démarrer et souhaite configurer son interface réseau. De cette manière, on peut centraliser la gestion des configurations réseau et toutes les machines bureautiques pourront recevoir des réglages identiques." msgid "A DHCP server provides many network-related parameters. The most common of these is an IP address and the network where the machine belongs, but it can also provide other information, such as DNS servers, WINS servers, NTP servers, and so on." msgstr "Un serveur DHCP fournit de nombreux paramètres réseau et notamment une adresse IP et le réseau d'appartenance de la machine. Mais il peut aussi indiquer d'autres informations, telles que les serveurs DNS, WINS et NTP." msgid "The Internet Software Consortium (also involved in developing bind) is the main author of the DHCP server. The matching Debian package is isc-dhcp-server." msgstr "L'Internet Software Consortium, qui développe bind, s'occupe également du serveur DHCP. Le paquet Debian correspondant est isc-dhcp-server." msgid "Configuring" msgstr "Configuration" #, fuzzy #| msgid "DNSzone" msgid "DHCP" msgstr "DNSzone" #, fuzzy #| msgid "servername" msgid "serverDHCP" msgstr "serveurde noms" #, fuzzy #| msgid "zoneDNS" msgid "daemondhcpd" msgstr "zoneDNS" #, fuzzy #| msgid "/etc/bind/named.conf" msgid "/etc/etc/dhcp/dhcpd.conf" msgstr "/etc/bind/named.conf" #, fuzzy #| msgid "/etc/bind/named.conf" msgid "/etc/etc/dhcp/dhcpd6.conf" msgstr "/etc/bind/named.conf" #, fuzzy #| msgid "The first elements that need to be edited in the DHCP server configuration file (/etc/dhcp/dhcpd.conf) are the domain name and the DNS servers. If this server is alone on the local network (as defined by the broadcast propagation), the authoritative directive must also be enabled (or uncommented). One also needs to create a subnet section describing the local network and the configuration information to be provided. The following example fits a 192.168.0.0/24 local network with a router at 192.168.0.1 serving as the gateway. Available IP addresses are in the range 192.168.0.128 to 192.168.0.254." msgid "The first elements that need to be edited in the DHCP server configuration files (/etc/dhcp/dhcpd.conf, and /etc/dhcp/dhcpd6.conf for IPv6) are the domain name and the DNS servers. If this server is alone on the local network (as defined by the broadcast propagation), the authoritative directive must also be enabled (or uncommented). One also needs to create a subnet section describing the local network and the configuration information to be provided. The following example fits a 192.168.0.0/24 local network with a router at 192.168.0.1 serving as the gateway. Available IP addresses are in the range 192.168.0.128 to 192.168.0.254." msgstr "Les premiers éléments à modifier dans le fichier de configuration du serveur DHCP, /etc/dhcp/dhcpd.conf, sont le nom de domaine et les serveurs DNS. Il faut aussi activer (en la décommentant) l'option authoritative si ce serveur est le seul sur le réseau local (tel que défini par la limite de propagation du broadcast, mécanisme employé pour joindre le serveur DHCP). On créera aussi une section subnet décrivant le réseau local et les informations de configuration diffusées. L'exemple ci-dessous convient pour le réseau local 192.168.0.0/24, qui dispose d'un routeur (192.168.0.1) faisant office de passerelle externe. Les adresses IP disponibles sont comprises entre 192.168.0.128 et 192.168.0.254." msgid "Excerpt of /etc/dhcp/dhcpd.conf" msgstr "Extrait du fichier /etc/dhcp/dhcpd.conf" msgid "" "\n" "#\n" "# Sample configuration file for ISC dhcpd for Debian\n" "#\n" "\n" "# The ddns-updates-style parameter controls whether or not the server will\n" "# attempt to do a DNS update when a lease is confirmed. We default to the\n" "# behavior of the version 2 packages ('none', since DHCP v2 didn't\n" "# have support for DDNS.)\n" "ddns-update-style interim;\n" "\n" "# option definitions common to all supported networks...\n" "option domain-name \"internal.falcot.com\";\n" "option domain-name-servers ns.internal.falcot.com;\n" "\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "\n" "# If this DHCP server is the official DHCP server for the local\n" "# network, the authoritative directive should be uncommented.\n" "authoritative;\n" "\n" "# Use this to send dhcp log messages to a different log file (you also\n" "# have to hack syslog.conf to complete the redirection).\n" "log-facility local7;\n" "\n" "# My subnet\n" "subnet 192.168.0.0 netmask 255.255.255.0 {\n" " option routers 192.168.0.1;\n" " option broadcast-address 192.168.0.255;\n" " range 192.168.0.128 192.168.0.254;\n" " ddns-domainname \"internal.falcot.com\";\n" "}" msgstr "" "\n" "#\n" "# Sample configuration file for ISC dhcpd for Debian\n" "#\n" "\n" "# The ddns-updates-style parameter controls whether or not the server will\n" "# attempt to do a DNS update when a lease is confirmed. We default to the\n" "# behavior of the version 2 packages ('none', since DHCP v2 didn't\n" "# have support for DDNS.)\n" "ddns-update-style interim;\n" "\n" "# option definitions common to all supported networks...\n" "option domain-name \"interne.falcot.com\";\n" "option domain-name-servers ns.interne.falcot.com;\n" "\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "\n" "# If this DHCP server is the official DHCP server for the local\n" "# network, the authoritative directive should be uncommented.\n" "authoritative;\n" "\n" "# Use this to send dhcp log messages to a different log file (you also\n" "# have to hack syslog.conf to complete the redirection).\n" "log-facility local7;\n" "\n" "# My subnet\n" "subnet 192.168.0.0 netmask 255.255.255.0 {\n" " option routers 192.168.0.1;\n" " option broadcast-address 192.168.0.255;\n" " range 192.168.0.128 192.168.0.254;\n" " ddns-domainname \"interne.falcot.com\";\n" "}" msgid "DHCP and DNS" msgstr "DHCP et DNS" msgid "DNSautomated updates" msgstr "DNSmise à jour automatique" #, fuzzy #| msgid "ripngd" msgid "bind" msgstr "ripngd" msgid "A nice feature is the automated registering of DHCP clients in the DNS zone, so that each machine gets a significant name (rather than something impersonal such as machine-192-168-0-131.internal.falcot.com). Using this feature requires configuring the DNS server to accept updates to the internal.falcot.com DNS zone from the DHCP server, and configuring the latter to submit updates for each registration." msgstr "Une fonctionnalité appréciée est l'enregistrement automatique des clients DHCP dans la zone DNS de sorte que chaque machine ait un nom significatif (et pas automatique comme machine-192-168-0-131.interne.falcot.com). Pour exploiter cette possibilité, il faut autoriser le serveur DHCP à mettre à jour la zone DNS interne.falcot.com et configurer celui-ci pour qu'il s'en charge." #, fuzzy #| msgid "In the bind case, the allow-update directive needs to be added to each of the zones that the DHCP server is to edit (the one for the internal.falcot.com domain, and the reverse zone). This directive lists the IP addresses allowed to perform these updates; it should therefore contain the possible addresses of the DHCP server (both the local address and the public address, if appropriate)." msgid "In the bind case (see ), the allow-update directive needs to be added to each of the zones that the DHCP server is to edit (the one for the internal.falcot.com domain, and the reverse zone). This directive lists the IP addresses allowed to perform these updates; it should therefore contain the possible addresses of the DHCP server (both the local address and the public address, if appropriate)." msgstr "Dans le cas de bind, on ajoutera la directive allow-update aux deux zones que le serveur DHCP devra modifier (celle du domaine interne.falcot.com et celle de la résolution inverse). Cette directive donne la liste des adresses autorisées à effectuer la mise à jour ; on y consignera donc les adresses possibles du serveur DHCP (adresses IP locales et publiques le cas échéant)." msgid "" "\n" "allow-update { 127.0.0.1 192.168.0.1 212.94.201.10 !any };" msgstr "" "\n" "allow-update { 127.0.0.1 192.168.0.1 212.94.201.10 !any };" msgid "Beware! A zone that can be modified will be changed by bind, and the latter will overwrite its configuration files at regular intervals. Since this automated procedure produces files that are less human-readable than manually-written ones, the Falcot administrators handle the internal.falcot.com domain with a delegated DNS server; this means the falcot.com zone file stays firmly under their manual control." msgstr "Attention ! Une zone modifiable sera changée par bind, qui va donc réécrire régulièrement ses fichiers de configuration. Cette procédure automatique produisant des fichiers moins lisibles que les productions manuelles, les administrateurs de Falcot gèrent le sous-domaine interne.falcot.com à l'aide d'un serveur DNS délégué. Le fichier de la zone falcot.com reste ainsi entièrement sous leur contrôle." #, fuzzy #| msgid "The DHCP server configuration excerpt above already includes the directives required for DNS zone updates: they are the ddns-update-style interim; and ddns-domain-name \"internal.falcot.com\"; lines in the block describing the subnet." msgid "The DHCP server configuration excerpt above already includes the directives required for DNS zone updates: they are the ddns-update-style interim; and ddns-domain-name \"internal.falcot.com\"; lines." msgstr "L'exemple de fichier de configuration de serveur DHCP de la section précédente comporte déjà les directives nécessaires à l'activation de la mise à jour du DNS : il s'agit des lignes ddns-update-style interim ; et ddns-domain-name \"interne.falcot.com\"; dans le bloc décrivant le réseau." msgid "Network Diagnosis Tools" msgstr "Outils de diagnostic réseau" #, fuzzy #| msgid "networkgateway" msgid "networkdiagnosis" msgstr "réseaupasserelle" #, fuzzy #| msgid "When a network application does not run as expected, it is important to be able to look under the hood. Even when everything seems to run smoothly, running a network diagnosis can help ensure everything is working as it should. Several diagnosis tools exists for this purpose; each one operates on a different level." msgid "When a network application does not run as expected, it is important to be able to look under the hood. Even when everything seems to run smoothly, running a network diagnosis can help ensure everything is working as it should. Several diagnosis tools exists for this purpose; each one operates on a different level. It would go beyond the scope of this book to discuss all tools, so we will focus on the more well-known and commonly used tools in the following sections." msgstr "Lorsqu'une application réseau ne fonctionne pas comme on l'attend, il est important de pouvoir regarder de plus près ce qui se passe. Même lorsque tout semble fonctionner, il est utile de lancer des diagnostics sur le réseau, pour vérifier qu'il n'y a rien d'anormal. On dispose pour cela de plusieurs outils de diagnostic, qui opèrent à divers niveaux." msgid "Local Diagnosis: netstat" msgstr "Diagnostic local : netstat" msgid "netstat" msgstr "netstat" msgid "Let's first mention the netstat command (in the net-tools package); it displays an instant summary of a machine's network activity. When invoked with no argument, this command lists all open connections; this list can be very verbose since it includes many Unix-domain sockets (widely used by daemons) which do not involve the network at all (for example, dbus communication, X11 traffic, and communications between virtual filesystems and the desktop)." msgstr "Citons tout d'abord la commande netstat (du paquet net-tools), qui affiche sur une machine un résumé instantané de son activité réseau. Invoquée sans arguments, cette commande se contente de lister toutes les connexions ouvertes. Or, cette liste est très vite verbeuse et indigeste. En effet, elle inclut aussi les connexions en domaine Unix, qui ne passent pas par le réseau mais sont très nombreuses sur un système standard, car utilisées par un grand nombre de démons." msgid "Common invocations therefore use options that alter netstat's behavior. The most frequently used options include:" msgstr "On utilise donc généralement des options, qui permettent de modifier le comportement de netstat. Parmi les options les plus courantes, on trouve :" msgid "-t, which filters the results to only include TCP connections;" msgstr "-t, qui filtre les résultats renvoyés pour que seules les connexions TCP soient listées ;" msgid "-u, which works similarly for UDP connections; these options are not mutually exclusive, and one of them is enough to stop displaying Unix-domain connections;" msgstr "-u, qui fonctionne de la même manière mais pour les connexions UDP ; ces deux options ne s'excluent pas mutuellement et la présence des deux aura pour seul effet visible de masquer les connexions du domaine Unix ;" msgid "-a, to also list listening sockets (waiting for incoming connections);" msgstr "-a, qui liste également les sockets en écoute (en attente de connexions entrantes) ;" msgid "-n, to display the results numerically: IP addresses (no DNS resolution), port numbers (no aliases as defined in /etc/services) and user ids (no login names);" msgstr "-n, qui affiche sous forme numérique les adresses IP (sans résolution DNS), les numéros de ports (et non leur alias tel que défini dans /etc/services) et les numéros d'utilisateurs (et non leur nom de connexion) ;" msgid "-p, to list the processes involved; this option is only useful when netstat is run as root, since normal users will only see their own processes;" msgstr "-p, qui affiche les processus mis en jeu ; cette option n'est réellement utile que lorsque netstat est invoqué par l'utilisateur root, faute de quoi seuls les processus appartenant au même utilisateur seront listés ;" msgid "-c, to continuously refresh the list of connections." msgstr "-c, qui rafraîchit la liste des connexions en continu." msgid "Other options, documented in the netstat 8 manual page, provide an even finer control over the displayed results. In practice, the first five options are so often used together that systems and network administrators practically acquired netstat -tupan as a reflex. Typical results, on a lightly loaded machine, may look like the following:" msgstr "D'autres options (documentées dans la page de manuel netstat 8) permettent de contrôler encore plus finement les résultats obtenus ; en pratique, on utilise si souvent la conjonction des cinq premières options que la commande netstat -tupan est quasiment devenue un réflexe chez les administrateurs systèmes et réseaux. Un résultat typique sur une machine peu active ressemble à ceci :" msgid "" "\n" "# netstat -tupan\n" "Active Internet connections (servers and established)\n" "Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name\n" "tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 397/rpcbind \n" "tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 431/sshd \n" "tcp 0 0 0.0.0.0:36568 0.0.0.0:* LISTEN 407/rpc.statd \n" "tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 762/exim4 \n" "tcp 0 272 192.168.1.242:22 192.168.1.129:44452 ESTABLISHED 1172/sshd: roland [\n" "tcp6 0 0 :::111 :::* LISTEN 397/rpcbind \n" "tcp6 0 0 :::22 :::* LISTEN 431/sshd \n" "tcp6 0 0 ::1:25 :::* LISTEN 762/exim4 \n" "tcp6 0 0 :::35210 :::* LISTEN 407/rpc.statd \n" "udp 0 0 0.0.0.0:39376 0.0.0.0:* 916/dhclient \n" "udp 0 0 0.0.0.0:996 0.0.0.0:* 397/rpcbind \n" "udp 0 0 127.0.0.1:1007 0.0.0.0:* 407/rpc.statd \n" "udp 0 0 0.0.0.0:68 0.0.0.0:* 916/dhclient \n" "udp 0 0 0.0.0.0:48720 0.0.0.0:* 451/avahi-daemon: r\n" "udp 0 0 0.0.0.0:111 0.0.0.0:* 397/rpcbind \n" "udp 0 0 192.168.1.242:123 0.0.0.0:* 539/ntpd \n" "udp 0 0 127.0.0.1:123 0.0.0.0:* 539/ntpd \n" "udp 0 0 0.0.0.0:123 0.0.0.0:* 539/ntpd \n" "udp 0 0 0.0.0.0:5353 0.0.0.0:* 451/avahi-daemon: r\n" "udp 0 0 0.0.0.0:39172 0.0.0.0:* 407/rpc.statd \n" "udp6 0 0 :::996 :::* 397/rpcbind \n" "udp6 0 0 :::34277 :::* 407/rpc.statd \n" "udp6 0 0 :::54852 :::* 916/dhclient \n" "udp6 0 0 :::111 :::* 397/rpcbind \n" "udp6 0 0 :::38007 :::* 451/avahi-daemon: r\n" "udp6 0 0 fe80::5054:ff:fe99::123 :::* 539/ntpd \n" "udp6 0 0 2001:bc8:3a7e:210:a:123 :::* 539/ntpd \n" "udp6 0 0 2001:bc8:3a7e:210:5:123 :::* 539/ntpd \n" "udp6 0 0 ::1:123 :::* 539/ntpd \n" "udp6 0 0 :::123 :::* 539/ntpd \n" "udp6 0 0 :::5353 :::* 451/avahi-daemon: r\n" "" msgstr "" "\n" "# netstat -tupan\n" "Connexions Internet actives (serveurs et établies)\n" "Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name\n" "tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 397/rpcbind \n" "tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 431/sshd \n" "tcp 0 0 0.0.0.0:36568 0.0.0.0:* LISTEN 407/rpc.statd \n" "tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 762/exim4 \n" "tcp 0 272 192.168.1.242:22 192.168.1.129:44452 ESTABLISHED 1172/sshd: roland [\n" "tcp6 0 0 :::111 :::* LISTEN 397/rpcbind \n" "tcp6 0 0 :::22 :::* LISTEN 431/sshd \n" "tcp6 0 0 ::1:25 :::* LISTEN 762/exim4 \n" "tcp6 0 0 :::35210 :::* LISTEN 407/rpc.statd \n" "udp 0 0 0.0.0.0:39376 0.0.0.0:* 916/dhclient \n" "udp 0 0 0.0.0.0:996 0.0.0.0:* 397/rpcbind \n" "udp 0 0 127.0.0.1:1007 0.0.0.0:* 407/rpc.statd \n" "udp 0 0 0.0.0.0:68 0.0.0.0:* 916/dhclient \n" "udp 0 0 0.0.0.0:48720 0.0.0.0:* 451/avahi-daemon: r\n" "udp 0 0 0.0.0.0:111 0.0.0.0:* 397/rpcbind \n" "udp 0 0 192.168.1.242:123 0.0.0.0:* 539/ntpd \n" "udp 0 0 127.0.0.1:123 0.0.0.0:* 539/ntpd \n" "udp 0 0 0.0.0.0:123 0.0.0.0:* 539/ntpd \n" "udp 0 0 0.0.0.0:5353 0.0.0.0:* 451/avahi-daemon: r\n" "udp 0 0 0.0.0.0:39172 0.0.0.0:* 407/rpc.statd \n" "udp6 0 0 :::996 :::* 397/rpcbind \n" "udp6 0 0 :::34277 :::* 407/rpc.statd \n" "udp6 0 0 :::54852 :::* 916/dhclient \n" "udp6 0 0 :::111 :::* 397/rpcbind \n" "udp6 0 0 :::38007 :::* 451/avahi-daemon: r\n" "udp6 0 0 fe80::5054:ff:fe99::123 :::* 539/ntpd \n" "udp6 0 0 2001:bc8:3a7e:210:a:123 :::* 539/ntpd \n" "udp6 0 0 2001:bc8:3a7e:210:5:123 :::* 539/ntpd \n" "udp6 0 0 ::1:123 :::* 539/ntpd \n" "udp6 0 0 :::123 :::* 539/ntpd \n" "udp6 0 0 :::5353 :::* 451/avahi-daemon: r\n" "" msgid "As expected, this lists established connections, two SSH connections in this case, and applications waiting for incoming connections (listed as LISTEN), notably the Exim4 email server listening on port 25." msgstr "On y retrouve bien les connexions établies (ESTABLISHED), ici deux connexions SSH, et les applications en attente de connexion (LISTEN), notamment le serveur de messagerie Exim4 sur le port 25." msgid "Remote Diagnosis: nmap" msgstr "Diagnostic distant : nmap" msgid "nmap" msgstr "nmap" msgid "nmap (in the similarly-named package) is, in a way, the remote equivalent for netstat. It can scan a set of “well-known” ports for one or several remote servers, and list the ports where an application is found to answer to incoming connections. Furthermore, nmap is able to identify some of these applications, sometimes even their version number. The counterpart of this tool is that, since it runs remotely, it cannot provide information on processes or users; however, it can operate on several targets at once." msgstr "nmap (du paquet éponyme) est en quelque sorte l'équivalent de netstat, mais s'utilise à distance. Il permet en effet de balayer un ensemble de ports classiques d'un ou plusieurs serveurs distants et de lister parmi ces ports ceux sur lesquels une application répond aux connexions entrantes. nmap est en outre capable d'identifier certaines de ces applications, parfois avec la version correspondante. La contrepartie de cet outil est que, comme il fonctionne à distance, il ne peut pas lister les connexions établies ni obtenir d'information sur les processus ou les utilisateurs ; en revanche, on peut le lancer sur plusieurs cibles en même temps." msgid "A typical nmap invocation only uses the -A option (so that nmap attempts to identify the versions of the server software it finds) followed by one or more IP addresses or DNS names of machines to scan. Again, many more options exist to finely control the behavior of nmap; please refer to the documentation in the nmap 1 manual page." msgstr "Une utilisation typique de nmap utilise simplement l'option -A, qui déclenche les tentatives d'identification des versions des logiciels serveurs, suivie d'une ou plusieurs adresses ou noms DNS de machines à tester. Ici encore, de nombreuses options existent et permettent de contrôler finement le comportement de nmap ; on se référera à la documentation, dans la page de manuel nmap 1 ." #, fuzzy #| msgid "" #| "\n" #| "# nmap mirtuel\n" #| "\n" #| "Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-09 16:46 CET\n" #| "Nmap scan report for mirtuel (192.168.1.242)\n" #| "Host is up (0.000013s latency).\n" #| "rDNS record for 192.168.1.242: mirtuel.internal.placard.fr.eu.org\n" #| "Not shown: 998 closed ports\n" #| "PORT STATE SERVICE\n" #| "22/tcp open ssh\n" #| "111/tcp open rpcbind\n" #| "\n" #| "Nmap done: 1 IP address (1 host up) scanned in 2.41 seconds\n" #| "# nmap -A localhost\n" #| "\n" #| "Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-09 16:46 CET\n" #| "Nmap scan report for localhost (127.0.0.1)\n" #| "Host is up (0.000013s latency).\n" #| "Other addresses for localhost (not scanned): 127.0.0.1\n" #| "Not shown: 997 closed ports\n" #| "PORT STATE SERVICE VERSION\n" #| "22/tcp open ssh OpenSSH 6.7p1 Debian 3 (protocol 2.0)\n" #| "|_ssh-hostkey: ERROR: Script execution failed (use -d to debug)\n" #| "25/tcp open smtp Exim smtpd 4.84\n" #| "| smtp-commands: mirtuel Hello localhost [127.0.0.1], SIZE 52428800, 8BITMIME, PIPELINING, HELP, \n" #| "|_ Commands supported: AUTH HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP \n" #| "111/tcp open rpcbind 2-4 (RPC #100000)\n" #| "| rpcinfo: \n" #| "| program version port/proto service\n" #| "| 100000 2,3,4 111/tcp rpcbind\n" #| "| 100000 2,3,4 111/udp rpcbind\n" #| "| 100024 1 36568/tcp status\n" #| "|_ 100024 1 39172/udp status\n" #| "Device type: general purpose\n" #| "Running: Linux 3.X\n" #| "OS CPE: cpe:/o:linux:linux_kernel:3\n" #| "OS details: Linux 3.7 - 3.15\n" #| "Network Distance: 0 hops\n" #| "Service Info: Host: mirtuel; OS: Linux; CPE: cpe:/o:linux:linux_kernel\n" #| "\n" #| "OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .\n" #| "Nmap done: 1 IP address (1 host up) scanned in 11.54 seconds\n" #| "" msgid "" "\n" "# nmap debian\n" "# nmap -A localhost\n" "" msgstr "" "\n" "# nmap mirtuel\n" "\n" "Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-09 16:46 CET\n" "Nmap scan report for mirtuel (192.168.1.242)\n" "Host is up (0.000013s latency).\n" "rDNS record for 192.168.1.242: mirtuel.internal.placard.fr.eu.org\n" "Not shown: 998 closed ports\n" "PORT STATE SERVICE\n" "22/tcp open ssh\n" "111/tcp open rpcbind\n" "\n" "Nmap done: 1 IP address (1 host up) scanned in 2.41 seconds\n" "# nmap -A localhost\n" "\n" "Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-09 16:46 CET\n" "Nmap scan report for localhost (127.0.0.1)\n" "Host is up (0.000013s latency).\n" "Other addresses for localhost (not scanned): 127.0.0.1\n" "Not shown: 997 closed ports\n" "PORT STATE SERVICE VERSION\n" "22/tcp open ssh OpenSSH 6.7p1 Debian 3 (protocol 2.0)\n" "|_ssh-hostkey: ERROR: Script execution failed (use -d to debug)\n" "25/tcp open smtp Exim smtpd 4.84\n" "| smtp-commands: mirtuel Hello localhost [127.0.0.1], SIZE 52428800, 8BITMIME, PIPELINING, HELP, \n" "|_ Commands supported: AUTH HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP \n" "111/tcp open rpcbind 2-4 (RPC #100000)\n" "| rpcinfo: \n" "| program version port/proto service\n" "| 100000 2,3,4 111/tcp rpcbind\n" "| 100000 2,3,4 111/udp rpcbind\n" "| 100024 1 36568/tcp status\n" "|_ 100024 1 39172/udp status\n" "Device type: general purpose\n" "Running: Linux 3.X\n" "OS CPE: cpe:/o:linux:linux_kernel:3\n" "OS details: Linux 3.7 - 3.15\n" "Network Distance: 0 hops\n" "Service Info: Host: mirtuel; OS: Linux; CPE: cpe:/o:linux:linux_kernel\n" "\n" "OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .\n" "Nmap done: 1 IP address (1 host up) scanned in 11.54 seconds\n" "" #, fuzzy #| msgid "As expected, the SSH and Exim4 applications are listed. Note that not all applications listen on all IP addresses; since Exim4 is only accessible on the lo loopback interface, it only appears during an analysis of localhost and not when scanning mirtuel (which maps to the eth0 interface on the same machine)." msgid "As expected, e.g. the SSH, Apache and Postfix applications are listed. Note that not all applications listen on all IP addresses; since Postfix is only accessible on the lo loopback interface, it only appears during an analysis of localhost and not when scanning debian (which maps to the enp1s0 interface on the same machine)." msgstr "On retrouve bien les applications SSH et Exim4. Notez que toutes les applications n'écoutent pas sur toutes les adresses IP ; ainsi, comme Exim4 n'est accessible que sur l'interface de boucle locale lo, il n'apparaît que lors d'une analyse de localhost et non de mirtuel (l'interface réseau eth0 de la même machine)." msgid "Sniffers: tcpdump and wireshark" msgstr "Les sniffers : tcpdump et wireshark" msgid "tcpdump" msgstr "tcpdump" msgid "wireshark" msgstr "wireshark" msgid "Sometimes, one needs to look at what actually goes on the wire, packet by packet. These cases call for a “frame analyzer”, more widely known as a sniffer. Such a tool observes all the packets that reach a given network interface, and displays them in a user-friendly way." msgstr "Il arrive parfois que l'on ait besoin de voir ce qui passe réellement sur le réseau, paquet par paquet. On utilise dans ce cas un « analyseur de trame », plus connu sous le nom de sniffer (renifleur). Cet outil scrute tous les paquets qui atteignent une interface réseau et les affiche de manière plus lisible à l'utilisateur." msgid "The venerable tool in this domain is tcpdump, available as a standard tool on a wide range of platforms. It allows many kinds of network traffic capture, but the representation of this traffic stays rather obscure. We will therefore not describe it in further detail." msgstr "L'ancêtre dans ce domaine est sans conteste tcpdump (dans le paquet du même nom). Il est disponible en standard sur un très grand nombre de plates-formes et permet toutes sortes de captures de trafic réseau, mais la représentation de ce trafic reste assez obscure. Par conséquent, nous ne nous étendrons pas dessus." msgid "A more recent (and more modern) tool, wireshark (in the wireshark package), has become the new reference in network traffic analysis due to its many decoding modules that allow for a simplified analysis of the captured packets. The packets are displayed graphically with an organization based on the protocol layers. This allows a user to visualize all protocols involved in a packet. For example, given a packet containing an HTTP request, wireshark displays, separately, the information concerning the physical layer, the Ethernet layer, the IP packet information, the TCP connection parameters, and finally the HTTP request itself." msgstr "Plus récent et plus moderne, l'outil wireshark (paquet wireshark) est devenu la référence dans l'analyse de trafic réseau, notamment grâce à ses nombreux modules de décodage qui permettent une analyse simplifiée des paquets capturés. La représentation graphique des paquets est en effet organisée par couches successives, ce qui permet de visualiser chacun des protocoles impliqués dans un paquet. Par exemple, pour un paquet correspondant à une requête HTTP, on verra de manière séparée les informations correspondant à la couche physique, la couche Ethernet, les informations du paquet IP, puis celles de la connexion TCP, puis enfin la requête HTTP en tant que telle. On pourra ainsi se focaliser sur une couche particulière." msgid "The wireshark network traffic analyzer" msgstr "Analyseur de trafic réseau wireshark" #, fuzzy #| msgid "In our example, the packets traveling over SSH are filtered out (with the !tcp.port == 22 filter). The packet currently displayed was developed at the HTTP layer." msgid "In our example, the packets traveling over SSH are filtered out (with the !tcp.port == 22 filter). The packet currently displayed was developed at the transport layer of the SSHv2 protocol." msgstr "Dans notre exemple, seuls les paquets n'ayant pas transité par SSH sont affichés (grâce au filtre !tcp.port == 22). Le paquet en cours d'analyse approfondie a été développé à la couche HTTP." msgid "TIP wireshark with no graphical interface: tshark" msgstr "ASTUCE wireshark sans interface graphique : tshark" msgid "tshark" msgstr "tshark" msgid "When one cannot run a graphical interface, or does not wish to do so for whatever reason, a text-only version of wireshark also exists under the name tshark (in a separate tshark package). Most of the capture and decoding features are still available, but the lack of a graphical interface necessarily limits the interactions with the program (filtering packets after they've been captured, tracking of a given TCP connection, and so on). It can still be used as a first approach. If further manipulations are intended and require the graphical interface, the packets can be saved to a file and this file can be loaded into a graphical wireshark running on another machine." msgstr "Lorsque l'on ne souhaite pas lancer d'interface graphique, ou que c'est impossible pour une raison ou une autre, on peut utiliser une version en texte seul de wireshark appelée tshark (dans un paquet tshark séparé). La plupart des fonctionnalités de capture et de décodage des paquets restent présentes, mais le manque d'interface graphique limite forcément les interactions avec le programme (filtrage des paquets après la capture, suivi d'une connexion TCP, etc.). On l'emploiera donc pour une première approche. Si l'on s'aperçoit que l'interface est importante pour les manipulations que l'on a en tête, on pourra toutefois sauvegarder les paquets capturés dans un fichier et importer ce dernier dans un wireshark graphique sur une autre machine." #, fuzzy #~| msgid "Barring a specific QoS configuration, the Linux kernel uses the pfifo_fast queue scheduler, which provides a few interesting features by itself. The priority of each processed IP packet is based on the ToS field (Type of Service) of this packet; modifying this field is enough to take advantage of the scheduling features. There are five possible values:" #~ msgid "Barring a specific QoS configuration, the Linux kernel uses the pfifo_fast queue scheduler, which provides a few interesting features by itself. The priority of each processed IP packet is based on the DSCP field (Differentiated of Services Code Point) of this packet; modifying this 6-bit field is enough to take advantage of the scheduling features. Refer to for more information." #~ msgstr "En l'absence d'une configuration particulière de QoS, le noyau Linux emploie la file d'attente pfifo_fast, qui propose déjà quelques fonctionnalités intéressantes. Pour établir les priorités des paquets IP, elle utilise leur champ ToS (Type of Service, ou type de service) — qu'il suffira donc de modifier pour bénéficier de cette file. Ce champ peut recevoir cinq valeurs :" #~ msgid "TCP, port" #~ msgstr "TCP, port" #~ msgid "UDP, port" #~ msgstr "UDP, port" #~ msgid "SNAT" #~ msgstr "SNAT" #~ msgid "DNAT" #~ msgstr "DNAT" #, fuzzy #~| msgid "X.509, certificate" #~ msgid "certificates" #~ msgstr "X.509, certificat" #~ msgid "X.509, certificate" #~ msgstr "X.509, certificat" #~ msgid "SSH" #~ msgstr "SSH" #~ msgid "Point-to-Point Tunneling Protocol" #~ msgstr "Point-to-Point Tunneling Protocol" #, fuzzy #~| msgid "gateway" #~ msgid "net neutrality" #~ msgstr "passerelle" #~ msgid "In the PPP case, creating a script that calls wondershaper in /etc/ppp/ip-up.d/ will enable traffic control as soon as the connection is up." #~ msgstr "Dans le cas de PPP, la création d'un script appelant wondershaper dans /etc/ppp/ip-up.d/ activera le contrôle de trafic dès le démarrage de la connexion." #, fuzzy #~| msgid "route" #~ msgid "ip route" #~ msgstr "route" #~ msgid "IPv6 firewall" #~ msgstr "pare-feu IPv6" #~ msgid "A: IPv4 address. A, DNS record" #~ msgstr "A : attribution d'une adresse IPv4. A, enregistrement DNS" #~ msgid "AAAA: IPv6 address. AAAA, DNS record" #~ msgstr "AAAA : correspondance nom vers adresse IPv6. AAAA, enregistrement DNS" #~ msgid "DNS record" #~ msgstr "DNSenregistrement" #~ msgid "DHCP" #~ msgstr "DHCP" #~ msgid "NOTE easy-rsa before Jessie" #~ msgstr "NOTE easy-rsa avant Jessie" #~ msgid "In versions of Debian up to Wheezy, easy-rsa was distributed as part of the openvpn package, and its scripts were to be found under /usr/share/doc/openvpn/examples/easy-rsa/2.0/. Setting up a CA involved copying that directory, instead of using the make-cadir command as documented here." #~ msgstr "Jusqu'à Wheezy, easy-rsa faisait partie du paquet openvpn et les scripts se trouvaient dans /usr/share/doc/openvpn/examples/easy-rsa/2.0/. Pour mettre en place une autorité de certification il fallait copier ce répertoire, la commande make-cadir documentée ici n'existant pas encore." #~ msgid "" #~ "\n" #~ "$ vim vars\n" #~ "$ grep KEY_ vars\n" #~ "export KEY_CONFIG=`$EASY_RSA/whichopensslcnf $EASY_RSA`\n" #~ "export KEY_DIR=\"$EASY_RSA/keys\"\n" #~ "echo NOTE: If you run ./clean-all, I will be doing a rm -rf on $KEY_DIR\n" #~ "export KEY_SIZE=2048\n" #~ "export KEY_EXPIRE=3650\n" #~ "export KEY_COUNTRY=\"FR\"\n" #~ "export KEY_PROVINCE=\"Loire\"\n" #~ "export KEY_CITY=\"Saint-Étienne\"\n" #~ "export KEY_ORG=\"Falcot Corp\"\n" #~ "export KEY_EMAIL=\"admin@falcot.com\"\n" #~ "export KEY_OU=\"Certificate authority\"\n" #~ "export KEY_NAME=\"Certificate authority for Falcot Corp\"\n" #~ "# If you'd like to sign all keys with the same Common Name, uncomment the KEY_CN export below\n" #~ "# export KEY_CN=\"CommonName\"\n" #~ "$ . ./vars\n" #~ "NOTE: If you run ./clean-all, I will be doing a rm -rf on /home/roland/pki-falcot/keys\n" #~ "$ ./clean-all\n" #~ "" #~ msgstr "" #~ "\n" #~ "$ vim vars\n" #~ "$ grep KEY_ vars\n" #~ "export KEY_CONFIG=`$EASY_RSA/whichopensslcnf $EASY_RSA`\n" #~ "export KEY_DIR=\"$EASY_RSA/keys\"\n" #~ "echo NOTE: If you run ./clean-all, I will be doing a rm -rf on $KEY_DIR\n" #~ "export KEY_SIZE=2048\n" #~ "export KEY_EXPIRE=3650\n" #~ "export KEY_COUNTRY=\"FR\"\n" #~ "export KEY_PROVINCE=\"Loire\"\n" #~ "export KEY_CITY=\"Saint-Étienne\"\n" #~ "export KEY_ORG=\"Falcot Corp\"\n" #~ "export KEY_EMAIL=\"admin@falcot.com\"\n" #~ "export KEY_OU=\"Certificate authority\"\n" #~ "export KEY_NAME=\"Certificate authority for Falcot Corp\"\n" #~ "# If you'd like to sign all keys with the same Common Name, uncomment the KEY_CN export below\n" #~ "# export KEY_CN=\"CommonName\"\n" #~ "$ . ./vars\n" #~ "NOTE: If you run ./clean-all, I will be doing a rm -rf on /home/roland/pki-falcot/keys\n" #~ "$ ./clean-all\n" #~ "" #~ msgid "" #~ "\n" #~ "$ ./build-key-server vpn.falcot.com\n" #~ "Generating a 2048 bit RSA private key\n" #~ ".....................................................................................................................+++\n" #~ "...........+++\n" #~ "writing new private key to 'vpn.falcot.com.key'\n" #~ "-----\n" #~ "You are about to be asked to enter information that will be incorporated\n" #~ "into your certificate request.\n" #~ "What you are about to enter is what is called a Distinguished Name or a DN.\n" #~ "There are quite a few fields but you can leave some blank\n" #~ "For some fields there will be a default value,\n" #~ "If you enter '.', the field will be left blank.\n" #~ "-----\n" #~ "Country Name (2 letter code) [FR]:\n" #~ "State or Province Name (full name) [Loire]:\n" #~ "Locality Name (eg, city) [Saint-Étienne]:\n" #~ "Organization Name (eg, company) [Falcot Corp]:\n" #~ "Organizational Unit Name (eg, section) [Certificate authority]:\n" #~ "Common Name (eg, your name or your server's hostname) [vpn.falcot.com]:\n" #~ "Name [Certificate authority for Falcot Corp]:\n" #~ "Email Address [admin@falcot.com]:\n" #~ "\n" #~ "Please enter the following 'extra' attributes\n" #~ "to be sent with your certificate request\n" #~ "A challenge password []:\n" #~ "An optional company name []:\n" #~ "Using configuration from /home/roland/pki-falcot/openssl-1.0.0.cnf\n" #~ "Check that the request matches the signature\n" #~ "Signature ok\n" #~ "The Subject's Distinguished Name is as follows\n" #~ "countryName :PRINTABLE:'FR'\n" #~ "stateOrProvinceName :PRINTABLE:'Loire'\n" #~ "localityName :T61STRING:'Saint-\\0xFFFFFFC3\\0xFFFFFF89tienne'\n" #~ "organizationName :PRINTABLE:'Falcot Corp'\n" #~ "organizationalUnitName:PRINTABLE:'Certificate authority'\n" #~ "commonName :PRINTABLE:'vpn.falcot.com'\n" #~ "name :PRINTABLE:'Certificate authority for Falcot Corp'\n" #~ "emailAddress :IA5STRING:'admin@falcot.com'\n" #~ "Certificate is to be certified until Mar 6 14:54:56 2025 GMT (3650 days)\n" #~ "Sign the certificate? [y/n]:y\n" #~ "\n" #~ "\n" #~ "1 out of 1 certificate requests certified, commit? [y/n]y\n" #~ "Write out database with 1 new entries\n" #~ "Data Base Updated\n" #~ "$ ./build-dh\n" #~ "Generating DH parameters, 2048 bit long safe prime, generator 2\n" #~ "This is going to take a long time\n" #~ "[…]\n" #~ "" #~ msgstr "" #~ "\n" #~ "$ ./build-key-server vpn.falcot.com\n" #~ "Generating a 2048 bit RSA private key\n" #~ ".....................................................................................................................+++\n" #~ "...........+++\n" #~ "writing new private key to 'vpn.falcot.com.key'\n" #~ "-----\n" #~ "You are about to be asked to enter information that will be incorporated\n" #~ "into your certificate request.\n" #~ "What you are about to enter is what is called a Distinguished Name or a DN.\n" #~ "There are quite a few fields but you can leave some blank\n" #~ "For some fields there will be a default value,\n" #~ "If you enter '.', the field will be left blank.\n" #~ "-----\n" #~ "Country Name (2 letter code) [FR]:\n" #~ "State or Province Name (full name) [Loire]:\n" #~ "Locality Name (eg, city) [Saint-Étienne]:\n" #~ "Organization Name (eg, company) [Falcot Corp]:\n" #~ "Organizational Unit Name (eg, section) [Certificate authority]:\n" #~ "Common Name (eg, your name or your server's hostname) [vpn.falcot.com]:\n" #~ "Name [Certificate authority for Falcot Corp]:\n" #~ "Email Address [admin@falcot.com]:\n" #~ "\n" #~ "Please enter the following 'extra' attributes\n" #~ "to be sent with your certificate request\n" #~ "A challenge password []:\n" #~ "An optional company name []:\n" #~ "Using configuration from /home/roland/pki-falcot/openssl-1.0.0.cnf\n" #~ "Check that the request matches the signature\n" #~ "Signature ok\n" #~ "The Subject's Distinguished Name is as follows\n" #~ "countryName :PRINTABLE:'FR'\n" #~ "stateOrProvinceName :PRINTABLE:'Loire'\n" #~ "localityName :T61STRING:'Saint-\\0xFFFFFFC3\\0xFFFFFF89tienne'\n" #~ "organizationName :PRINTABLE:'Falcot Corp'\n" #~ "organizationalUnitName:PRINTABLE:'Certificate authority'\n" #~ "commonName :PRINTABLE:'vpn.falcot.com'\n" #~ "name :PRINTABLE:'Certificate authority for Falcot Corp'\n" #~ "emailAddress :IA5STRING:'admin@falcot.com'\n" #~ "Certificate is to be certified until Mar 6 14:54:56 2025 GMT (3650 days)\n" #~ "Sign the certificate? [y/n]:y\n" #~ "\n" #~ "\n" #~ "1 out of 1 certificate requests certified, commit? [y/n]y\n" #~ "Write out database with 1 new entries\n" #~ "Data Base Updated\n" #~ "$ ./build-dh\n" #~ "Generating DH parameters, 2048 bit long safe prime, generator 2\n" #~ "This is going to take a long time\n" #~ "[…]\n" #~ "" #~ msgid "" #~ "\n" #~ "$ ./build-key JoeSmith\n" #~ "Generating a 2048 bit RSA private key\n" #~ "................................+++\n" #~ "..............................................+++\n" #~ "writing new private key to 'JoeSmith.key'\n" #~ "-----\n" #~ "You are about to be asked to enter information that will be incorporated\n" #~ "into your certificate request.\n" #~ "What you are about to enter is what is called a Distinguished Name or a DN.\n" #~ "There are quite a few fields but you can leave some blank\n" #~ "For some fields there will be a default value,\n" #~ "If you enter '.', the field will be left blank.\n" #~ "-----\n" #~ "Country Name (2 letter code) [FR]:\n" #~ "State or Province Name (full name) [Loire]:\n" #~ "Locality Name (eg, city) [Saint-Étienne]:\n" #~ "Organization Name (eg, company) [Falcot Corp]:\n" #~ "Organizational Unit Name (eg, section) [Certificate authority]:Development unit\n" #~ "Common Name (eg, your name or your server's hostname) [JoeSmith]:Joe Smith\n" #~ "[…]" #~ msgstr "" #~ "\n" #~ "$ ./build-key PierreDurand\n" #~ "Generating a 2048 bit RSA private key\n" #~ "................................+++\n" #~ "..............................................+++\n" #~ "writing new private key to 'PierreDurand.key'\n" #~ "-----\n" #~ "You are about to be asked to enter information that will be incorporated\n" #~ "into your certificate request.\n" #~ "What you are about to enter is what is called a Distinguished Name or a DN.\n" #~ "There are quite a few fields but you can leave some blank\n" #~ "For some fields there will be a default value,\n" #~ "If you enter '.', the field will be left blank.\n" #~ "-----\n" #~ "Country Name (2 letter code) [FR]:\n" #~ "State or Province Name (full name) [Loire]:\n" #~ "Locality Name (eg, city) [Saint-Étienne]:\n" #~ "Organization Name (eg, company) [Falcot SA]:\n" #~ "Organizational Unit Name (eg, section) [Certificate authority]:Development unit\n" #~ "Common Name (eg, your name or your server's hostname) [PierreDurand]:Pierre Durand\n" #~ "[…]" #~ msgid "racoon" #~ msgstr "racoon" #~ msgid "IPsec, despite being the standard in IP VPNs, is rather more involved in its implementation. The IPsec engine itself is integrated in the Linux kernel; the required user-space parts, the control and configuration tools, are provided by the ipsec-tools package. In concrete terms, each host's /etc/ipsec-tools.conf contains the parameters for IPsec tunnels (or Security Associations, in the IPsec terminology) that the host is concerned with; the /etc/init.d/setkey script provides a way to start and stop a tunnel (each tunnel is a secure link to another host connected to the virtual private network). This file can be built by hand from the documentation provided by the setkey 8 manual page. However, explicitly writing the parameters for all hosts in a non-trivial set of machines quickly becomes an arduous task, since the number of tunnels grows fast. Installing an IKE daemon (for IPsec Key Exchange) such as racoon or strongswan makes the process much simpler by bringing administration together at a central point, and more secure by rotating the keys periodically." #~ msgstr "IPsec, le standard en matière de réseau privé virtuel IP, est nettement plus difficile à mettre en œuvre. Il est intégré au noyau Linux et, pour l'employer sous Debian, il suffit d'installer le paquet ipsec-tools recelant des outils complémentaires et de paramétrage. Sur le plan pratique, le fichier /etc/ipsec-tools.conf de chaque hôte abrite les paramètres de « tunnels IPsec » (ou Security Association dans le vocabulaire IPsec) le concernant et le script /etc/init.d/setkey offre le moyen d'établir (paramètre start) ou de stopper (stop) un tunnel. Chaque tunnel est une liaison sûre avec un autre hôte connecté au réseau privé virtuel. On peut constituer ce fichier manuellement en s'aidant de la page de manuel setkey8. Mais administrer un parc étoffé ainsi, en paramétrant explicitement, devient difficile car le nombre de tunnels augmente vite. L'installation d'un démon IKE (IPsec Key Exchange, échange de clés IPsec) comme racoon ou strongswan simplifie tout cela en centralisant l'administration et améliore la sécurité en organisant une rotation des clés employées." #~ msgid "Normal-Service (0);" #~ msgstr "Normal-Service (0) (service normal) ;" #~ msgid "Minimize-Cost (2);" #~ msgstr "Minimize-Cost (2) (minimiser le coût) ;" #~ msgid "Maximize-Reliability (4);" #~ msgstr "Maximize-Reliability (4) (maximiser la fiabilité) ;" #~ msgid "Maximize-Throughput (8);" #~ msgstr "Maximize-Throughput (8) (maximiser le débit) ;" #~ msgid "Minimize-Delay (16)." #~ msgstr "Minimize-Delay (16) (minimiser le délai)." #~ msgid "ToS" #~ msgstr "ToS" #~ msgid "Type of Service" #~ msgstr "Type of Service" #~ msgid "" #~ "\n" #~ "iptables -t mangle -A PREROUTING -p tcp --sport ssh -j TOS --set-tos Minimize-Delay\n" #~ "iptables -t mangle -A PREROUTING -p tcp --dport ssh -j TOS --set-tos Minimize-Delay" #~ msgstr "" #~ "\n" #~ "iptables -t mangle -A PREROUTING -p tcp --sport ssh -j TOS --set-tos Minimize-Delay\n" #~ "iptables -t mangle -A PREROUTING -p tcp --dport ssh -j TOS --set-tos Minimize-Delay" #~ msgid "BABEL wireless mesh routing" #~ msgstr "BABEL, routage de réseau maillé sans fil" #~ msgid "babeld" #~ msgstr "babeld" #~ msgid "Daemons are enabled by editing the /etc/quagga/daemons file and creating the appropriate configuration file in /etc/quagga/; this configuration file must be named after the daemon, with a .conf extension, and belong to the quagga user and the quaggavty group, in order for the /etc/init.d/quagga script to invoke the daemon." #~ msgstr "On active un démon en modifiant le fichier /etc/quagga/daemons et en créant dans le répertoire /etc/quagga/ son fichier de configuration, qui doit porter son nom suivi de .conf et appartenir à l'utilisateur quagga et au groupe quaggavty — dans le cas contraire, le script /etc/init.d/quagga n'invoquera pas ce démon." #~ msgid "IPv6 connections can be restricted, in the same fashion as for IPv4: the standard Debian kernels include an adaptation of netfilter for IPv6. This IPv6-enabled netfilter is configured in a similar fashion to its IPv4 counterpart, except the program to use is ip6tables instead of iptables." #~ msgstr "Les connexions IPv6 peuvent être filtrées et restreintes comme avec IPv4 : il existe une adaptation de netfilter pour l'IPv6 compilée dans les noyaux Debian. Elle se configure comme la version classique, mais avec le programme ip6tables en lieu et place d'iptables." #~ msgid "Freenet6" #~ msgstr "Freenet6" #~ msgid "Gogo6" #~ msgstr "Gogo6" #~ msgid "To use a Freenet6 tunnel, you need to register for a Freenet6 Pro account on the website, then install the gogoc package and configure the tunnel. This requires editing the /etc/gogoc/gogoc.conf file: userid and password lines received by e-mail should be added, and server should be replaced with authenticated.freenet6.net." #~ msgstr "Pour exploiter cette possibilité, il faut s'inscrire et créer un compte Freenet6 Pro sur ce site web puis installer le paquet Debian gogoc et configurer ce tunnel. On intégrera au fichier /etc/gogoc/gogoc.conf les lignes userid et password reçues par courrier électronique et on remplacera server par authenticated.freenet6.net." #~ msgid "IPv6 connectivity is proposed to all machines on a local network by adding the three following directives to the /etc/gogoc/gogoc.conf file (assuming the local network is connected to the eth0 interface):" #~ msgstr "On proposera une connectivité IPv6 à toutes les machines du réseau local en modifiant dans le fichier /etc/gogoc/gogoc.conf les trois directives ci-dessous (le réseau local est supposé connecté à l'interface eth0) :" #~ msgid "" #~ "\n" #~ "host_type=router\n" #~ "prefixlen=56\n" #~ "if_prefix=eth0" #~ msgstr "" #~ "\n" #~ "host_type=router\n" #~ "prefixlen=56\n" #~ "if_prefix=eth0" #~ msgid "CULTURE ethereal and wireshark" #~ msgstr "CULTURE ethereal et wireshark" #~ msgid "ethereal" #~ msgstr "ethereal" #~ msgid "tethereal" #~ msgstr "tethereal" #~ msgid "wireshark seems to be relatively young; however, it is only the new name for a software application previously known as ethereal. When its main developer left the company where he was employed, he was not able to arrange for the transfer of the registered trademark. As an alternative he went for a name change; only the name and the icons for the software actually changed." #~ msgstr "wireshark, bien qu'apparu relativement récemment, est en réalité simplement le nouveau nom du logiciel ethereal. Lorsque le développeur principal a quitté la société qui l'employait, il n'a pas réussi à se faire transférer la marque déposée et il a donc opté pour un changement de nom, mais seuls le nom et l'icône du logiciel ont changé." #~ msgid "Presentation" #~ msgstr "Présentation"