Debian Codegraph @

fr-FR/10_network-infrastructure.po

raw
1 # AUTHOR <EMAIL@ADDRESS>, YEAR.
2 # Raphael Hertzog <[email protected]>, 2015.
3 msgid ""
4 msgstr ""
5 "Project-Id-Version: 0\n"
6 "POT-Creation-Date: 2022-08-10 10:50+0200\n"
7 "PO-Revision-Date: 2022-07-30 18:42+0200\n"
8 "Last-Translator: Galina Anikina <[email protected]>\n"
9 "Language-Team: French <https://hosted.weblate.org/projects/debian-handbook/10_network-infrastructure/fr/>\n"
10 "Language: fr-FR\n"
11 "MIME-Version: 1.0\n"
12 "Content-Type: application/x-publican; charset=UTF-8\n"
13 "Content-Transfer-Encoding: 8bit\n"
14 "Plural-Forms: nplurals=2; plural=n > 1;\n"
15 "X-Generator: Weblate 2.18-dev\n"
16
17 msgid "Network"
18 msgstr "Réseau"
19
20 msgid "Gateway"
21 msgstr "Passerelle"
22
23 msgid "TCP/IP"
24 msgstr "TCP/IP"
25
26 msgid "IPv6"
27 msgstr "IPv6"
28
29 msgid "DNS"
30 msgstr "DNS"
31
32 msgid "Bind"
33 msgstr "Bind"
34
35 msgid "DHCP"
36 msgstr "DHCP"
37
38 msgid "QoS"
39 msgstr "QoS"
40
41 msgid "Network Infrastructure"
42 msgstr "Infrastructure réseau"
43
44 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."
45 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."
46
47 msgid "<primary>gateway</primary>"
48 msgstr "<primary>passerelle</primary>"
49
50 msgid "<primary>network</primary><secondary>gateway</secondary>"
51 msgstr "<primary>réseau</primary><secondary>passerelle</secondary>"
52
53 msgid "<primary>router</primary>"
54 msgstr "<primary>routeur</primary>"
55
56 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."
57 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."
58
59 msgid "<emphasis>BACK TO BASICS</emphasis> IP packet"
60 msgstr "<emphasis>B.A.-BA</emphasis> Paquet IP"
61
62 msgid "<primary>packet</primary><secondary>IP</secondary>"
63 msgstr "<primary>paquet</primary><secondary>IP</secondary>"
64
65 #, fuzzy
66 #| msgid "<primary>DNS</primary><secondary>automated updates</secondary>"
67 msgid "<primary>IP</primary><seealso>Internet Protocol</seealso>"
68 msgstr "<primary>DNS</primary><secondary>mise à jour automatique</secondary>"
69
70 #, fuzzy
71 #| msgid "<primary>AH, protocol</primary>"
72 msgid "<primary>Internet Protocol</primary>"
73 msgstr "<primary>AH, protocole</primary>"
74
75 msgid "Most networks nowadays use the IP protocol (<emphasis>Internet Protocol</emphasis>). 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."
76 msgstr "Les réseaux employant le protocole Internet (IP — <foreignphrase>Internet Protocol</foreignphrase>) 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)."
77
78 msgid "<emphasis>BACK TO BASICS</emphasis> TCP/UDP"
79 msgstr "<emphasis>B.A.-BA</emphasis> TCP/UDP"
80
81 #, fuzzy
82 #| msgid "<primary>protocol</primary><secondary>ESP</secondary>"
83 msgid "<primary>protocol</primary><secondary>TCP</secondary>"
84 msgstr "<primary>protocole</primary><secondary>ESP</secondary>"
85
86 #, fuzzy
87 #| msgid "<primary>protocol</primary><secondary>ESP</secondary>"
88 msgid "<primary>protocol</primary><secondary>UDP</secondary>"
89 msgstr "<primary>protocole</primary><secondary>ESP</secondary>"
90
91 msgid "<primary>port</primary><secondary>TCP</secondary>"
92 msgstr "<primary>port</primary><secondary>TCP</secondary>"
93
94 msgid "<primary>port</primary><secondary>UDP</secondary>"
95 msgstr "<primary>port</primary><secondary>UDP</secondary>"
96
97 #, fuzzy
98 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
99 msgid "<primary>TCP</primary><secondary>port</secondary>"
100 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
101
102 #, fuzzy
103 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
104 msgid "<primary>UDP</primary><secondary>port</secondary>"
105 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
106
107 #, fuzzy
108 #| msgid "<primary>Dynamic Host Configuration Protocol</primary>"
109 msgid "<primary>Transmission Control Protocol</primary><seealso></seealso>"
110 msgstr "<primary><foreignphrase>Dynamic Host Configuration Protocol</foreignphrase></primary>"
111
112 #, fuzzy
113 #| msgid "<primary>protocol</primary><secondary>ESP</secondary>"
114 msgid "<primary>User Datagram Protocol</primary><seealso>UDP</seealso>"
115 msgstr "<primary>protocole</primary><secondary>ESP</secondary>"
116
117 msgid "Many programs do not handle the individual packets themselves, even though the data they transmit does travel over IP; they often use TCP (<emphasis>Transmission Control Protocol</emphasis>). 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."
118 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)."
119
120 msgid "Another protocol relying on IP is UDP (<emphasis>User Datagram Protocol</emphasis>). 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."
121 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."
122
123 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."
124 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."
125
126 msgid "<primary>Internet Assigned Numbers Authority</primary><seealso>IANA</seealso>"
127 msgstr ""
128
129 #, fuzzy
130 #| msgid "<primary>NAT</primary>"
131 msgid "<primary>IANA</primary>"
132 msgstr "<primary>NAT</primary>"
133
134 #, fuzzy
135 #| msgid "<primary>quality</primary><secondary>of service</secondary>"
136 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/services</filename></secondary>"
137 msgstr "<primary>qualité</primary><secondary>de service</secondary>"
138
139 #, fuzzy
140 #| msgid "Some of these port numbers — standardized by the IANA (<emphasis>Internet Assigned Numbers Authority</emphasis>) — are “well-known” for being associated with network services. For instance, TCP port 25 is generally used by the email server. <ulink type=\"block\" url=\"http://www.iana.org/assignments/port-numbers\" />"
141 msgid "Some of these port numbers — standardized by the IANA (<emphasis>Internet Assigned Numbers Authority</emphasis>) — 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 <filename>/etc/services</filename> file, also explained in <citerefentry><refentrytitle>services</refentrytitle> <manvolnum>5</manvolnum></citerefentry>, as well as in: <ulink type=\"block\" url=\"https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml\" />"
142 msgstr "Certains de ces numéros — standardisés par l'IANA (<foreignphrase>Internet Assigned Numbers Authority</foreignphrase>, 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. <ulink type=\"block\" url=\"http://www.iana.org/assignments/port-numbers\" />"
143
144 #, fuzzy
145 #| msgid "<primary>service</primary><secondary>quality</secondary>"
146 msgid "<primary>IP</primary><secondary>masquerading</secondary>"
147 msgstr "<primary>service</primary><secondary>qualité</secondary>"
148
149 #, fuzzy
150 #| msgid "<primary>network</primary><secondary>gateway</secondary>"
151 msgid "<primary>network</primary><secondary>masquerading</secondary>"
152 msgstr "<primary>réseau</primary><secondary>passerelle</secondary>"
153
154 msgid "When a local network uses a private address range (not routable on the Internet), the gateway needs to implement <emphasis>address masquerading</emphasis> 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."
155 msgstr "Lorsqu'un réseau local utilise une plage d'adresses privées (non routables sur Internet), la passerelle doit effectuer du <emphasis>masquerading</emphasis> (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 <foreignphrase>masquerading</foreignphrase> (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."
156
157 msgid "<primary>masquerading</primary>"
158 msgstr "<primary><foreignphrase>masquerading</foreignphrase></primary>"
159
160 msgid "<emphasis>CULTURE</emphasis> Private address range"
161 msgstr "<emphasis>CULTURE</emphasis> Plages d'adresses privées"
162
163 #, fuzzy
164 #| msgid "<primary>IP address</primary><secondary>private</secondary>"
165 msgid "<primary>IP</primary><secondary>private address</secondary>"
166 msgstr "<primary>adresse IP</primary><secondary>privée</secondary>"
167
168 msgid "<primary>private IP address</primary>"
169 msgstr "<primary>privée, adresse IP</primary>"
170
171 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, <literal>10.0.0.0/8</literal> (see sidebar <xref linkend=\"sidebar.networking-basics\" />), is a class-A range (with 2<superscript>24</superscript> IP addresses). The second one, <literal>172.16.0.0/12</literal>, gathers 16 class-B ranges (<literal>172.16.0.0/16</literal> to <literal>172.31.0.0/16</literal>), each containing 2<superscript>16</superscript> IP addresses. Finally, <literal>192.168.0.0/16</literal> is a class-B range (grouping 256 class-C ranges, <literal>192.168.0.0/24</literal> to <literal>192.168.255.0/24</literal>, with 256 IP addresses each). <ulink type=\"block\" url=\"http://www.faqs.org/rfcs/rfc1918.html\" />"
172 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, <literal>10.0.0.0/8</literal> (voir encadré <xref linkend=\"sidebar.networking-basics\" />), est une plage de classe A (contenant 2<superscript>24</superscript> adresses IP). La deuxième, <literal>172.16.0.0/12</literal>, rassemble 16 plages de classe B (<literal>172.16.0.0/16</literal> à <literal>172.31.0.0/16</literal>) pouvant contenir chacune 2<superscript>16</superscript> adresses IP. La dernière, <literal>192.168.0.0/16</literal>, est une plage de classe B (regroupant les 256 plages de classe C <literal>192.168.0.0/24</literal> à <literal>192.168.255.0/24</literal>, de 256 adresses IP chacune). <ulink type=\"block\" url=\"http://www.faqs.org/rfcs/rfc1918.html\" />"
173
174 msgid "The gateway can also perform two kinds of <emphasis>network address translation</emphasis> (or NAT for short). The first kind, <emphasis>Destination NAT</emphasis> (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 <emphasis>Source NAT</emphasis> (SNAT), of which <emphasis>masquerading</emphasis> 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)."
175 msgstr "La passerelle peut également effectuer une traduction d'adresses réseau (<emphasis>NAT</emphasis>, ou <foreignphrase>Network Address Translation</foreignphrase>). Il en existe de deux types. Le <foreignphrase>Destination NAT</foreignphrase> (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 » <foreignphrase>(connection tracking)</foreignphrase> altérera aussi les autres paquets de la même connexion pour assurer la continuité de la communication. Son pendant, le <foreignphrase>Source NAT</foreignphrase> (SNAT), dont le <foreignphrase>masquerading</foreignphrase> 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)."
176
177 #, fuzzy
178 #| msgid "<primary>Network</primary><secondary>Address Translation</secondary>"
179 msgid "<primary>NAT</primary><seealso>Network Address Translation</seealso>"
180 msgstr "<primary><foreignphrase>Network</foreignphrase></primary><secondary><foreignphrase>Address Translation</foreignphrase></secondary>"
181
182 #, fuzzy
183 #| msgid "<primary>Network</primary><secondary>Address Translation</secondary>"
184 msgid "<primary>Network Address Translation</primary><seealso>NAT</seealso>"
185 msgstr "<primary><foreignphrase>Network</foreignphrase></primary><secondary><foreignphrase>Address Translation</foreignphrase></secondary>"
186
187 #, fuzzy
188 #| msgid "<primary>Network</primary><secondary>Address Translation</secondary>"
189 msgid "<primary>network</primary><secondary>address translation</secondary><seealso>NAT</seealso>"
190 msgstr "<primary><foreignphrase>Network</foreignphrase></primary><secondary><foreignphrase>Address Translation</foreignphrase></secondary>"
191
192 #, fuzzy
193 #| msgid "<primary>network</primary><secondary>gateway</secondary>"
194 msgid "<primary>network</primary><secondary>NAT</secondary>"
195 msgstr "<primary>réseau</primary><secondary>passerelle</secondary>"
196
197 #, fuzzy
198 #| msgid "<primary>DNS</primary><secondary>automated updates</secondary>"
199 msgid "<primary>SNAT</primary><seealso>Source NAT</seealso>"
200 msgstr "<primary>DNS</primary><secondary>mise à jour automatique</secondary>"
201
202 #, fuzzy
203 #| msgid "<primary>Source NAT</primary>"
204 msgid "<primary>Source NAT</primary><seealso>SNAT</seealso>"
205 msgstr "<primary><foreignphrase>Source NAT</foreignphrase></primary>"
206
207 #, fuzzy
208 #| msgid "<primary>DNS</primary><secondary>automated updates</secondary>"
209 msgid "<primary>DNAT</primary><seealso>Destination NAT</seealso>"
210 msgstr "<primary>DNS</primary><secondary>mise à jour automatique</secondary>"
211
212 #, fuzzy
213 #| msgid "<primary>Destination NAT</primary>"
214 msgid "<primary>Destination NAT</primary><seealso>DNAT</seealso>"
215 msgstr "<primary><foreignphrase>Destination NAT</foreignphrase></primary>"
216
217 msgid "<emphasis>BACK TO BASICS</emphasis> Port forwarding"
218 msgstr "<emphasis>B.A.-BA</emphasis> <foreignphrase>Port forwarding</foreignphrase>"
219
220 msgid "<primary>port forwarding</primary>"
221 msgstr "<primary><foreignphrase>port forwarding</foreignphrase></primary>"
222
223 #, fuzzy
224 #| msgid "<primary>network</primary><secondary>gateway</secondary>"
225 msgid "<primary>network</primary><secondary>port forwarding</secondary>"
226 msgstr "<primary>réseau</primary><secondary>passerelle</secondary>"
227
228 #, fuzzy
229 #| msgid "<primary><command>ripd</command></primary>"
230 msgid "<primary><command>redir</command></primary>"
231 msgstr "<primary><command>ripd</command></primary>"
232
233 msgid "A concrete application of DNAT is <emphasis>port forwarding</emphasis>. 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 <command>ssh</command> (see <xref linkend=\"sect.ssh-port-forwarding\" />) or <command>redir</command>."
234 msgstr "Le <foreignphrase>port forwarding</foreignphrase>, 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 à <command>ssh</command> (voir <xref linkend=\"sect.ssh-port-forwarding\" />) ou <command>redir</command>."
235
236 msgid "<primary>filesystem</primary><secondary>virtual</secondary><tertiary><filename>/proc/</filename></tertiary>"
237 msgstr ""
238
239 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 <filename>/proc/</filename> virtual filesystem:"
240 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 <emphasis>/proc</emphasis> :"
241
242 msgid ""
243 "\n"
244 "<computeroutput># </computeroutput><userinput>echo 1 &gt; /proc/sys/net/ipv4/conf/default/forwarding</userinput>"
245 msgstr ""
246 "\n"
247 "<computeroutput># </computeroutput><userinput>echo 1 &gt; /proc/sys/net/ipv4/conf/default/forwarding</userinput>"
248
249 #, fuzzy
250 #| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>"
251 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/sysctl.conf</filename></secondary>"
252 msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>"
253
254 #, fuzzy
255 #| msgid "<primary>traffic</primary><secondary>limitation</secondary>"
256 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/sysctl.d/</filename></secondary>"
257 msgstr "<primary>trafic</primary><secondary>limitation</secondary>"
258
259 #, fuzzy
260 #| msgid "This option can also be automatically enabled on boot if <filename>/etc/sysctl.conf</filename> sets the <literal>net.ipv4.conf.default.forwarding</literal> option to <literal>1</literal>."
261 msgid "This option can also be automatically enabled on boot if <filename>/etc/sysctl.conf</filename> or a configuration file in <filename>/etc/sysctl.d/</filename> sets the <literal>net.ipv4.conf.default.forwarding</literal> option to <literal>1</literal>."
262 msgstr "Pour activer cette option automatiquement à chaque démarrage, on positionnera dans le fichier <filename>/etc/sysctl.conf</filename> l'option <literal>net.ipv4.conf.default.forwarding</literal> à <literal>1</literal>."
263
264 msgid "The <filename>/etc/sysctl.conf</filename> file"
265 msgstr "Fichier <filename>/etc/sysctl.conf</filename>"
266
267 msgid ""
268 "\n"
269 "net.ipv4.conf.default.forwarding = 1\n"
270 "net.ipv4.conf.default.rp_filter = 1\n"
271 "net.ipv4.tcp_syncookies = 1"
272 msgstr ""
273 "\n"
274 "net.ipv4.conf.default.forwarding = 1\n"
275 "net.ipv4.conf.default.rp_filter = 1\n"
276 "net.ipv4.tcp_syncookies = 1"
277
278 msgid "The same effect can be obtained for IPv6 by simply replacing <literal>ipv4</literal> with <literal>ipv6</literal> in the manual command and using the <literal>net.ipv6.conf.all.forwarding</literal> line in <filename>/etc/sysctl.conf</filename>."
279 msgstr "Pour IPv6, on remplacera simplement <literal>ipv4</literal> par <literal>ipv6</literal> dans la commande et on modifiera la ligne <literal>net.ipv6.conf.all.forwarding</literal> dans <filename>/etc/sysctl.conf</filename>."
280
281 msgid "Enabling IPv4 masquerading is a slightly more complex operation that involves configuring the <emphasis>netfilter</emphasis> firewall."
282 msgstr "Activer le <foreignphrase>masquerading</foreignphrase> IPv4 est une opération plus complexe, nécessitant de configurer le pare-feu <emphasis>netfilter</emphasis>."
283
284 msgid "Similarly, using NAT (for IPv4) requires configuring <emphasis>netfilter</emphasis>. Since the primary purpose of this component is packet filtering, the details are listed in <xref linkend=\"security\" xrefstyle=\"select: label quotedtitle nopage\" /> (see <xref linkend=\"sect.firewall-packet-filtering\" />)."
285 msgstr "L'emploi du NAT (en IPv4) nécessite lui aussi de configurer <emphasis>netfilter</emphasis>. 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 <xref linkend=\"sect.firewall-packet-filtering\" />)."
286
287 #, fuzzy
288 #| msgid "<primary>X.509, certificate</primary>"
289 msgid "X.509 certificates"
290 msgstr "<primary>X.509, certificat</primary>"
291
292 msgid "<primary>certificate</primary><secondary>X.509</secondary>"
293 msgstr "<primary>certificat X.509</primary>"
294
295 msgid "<primary>SSL</primary>"
296 msgstr "<primary>SSL</primary>"
297
298 #, fuzzy
299 #| msgid "<primary>record</primary><secondary>DNS</secondary>"
300 msgid "<primary>Secure Socket Layer</primary><seealso>SSL</seealso>"
301 msgstr "<primary>enregistrement</primary><secondary>DNS</secondary>"
302
303 msgid "<primary>TLS</primary>"
304 msgstr "<primary>TLS</primary>"
305
306 #, fuzzy
307 #| msgid "<primary>port</primary><secondary>TCP</secondary>"
308 msgid "<primary>Transport Layer Security</primary><seealso>TLS</seealso>"
309 msgstr "<primary>port</primary><secondary>TCP</secondary>"
310
311 msgid "<primary>X.509</primary><secondary>certificates</secondary>"
312 msgstr "<primary>X.509</primary><secondary>certificats</secondary>"
313
314 #, fuzzy
315 #| msgid "<primary>DNS</primary><secondary>automated updates</secondary>"
316 msgid "<primary>CA</primary><seealso>Certificate Authority</seealso>"
317 msgstr "<primary>DNS</primary><secondary>mise à jour automatique</secondary>"
318
319 #, fuzzy
320 #| msgid "<primary>X.509, certificate</primary>"
321 msgid "<primary>Certificate Authority</primary>"
322 msgstr "<primary>X.509, certificat</primary>"
323
324 msgid "Certificates are an important building block of many network services built on cryptographic protocols, when they need some sort of central authentication."
325 msgstr ""
326
327 #, fuzzy
328 #| msgid "<primary>IKE</primary>"
329 msgid "<primary>IETF</primary>"
330 msgstr "<primary>IKE</primary>"
331
332 #, fuzzy
333 #| msgid "The SSL protocol (<emphasis>Secure Socket Layer</emphasis>) was invented by Netscape to secure connections to web servers. It was later standardized by IETF under the acronym TLS (<emphasis>Transport Layer Security</emphasis>). Since then TLS continued to evolve and nowadays SSL is deprecated due to multiple design flaws that have been discovered."
334 msgid "Among those protocols, SSL (<emphasis>Secure Socket Layer</emphasis>) was invented by Netscape to secure connections to web servers. It was later standardized by IETF under the acronym TLS (<emphasis>Transport Layer Security</emphasis>). Since then TLS continued to evolve, and nowadays SSL is deprecated due to multiple design flaws that have been discovered."
335 msgstr "SSL <foreignphrase>(Secure Socket Layer)</foreignphrase> 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 <foreignphrase>(Transport Layer Security)</foreignphrase>. 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."
336
337 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."
338 msgstr ""
339
340 #, fuzzy
341 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
342 msgid "<primary>certificate</primary><secondary>root certificate</secondary>"
343 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
344
345 #, fuzzy
346 #| 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 <emphasis>Certification Authority</emphasis> (CA), formalized by the X.509 standard. This term covers an entity that holds a trusted key pair known as a <emphasis>root certificate</emphasis>. 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."
347 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 <emphasis>Certification Authority</emphasis> (CA), formalized by the X.509 standard. This term covers an entity that holds a trusted key pair known as a <emphasis>root certificate</emphasis>. 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."
348 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, <foreignphrase>Certificate Authority</foreignphrase>) 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."
349
350 msgid "You can implement a CA (as described in <xref linkend=\"sect.easy-rsa\" />), 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."
351 msgstr ""
352
353 msgid "Creating gratis trusted certificates"
354 msgstr ""
355
356 #, fuzzy
357 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
358 msgid "<primary>certificate</primary><secondary>trusted certificate</secondary>"
359 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
360
361 #, fuzzy
362 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
363 msgid "<primary>certificate</primary><secondary>snakeoil certificate</secondary>"
364 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
365
366 #, fuzzy
367 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
368 msgid "<primary>certificate</primary><secondary>letsencrypt</secondary><seealso><emphasis role=\"pkg\">certbot</emphasis></seealso>"
369 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
370
371 msgid "Many programs create and use snakeoil certificates by default (see sidebar <xref linkend=\"sidebar.snakeoil-certs\" />). Fortunately the <emphasis role=\"pkg\">certbot</emphasis> package brings everything we need to create our own trusted certificates, provided by the \"Lets Encrypt\" initiative (see sidebar <xref linkend=\"sidebar.letsencrypt\" />), which can also be used for mail transport agents (Postfix), mail delivery agents (Dovecot, Cyrus, etc.), and other network services."
372 msgstr ""
373
374 msgid "The Falcot administrators just want to create a certificate for their website, which runs on Apache. There is a convenient Apache plugin for <emphasis role=\"pkg\">certbot</emphasis> that automatically edits the Apache configuration to serve the obtained certificate, so they make use of it:"
375 msgstr ""
376
377 #, fuzzy
378 #| msgid "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>"
379 msgid "<primary><emphasis role=\"pkg\">certbot</emphasis></primary>"
380 msgstr "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>"
381
382 #, fuzzy
383 #| msgid "<primary><emphasis role=\"pkg\">iputils-tracepath</emphasis></primary>"
384 msgid "<primary><emphasis role=\"pkg\">python3-certbot-apache</emphasis></primary>"
385 msgstr "<primary><emphasis>iputils-tracepath</emphasis></primary>"
386
387 #, fuzzy
388 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
389 msgid "<primary>Apache</primary><secondary><emphasis role=\"pkg\">certbot</emphasis></secondary>"
390 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
391
392 #, fuzzy
393 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
394 msgid "<primary>Apache</primary><secondary><emphasis role=\"pkg\">python3-certbot-apache</emphasis></secondary>"
395 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
396
397 #, fuzzy
398 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
399 msgid "<primary>Apache</primary><secondary>trusted certificates</secondary>"
400 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
401
402 msgid ""
403 "\n"
404 "<computeroutput># </computeroutput><userinput>apt install python3-certbot-apache\n"
405 "</userinput><computeroutput>[...]\n"
406 "# </computeroutput><userinput>certbot --apache\n"
407 "</userinput><computeroutput>aving debug log to /var/log/letsencrypt/letsencrypt.log\n"
408 "Plugins selected: Authenticator apache, Installer apache\n"
409 "Enter email address (used for urgent renewal and security notices)\n"
410 " (Enter 'c' to cancel): </computeroutput><userinput>[email protected]\n"
411 "</userinput><computeroutput>\n"
412 "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n"
413 "Please read the Terms of Service at\n"
414 "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must\n"
415 "agree in order to register with the ACME server. Do you agree?\n"
416 "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n"
417 "(Y)es/(N)o: </computeroutput><userinput>Y\n"
418 "</userinput><computeroutput>\n"
419 "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n"
420 "Would you be willing, once your first certificate is successfully issued, to\n"
421 "share your email address with the Electronic Frontier Foundation, a founding\n"
422 "partner of the Let's Encrypt project and the non-profit organization that\n"
423 "develops Certbot? We'd like to send you email about our work encrypting the web,\n"
424 "EFF news, campaigns, and ways to support digital freedom.\n"
425 "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n"
426 "(Y)es/(N)o: </computeroutput><userinput> N\n"
427 "</userinput><computeroutput>\n"
428 "Account registered.\n"
429 "\n"
430 "No names were found in your configuration files. Please enter in your domain\n"
431 "name(s) (comma and/or space separated) (Enter 'c' to cancel): </computeroutput><userinput>falcot.com\n"
432 "</userinput><computeroutput>\n"
433 "Requesting a certificate for falcot.com\n"
434 "Performing the following challenges:\n"
435 "http-01 challenge for falcot.com\n"
436 "Enabled Apache rewrite module\n"
437 "Waiting for verification...\n"
438 "Cleaning up challenges\n"
439 "Created an SSL vhost at /etc/apache2/sites-available/000-default-le-ssl.conf\n"
440 "Enabled Apache socache_shmcb module\n"
441 "Enabled Apache ssl module\n"
442 "Deploying Certificate to VirtualHost /etc/apache2/sites-available/000-default-le-ssl.conf\n"
443 "Enabling available site: /etc/apache2/sites-available/000-default-le-ssl.conf\n"
444 "\n"
445 "Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.\n"
446 "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n"
447 "1: No redirect - Make no further changes to the webserver configuration.\n"
448 "2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for\n"
449 "new sites, or if you're confident your site works on HTTPS. You can undo this\n"
450 "change by editing your web server's configuration.\n"
451 "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n"
452 "Select the appropriate number [1-2] then [enter] (press 'c' to cancel):</computeroutput> <userinput>2\n"
453 "</userinput><computeroutput>\n"
454 "Enabled Apache rewrite module\n"
455 "Redirecting vhost in /etc/apache2/sites-enabled/000-default.conf to ssl vhost in /etc/apache2/sites-available/000-default-le-ssl.conf\n"
456 "\n"
457 "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n"
458 "Congratulations! You have successfully enabled https://falcot.com\n"
459 "\n"
460 "You should test your configuration at:\n"
461 "https://www.ssllabs.com/ssltest/analyze.html?d=falcot.com\n"
462 "- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n"
463 "\n"
464 "IMPORTANT NOTES:\n"
465 " - Congratulations! Your certificate and chain have been saved at:\n"
466 " /etc/letsencrypt/live/falcot.com/fullchain.pem\n"
467 " Your key file has been saved at:\n"
468 " /etc/letsencrypt/live/falcot.com/privkey.pem\n"
469 " Your cert will expire on 2022-06-04. To obtain a new or tweaked\n"
470 " version of this certificate in the future, simply run certbot again\n"
471 " with the \"certonly\" option. To non-interactively renew *all* of\n"
472 " your certificates, run \"certbot renew\"\n"
473 " - Your account credentials have been saved in your Certbot\n"
474 " configuration directory at /etc/letsencrypt. You should make a\n"
475 " secure backup of this folder now. This configuration directory will\n"
476 " also contain certificates and private keys obtained by Certbot so\n"
477 " making regular backups of this folder is ideal.\n"
478 " - If you like Certbot, please consider supporting our work by:\n"
479 "\n"
480 " Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate\n"
481 " Donating to EFF: https://eff.org/donate-le\n"
482 "</computeroutput>"
483 msgstr ""
484
485 #, fuzzy
486 #| msgid "<emphasis>CULTURE</emphasis> Private address range"
487 msgid "<emphasis>CULTURE</emphasis> The Let's Encrypt Initiative"
488 msgstr "<emphasis>CULTURE</emphasis> Plages d'adresses privées"
489
490 #, fuzzy
491 #| msgid "<primary>IPsec</primary>"
492 msgid "<primary>Let's Encrypt</primary>"
493 msgstr "<primary>IPsec</primary>"
494
495 msgid "The <ulink url=\"https://letsencrypt.org/\">Let's Encrypt</ulink> 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 <acronym>EFF</acronym> 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). <ulink type=\"block\" url=\"https://letsencrypt.org/how-it-works/\" />"
496 msgstr ""
497
498 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 <command>certonly</command> and <command>--webroot</command>. You would have to specify a <command>--webroot-path</command> (abbreviated <command>-w</command>), which should contain the files served. The command looks as follows:"
499 msgstr ""
500
501 msgid "<computeroutput># </computeroutput><userinput>certbot certonly --webroot -w <replaceable>/var/www/html</replaceable> -d www.<replaceable>DOMAIN</replaceable>.com -d <replaceable>DOMAIN</replaceable>.com</userinput>"
502 msgstr ""
503
504 msgid "You need to restart all services using the certificates that you have created."
505 msgstr ""
506
507 #, fuzzy
508 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
509 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/cron.d/certbot</filename></secondary>"
510 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
511
512 #, fuzzy
513 #| msgid "<primary><command>route</command></primary>"
514 msgid "<primary><command>certbot</command></primary>"
515 msgstr "<primary><command>route</command></primary>"
516
517 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 <command>certbot renew</command> command. However, we shouldn't renew every certificate manually, but automatically. A basic cron job is included by <emphasis role=\"pkg\">certbot</emphasis> in <filename>/etc/cron.d/certbot</filename>. To ensure that certificates can be automatically renewed, you can execute <command>certbot renew --dry-run</command>."
518 msgstr ""
519
520 msgid "Public Key Infrastructure: <emphasis>easy-rsa</emphasis>"
521 msgstr "Infrastructure de clés publiques <emphasis>easy-rsa</emphasis>"
522
523 #, fuzzy
524 #| msgid "<primary>PKI (Public Key Infrastructure)</primary>"
525 msgid "<primary>PKI</primary><seealso>Public Key Infrastructure</seealso>"
526 msgstr "<primary>PKI (Public Key Infrastructure)</primary>"
527
528 msgid "<primary>Public Key Infrastructure</primary>"
529 msgstr "<primary>infrastructure de clés publiques</primary>"
530
531 #, fuzzy
532 #| msgid "<primary>NAT</primary>"
533 msgid "<primary>X.509</primary>"
534 msgstr "<primary>NAT</primary>"
535
536 msgid "<primary><emphasis>easy-rsa</emphasis></primary>"
537 msgstr "<primary><emphasis>easy-rsa</emphasis></primary>"
538
539 msgid "<primary>RSA (algorithm)</primary>"
540 msgstr "<primary>RSA (algorithme)</primary>"
541
542 #, fuzzy
543 #| msgid "<primary>port</primary><secondary>TCP</secondary>"
544 msgid "<primary>algorithm</primary><secondary>RSA</secondary>"
545 msgstr "<primary>port</primary><secondary>TCP</secondary>"
546
547 msgid "<primary>key pair</primary>"
548 msgstr "<primary>biclé</primary>"
549
550 #, fuzzy
551 #| 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."
552 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."
553 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é »."
554
555 #, fuzzy
556 #| 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 <emphasis role=\"pkg\">easy-rsa</emphasis> package provides tools to serve as an X.509 certification infrastructure, implemented as a set of scripts using the <command>openssl</command> command."
557 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 <emphasis role=\"pkg\">easy-rsa</emphasis> package provides tools to serve as an X.509 certification infrastructure, implemented as a set of scripts using the <command>openssl</command> command."
558 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 <emphasis role=\"pkg\">easy-rsa</emphasis> peut être employé comme infrastructure de gestion de certificats X.509, il s'appuie sur un ensemble de scripts utilisant la commande <command>openssl</command>."
559
560 #, fuzzy
561 #| msgid "<emphasis>CULTURE</emphasis> SSL and TLS"
562 msgid "<emphasis>ALTERNATIVE</emphasis> GnuTLS"
563 msgstr "<emphasis>CULTURE</emphasis> SSL et TLS"
564
565 msgid "<primary>DTLS</primary>"
566 msgstr "<primary>DTLS</primary>"
567
568 msgid "<primary>GnuTLS</primary>"
569 msgstr "<primary>GnuTLS</primary>"
570
571 msgid "GnuTLS can also be used to generate a CA, and deal with other technologies around the TLS, DTLS and SSL protocols."
572 msgstr ""
573
574 msgid "The package <emphasis role=\"pkg\">gnutls-bin</emphasis> contains the command-line utilities. It is also useful to install the <emphasis role=\"pkg\">gnutls-doc</emphasis> package, which includes extensive documentation."
575 msgstr ""
576
577 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."
578 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."
579
580 msgid ""
581 "\n"
582 "<computeroutput>$ </computeroutput><userinput>make-cadir pki-falcot\n"
583 "</userinput><computeroutput>$ </computeroutput><userinput>cd pki-falcot</userinput>"
584 msgstr ""
585 "\n"
586 "<computeroutput>$ </computeroutput><userinput>make-cadir pki-falcot\n"
587 "</userinput><computeroutput>$ </computeroutput><userinput>cd pki-falcot</userinput>"
588
589 #, fuzzy
590 #| msgid "They then store the required parameters into the <filename>vars</filename> file, especially those named with a <literal>KEY_</literal> prefix; these variables are then integrated into the environment:"
591 msgid "They then store the required parameters into the <filename>vars</filename> file, which can be uncommented and edited:"
592 msgstr "Ils placent les paramètres nécessaires dans le fichier <filename>vars</filename> et notamment ceux débutant par <literal>KEY_</literal>, puis ils les intègrent dans l'environnement :"
593
594 msgid ""
595 "\n"
596 "<computeroutput>$ </computeroutput><userinput>grep EASYRSA vars\n"
597 "</userinput><computeroutput><![CDATA[if [ -z \"$EASYRSA_CALLER\" ]; then\n"
598 "# easyrsa. More specific variables for specific files (e.g., EASYRSA_SSL_CONF)\n"
599 "#set_var EASYRSA\t\"${0%/*}\"\n"
600 "#set_var EASYRSA_OPENSSL\t\"openssl\"\n"
601 "#set_var EASYRSA_OPENSSL\t\"C:/Program Files/OpenSSL-Win32/bin/openssl.exe\"\n"
602 "#set_var EASYRSA_PKI\t\t\"$PWD/pki\"\n"
603 "#set_var EASYRSA_TEMP_DIR\t\"$EASYRSA_PKI\"\n"
604 "#set_var EASYRSA_DN\t\"cn_only\"\n"
605 "set_var EASYRSA_REQ_COUNTRY\t\"FR\"\n"
606 "set_var EASYRSA_REQ_PROVINCE\t\"Loire\"\n"
607 "set_var EASYRSA_REQ_CITY\t\"Saint-Étienne\"\n"
608 "set_var EASYRSA_REQ_ORG\t\"Falcot Corp\"\n"
609 "set_var EASYRSA_REQ_EMAIL\t\"[email protected]\"\n"
610 "set_var EASYRSA_REQ_OU\t\t\"Certificate authority\"\n"
611 "#set_var EASYRSA_KEY_SIZE\t2048\n"
612 "#set_var EASYRSA_ALGO\t\trsa\n"
613 "#set_var EASYRSA_CURVE\t\tsecp384r1\n"
614 "#set_var EASYRSA_CA_EXPIRE\t3650\n"
615 "#set_var EASYRSA_CERT_EXPIRE\t825\n"
616 "#set_var EASYRSA_CRL_DAYS\t180\n"
617 "#set_var EASYRSA_CERT_RENEW\t30\n"
618 "#set_var EASYRSA_RAND_SN\t\"yes\"\n"
619 "#set_var EASYRSA_NS_SUPPORT\t\"no\"\n"
620 "#set_var EASYRSA_NS_COMMENT\t\"Easy-RSA Generated Certificate\"\n"
621 "#set_var EASYRSA_TEMP_FILE\t\"$EASYRSA_PKI/extensions.temp\"\n"
622 "# when undefined here, default behaviour is to look in $EASYRSA_PKI first, then\n"
623 "# fallback to $EASYRSA for the 'x509-types' dir. You may override this\n"
624 "#set_var EASYRSA_EXT_DIR\t\"$EASYRSA/x509-types\"\n"
625 "#set_var EASYRSA_KDC_REALM \"CHANGEME.EXAMPLE.COM\"\n"
626 "# EASYRSA_PKI or EASYRSA dir (in that order.) NOTE that this file is Easy-RSA\n"
627 "#set_var EASYRSA_SSL_CONF\t\"$EASYRSA/openssl-easyrsa.cnf\"\n"
628 "#set_var EASYRSA_REQ_CN\t\t\"ChangeMe\"\n"
629 "#set_var EASYRSA_DIGEST\t\t\"sha256\"\n"
630 "#set_var EASYRSA_BATCH\t\t\"\"\n"
631 "]]>$ </computeroutput><userinput>vim vars\n"
632 "</userinput><computeroutput>$ </computeroutput>"
633 msgstr ""
634
635 msgid "Now we prepare the public key infrastructure directory with the following command:"
636 msgstr ""
637
638 #, fuzzy
639 #| msgid ""
640 #| "\n"
641 #| "<computeroutput>$ </computeroutput><userinput>make-cadir pki-falcot\n"
642 #| "</userinput><computeroutput>$ </computeroutput><userinput>cd pki-falcot</userinput>"
643 msgid ""
644 "\n"
645 "<computeroutput>$ </computeroutput><userinput>./easyrsa init-pki\n"
646 "</userinput><computeroutput>\n"
647 "\n"
648 "init-pki complete; you may now create a CA or requests.\n"
649 "Your newly created PKI dir is: /home/debian/pki-falcot/pki\n"
650 "\n"
651 "</computeroutput>"
652 msgstr ""
653 "\n"
654 "<computeroutput>$ </computeroutput><userinput>make-cadir pki-falcot\n"
655 "</userinput><computeroutput>$ </computeroutput><userinput>cd pki-falcot</userinput>"
656
657 #, fuzzy
658 #| 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 <filename>keys/ca.crt</filename> and <filename>keys/ca.key</filename> during this step):"
659 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 <filename>pki/ca.crt</filename> and <filename>pki/private/ca.key</filename> during this step). We can add the option <literal>nopass</literal> to avoid entering a password each time the private key is used:"
660 msgstr "Ils créent alors la biclé de l'autorité de certification (les fichiers <filename>keys/ca.crt</filename> et <filename>keys/ca.key</filename> sont créés au cours de cette opération) :"
661
662 #, fuzzy
663 #| msgid ""
664 #| "\n"
665 #| "<computeroutput>$ </computeroutput><userinput>./build-ca</userinput>\n"
666 #| "<computeroutput>Generating a 2048 bit RSA private key\n"
667 #| "...................................................................+++\n"
668 #| "...+++\n"
669 #| "writing new private key to 'ca.key'\n"
670 #| "-----\n"
671 #| "You are about to be asked to enter information that will be incorporated\n"
672 #| "into your certificate request.\n"
673 #| "What you are about to enter is what is called a Distinguished Name or a DN.\n"
674 #| "There are quite a few fields but you can leave some blank\n"
675 #| "For some fields there will be a default value,\n"
676 #| "If you enter '.', the field will be left blank.\n"
677 #| "-----\n"
678 #| "Country Name (2 letter code) [FR]:\n"
679 #| "State or Province Name (full name) [Loire]:\n"
680 #| "Locality Name (eg, city) [Saint-Étienne]:\n"
681 #| "Organization Name (eg, company) [Falcot Corp]:\n"
682 #| "Organizational Unit Name (eg, section) [Certificate authority]:\n"
683 #| "Common Name (eg, your name or your server's hostname) [Falcot Corp CA]:\n"
684 #| "Name [Certificate authority for Falcot Corp]:\n"
685 #| "Email Address [[email protected]]:\n"
686 #| "</computeroutput>"
687 msgid ""
688 "\n"
689 "<computeroutput>$ </computeroutput><userinput>./easyrsa build-ca nopass</userinput>\n"
690 "<computeroutput>\n"
691 "Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n"
692 "Generating RSA private key, 2048 bit long modulus (2 primes)\n"
693 "..................+++++\n"
694 "...............................+++++\n"
695 "e is 65537 (0x010001)\n"
696 "You are about to be asked to enter information that will be incorporated\n"
697 "into your certificate request.\n"
698 "What you are about to enter is what is called a Distinguished Name or a DN.\n"
699 "There are quite a few fields but you can leave some blank\n"
700 "For some fields there will be a default value,\n"
701 "If you enter '.', the field will be left blank.\n"
702 "-----\n"
703 "Common Name (eg: your user, host, or server name) [Easy-RSA CA]:\n"
704 "\n"
705 "CA creation complete and you may now import and sign cert requests.\n"
706 "Your new CA certificate file for publishing is at:\n"
707 "/home/debian/pki-falcot/pki/ca.crt\n"
708 "\n"
709 "</computeroutput>"
710 msgstr ""
711 "\n"
712 "<computeroutput>$ </computeroutput><userinput>./build-ca</userinput>\n"
713 "<computeroutput>Generating a 2048 bit RSA private key\n"
714 "...................................................................+++\n"
715 "...+++\n"
716 "writing new private key to 'ca.key'\n"
717 "-----\n"
718 "You are about to be asked to enter information that will be incorporated\n"
719 "into your certificate request.\n"
720 "What you are about to enter is what is called a Distinguished Name or a DN.\n"
721 "There are quite a few fields but you can leave some blank\n"
722 "For some fields there will be a default value,\n"
723 "If you enter '.', the field will be left blank.\n"
724 "-----\n"
725 "Country Name (2 letter code) [FR]:\n"
726 "State or Province Name (full name) [Loire]:\n"
727 "Locality Name (eg, city) [Saint-Étienne]:\n"
728 "Organization Name (eg, company) [Falcot Corp]:\n"
729 "Organizational Unit Name (eg, section) [Certificate authority]:\n"
730 "Common Name (eg, your name or your server's hostname) [Falcot Corp CA]:\n"
731 "Name [Certificate authority for Falcot Corp]:\n"
732 "Email Address [[email protected]]:\n"
733 "</computeroutput>"
734
735 #, fuzzy
736 #| msgid "<primary><filename>named.conf</filename></primary>"
737 msgid "<primary><filename>dh.pem</filename></primary>"
738 msgstr "<primary><filename>named.conf</filename></primary>"
739
740 #, fuzzy
741 #| 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 <literal>vpn.falcot.com</literal>; this name is re-used for the generated key files (<filename>keys/vpn.falcot.com.crt</filename> for the public certificate, <filename>keys/vpn.falcot.com.key</filename> for the private key):"
742 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 <xref linkend=\"sect.virtual-private-network\" />) that is identified by the DNS name <literal>vpn.falcot.com</literal>; this name is re-used for the generated key files (<filename>keys/vpn.falcot.com.crt</filename> for the public certificate, <filename>keys/vpn.falcot.com.key</filename> for the private key):"
743 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 <literal>vpn.falcot.com</literal> ; ce nom est employé dans les fichiers de clés générés (<filename>keys/vpn.falcot.com.crt</filename> pour le certificat public et <filename>keys/vpn.falcot.com.key</filename> pour la clé privée) :"
744
745 msgid ""
746 "\n"
747 "<computeroutput>$ </computeroutput><userinput>./easyrsa gen-req vpn.falcot.com nopass\n"
748 "</userinput><computeroutput>\n"
749 "Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n"
750 "Generating a RSA private key\n"
751 "......................................+++++\n"
752 "..........................................................................+++++\n"
753 "writing new private key to '/home/debian/pki-falcot/pki/easy-rsa-5515.0PwyXl/tmp.g1c6u6'\n"
754 "-----\n"
755 "You are about to be asked to enter information that will be incorporated\n"
756 "into your certificate request.\n"
757 "What you are about to enter is what is called a Distinguished Name or a DN.\n"
758 "There are quite a few fields but you can leave some blank\n"
759 "For some fields there will be a default value,\n"
760 "If you enter '.', the field will be left blank.\n"
761 "-----\n"
762 "Common Name (eg: your user, host, or server name) [vpn.falcot.com]:\n"
763 "\n"
764 "Keypair and certificate request completed. Your files are:\n"
765 "req: /home/debian/pki-falcot/pki/reqs/vpn.falcot.com.req\n"
766 "key: /home/debian/pki-falcot/pki/private/vpn.falcot.com.key\n"
767 "\n"
768 "\n"
769 "$ </computeroutput><userinput>./easyrsa sign-req server vpn.falcot.com\n"
770 "</userinput><computeroutput>\n"
771 "Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n"
772 "\n"
773 "\n"
774 "You are about to sign the following certificate.\n"
775 "Please check over the details shown below for accuracy. Note that this request\n"
776 "has not been cryptographically verified. Please be sure it came from a trusted\n"
777 "source or that you have verified the request checksum with the sender.\n"
778 "\n"
779 "Request subject, to be signed as a server certificate for 825 days:\n"
780 "\n"
781 "subject=\n"
782 " commonName = vpn.falcot.com\n"
783 "\n"
784 "\n"
785 "Type the word 'yes' to continue, or any other input to abort.\n"
786 " Confirm request details: <userinput>yes\n"
787 "</userinput>Using configuration from /home/debian/pki-falcot/pki/easy-rsa-5603.87iCIa/tmp.u8r8Fj\n"
788 "Check that the request matches the signature\n"
789 "Signature ok\n"
790 "The Subject's Distinguished Name is as follows\n"
791 "commonName :ASN.1 12:'vpn.falcot.com'\n"
792 "Certificate is to be certified until May 27 15:26:29 2024 GMT (825 days)\n"
793 "\n"
794 "Write out database with 1 new entries\n"
795 "Data Base Updated\n"
796 "\n"
797 "Certificate created at: /home/debian/pki-falcot/pki/issued/vpn.falcot.com.crt\n"
798 "\n"
799 "\n"
800 "$ </computeroutput><userinput>./easyrsa gen-dh\n"
801 "</userinput><computeroutput>\n"
802 "Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n"
803 "Generating DH parameters, 2048 bit long safe prime, generator 2\n"
804 "This is going to take a long time\n"
805 "[…]\n"
806 "\n"
807 "DH parameters of size 2048 created at /home/debian/pki-falcot/pki/dh.pem\n"
808 "\n"
809 "</computeroutput>"
810 msgstr ""
811
812 msgid "The following step creates certificates for the VPN clients; one certificate is required for each computer or person allowed to use the VPN:"
813 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 :"
814
815 msgid ""
816 "\n"
817 "<computeroutput>$ </computeroutput><userinput>./easyrsa build-client-full JoeSmith nopass\n"
818 "</userinput><computeroutput>\n"
819 "Using SSL: openssl OpenSSL 1.1.1k 25 Mar 2021\n"
820 "Generating a RSA private key\n"
821 "...................................+++++\n"
822 ".........................................................................................+++++\n"
823 "writing new private key to '/home/debian/pki-falcot/pki/easy-rsa-5694.DOYwSn/tmp.RKlbOE'\n"
824 "-----\n"
825 "Using configuration from /home/debian/pki-falcot/pki/easy-rsa-5694.DOYwSn/tmp.d5QHAC\n"
826 "Check that the request matches the signature\n"
827 "Signature ok\n"
828 "The Subject's Distinguished Name is as follows\n"
829 "commonName :ASN.1 12:'JoeSmith'\n"
830 "Certificate is to be certified until May 27 15:29:25 2024 GMT (825 days)\n"
831 "\n"
832 "Write out database with 1 new entries\n"
833 "Data Base Updated\n"
834 "\n"
835 "</computeroutput>"
836 msgstr ""
837
838 msgid "Virtual Private Network"
839 msgstr "Réseau privé virtuel"
840
841 msgid "<primary>network</primary><secondary>virtual private</secondary>"
842 msgstr "<primary>réseau</primary><secondary>privé virtuel</secondary>"
843
844 msgid "<primary>VPN</primary>"
845 msgstr "<primary>VPN</primary>"
846
847 #, fuzzy
848 #| msgid "<primary>virtual private network</primary>"
849 msgid "<primary>virtual private network</primary><seealso>VPN</seealso>"
850 msgstr "<primary><foreignphrase>Virtual Private Network</foreignphrase></primary>"
851
852 #, fuzzy
853 #| msgid "<primary>packet</primary><secondary>IP</secondary>"
854 msgid "<primary>IP</primary><secondary>IPsec</secondary>"
855 msgstr "<primary>paquet</primary><secondary>IP</secondary>"
856
857 msgid "A <emphasis>Virtual Private Network</emphasis> (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."
858 msgstr "Un réseau privé virtuel (<foreignphrase>Virtual Private Network</foreignphrase>, 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."
859
860 #, fuzzy
861 #| 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."
862 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."
863 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."
864
865 msgid "OpenVPN"
866 msgstr "OpenVPN"
867
868 msgid "<primary>OpenVPN</primary>"
869 msgstr "<primary>OpenVPN</primary>"
870
871 #, fuzzy
872 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
873 msgid "<primary>VPN</primary><secondary>OpenVPN</secondary>"
874 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
875
876 #, fuzzy
877 #| msgid "<primary>network</primary><secondary>virtual private</secondary>"
878 msgid "<primary>network</primary><secondary><literal>tun</literal> interface</secondary>"
879 msgstr "<primary>réseau</primary><secondary>privé virtuel</secondary>"
880
881 #, fuzzy
882 #| msgid "<primary>network</primary><secondary>virtual private</secondary>"
883 msgid "<primary>network</primary><secondary><literal>tap</literal> interface</secondary>"
884 msgstr "<primary>réseau</primary><secondary>privé virtuel</secondary>"
885
886 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 <literal>tun</literal> (for IP-level tunnels) and <literal>tap</literal> (for Ethernet-level tunnels) interfaces are supported. In practice, <literal>tun</literal> 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."
887 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 <literal>tun</literal> (tunnel de niveau IP) que <literal>tap</literal> (tunnel de niveau Ethernet). Concrètement, on emploiera des interfaces <literal>tun</literal> sauf lorsque l'on souhaite intégrer les clients VPN dans le réseau local du serveur par le biais d'un pont Ethernet <foreignphrase>(bridge)</foreignphrase>."
888
889 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."
890 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."
891
892 msgid "Configuring the OpenVPN Server"
893 msgstr "Configuration du serveur OpenVPN"
894
895 #, fuzzy
896 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
897 msgid "<primary>OpenVPN</primary><secondary>server</secondary>"
898 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
899
900 #, fuzzy
901 #| msgid "Now all certificates have been created, they need to be copied where appropriate: the root certificate's public key (<filename>keys/ca.crt</filename>) will be stored on all machines (both server and clients) as <filename>/etc/ssl/certs/Falcot_CA.crt</filename>. The server's certificate is installed only on the server (<filename>keys/vpn.falcot.com.crt</filename> goes to <filename>/etc/ssl/vpn.falcot.com.crt</filename>, and <filename>keys/vpn.falcot.com.key</filename> goes to <filename>/etc/ssl/private/vpn.falcot.com.key</filename> with restricted permissions so that only the administrator can read it), with the corresponding Diffie-Hellman parameters (<filename>keys/dh2048.pem</filename>) installed to <filename>/etc/openvpn/dh2048.pem</filename>. Client certificates are installed on the corresponding VPN client in a similar fashion."
902 msgid "After all certificates have been created (follow the instructions from <xref linkend=\"sect.easy-rsa\" />), they need to be copied where appropriate: the root certificate's public key (<filename>pki/ca.crt</filename>) will be stored on all machines (both server and clients) as <filename>/etc/ssl/certs/Falcot_CA.crt</filename>. The server's certificate is installed only on the server (<filename>pki/issued/vpn.falcot.com.crt</filename> goes to <filename>/etc/ssl/certs/vpn.falcot.com.crt</filename>, and <filename>pki/private/vpn.falcot.com.key</filename> goes to <filename>/etc/ssl/private/vpn.falcot.com.key</filename> with restricted permissions so that only the administrator can read it), with the corresponding Diffie-Hellman parameters (<filename>pki/dh.pem</filename>) installed to <filename>/etc/openvpn/dh.pem</filename>. Client certificates are installed on the corresponding VPN client in a similar fashion."
903 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 (<filename>keys/ca.crt</filename>) se trouvera sur toutes les machines (serveur et clients), en <filename>/etc/ssl/certs/Falcot_CA.crt</filename>. Le certificat serveur s'installe uniquement sur le serveur (<filename>keys/vpn.falcot.com.crt</filename> en <filename>/etc/ssl/vpn.falcot.com.crt</filename> et <filename>keys/vpn.falcot.com.key</filename> en <filename>/etc/ssl/private/vpn.falcot.com.key</filename> avec des droits restreints pour que seul l'administrateur puisse le lire) accompagné des paramètres Diffie-Hellman (<filename>keys/dh2048.pem</filename>) que l'on peut installer en <filename>/etc/openvpn/dh2048.pem</filename>. Chaque certificat client s'installe de manière similaire sur le client VPN correspondant."
904
905 #, fuzzy
906 #| msgid "<primary>firewall</primary><secondary>IPv6</secondary>"
907 msgid "<primary><filename>/etc</filename></primary><secondary>/etc/ssl/</secondary>"
908 msgstr "<primary>IPv6</primary><secondary>pare-feu</secondary>"
909
910 #, fuzzy
911 #| msgid "<primary>firewall</primary><secondary>IPv6</secondary>"
912 msgid "<primary><filename>/etc</filename></primary><secondary>/etc/openvpn/dh.pem</secondary>"
913 msgstr "<primary>IPv6</primary><secondary>pare-feu</secondary>"
914
915 #, fuzzy
916 #| msgid "<primary>traffic</primary><secondary>control</secondary>"
917 msgid "<primary><filename>/etc</filename></primary><secondary>/etc/openvpn/*.conf</secondary>"
918 msgstr "<primary>trafic</primary><secondary>contrôle</secondary>"
919
920 #, fuzzy
921 #| msgid "By default, the OpenVPN initialization script tries starting all virtual private networks defined in <filename>/etc/openvpn/*.conf</filename>. Setting up a VPN server is therefore a matter of storing a corresponding configuration file in this directory. A good starting point is <filename>/usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz</filename>, which leads to a rather standard server. Of course, some parameters need to be adapted: <literal>ca</literal>, <literal>cert</literal>, <literal>key</literal> and <literal>dh</literal> need to describe the selected locations (respectively, <literal>/etc/ssl/certs/Falcot_CA.crt</literal>, <literal>/etc/ssl/vpn.falcot.com.crt</literal>, <literal>/etc/ssl/private/vpn.falcot.com.key</literal> and <literal>/etc/openvpn/dh2048.pem</literal>). The <literal>server 10.8.0.0 255.255.255.0</literal> directive defines the subnet to be used by the VPN; the server uses the first IP address in that range (<literal>10.8.0.1</literal>) and the rest of the addresses are allocated to clients."
922 msgid "By default, the OpenVPN initialization script tries starting all virtual private networks defined in <filename>/etc/openvpn/*.conf</filename>. Setting up a VPN server is therefore a matter of storing a corresponding configuration file in this directory. A good starting point is <filename>/usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz</filename>, which leads to a rather standard server. Of course, some parameters need to be adapted: <literal>ca</literal>, <literal>cert</literal>, <literal>key</literal> and <literal>dh</literal> need to describe the selected locations (respectively, <literal>/etc/ssl/certs/Falcot_CA.crt</literal>, <literal>/etc/ssl/vpn.falcot.com.crt</literal>, <literal>/etc/ssl/private/vpn.falcot.com.key</literal> and <literal>/etc/openvpn/dh.pem</literal>). The <literal>server 10.8.0.0 255.255.255.0</literal> directive defines the subnet to be used by the VPN; the server uses the first IP address in that range (<literal>10.8.0.1</literal>) and the rest of the addresses are allocated to clients."
923 msgstr "Par défaut, le script d'initialisation d'OpenVPN tente de démarrer tous les réseaux privés virtuels définis dans <filename>/etc/openvpn/*.conf</filename>. 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 <filename>/usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz</filename>, une configuration serveur relativement standard. Il faut évidemment éditer les paramètres <literal>ca</literal>, <literal>cert</literal>, <literal>key</literal> et <literal>dh</literal> pour indiquer les emplacements retenus (<literal>/etc/ssl/certs/Falcot_CA.crt</literal>, <literal>/etc/ssl/vpn.falcot.com.crt</literal>, <literal>/etc/ssl/private/vpn.falcot.com.key</literal> et <literal>/etc/openvpn/dh2048.pem</literal> respectivement). La directive <literal>server 10.8.0.0 255.255.255.0</literal> indique le sous-réseau employé par le VPN : le serveur dispose de la première IP (<literal>10.8.0.1</literal>) et les clients se voient attribuer le reste des adresses."
924
925 #, fuzzy
926 #| msgid "<primary>traffic</primary><secondary>control</secondary>"
927 msgid "<primary><filename>/etc</filename></primary><secondary>/etc/network/interfaces</secondary>"
928 msgstr "<primary>trafic</primary><secondary>contrôle</secondary>"
929
930 #, fuzzy
931 #| msgid "<primary>network</primary><secondary>virtual private</secondary>"
932 msgid "<primary>network</primary><secondary>virtual interface</secondary>"
933 msgstr "<primary>réseau</primary><secondary>privé virtuel</secondary>"
934
935 #, fuzzy
936 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
937 msgid "<primary>OpenVPN</primary><secondary>network interface</secondary>"
938 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
939
940 #, fuzzy
941 #| msgid "With this configuration, starting OpenVPN creates the virtual network interface, usually under the <literal>tun0</literal> 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, <command>openvpn --mktun --dev vpn --dev-type tun</command> creates a virtual network interface named <literal>vpn</literal> with type <literal>tun</literal>; this command can easily be integrated in the firewall configuration script, or in an <literal>up</literal> directive of the <filename>/etc/network/interfaces</filename> file. The OpenVPN configuration file must also be updated accordingly, with the <literal>dev vpn</literal> and <literal>dev-type tun</literal> directives."
942 msgid "With this configuration, starting OpenVPN creates the virtual network interface, usually under the <literal>tun0</literal> 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, <command>openvpn --mktun --dev vpn --dev-type tun</command> creates a virtual network interface named <literal>vpn</literal> with type <literal>tun</literal>; this command can easily be integrated in the firewall configuration script, or in an <literal>up</literal> directive of the <filename>/etc/network/interfaces</filename> file, or a <emphasis role=\"package\">udev</emphasis> rule can be added to that end. The OpenVPN configuration file must also be updated accordingly, with the <literal>dev vpn</literal> and <literal>dev-type tun</literal> directives."
943 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 <literal>tun0</literal>. 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 <command>openvpn --mktun --dev vpn --dev-type tun</command> crée une interface réseau virtuelle nommée <literal>vpn</literal> et de type <literal>tun</literal> ; elle peut facilement s'intégrer au début du script de configuration du pare-feu ou dans une directive <literal>up</literal> de <filename>/etc/network/interfaces</filename>. Le fichier de configuration d'OpenVPN doit être mis à jour en conséquence avec les directives <literal>dev vpn</literal> et <literal>dev-type tun</literal>."
944
945 #, fuzzy
946 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
947 msgid "<primary>OpenVPN</primary><secondary>push route</secondary>"
948 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
949
950 msgid "Barring further action, VPN clients can only access the VPN server itself by way of the <literal>10.8.0.1</literal> address. Granting the clients access to the local network (192.168.0.0/24), requires adding a <literal>push route 192.168.0.0 255.255.255.0</literal> 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 <xref linkend=\"sect.gateway\" />)."
951 msgstr "Sans mesures supplémentaires, les clients VPN n'ont accès qu'au serveur VPN, par l'intermédiaire de l'adresse IP <literal>10.8.0.1</literal>. Pour donner accès au réseau local (192.168.0.0/24), il faut ajouter une directive <literal>push route 192.168.0.0 255.255.255.0</literal> à 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 <xref linkend=\"sect.gateway\" />)."
952
953 msgid "Configuring the OpenVPN Client"
954 msgstr "Configuration du client OpenVPN"
955
956 #, fuzzy
957 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
958 msgid "<primary>OpenVPN</primary><secondary>client</secondary>"
959 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
960
961 msgid "Setting up an OpenVPN client also requires creating a configuration file in <filename>/etc/openvpn/</filename>. A standard configuration can be obtained by using <filename>/usr/share/doc/openvpn/examples/sample-config-files/client.conf</filename> as a starting point. The <literal>remote vpn.falcot.com 1194</literal> directive describes the address and port of the OpenVPN server; the <literal>ca</literal>, <literal>cert</literal> and <literal>key</literal> also need to be adapted to describe the locations of the key files."
962 msgstr "Pour mettre en place un client OpenVPN, il faut également déposer un fichier de configuration dans <filename>/etc/openvpn/</filename>. On pourra s'inspirer de <filename>/usr/share/doc/openvpn/examples/sample-config-files/client.conf</filename> pour une configuration standard. La directive <literal>remote vpn.falcot.com 1194</literal> indique l'adresse et le port du serveur OpenVPN. Les directives <literal>ca</literal>, <literal>cert</literal> et <literal>key</literal> doivent aussi être modifiées pour indiquer l'emplacement des différentes clés."
963
964 #, fuzzy
965 #| msgid "<primary>network</primary><secondary>virtual private</secondary>"
966 msgid "<primary>OpenVPN</primary><secondary><literal>AUTOSTART</literal></secondary>"
967 msgstr "<primary>réseau</primary><secondary>privé virtuel</secondary>"
968
969 #, fuzzy
970 #| msgid "<primary>traffic</primary><secondary>limitation</secondary>"
971 msgid "<primary><filename>/etc</filename></primary><secondary>/etc/default/openvpn</secondary>"
972 msgstr "<primary>trafic</primary><secondary>limitation</secondary>"
973
974 #, fuzzy
975 #| msgid "<primary>server</primary><secondary>name</secondary>"
976 msgid "<primary>service</primary><secondary><filename>[email protected]</filename></secondary>"
977 msgstr "<primary>serveur</primary><secondary>de noms</secondary>"
978
979 #, fuzzy
980 #| msgid "If the VPN should not be started automatically on boot, set the <literal>AUTOSTART</literal> directive to <literal>none</literal> in the <filename>/etc/default/openvpn</filename> file. Starting or stopping a given VPN connection is always possible with the commands <command>service openvpn@<replaceable>name</replaceable> start</command> and <command>service openvpn@<replaceable>name</replaceable> stop</command> (where the connection <replaceable>name</replaceable> matches the one defined in <filename>/etc/openvpn/<replaceable>name</replaceable>.conf</filename>)."
981 msgid "If the VPN should not be started automatically on boot, set the <literal>AUTOSTART</literal> directive to <literal>none</literal> in the <filename>/etc/default/openvpn</filename> file. Starting or stopping a given VPN connection is always possible with the commands <command>systemctl start openvpn@<replaceable>name</replaceable></command> and <command>systemctl stop openvpn@<replaceable>name</replaceable></command> (where the connection <replaceable>name</replaceable> matches the one defined in <filename>/etc/openvpn/<replaceable>name</replaceable>.conf</filename>)."
982 msgstr "Si l'on ne veut pas que la connexion au VPN soit automatiquement mise en place au démarrage, on peut positionner <literal>AUTOSTART</literal> à <literal>none</literal> dans <filename>/etc/default/openvpn</filename>. On peut toujours démarrer/stopper une connexion VPN spécifique avec <command>service openvpn@<replaceable>nom</replaceable> start</command> et <command>service openvpn@<replaceable>nom</replaceable> stop</command> (la connexion <replaceable>nom</replaceable> correspond à celle définie dans <filename>/etc/openvpn/<replaceable>nom</replaceable>.conf</filename>)."
983
984 #, fuzzy
985 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
986 msgid "<primary>OpenVPN</primary><secondary><emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis></secondary>"
987 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
988
989 #, fuzzy
990 #| msgid "The <emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis> package contains an extension to Network Manager (see <xref linkend=\"sect.roaming-network-config\" />) 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. <indexterm><primary><emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis></primary></indexterm>"
991 msgid "The <emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis> package contains an extension to Network Manager (see <xref linkend=\"sect.roaming-network-config\" />) 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."
992 msgstr "Le paquet <emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis> est une extension de Network Manager (voir <xref linkend=\"sect.roaming-network-config\" />) 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. <indexterm><primary><emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis></primary></indexterm>"
993
994 #, fuzzy
995 #| msgid "<primary><emphasis role=\"pkg\">iputils-ping</emphasis></primary>"
996 msgid "<primary><emphasis role=\"pkg\">network-manager-openvpn-gnome</emphasis></primary>"
997 msgstr "<primary><emphasis>iputils-ping</emphasis></primary>"
998
999 msgid "Virtual Private Network with SSH"
1000 msgstr "Réseau privé virtuel avec SSH"
1001
1002 #, fuzzy
1003 #| msgid "<primary>port</primary><secondary>TCP</secondary>"
1004 msgid "<primary>SSH</primary><secondary>VPN</secondary>"
1005 msgstr "<primary>port</primary><secondary>TCP</secondary>"
1006
1007 msgid "<primary>PPP</primary>"
1008 msgstr "<primary>PPP</primary>"
1009
1010 #, fuzzy
1011 #| 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: <ulink type=\"block\" url=\"http://www.tldp.org/HOWTO/ppp-ssh/\" />"
1012 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: <ulink type=\"block\" url=\"https://www.tldp.org/HOWTO/ppp-ssh/\" />"
1013 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 : <ulink type=\"block\" url=\"http://www.tldp.org/HOWTO/ppp-ssh/\" />"
1014
1015 #, fuzzy
1016 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
1017 msgid "<primary>SSH</primary><secondary><literal>PermitTunnel</literal></secondary>"
1018 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
1019
1020 #, fuzzy
1021 #| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>"
1022 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ssh/sshd_config</filename></secondary>"
1023 msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>"
1024
1025 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 (<literal>tun*</literal>) 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 <literal>PermitTunnel</literal> to “yes” in the SSH server configuration file (<filename>/etc/ssh/sshd_config</filename>). When establishing the SSH connection, the creation of a tunnel must be explicitly requested with the <literal>-w any:any</literal> option (<literal>any</literal> can be replaced with the desired <literal>tun</literal> 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)."
1026 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 (<literal>tun*</literal>) 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 <literal>PermitTunnel</literal> à « yes » dans la configuration du serveur SSH (<filename>/etc/ssh/sshd_config</filename>). Lors de l'établissement de la connexion, il faut explicitement demander la création d'un tunnel en passant l'option <literal>-w any:any</literal> (on peut remplacer <literal>any</literal> par le numéro de périphérique <literal>tun</literal> 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)."
1027
1028 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."
1029 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."
1030
1031 #, fuzzy
1032 #| 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: <ulink type=\"block\" url=\"http://sites.inka.de/sites/bigred/devel/tcp-tcp.html\" /> VPNs over SSH should therefore be restricted to one-off tunnels with no performance constraints."
1033 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: <ulink type=\"block\" url=\"http://sites.inka.de/sites/bigred/devel/tcp-tcp.html\" />"
1034 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 <foreignphrase>timeout</foreignphrase> (délai maximal d'attente). Le site suivant détaille ces problèmes : <ulink type=\"block\" url=\"http://sites.inka.de/sites/bigred/devel/tcp-tcp.html\" /> On réservera donc l'utilisation de cette méthode aux tunnels établis ponctuellement et qui n'ont pas de fortes contraintes de performance."
1035
1036 msgid "VPNs over SSH should therefore be restricted to one-off tunnels with no performance constraints."
1037 msgstr ""
1038
1039 msgid "IPsec"
1040 msgstr "IPsec"
1041
1042 msgid "<primary>IPsec</primary>"
1043 msgstr "<primary>IPsec</primary>"
1044
1045 #, fuzzy
1046 #| msgid "<primary>protocol</primary><secondary>ESP</secondary>"
1047 msgid "<primary>Internet Protocol Security</primary><see>IPsec</see>"
1048 msgstr "<primary>protocole</primary><secondary>ESP</secondary>"
1049
1050 msgid "<primary><command>libreswan</command></primary>"
1051 msgstr "<primary><command>libreswan</command></primary>"
1052
1053 msgid "<primary><command>strongswan</command></primary>"
1054 msgstr "<primary><command>strongswan</command></primary>"
1055
1056 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 <emphasis role=\"pkg\">libreswan</emphasis> package or the <emphasis role=\"pkg\">strongswan</emphasis> package. Here we describe briefly the first of these options."
1057 msgstr ""
1058
1059 #, fuzzy
1060 #| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>"
1061 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ipsec.conf</filename></secondary>"
1062 msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>"
1063
1064 #, fuzzy
1065 #| msgid "<primary>server</primary><secondary>name</secondary>"
1066 msgid "<primary>IPsec</primary><secondary>tunnel</secondary>"
1067 msgstr "<primary>serveur</primary><secondary>de noms</secondary>"
1068
1069 msgid "First, we install the <emphasis role=\"pkg\">libreswan</emphasis> package. In concrete terms, each host's <filename>/etc/ipsec.conf</filename> contains the parameters for <emphasis>IPsec tunnels</emphasis> (or <emphasis>Security Associations</emphasis>, in the IPsec terminology) that the host is concerned with. There are many configuration examples in <filename>/usr/share/doc/libreswan/</filename>, but Libreswan's online documentation has more examples with explanations: <ulink type=\"block\" url=\"https://libreswan.org/wiki/\" />"
1070 msgstr ""
1071
1072 #, fuzzy
1073 #| msgid "<primary>server</primary><secondary>name</secondary>"
1074 msgid "<primary>service</primary><secondary><filename>ipsec.service</filename></secondary>"
1075 msgstr "<primary>serveur</primary><secondary>de noms</secondary>"
1076
1077 msgid "The IPsec service can be controlled with <command>systemctl</command>; for example, <command>systemctl start ipsec</command> will start the IPsec service."
1078 msgstr ""
1079
1080 msgid "<primary>IKE</primary>"
1081 msgstr "<primary>IKE</primary>"
1082
1083 #, fuzzy
1084 #| msgid "<primary>IPsec</primary>"
1085 msgid "<primary>IPsec Key Exchange</primary><see>IKE</see>"
1086 msgstr "<primary>IPsec</primary>"
1087
1088 #, fuzzy
1089 #| msgid "<primary>IPsec</primary><secondary>IPsec Key Exchange</secondary>"
1090 msgid "<primary>IPsec</primary><secondary>IPsec Key Exchange</secondary><seealso>IKE</seealso>"
1091 msgstr "<primary>IPsec</primary><secondary>échange de clefs IPsec</secondary>"
1092
1093 msgid "<primary><command>setkey</command></primary>"
1094 msgstr "<primary><command>setkey</command></primary>"
1095
1096 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."
1097 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."
1098
1099 msgid "<emphasis>CAUTION</emphasis> IPsec and NAT"
1100 msgstr "<emphasis>ATTENTION</emphasis> <emphasis>IPsec</emphasis> et <emphasis>NAT</emphasis>"
1101
1102 msgid "<primary>NAT</primary>"
1103 msgstr "<primary>NAT</primary>"
1104
1105 msgid "<primary>NAT-T</primary>"
1106 msgstr "<primary>NAT-T</primary>"
1107
1108 #, fuzzy
1109 #| msgid "<primary>NAT Traversal</primary>"
1110 msgid "<primary>NAT Traversal</primary><seealso>NAT-T</seealso>"
1111 msgstr "<primary><foreignphrase>Nat Traversal</foreignphrase></primary>"
1112
1113 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 <emphasis>NAT-T</emphasis> technique (for <emphasis>NAT Traversal</emphasis>), which basically encapsulates the IPsec packet within a standard UDP packet."
1114 msgstr "<emphasis>IPsec</emphasis> cohabite difficilement avec NAT sur un pare-feu. En effet, <emphasis>IPsec</emphasis> signant les paquets, toute modification de ceux-ci à la volée invalidera leur signature et les fera refuser. Les différentes implémentations d'<emphasis>IPsec</emphasis> proposent désormais la technique <foreignphrase>NAT-T</foreignphrase> (<foreignphrase>NAT Traversal</foreignphrase>, ou traversée de NAT), qui consiste à encapsuler le paquet <emphasis>IPsec</emphasis> dans un paquet UDP."
1115
1116 msgid "<emphasis>SECURITY</emphasis> IPsec and firewalls"
1117 msgstr "<emphasis>SÉCURITÉ</emphasis> <emphasis>IPsec</emphasis> et pare-feu"
1118
1119 msgid "<primary>ESP, protocol</primary>"
1120 msgstr "<primary>ESP, protocole</primary>"
1121
1122 msgid "<primary>AH, protocol</primary>"
1123 msgstr "<primary>AH, protocole</primary>"
1124
1125 msgid "<primary>protocol</primary><secondary>AH</secondary>"
1126 msgstr "<primary>protocole</primary><secondary>AH</secondary>"
1127
1128 msgid "<primary>protocol</primary><secondary>ESP</secondary>"
1129 msgstr "<primary>protocole</primary><secondary>ESP</secondary>"
1130
1131 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)."
1132 msgstr "Le fonctionnement d'<emphasis>IPsec</emphasis> 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 <emphasis>IPsec</emphasis> 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)."
1133
1134 msgid "PPTP"
1135 msgstr "PPTP"
1136
1137 msgid "<primary>PPTP</primary>"
1138 msgstr "<primary>PPTP</primary>"
1139
1140 msgid "<primary>GRE, protocol</primary>"
1141 msgstr "<primary>GRE, protocole</primary>"
1142
1143 msgid "<primary>protocol</primary><secondary>GRE</secondary>"
1144 msgstr "<primary>protocole</primary><secondary>GRE</secondary>"
1145
1146 msgid "PPTP (for <emphasis>Point-to-Point Tunneling Protocol</emphasis>) uses two communication channels, one for control data and one for payload data; the latter uses the GRE protocol (<emphasis>Generic Routing Encapsulation</emphasis>). A standard PPP link is then set up over the data exchange channel."
1147 msgstr "PPTP (<foreignphrase>Point-to-Point Tunneling Protocol</foreignphrase>, 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 — <foreignphrase>Generic Routing Encapsulation</foreignphrase>, ou encapsulation de routage générique). Une connexion PPP standard s'établit sur le canal d'échange de données."
1148
1149 msgid "Configuring the Client"
1150 msgstr "Configuration du client"
1151
1152 #, fuzzy
1153 #| msgid "<primary>port</primary><secondary>TCP</secondary>"
1154 msgid "<primary>PPTP</primary><secondary>Client</secondary>"
1155 msgstr "<primary>port</primary><secondary>TCP</secondary>"
1156
1157 msgid "<primary><emphasis role=\"pkg\">pptp-linux</emphasis></primary>"
1158 msgstr "<primary><emphasis>pptp-linux</emphasis></primary>"
1159
1160 msgid "The <emphasis role=\"pkg\">pptp-linux</emphasis> package contains an easily-configured PPTP client for Linux. The following instructions take their inspiration from the official documentation: <ulink type=\"block\" url=\"http://pptpclient.sourceforge.net/howto-debian.phtml\" />"
1161 msgstr "Le paquet <emphasis role=\"pkg\">pptp-linux</emphasis> est facile à configurer. Les instructions suivantes sont inspirées de sa documentation officielle : <ulink type=\"block\" url=\"http://pptpclient.sourceforge.net/howto-debian.phtml\" />"
1162
1163 #, fuzzy
1164 #| msgid "<primary>server</primary><secondary>name</secondary>"
1165 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ppp/</filename></secondary>"
1166 msgstr "<primary>serveur</primary><secondary>de noms</secondary>"
1167
1168 msgid "The Falcot administrators created several files: <filename>/etc/ppp/options.pptp</filename>, <filename>/etc/ppp/peers/falcot</filename>, <filename>/etc/ppp/ip-up.d/falcot</filename>, and <filename>/etc/ppp/ip-down.d/falcot</filename>."
1169 msgstr "Les administrateurs de Falcot ont créé plusieurs fichiers : <filename>/etc/ppp/options.pptp</filename>, <filename>/etc/ppp/peers/falcot</filename>, <filename>/etc/ppp/ip-up.d/falcot</filename> et <filename>/etc/ppp/ip-down.d/falcot</filename>."
1170
1171 msgid "The <filename>/etc/ppp/options.pptp</filename> file"
1172 msgstr "Fichier <filename>/etc/ppp/options.pptp</filename>"
1173
1174 msgid ""
1175 "\n"
1176 "# PPP options used for a PPTP connection\n"
1177 "lock\n"
1178 "noauth\n"
1179 "nobsdcomp\n"
1180 "nodeflate"
1181 msgstr ""
1182 "\n"
1183 "# Options PPP employées pour une connexion PPTP\n"
1184 "lock\n"
1185 "noauth\n"
1186 "nobsdcomp\n"
1187 "nodeflate"
1188
1189 msgid "The <filename>/etc/ppp/peers/falcot</filename> file"
1190 msgstr "Fichier <filename>/etc/ppp/peers/falcot</filename>"
1191
1192 msgid ""
1193 "\n"
1194 "# vpn.falcot.com is the PPTP server\n"
1195 "pty \"pptp vpn.falcot.com --nolaunchpppd\"\n"
1196 "# the connection will identify as the \"vpn\" user\n"
1197 "user vpn\n"
1198 "remotename pptp\n"
1199 "# encryption is needed\n"
1200 "require-mppe-128\n"
1201 "file /etc/ppp/options.pptp\n"
1202 "ipparam falcot"
1203 msgstr ""
1204 "\n"
1205 "# vpn.falcot.com est le serveur PPTP\n"
1206 "pty \"pptp vpn.falcot.com --nolaunchpppd\"\n"
1207 "# la connexion s'identifiera comme utilisateur « vpn »\n"
1208 "user vpn\n"
1209 "remotename pptp\n"
1210 "# la prise en charge du chiffrement est nécessaire\n"
1211 "require-mppe-128\n"
1212 "file /etc/ppp/options.pptp\n"
1213 "ipparam falcot"
1214
1215 msgid "The <filename>/etc/ppp/ip-up.d/falcot</filename> file"
1216 msgstr "Fichier <filename>/etc/ppp/ip-up.d/falcot</filename>"
1217
1218 #, fuzzy
1219 #| msgid ""
1220 #| "\n"
1221 #| "# Create the route to the Falcot network\n"
1222 #| "if [ \"$6\" = \"falcot\" ]; then\n"
1223 #| " # 192.168.0.0/24 is the (remote) Falcot network\n"
1224 #| " route add -net 192.168.0.0 netmask 255.255.255.0 dev $1\n"
1225 #| "fi"
1226 msgid ""
1227 "\n"
1228 "# Create the route to the Falcot network\n"
1229 "if [ \"$6\" = \"falcot\" ]; then\n"
1230 " # 192.168.0.0/24 is the (remote) Falcot network\n"
1231 " ip route add 192.168.0.0/24 dev $1\n"
1232 "fi"
1233 msgstr ""
1234 "\n"
1235 "# Créer la route vers le réseau local de Falcot\n"
1236 "if [ \"$6\" = \"falcot\" ]; then\n"
1237 " # 192.168.0.0/24 est le réseau distant chez Falcot\n"
1238 " route add -net 192.168.0.0 netmask 255.255.255.0 dev $1\n"
1239 "fi"
1240
1241 msgid "The <filename>/etc/ppp/ip-down.d/falcot</filename> file"
1242 msgstr "Fichier <filename>/etc/ppp/ip-down.d/falcot</filename>"
1243
1244 #, fuzzy
1245 #| msgid ""
1246 #| "\n"
1247 #| "# Delete the route to the Falcot network\n"
1248 #| "if [ \"$6\" = \"falcot\" ]; then\n"
1249 #| " # 192.168.0.0/24 is the (remote) Falcot network\n"
1250 #| " route del -net 192.168.0.0 netmask 255.255.255.0 dev $1\n"
1251 #| "fi"
1252 msgid ""
1253 "\n"
1254 "# Delete the route to the Falcot network\n"
1255 "if [ \"$6\" = \"falcot\" ]; then\n"
1256 " # 192.168.0.0/24 is the (remote) Falcot network\n"
1257 " ip route del 192.168.0.0/24 dev $1\n"
1258 "fi"
1259 msgstr ""
1260 "\n"
1261 "# Supprimer la route vers le réseau local de Falcot\n"
1262 "if [ \"$6\" = \"falcot\" ]; then\n"
1263 " # 192.168.0.0/24 est le réseau distant chez Falcot\n"
1264 " route del -net 192.168.0.0 netmask 255.255.255.0 dev $1\n"
1265 "fi"
1266
1267 msgid "<emphasis>SECURITY</emphasis> MPPE"
1268 msgstr "<emphasis>SÉCURITÉ</emphasis> MPPE"
1269
1270 msgid "<primary>MPPE</primary>"
1271 msgstr "<primary>MPPE</primary>"
1272
1273 #, fuzzy
1274 #| msgid "<primary>Microsoft</primary><secondary>Point-to-Point Encryption</secondary>"
1275 msgid "<primary>Microsoft</primary><secondary>Point-to-Point Encryption</secondary><see>MPPE</see>"
1276 msgstr "<primary>Microsoft</primary><secondary><foreignphrase>Point-to-Point Encryption</foreignphrase></secondary>"
1277
1278 msgid "Securing PPTP involves using the MPPE feature (<emphasis>Microsoft Point-to-Point Encryption</emphasis>), which is available in official Debian kernels as a module."
1279 msgstr "La sécurisation de PPTP recourt à MPPE (<foreignphrase>Microsoft Point-to-Point Encryption</foreignphrase>, ou chiffrement point à point de Microsoft), fonctionnalité intégrée sous forme de module dans les noyaux Debian officiels."
1280
1281 msgid "Configuring the Server"
1282 msgstr "Configuration du serveur"
1283
1284 #, fuzzy
1285 #| msgid "<primary><command>bgpd</command></primary>"
1286 msgid "<primary><command>pptpd</command></primary>"
1287 msgstr "<primary><command>bgpd</command></primary>"
1288
1289 msgid "<emphasis>CAUTION</emphasis> PPTP and firewalls"
1290 msgstr "<emphasis>ATTENTION</emphasis> PPTP et pare-feu"
1291
1292 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."
1293 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."
1294
1295 #, fuzzy
1296 #| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>"
1297 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/pptpd.conf</filename></secondary>"
1298 msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>"
1299
1300 msgid "<command>pptpd</command> is the PPTP server for Linux. Its main configuration file, <filename>/etc/pptpd.conf</filename>, requires very few changes: <emphasis>localip</emphasis> (local IP address) and <emphasis>remoteip</emphasis> (remote IP address). In the example below, the PPTP server always uses the <literal>192.168.0.199</literal> address, and PPTP clients receive IP addresses from <literal>192.168.0.200</literal> to <literal>192.168.0.250</literal>."
1301 msgstr "<command>pptpd</command> est le serveur PPTP pour Linux. Son fichier de configuration principal <filename>/etc/pptpd.conf</filename> n'a presque pas besoin de modifications ; il faut juste y renseigner <emphasis>localip</emphasis> (adresse IP locale) et <emphasis>remoteip</emphasis> (adresse IP distante). Dans le fichier suivant, le serveur PPTP a toujours l'adresse IP <literal>192.168.0.199</literal> et les clients PPTP reçoivent des adresses IP comprises entre <literal>192.168.0.200</literal> et <literal>192.168.0.250</literal>."
1302
1303 msgid "The <filename>/etc/pptpd.conf</filename> file"
1304 msgstr "Fichier <filename>/etc/pptpd.conf</filename>"
1305
1306 #, fuzzy
1307 #| msgid ""
1308 #| "\n"
1309 #| "# TAG: speed\n"
1310 #| "#\n"
1311 #| "# Specifies the speed for the PPP daemon to talk at.\n"
1312 #| "#\n"
1313 #| "speed 115200\n"
1314 #| "\n"
1315 #| "# TAG: option\n"
1316 #| "#\n"
1317 #| "# Specifies the location of the PPP options file.\n"
1318 #| "# By default PPP looks in '/etc/ppp/options'\n"
1319 #| "#\n"
1320 #| "option /etc/ppp/pptpd-options\n"
1321 #| "\n"
1322 #| "# TAG: debug\n"
1323 #| "#\n"
1324 #| "# Turns on (more) debugging to syslog\n"
1325 #| "#\n"
1326 #| "# debug\n"
1327 #| "\n"
1328 #| "# TAG: localip\n"
1329 #| "# TAG: remoteip\n"
1330 #| "#\n"
1331 #| "# Specifies the local and remote IP address ranges.\n"
1332 #| "#\n"
1333 #| "# You can specify single IP addresses separated by commas or you can\n"
1334 #| "# specify ranges, or both. For example:\n"
1335 #| "#\n"
1336 #| "# 192.168.0.234,192.168.0.245-249,192.168.0.254\n"
1337 #| "#\n"
1338 #| "# IMPORTANT RESTRICTIONS:\n"
1339 #| "#\n"
1340 #| "# 1. No spaces are permitted between commas or within addresses.\n"
1341 #| "#\n"
1342 #| "# 2. If you give more IP addresses than MAX_CONNECTIONS, it will\n"
1343 #| "# start at the beginning of the list and go until it gets\n"
1344 #| "# MAX_CONNECTIONS IPs. Others will be ignored.\n"
1345 #| "#\n"
1346 #| "# 3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,\n"
1347 #| "# you must type 234-238 if you mean this.\n"
1348 #| "#\n"
1349 #| "# 4. If you give a single localIP, that's ok - all local IPs will\n"
1350 #| "# be set to the given one. You MUST still give at least one remote\n"
1351 #| "# IP for each simultaneous client.\n"
1352 #| "#\n"
1353 #| "#localip 192.168.0.234-238,192.168.0.245\n"
1354 #| "#remoteip 192.168.1.234-238,192.168.1.245\n"
1355 #| "#localip 10.0.1.1\n"
1356 #| "#remoteip 10.0.1.2-100\n"
1357 #| "localip 192.168.0.199\n"
1358 #| "remoteip 192.168.0.200-250"
1359 msgid ""
1360 "\n"
1361 "[..]\n"
1362 "# TAG: localip\n"
1363 "# TAG: remoteip\n"
1364 "# Specifies the local and remote IP address ranges.\n"
1365 "#\n"
1366 "# These options are ignored if delegate option is set.\n"
1367 "#\n"
1368 "# Any addresses work as long as the local machine takes care of the\n"
1369 "# routing. But if you want to use MS-Windows networking, you should\n"
1370 "# use IP addresses out of the LAN address space and use the proxyarp\n"
1371 "# option in the pppd options file, or run bcrelay.\n"
1372 "#\n"
1373 "# You can specify single IP addresses seperated by commas or you can\n"
1374 "# specify ranges, or both. For example:\n"
1375 "#\n"
1376 "# 192.168.0.234,192.168.0.245-249,192.168.0.254\n"
1377 "#\n"
1378 "# IMPORTANT RESTRICTIONS:\n"
1379 "#\n"
1380 "# 1. No spaces are permitted between commas or within addresses.\n"
1381 "#\n"
1382 "# 2. If you give more IP addresses than the value of connections,\n"
1383 "# it will start at the beginning of the list and go until it\n"
1384 "# gets connections IPs. Others will be ignored.\n"
1385 "#\n"
1386 "# 3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,\n"
1387 "# you must type 234-238 if you mean this.\n"
1388 "#\n"
1389 "# 4. If you give a single localIP, that's ok - all local IPs will\n"
1390 "# be set to the given one. You MUST still give at least one remote\n"
1391 "# IP for each simultaneous client.\n"
1392 "#\n"
1393 "# (Recommended)\n"
1394 "#localip 192.168.0.1\n"
1395 "#remoteip 192.168.0.234-238,192.168.0.245\n"
1396 "# or\n"
1397 "#localip 192.168.0.234-238,192.168.0.245\n"
1398 "#remoteip 192.168.1.234-238,192.168.1.245\n"
1399 "localip 192.168.0.199\n"
1400 "remoteip 192.168.0.200-250"
1401 msgstr ""
1402 "\n"
1403 "# TAG: speed\n"
1404 "#\n"
1405 "# Specifies the speed for the PPP daemon to talk at.\n"
1406 "#\n"
1407 "speed 115200\n"
1408 "\n"
1409 "# TAG: option\n"
1410 "#\n"
1411 "# Specifies the location of the PPP options file.\n"
1412 "# By default PPP looks in '/etc/ppp/options'\n"
1413 "#\n"
1414 "option /etc/ppp/pptpd-options\n"
1415 "\n"
1416 "# TAG: debug\n"
1417 "#\n"
1418 "# Turns on (more) debugging to syslog\n"
1419 "#\n"
1420 "# debug\n"
1421 "\n"
1422 "# TAG: localip\n"
1423 "# TAG: remoteip\n"
1424 "#\n"
1425 "# Specifies the local and remote IP address ranges.\n"
1426 "#\n"
1427 "# You can specify single IP addresses separated by commas or you can\n"
1428 "# specify ranges, or both. For example:\n"
1429 "#\n"
1430 "# 192.168.0.234,192.168.0.245-249,192.168.0.254\n"
1431 "#\n"
1432 "# IMPORTANT RESTRICTIONS:\n"
1433 "#\n"
1434 "# 1. No spaces are permitted between commas or within addresses.\n"
1435 "#\n"
1436 "# 2. If you give more IP addresses than MAX_CONNECTIONS, it will\n"
1437 "# start at the beginning of the list and go until it gets\n"
1438 "# MAX_CONNECTIONS IPs. Others will be ignored.\n"
1439 "#\n"
1440 "# 3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,\n"
1441 "# you must type 234-238 if you mean this.\n"
1442 "#\n"
1443 "# 4. If you give a single localIP, that's ok - all local IPs will\n"
1444 "# be set to the given one. You MUST still give at least one remote\n"
1445 "# IP for each simultaneous client.\n"
1446 "#\n"
1447 "#localip 192.168.0.234-238,192.168.0.245\n"
1448 "#remoteip 192.168.1.234-238,192.168.1.245\n"
1449 "#localip 10.0.1.1\n"
1450 "#remoteip 10.0.1.2-100\n"
1451 "localip 192.168.0.199\n"
1452 "remoteip 192.168.0.200-250"
1453
1454 #, fuzzy
1455 #| msgid "<primary>traffic</primary><secondary>limitation</secondary>"
1456 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ppp/pptpd-options</filename></secondary>"
1457 msgstr "<primary>trafic</primary><secondary>limitation</secondary>"
1458
1459 msgid "The PPP configuration used by the PPTP server also requires a few changes in <filename>/etc/ppp/pptpd-options</filename>. The important parameters are the server name (<literal>pptp</literal>), the domain name (<literal>falcot.com</literal>), and the IP addresses for DNS and WINS servers."
1460 msgstr "Il faut aussi modifier la configuration PPP employée par le serveur PPTP, consignée dans le fichier <filename>/etc/ppp/pptpd-options</filename>. Les paramètres importants à changer sont les noms du serveur (<literal>pptp</literal>) et du domaine (<literal>falcot.com</literal>) ainsi que les adresses IP des serveurs DNS et Wins."
1461
1462 msgid "The <filename>/etc/ppp/pptpd-options</filename> file"
1463 msgstr "Fichier <filename>/etc/ppp/pptpd-options</filename>"
1464
1465 #, fuzzy
1466 #| msgid ""
1467 #| "\n"
1468 #| "## turn pppd syslog debugging on\n"
1469 #| "#debug\n"
1470 #| "\n"
1471 #| "## change 'servername' to whatever you specify as your server name in chap-secrets\n"
1472 #| "name pptp\n"
1473 #| "## change the domainname to your local domain\n"
1474 #| "domain falcot.com\n"
1475 #| "\n"
1476 #| "## these are reasonable defaults for WinXXXX clients\n"
1477 #| "## for the security related settings\n"
1478 #| "# The Debian pppd package now supports both MSCHAP and MPPE, so enable them\n"
1479 #| "# here. Please note that the kernel support for MPPE must also be present!\n"
1480 #| "auth\n"
1481 #| "require-chap\n"
1482 #| "require-mschap\n"
1483 #| "require-mschap-v2\n"
1484 #| "require-mppe-128\n"
1485 #| "\n"
1486 #| "## Fill in your addresses\n"
1487 #| "ms-dns 192.168.0.1\n"
1488 #| "ms-wins 192.168.0.1\n"
1489 #| "\n"
1490 #| "## Fill in your netmask\n"
1491 #| "netmask 255.255.255.0\n"
1492 #| "\n"
1493 #| "## some defaults\n"
1494 #| "nodefaultroute\n"
1495 #| "proxyarp\n"
1496 #| "lock"
1497 msgid ""
1498 "\n"
1499 "# Enable connection debugging facilities.\n"
1500 "# (see your syslog configuration for where pppd sends to)\n"
1501 "#debug\n"
1502 "\n"
1503 "# Name of the local system for authentication purposes\n"
1504 "# (must match the second field in /etc/ppp/chap-secrets entries)\n"
1505 "name pptpd\n"
1506 "\n"
1507 "# Optional: domain name to use for authentication\n"
1508 "## change the domainname to your local domain\n"
1509 "domain falcot.com\n"
1510 "\n"
1511 "# Authentication\n"
1512 "## these are reasonable defaults for WinXXXX clients\n"
1513 "## for the security related settings\n"
1514 "auth\n"
1515 "refuse-pap\n"
1516 "refuse-chap\n"
1517 "refuse-mschap\n"
1518 "# Require the peer to authenticate itself using MS-CHAPv2 [Microsoft\n"
1519 "# Challenge Handshake Authentication Protocol, Version 2] authentication.\n"
1520 "require-mschap-v2\n"
1521 "# Require MPPE 128-bit encryption\n"
1522 "# (note that MPPE requires the use of MSCHAP-V2 during authentication)\n"
1523 "require-mppe-128\n"
1524 "\n"
1525 "# Network and Routing\n"
1526 "## Fill in your addresses\n"
1527 "ms-dns 192.168.0.1\n"
1528 "ms-wins 192.168.0.1\n"
1529 "\n"
1530 "## Fill in your netmask\n"
1531 "netmask 255.255.255.0\n"
1532 "\n"
1533 "## some defaults\n"
1534 "nodefaultroute\n"
1535 "proxyarp\n"
1536 "lock"
1537 msgstr ""
1538 "\n"
1539 "## turn pppd syslog debugging on\n"
1540 "#debug\n"
1541 "\n"
1542 "## change 'servername' to whatever you specify as your server name in chap-secrets\n"
1543 "name pptp\n"
1544 "## change the domainname to your local domain\n"
1545 "domain falcot.com\n"
1546 "\n"
1547 "## these are reasonable defaults for WinXXXX clients\n"
1548 "## for the security related settings\n"
1549 "# The Debian pppd package now supports both MSCHAP and MPPE, so enable them\n"
1550 "# here. Please note that the kernel support for MPPE must also be present!\n"
1551 "auth\n"
1552 "require-chap\n"
1553 "require-mschap\n"
1554 "require-mschap-v2\n"
1555 "require-mppe-128\n"
1556 "\n"
1557 "## Fill in your addresses\n"
1558 "ms-dns 192.168.0.1\n"
1559 "ms-wins 192.168.0.1\n"
1560 "\n"
1561 "## Fill in your netmask\n"
1562 "netmask 255.255.255.0\n"
1563 "\n"
1564 "## some defaults\n"
1565 "nodefaultroute\n"
1566 "proxyarp\n"
1567 "lock"
1568
1569 #, fuzzy
1570 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
1571 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ppp/chap-secrets</filename></secondary>"
1572 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
1573
1574 msgid "The last step involves registering the <literal>vpn</literal> user (and the associated password) in the <filename>/etc/ppp/chap-secrets</filename> file. Contrary to other instances where an asterisk (<literal>*</literal>) would work, the server name must be filled explicitly here. Furthermore, Windows PPTP clients identify themselves under the <literal><replaceable>DOMAIN</replaceable>\\\\<replaceable>USER</replaceable></literal> form, instead of only providing a user name. This explains why the file also mentions the <literal>FALCOT\\\\vpn</literal> user. It is also possible to specify individual IP addresses for users; an asterisk in this field specifies that dynamic addressing should be used."
1575 msgstr "La dernière étape est d'enregistrer l'utilisateur <literal>vpn</literal> et le mot de passe associé dans le fichier <filename>/etc/ppp/chap-secrets</filename>. Le nom du serveur doit y être renseigné explicitement, l'astérisque (<literal>*</literal>) habituel ne fonctionnant pas. Par ailleurs, il faut savoir que les clients PPTP sous Windows s'identifient sous la forme <literal><replaceable>DOMAINE</replaceable>\\\\<replaceable>UTILISATEUR</replaceable></literal> au lieu de se contenter du nom d'utilisateur. C'est pourquoi on trouve aussi dans ce fichier l'utilisateur <literal>FALCOT\\\\vpn</literal>. 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."
1576
1577 msgid "The <filename>/etc/ppp/chap-secrets</filename> file"
1578 msgstr "Fichier <filename>/etc/ppp/chap-secrets</filename>"
1579
1580 msgid ""
1581 "\n"
1582 "# Secrets for authentication using CHAP\n"
1583 "# client server secret IP addresses\n"
1584 "vpn pptp f@Lc3au *\n"
1585 "FALCOT\\\\vpn pptp f@Lc3au *"
1586 msgstr ""
1587 "\n"
1588 "# Secrets for authentication using CHAP\n"
1589 "# client server secret IP addresses\n"
1590 "vpn pptp f@Lc3au *\n"
1591 "FALCOT\\\\vpn pptp f@Lc3au *"
1592
1593 msgid "<emphasis>SECURITY</emphasis> PPTP vulnerabilities"
1594 msgstr "<emphasis>SÉCURITÉ</emphasis> Failles de PPTP"
1595
1596 #, fuzzy
1597 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
1598 msgid "<primary>PPTP</primary><secondary>vulnerabilities</secondary>"
1599 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
1600
1601 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 <literal>require-mppe-128</literal> and <literal>require-mschap-v2</literal>) would make the service vulnerable again."
1602 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 <literal>require-mppe-128</literal> et <literal>require-mschap-v2</literal>) rendrait le service à nouveau vulnérable."
1603
1604 msgid "Quality of Service"
1605 msgstr "Qualité de service"
1606
1607 msgid "Principle and Mechanism"
1608 msgstr "Principe et fonctionnement"
1609
1610 #, fuzzy
1611 #| msgid "<primary>network</primary><secondary>gateway</secondary>"
1612 msgid "<primary>network</primary><secondary>QoS</secondary>"
1613 msgstr "<primary>réseau</primary><secondary>passerelle</secondary>"
1614
1615 msgid "<primary>QoS</primary>"
1616 msgstr "<primary><foreignphrase>QoS</foreignphrase></primary>"
1617
1618 #, fuzzy
1619 #| msgid "<primary>quality of service</primary>"
1620 msgid "<primary>Quality of Service</primary><see>QoS</see>"
1621 msgstr "<primary><foreignphrase>quality of service</foreignphrase></primary>"
1622
1623 #, fuzzy
1624 #| msgid "<primary>quality</primary><secondary>of service</secondary>"
1625 msgid "<primary>quality</primary><secondary>of service</secondary><see>QoS</see>"
1626 msgstr "<primary>qualité</primary><secondary>de service</secondary>"
1627
1628 #, fuzzy
1629 #| msgid "<primary>service</primary><secondary>quality</secondary>"
1630 msgid "<primary>service</primary><secondary>quality</secondary><see>QoS</see>"
1631 msgstr "<primary>service</primary><secondary>qualité</secondary>"
1632
1633 msgid "<emphasis>Quality of Service</emphasis> (or <emphasis>QoS</emphasis> 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 <emphasis>traffic shaping</emphasis>, 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."
1634 msgstr "Le terme QoS <foreignphrase>(Quality of Service)</foreignphrase> 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 <foreignphrase>shaping</foreignphrase>. 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."
1635
1636 #, fuzzy
1637 #| msgid "<emphasis>CULTURE</emphasis> SSL and TLS"
1638 msgid "<emphasis>CULTURE</emphasis> Net neutrality and QoS"
1639 msgstr "<emphasis>CULTURE</emphasis> SSL et TLS"
1640
1641 #, fuzzy
1642 #| msgid "<primary>network</primary><secondary>gateway</secondary>"
1643 msgid "<primary>network</primary><secondary>neutrality</secondary>"
1644 msgstr "<primary>réseau</primary><secondary>passerelle</secondary>"
1645
1646 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."
1647 msgstr ""
1648
1649 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."
1650 msgstr ""
1651
1652 msgid "It is also possible to alter the priorities on traffic, which allows prioritizing packets related to interactive services (such as <command>ssh</command> and <command>telnet</command>) or to services that only deal with small blocks of data."
1653 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 (<command>ssh</command>, <command>telnet</command>) ou à des services échangeant de petits blocs de données."
1654
1655 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."
1656 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 (<foreignphrase>scheduler</foreignphrase>, ou ordonnanceur), dont les mécanismes variés couvrent tout le spectre des besoins possibles."
1657
1658 msgid "<emphasis>CULTURE</emphasis> LARTC — <emphasis>Linux Advanced Routing &amp; Traffic Control</emphasis>"
1659 msgstr "<emphasis>CULTURE</emphasis> LARTC — <foreignphrase>Linux Advanced Routing &amp; Trafic Control</foreignphrase>"
1660
1661 #, fuzzy
1662 #| msgid "<primary>network</primary><secondary>virtual private</secondary>"
1663 msgid "<primary>network</primary><secondary>advanced routing</secondary><seealso>routing</seealso>"
1664 msgstr "<primary>réseau</primary><secondary>privé virtuel</secondary>"
1665
1666 msgid "<primary>routing</primary><secondary>advanced</secondary>"
1667 msgstr "<primary>routage</primary><secondary>avancé</secondary>"
1668
1669 msgid "<primary>traffic</primary><secondary>control</secondary>"
1670 msgstr "<primary>trafic</primary><secondary>contrôle</secondary>"
1671
1672 msgid "<primary>control of traffic</primary>"
1673 msgstr "<primary>contrôle du trafic</primary>"
1674
1675 #, fuzzy
1676 #| msgid "The <emphasis>Linux Advanced Routing &amp; Traffic Control</emphasis> HOWTO is the reference document covering everything there is to know about network quality of service. <ulink type=\"block\" url=\"http://www.lartc.org/howto/\" />"
1677 msgid "The <emphasis>Linux Advanced Routing &amp; Traffic Control</emphasis> HOWTO is the reference document covering everything there is to know about network quality of service. <ulink type=\"block\" url=\"https://www.lartc.org/howto/\" />"
1678 msgstr "Le <foreignphrase>HOWTO</foreignphrase> 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. <ulink type=\"block\" url=\"http://www.linux-france.org/prj/inetdoc/guides/lartc/lartc.html\" />"
1679
1680 msgid "Configuring and Implementing"
1681 msgstr "Configuration et mise en œuvre"
1682
1683 msgid "<primary><emphasis>iproute</emphasis></primary>"
1684 msgstr "<primary><emphasis>iproute</emphasis></primary>"
1685
1686 msgid "<primary><command>tc</command></primary>"
1687 msgstr "<primary><command>tc</command></primary>"
1688
1689 msgid "QoS parameters are set through the <command>tc</command> command (provided by the <emphasis role=\"pkg\">iproute</emphasis> package). Since its interface is quite complex, using higher-level tools is recommended."
1690 msgstr "Le QoS se paramètre avec le logiciel <command>tc</command>, du paquet Debian <emphasis role=\"pkg\">iproute</emphasis>. Son interface étant extrêmement complexe, il est préférable d'employer des outils de plus haut niveau."
1691
1692 msgid "Reducing Latencies: <command>wondershaper</command>"
1693 msgstr "Minimiser le temps de latence : <command>wondershaper</command>"
1694
1695 msgid "<primary><command>wondershaper</command></primary>"
1696 msgstr "<primary><command>wondershaper</command></primary>"
1697
1698 msgid "<primary>limitation of traffic</primary>"
1699 msgstr "<primary>limitation de trafic</primary>"
1700
1701 msgid "<primary>traffic</primary><secondary>limitation</secondary>"
1702 msgstr "<primary>trafic</primary><secondary>limitation</secondary>"
1703
1704 msgid "The main purpose of <command>wondershaper</command> (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."
1705 msgstr "L'objectif de <command>wondershaper</command> (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."
1706
1707 #, fuzzy
1708 #| msgid "Once a network interface is configured, setting up this traffic limitation is achieved by running <command>wondershaper <replaceable>interface</replaceable> <replaceable>download_rate</replaceable> <replaceable>upload_rate</replaceable></command>. The interface can be <literal>eth0</literal> or <literal>ppp0</literal> for example, and both rates are expressed in kilobits per second. The <command>wondershaper remove <replaceable>interface</replaceable></command> command disables traffic control on the specified interface."
1709 msgid "Once a network interface is configured, setting up this traffic limitation is achieved by running <command>wondershaper <replaceable>interface</replaceable> <replaceable>download_rate</replaceable> <replaceable>upload_rate</replaceable></command>. The interface can be <literal>enp1s0</literal>, <literal>eth0</literal> or <literal>ppp0</literal> for example, and both rates are expressed in kilobits per second. The <command>wondershaper remove <replaceable>interface</replaceable></command> command disables traffic control on the specified interface."
1710 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 <command>wondershaper <replaceable>interface</replaceable> <replaceable>débit_descendant</replaceable> <replaceable>débit_montant</replaceable></command>. L'interface sera par exemple <literal>eth0</literal> ou <literal>ppp0</literal> et les deux débits (descendant et montant) s'expriment en kilobits par seconde. La commande <command>wondershaper remove <replaceable>interface</replaceable></command> désactive le contrôle du trafic sur l'interface indiquée."
1711
1712 #, fuzzy
1713 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
1714 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/network/interfaces</filename></secondary>"
1715 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
1716
1717 #, fuzzy
1718 #| msgid "For an Ethernet connection, this script is best called right after the interface is configured. This is done by adding <literal>up</literal> and <literal>down</literal> directives to the <filename>/etc/network/interfaces</filename> file allowing declared commands to be run, respectively, after the interface is configured and before it is deconfigured. For example:"
1719 msgid "For an Ethernet connection, historically this script would be called right after the interface is configured. This is done by adding <literal>up</literal> and <literal>down</literal> directives to the <filename>/etc/network/interfaces</filename> 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 <command>wondershaper</command> in <filename>/etc/ppp/ip-up.d/</filename> will enable traffic control as soon as the connection is up. Below is an example using this first method:"
1720 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 <filename>/etc/network/interfaces</filename> pour y ajouter des directives <literal>up</literal> (indiquant une commande à exécuter après configuration de l'interface) et <literal>down</literal> (indiquant une commande à exécuter après déconfiguration de l'interface) comme suit :"
1721
1722 msgid "Changes in the <filename>/etc/network/interfaces</filename> file"
1723 msgstr "Modification du fichier <filename>/etc/network/interfaces</filename>"
1724
1725 msgid ""
1726 "\n"
1727 "iface eth0 inet dhcp\n"
1728 " up /sbin/wondershaper eth0 500 100\n"
1729 " down /sbin/wondershaper remove eth0"
1730 msgstr ""
1731 "\n"
1732 "iface eth0 inet dhcp\n"
1733 " up /sbin/wondershaper eth0 500 100\n"
1734 " down /sbin/wondershaper remove eth0"
1735
1736 msgid "<emphasis>GOING FURTHER</emphasis> Optimal configuration"
1737 msgstr "<emphasis>POUR ALLER PLUS LOIN</emphasis> Configuration optimale"
1738
1739 msgid "The <filename>/usr/share/doc/wondershaper/README.Debian.gz</filename> 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."
1740 msgstr "Le fichier <filename>/usr/share/doc/wondershaper/README.Debian.gz</filename> 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."
1741
1742 msgid "Standard Configuration"
1743 msgstr "Configuration standard"
1744
1745 msgid "<primary>DSCP</primary>"
1746 msgstr "<primary>DSCP</primary>"
1747
1748 #, fuzzy
1749 #| msgid "<primary>reverse zone</primary>"
1750 msgid "<primary>Differentiated Services Code Point</primary><see>DSCP</see>"
1751 msgstr "<primary>inverse, zone</primary>"
1752
1753 #, fuzzy
1754 #| msgid "Barring a specific QoS configuration, the Linux kernel uses the <literal>pfifo_fast</literal> queue scheduler, which provides a few interesting features by itself. The priority of each processed IP packet is based on the ToS field (<emphasis>Type of Service</emphasis>) of this packet; modifying this field is enough to take advantage of the scheduling features. There are five possible values:"
1755 msgid "Barring a specific QoS configuration, the Linux kernel uses the <literal>pfifo_fast</literal> queue scheduler, which provides a few interesting features by itself. The priority of each processed IP packet is based on the DSCP field (<emphasis>Differentiated Services Code Point</emphasis>) of this packet; modifying this 6-bit field is enough to take advantage of the scheduling features. Refer to <ulink url=\"https://en.wikipedia.org/wiki/Differentiated_services#Class_Selector\" /> for more information."
1756 msgstr "En l'absence d'une configuration particulière de QoS, le noyau Linux emploie la file d'attente <literal>pfifo_fast</literal>, qui propose déjà quelques fonctionnalités intéressantes. Pour établir les priorités des paquets IP, elle utilise leur champ ToS (<foreignphrase>Type of Service</foreignphrase>, ou type de service) — qu'il suffira donc de modifier pour bénéficier de cette file. Ce champ peut recevoir cinq valeurs :"
1757
1758 #, fuzzy
1759 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
1760 msgid "<primary>IP</primary><secondary>netfilter</secondary>"
1761 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
1762
1763 #, fuzzy
1764 #| msgid "The ToS field can be set by applications that generate IP packets, or modified on the fly by <emphasis>netfilter</emphasis>. The following rules are sufficient to increase responsiveness for a server's SSH service:"
1765 msgid "The DSCP field can be set by applications that generate IP packets, or modified on the fly by <emphasis>netfilter</emphasis>. The following rules are sufficient to increase responsiveness for a server's SSH service, note that the DSCP field must be set in hexadecimal:"
1766 msgstr "Le champ ToS peut être positionné par les applications qui génèrent des paquets IP ou modifié à la volée par <emphasis>netfilter</emphasis>. Avec la règle ci-dessous, il est ainsi possible d'améliorer l'interactivité du service SSH d'un serveur :"
1767
1768 msgid ""
1769 "\n"
1770 "nft add table ip mangle\n"
1771 "nft add rule ip mangle PREROUTING tcp sport 22 counter ip dscp set 0x04\n"
1772 "nft add rule ip mangle PREROUTING tcp dport 22 counter ip dscp set 0x04"
1773 msgstr ""
1774
1775 msgid "Dynamic Routing"
1776 msgstr "Routage dynamique"
1777
1778 #, fuzzy
1779 #| msgid "<primary>routing</primary><secondary>dynamic</secondary>"
1780 msgid "<primary>routing</primary><secondary>dynamic</secondary><seealso><command>frr</command></seealso>"
1781 msgstr "<primary>routage</primary><secondary>dynamique</secondary>"
1782
1783 #, fuzzy
1784 #| msgid "<primary><command>ripd</command></primary>"
1785 msgid "<primary><command>frr</command></primary>"
1786 msgstr "<primary><command>ripd</command></primary>"
1787
1788 #, fuzzy
1789 #| msgid "<primary><command>quagga</command></primary>"
1790 msgid "<primary><command>quagga</command></primary><see><command>frr</command></see>"
1791 msgstr "<primary><command>quagga</command></primary>"
1792
1793 #, fuzzy
1794 #| msgid "<primary><command>zebra</command></primary>"
1795 msgid "<primary><command>zebra</command></primary><see><command>frr</command></see>"
1796 msgstr "<primary><command>zebra</command></primary>"
1797
1798 #, fuzzy
1799 #| msgid "The reference tool for dynamic routing is currently <command>quagga</command>, from the similarly-named package; it used to be <command>zebra</command> until development of the latter stopped. However, <command>quagga</command> kept the names of the programs for compatibility reasons which explains the <command>zebra</command> commands below."
1800 msgid "The reference tool for dynamic routing is currently <command>frr</command> from the similarly-named package; it used to be <command>quagga</command>, and before that <command>zebra</command> until development of these stopped. However, <command>frr</command> kept the names of the programs for compatibility reasons which explains the <command>zebra</command> commands below."
1801 msgstr "Le logiciel <command>quagga</command> (du paquet Debian éponyme) est désormais la référence en matière de routage dynamique (il a supplanté <command>zebra</command>, dont le développement s'est arrêté). Cependant, pour des raisons de compatibilité, le projet <command>quagga</command> a conservé les noms des exécutables : c'est pourquoi on retrouve le programme <command>zebra</command> plus loin."
1802
1803 msgid "<emphasis>BACK TO BASICS</emphasis> Dynamic routing"
1804 msgstr "<emphasis>B.A.-BA</emphasis> Routage dynamique"
1805
1806 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)."
1807 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.)."
1808
1809 #, fuzzy
1810 #| msgid "<primary>traffic</primary><secondary>limitation</secondary>"
1811 msgid "<primary><command>ip</command></primary><secondary><literal>route</literal></secondary>"
1812 msgstr "<primary>trafic</primary><secondary>limitation</secondary>"
1813
1814 msgid "<primary><command>route</command></primary>"
1815 msgstr "<primary><command>route</command></primary>"
1816
1817 #, fuzzy
1818 #| msgid "In the Linux kernel, a route links a network device to a set of machines that can be reached through this device. The <command>route</command> command defines new routes and displays existing ones."
1819 msgid "In the Linux kernel, a route links a network device to a set of machines that can be reached through this device. The <command>ip</command> command, when <literal>route</literal> is used as the first argument, defines new routes and displays existing ones. The <command>route</command> command was used for that purpose, but it is deprecated in favor of <command>ip</command>."
1820 msgstr "Pour le noyau Linux, une route associe un périphérique réseau à un ensemble de machines qu'il peut atteindre. La commande <command>route</command> permet de les définir et de les consulter."
1821
1822 #, fuzzy
1823 #| 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 <command>zebra</command> daemon collects information from other daemons and handles static routing tables accordingly. The other daemons are known as <command>bgpd</command>, <command>ospfd</command>, <command>ospf6d</command>, <command>ripd</command>, <command>ripngd</command>, <command>isisd</command>, and <command>babeld</command>."
1824 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 <literal>zebra</literal> and <literal>staticd</literal> daemons, which are always started, collect information from other daemons and handle static routing tables accordingly. The other daemons are known as <command>bgpd</command>, <command>ospfd</command>, <command>ospf6d</command>, <command>ripd</command>, <command>ripngd</command>, <command>isisd</command>, etc."
1825 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 <command>zebra</command> centralise les informations reçues des autres démons (<command>bgpd</command>, <command>ospfd</command>, <command>ospf6d</command>, <command>ripd</command>, <command>ripngd</command> et <command>babeld</command>) et gère les tables de routage statiques."
1826
1827 msgid "<primary>OSPF</primary>"
1828 msgstr "<primary>OSPF</primary>"
1829
1830 msgid "<primary>BGP</primary>"
1831 msgstr "<primary>BGP</primary>"
1832
1833 msgid "<primary>RIP</primary>"
1834 msgstr "<primary>RIP</primary>"
1835
1836 msgid "<primary>IS-IS</primary>"
1837 msgstr "<primary>IS-IS</primary>"
1838
1839 msgid "<primary><command>bgpd</command></primary>"
1840 msgstr "<primary><command>bgpd</command></primary>"
1841
1842 msgid "<primary><command>ospfd</command></primary>"
1843 msgstr "<primary><command>ospfd</command></primary>"
1844
1845 msgid "<primary><command>ospf6d</command></primary>"
1846 msgstr "<primary><command>ospf6d</command></primary>"
1847
1848 msgid "<primary><command>ripd</command></primary>"
1849 msgstr "<primary><command>ripd</command></primary>"
1850
1851 msgid "<primary><command>ripngd</command></primary>"
1852 msgstr "<primary><command>ripngd</command></primary>"
1853
1854 msgid "<primary><command>isisd</command></primary>"
1855 msgstr "<primary><command>isisd</command></primary>"
1856
1857 #, fuzzy
1858 #| msgid "<primary>server</primary><secondary>name</secondary>"
1859 msgid "<primary>service</primary><secondary><filename>frr.service</filename></secondary>"
1860 msgstr "<primary>serveur</primary><secondary>de noms</secondary>"
1861
1862 msgid "Daemons are enabled by creating the <filename>/etc/frr/<replaceable>daemon</replaceable>.conf</filename> config file, <replaceable>daemon</replaceable> being the name of the daemon to use, and editing the <filename>/etc/frr/daemon</filename> configuration file. The daemon config file must belong to the <literal>frr</literal> user and group with permissions of <literal>0640</literal> in order for the <filename>/etc/init.d/frr</filename> script or the <filename>frr.service</filename> systemd service file to invoke the daemon. The package <emphasis role=\"pkg\">frr</emphasis> provides configuration examples under <filename>/usr/share/doc/frr/examples/</filename>."
1863 msgstr ""
1864
1865 #, fuzzy
1866 #| 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 <emphasis role=\"pkg\">quagga-doc</emphasis> provides ample explanation in the form of an <command>info</command> file. The same contents may be more easily browsed as HTML on the Quagga website: <ulink type=\"block\" url=\"http://www.nongnu.org/quagga/docs/docs-info.html\" />"
1867 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 <emphasis role=\"pkg\">frr-doc</emphasis> provides ample explanation in the form of both <command>info</command> and HTML files. The same contents may be more browsed on the project's website: <ulink type=\"block\" url=\"http://docs.frrouting.org/en/latest/\" />"
1868 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 <command>info</command> du paquet <emphasis role=\"pkg\">quagga-doc</emphasis> n'est pas avare d'explications. Par souci d'ergonomie, il est aussi possible de consulter ce manuel au format HTML à l'adresse suivante : <ulink type=\"block\" url=\"http://www.nongnu.org/quagga/docs/docs-info.html\" />"
1869
1870 #, fuzzy
1871 #| msgid "In addition, the syntax is very close to a standard router's configuration interface, and network administrators will adapt quickly to <command>quagga</command>."
1872 msgid "In addition, the syntax is very close to a standard router's configuration interface, and network administrators will adapt quickly to <command>frr</command>."
1873 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 à <command>quagga</command>."
1874
1875 msgid "<emphasis>IN PRACTICE</emphasis> OSPF, BGP or RIP?"
1876 msgstr "<emphasis>EN PRATIQUE</emphasis> OSPF, BGP ou RIP ?"
1877
1878 #, fuzzy
1879 #| msgid "<primary>protocol</primary><secondary>ESP</secondary>"
1880 msgid "<primary>protocol</primary><secondary>BGP</secondary>"
1881 msgstr "<primary>protocole</primary><secondary>ESP</secondary>"
1882
1883 #, fuzzy
1884 #| msgid "<primary>protocol</primary><secondary>ESP</secondary>"
1885 msgid "<primary>protocol</primary><secondary>RIP</secondary>"
1886 msgstr "<primary>protocole</primary><secondary>ESP</secondary>"
1887
1888 #, fuzzy
1889 #| 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."
1890 msgid "<acronym>OSPF</acronym> (Open Shortest Path First) is generally the best protocol to use for dynamic routing on private networks, but <acronym>BGP</acronym> (Border Gateway Protocol) is more common for Internet-wide routing. <acronym>RIP</acronym> (Routing Information Protocol) is rather ancient, and hardly used anymore."
1891 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é."
1892
1893 #, fuzzy
1894 #| msgid "<primary>port</primary><secondary>TCP</secondary>"
1895 msgid "<primary>IP</primary><secondary>v4</secondary><seealso>IPv4</seealso>"
1896 msgstr "<primary>port</primary><secondary>TCP</secondary>"
1897
1898 #, fuzzy
1899 #| msgid "<primary>firewall</primary><secondary>IPv6</secondary>"
1900 msgid "<primary>IP</primary><secondary>v6</secondary><seealso>IPv6</seealso>"
1901 msgstr "<primary>IPv6</primary><secondary>pare-feu</secondary>"
1902
1903 #, fuzzy
1904 #| msgid "<primary>IPv6</primary>"
1905 msgid "<primary>IPv4</primary>"
1906 msgstr "<primary>IPv6</primary>"
1907
1908 msgid "<primary>IPv6</primary>"
1909 msgstr "<primary>IPv6</primary>"
1910
1911 msgid "<primary><emphasis role=\"pkg\">iputils-ping</emphasis></primary>"
1912 msgstr "<primary><emphasis>iputils-ping</emphasis></primary>"
1913
1914 msgid "<primary><emphasis role=\"pkg\">iputils-tracepath</emphasis></primary>"
1915 msgstr "<primary><emphasis>iputils-tracepath</emphasis></primary>"
1916
1917 #, fuzzy
1918 #| 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)."
1919 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)."
1920 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)."
1921
1922 msgid "Debian kernels include IPv6 handling in the core kernel (with the exception of some architectures that have it compiled as a module named <literal>ipv6</literal>). Basic tools such as <command>ping</command> and <command>traceroute</command> have their IPv6 equivalents in <command>ping6</command> and <command>traceroute6</command>, available respectively in the <emphasis role=\"pkg\">iputils-ping</emphasis> and <emphasis role=\"pkg\">iputils-tracepath</emphasis> packages."
1923 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 <literal>ipv6</literal> optionnel). Les outils de base comme <command>ping</command> et <command>traceroute</command> ont pour équivalents IPv6 <command>ping6</command> et <command>traceroute6</command>, respectivement disponibles dans les paquets Debian <emphasis role=\"pkg\">iputils-ping</emphasis> et <emphasis role=\"pkg\">iputils-tracepath</emphasis>."
1924
1925 msgid "The IPv6 network is configured similarly to IPv4, in <filename>/etc/network/interfaces</filename>. 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."
1926 msgstr "On peut configurer le réseau IPv6 comme un réseau IPv4, à travers le fichier <filename>/etc/network/interfaces</filename>. 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."
1927
1928 msgid "Example of IPv6 configuration"
1929 msgstr "Exemple de configuration IPv6"
1930
1931 #, fuzzy
1932 #| msgid ""
1933 #| "\n"
1934 #| "iface eth0 inet6 static\n"
1935 #| " address 2001:db8:1234:5::1:1\n"
1936 #| " netmask 64\n"
1937 #| " # Disabling auto-configuration\n"
1938 #| " # autoconf 0\n"
1939 #| " # The router is auto-configured and has no fixed address\n"
1940 #| " # (accept_ra 1). If it had:\n"
1941 #| " # gateway 2001:db8:1234:5::1"
1942 msgid ""
1943 "\n"
1944 "iface enp7s0 inet6 static\n"
1945 " address 2001:db8:1234:5::1:1/64\n"
1946 " # Disabling auto-configuration\n"
1947 " # autoconf 0\n"
1948 " # The router is auto-configured and has no fixed address\n"
1949 " # (accept_ra 1). If it had:\n"
1950 " # gateway 2001:db8:1234:5::1"
1951 msgstr ""
1952 "\n"
1953 "iface eth0 inet6 static\n"
1954 " address 2001:db8:1234:5::1:1\n"
1955 " netmask 64\n"
1956 " # Pour désactiver l'auto-configuration:\n"
1957 " # autoconf 0\n"
1958 " # Le routeur est auto-configuré et n'a pas d'adresse fixe.\n"
1959 " # (/proc/sys/net/ipv6/conf/all/accept_ra). Sinon pour le forcer:\n"
1960 " # gateway 2001:db8:1234:5::1"
1961
1962 #, fuzzy
1963 #| msgid "<primary>SSL</primary>"
1964 msgid "<primary>SLAAC</primary>"
1965 msgstr "<primary>SSL</primary>"
1966
1967 msgid "<primary>Stateless Address Autoconfiguration</primary><see>SLAAC</see>"
1968 msgstr ""
1969
1970 msgid "IPv6 subnets usually have a netmask of 64 bits. This means that 2<superscript>64</superscript> distinct addresses exist within the subnet. This allows Stateless Address Autoconfiguration (<acronym>SLAAC</acronym>) to pick an address based on the network interface's MAC address. By default, if <acronym>SLAAC</acronym> is activated in your network and IPv6 on your computer, the kernel will automatically find IPv6 routers and configure the network interfaces."
1971 msgstr "Les sous-réseaux IPv6 ont généralement un masque de 64 bits, ce qui autorise 2<superscript>64</superscript> adresses dans le sous-réseau. Cela permet l'autoconfiguration d'adresses sans état (<foreignphrase>Stateless Address Autoconfiguration</foreignphrase> ou <acronym>SLAAC</acronym>), qui choisit une adresse IPv6 à partir de l'adresse MAC de l'interface. Par défaut, si <acronym>SLAAC</acronym> est actif sur le réseau et IPv6 actif sur un ordinateur, le noyau va automatiquement trouver les routeurs IPv6 et configurer les interfaces."
1972
1973 #, fuzzy
1974 #| msgid "<primary>ISC</primary>"
1975 msgid "<primary>MAC</primary>"
1976 msgstr "<primary>ISC</primary>"
1977
1978 #, fuzzy
1979 #| msgid "<primary>IP address</primary><secondary>private</secondary>"
1980 msgid "<primary>IPv6</primary><secondary>privacy extensions</secondary>"
1981 msgstr "<primary>adresse IP</primary><secondary>privée</secondary>"
1982
1983 #, fuzzy
1984 #| msgid "This behavior may have privacy implications. If you switch networks frequently, e.g. with a laptop, you might not want your <acronym>MAC</acronym> 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 <filename>/etc/network/interfaces</filename>, activates these privacy extensions."
1985 msgid "This behavior may have privacy implications. If you switch networks frequently, e.g. with a laptop, you might not want your <acronym>MAC</acronym> 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 <filename>/etc/network/interfaces</filename>, activates these privacy extensions for the interface <replaceable>enp7s0</replaceable>."
1986 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 <acronym>MAC</acronym> 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 <acronym>MAC</acronym> 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 <acronym>SLAAC</acronym>. L'exemple qui suit, à insérer dans <filename>/etc/network/interfaces</filename>, active cette extension."
1987
1988 msgid "IPv6 privacy extensions"
1989 msgstr "Extension d'IPv6 pour la protection des données personnelles"
1990
1991 #, fuzzy
1992 #| msgid ""
1993 #| "\n"
1994 #| "iface eth0 inet6 auto\n"
1995 #| " # Prefer the randomly assigned addresses for outgoing connections.\n"
1996 #| " privext 2"
1997 msgid ""
1998 "\n"
1999 "iface enp7s0 inet6 auto\n"
2000 " # Prefer the randomly assigned addresses for outgoing connections.\n"
2001 " privext 2"
2002 msgstr ""
2003 "\n"
2004 "iface eth0 inet6 auto\n"
2005 " # Préférer l'adresse générée aléatoirement pour les connexions sortantes\n"
2006 " privext 2"
2007
2008 msgid "<emphasis>TIP</emphasis> Programs built with IPv6"
2009 msgstr "<emphasis>ASTUCE</emphasis> Programmes compilés avec IPv6"
2010
2011 #, fuzzy
2012 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
2013 msgid "<primary>mailing lists</primary><secondary><email>[email protected]</email></secondary>"
2014 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
2015
2016 #, fuzzy
2017 #| 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 <emphasis>debian-ipv6</emphasis> mailing-list. They might know about an IPv6-aware replacement and could file a bug to get the issue properly tracked. <ulink type=\"block\" url=\"http://lists.debian.org/debian-ipv6/\" />"
2018 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 <emphasis>debian-ipv6</emphasis> mailing-list. They might know about an IPv6-aware replacement and could file a bug to get the issue properly tracked. <ulink type=\"block\" url=\"https://lists.debian.org/debian-ipv6/\" />"
2019 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 <emphasis>debian-ipv6</emphasis>. 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é. <ulink type=\"block\" url=\"http://lists.debian.org/debian-ipv6/\" />"
2020
2021 #, fuzzy
2022 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2023 msgid "<primary>IPv6</primary><secondary>firewall</secondary>"
2024 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2025
2026 msgid "<primary>firewall</primary><secondary>IPv6</secondary>"
2027 msgstr "<primary>IPv6</primary><secondary>pare-feu</secondary>"
2028
2029 msgid "<primary><command>ip6tables</command></primary>"
2030 msgstr "<primary><command>ip6tables</command></primary>"
2031
2032 msgid "IPv6 connections can be restricted, in the same fashion as for IPv4. <command>nft</command> can be used to create firewall rules for IPv4 and IPv6 (see <xref linkend=\"sect.nftables\" />)."
2033 msgstr ""
2034
2035 msgid "Tunneling"
2036 msgstr "Tunnel"
2037
2038 #, fuzzy
2039 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2040 msgid "<primary>IPv6</primary><secondary>tunneling</secondary>"
2041 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2042
2043 msgid "<emphasis>CAUTION</emphasis> IPv6 tunneling and firewalls"
2044 msgstr "<emphasis>ATTENTION</emphasis> Tunnels IPv6 et pare-feu"
2045
2046 #, fuzzy
2047 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2048 msgid "<primary>IPv6</primary><secondary>tunnel broker</secondary>"
2049 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2050
2051 msgid "IPv6 tunneling over IPv4 (as opposed to native IPv6) requires the firewall to accept the traffic, which uses IPv4 protocol number 41."
2052 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."
2053
2054 #, fuzzy
2055 #| 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: <ulink type=\"block\" url=\"http://www.gogo6.com/freenet6/tunnelbroker\" />"
2056 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: <ulink type=\"block\" url=\"https://tunnelbroker.net\" />"
2057 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 : <ulink type=\"block\" url=\"http://www.gogo6.com/freenet6/tunnelbroker\" />"
2058
2059 #, fuzzy
2060 #| msgid "<primary>Source NAT</primary>"
2061 msgid "<primary>Hurricane Electric</primary>"
2062 msgstr "<primary><foreignphrase>Source NAT</foreignphrase></primary>"
2063
2064 #, fuzzy
2065 #| msgid "<primary>router</primary>"
2066 msgid "<primary>tunnel broker</primary>"
2067 msgstr "<primary>routeur</primary>"
2068
2069 msgid "To use a Hurricane Electric tunnel, you need to register an account, login, select a free tunnel and edit the file <filename>/etc/network/interfaces</filename> with the generated code."
2070 msgstr ""
2071
2072 msgid "<primary><command>radvd</command></primary>"
2073 msgstr "<primary><command>radvd</command></primary>"
2074
2075 #, fuzzy
2076 #| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>"
2077 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/radvd.conf</filename></secondary>"
2078 msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>"
2079
2080 #, fuzzy
2081 #| msgid "<primary>server</primary><secondary>name</secondary>"
2082 msgid "<primary>service</primary><secondary><filename>radvd.service</filename></secondary>"
2083 msgstr "<primary>serveur</primary><secondary>de noms</secondary>"
2084
2085 #, fuzzy
2086 #| 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 <command>radvd</command> daemon (from the similarly-named package). This IPv6 configuration daemon has a role similar to <command>dhcpd</command> in the IPv4 world."
2087 msgid "You can install and configure the <command>radvd</command> 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 <command>dhcpd</command> in the IPv4 world."
2088 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 <command>radvd</command> (du paquet éponyme). C'est un démon de configuration IPv6 jouant le même rôle que <command>dhcpd</command> pour le monde IPv4."
2089
2090 #, fuzzy
2091 #| msgid "<primary>network</primary><secondary>virtual private</secondary>"
2092 msgid "<primary><command>ip</command></primary><secondary><literal>address</literal></secondary>"
2093 msgstr "<primary>réseau</primary><secondary>privé virtuel</secondary>"
2094
2095 #, fuzzy
2096 #| msgid "The <filename>/etc/radvd.conf</filename> configuration file must then be created (see <filename>/usr/share/doc/radvd/examples/simple-radvd.conf</filename> 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 <command>ifconfig</command> command, in the block concerning the <literal>tun</literal> interface."
2097 msgid "The <filename>/etc/radvd.conf</filename> configuration file must then be created (see <filename>/usr/share/doc/radvd/examples/simple-radvd.conf</filename> 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 <command>ip a</command> command, in the block concerning the <literal>he-ipv6</literal> interface."
2098 msgstr "Il faut ensuite créer son fichier de configuration <filename>/etc/radvd.conf</filename> (par exemple en adaptant le fichier <filename>/usr/share/doc/radvd/examples/simple-radvd.conf</filename>). 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 <command>ifconfig</command> dans le bloc relatif à l'interface <literal>tun</literal>)."
2099
2100 #, fuzzy
2101 #| msgid "Then run <command>service gogoc restart</command> and <command>service radvd start</command>, and the IPv6 network should work."
2102 msgid "Then run <command>systemctl start radvd</command>. The IPv6 network should now work."
2103 msgstr "Après les commandes <command>service gogoc restart</command> et <command>service radvd start</command>, le réseau IPv6 sera enfin fonctionnel."
2104
2105 msgid "Domain Name Servers (DNS)"
2106 msgstr "Serveur de noms (DNS)"
2107
2108 msgid "<primary>DNS</primary>"
2109 msgstr "<primary>DNS</primary>"
2110
2111 #, fuzzy
2112 #| msgid "<primary>zone</primary><secondary>DNS</secondary>"
2113 msgid "<primary>Domain Name Service</primary><see>DNS</see>"
2114 msgstr "<primary>zone</primary><secondary>DNS</secondary>"
2115
2116 msgid "<primary>server</primary><secondary>name</secondary>"
2117 msgstr "<primary>serveur</primary><secondary>de noms</secondary>"
2118
2119 #, fuzzy
2120 #| msgid "<primary>Network</primary><secondary>Address Translation</secondary>"
2121 msgid "<primary>IP</primary><secondary>address mapping</secondary>"
2122 msgstr "<primary><foreignphrase>Network</foreignphrase></primary><secondary><foreignphrase>Address Translation</foreignphrase></secondary>"
2123
2124 #, fuzzy
2125 #| msgid "The <emphasis>Domain Name Service</emphasis> (DNS) is a fundamental component of the Internet: it maps host names to IP addresses (and vice-versa), which allows the use of <literal>www.debian.org</literal> instead of <literal>5.153.231.4</literal> or <literal>2001:41c8:1000:21::21:4</literal>."
2126 msgid "The <emphasis>Domain Name Service</emphasis> (DNS) is a fundamental component of the Internet: it maps host names to IP addresses (and vice-versa), which allows the use of <literal>www.debian.org</literal> instead of <literal>130.89.148.77</literal> or <literal>2001:67c:2564:a119::77</literal>."
2127 msgstr "Le service de gestion des noms <foreignphrase>(Domain Name Service)</foreignphrase> est fondamental sur Internet : il associe des noms à des adresses IP (et vice versa), ce qui permet de saisir <literal>france.debian.net</literal> en lieu et place de <literal>92.243.16.27</literal>."
2128
2129 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."
2130 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."
2131
2132 msgid "<primary>zone</primary><secondary>DNS</secondary>"
2133 msgstr "<primary>zone</primary><secondary>DNS</secondary>"
2134
2135 msgid "<primary>DNS</primary><secondary>zone</secondary>"
2136 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2137
2138 #, fuzzy
2139 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2140 msgid "<primary>DNS</primary><secondary>resource record</secondary>"
2141 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2142
2143 #, fuzzy
2144 #| msgid "Each zone can contain records of various kinds (<emphasis>Resource Records</emphasis>):"
2145 msgid "Each zone can contain records of various kinds (<emphasis>Resource Records</emphasis>), these are some of the most common:"
2146 msgstr "Chaque zone peut contenir différents types d'enregistrements <foreignphrase>(Resource Records)</foreignphrase>:"
2147
2148 msgid "<literal>A</literal> (<emphasis>address record</emphasis>): IPv4 address. This is the most common form to point a domain to an IPv4 address."
2149 msgstr ""
2150
2151 #, fuzzy
2152 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2153 msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>A</literal></tertiary>"
2154 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2155
2156 #, fuzzy
2157 #| msgid "<literal>CNAME</literal>: alias (<emphasis>canonical name</emphasis>). <indexterm><primary>CNAME, DNS record</primary></indexterm>"
2158 msgid "<literal>CNAME</literal> (<emphasis>canonical name record</emphasis>): alias"
2159 msgstr "<literal>CNAME</literal> : définition d'un alias. <indexterm><primary>CNAME, enregistrement DNS</primary></indexterm>"
2160
2161 #, fuzzy
2162 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2163 msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>CNAME</literal></tertiary>"
2164 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2165
2166 #, fuzzy
2167 #| msgid "<literal>MX</literal>: <emphasis>mail exchange</emphasis>, 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 <xref linkend=\"sidebar.smtp\" />); other servers are contacted in order of decreasing priority if the first one does not reply. <indexterm><primary>MX</primary><secondary>DNS record</secondary></indexterm>"
2168 msgid "<literal>MX</literal> (<emphasis>mail exchange</emphasis>): 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 <xref linkend=\"sidebar.smtp\" />); other servers are contacted in order of decreasing priority if the first one does not reply."
2169 msgstr "<literal>MX</literal> : 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é <xref linkend=\"sidebar.smtp\" />). S'il ne répond pas, le deuxième serveur sera contacté, etc. <indexterm><primary>MX</primary><secondary>enregistrement DNS</secondary></indexterm>"
2170
2171 #, fuzzy
2172 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2173 msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>MX</literal></tertiary>"
2174 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2175
2176 #, fuzzy
2177 #| msgid "<literal>PTR</literal>: 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, <literal>1.168.192.in-addr.arpa</literal> is the zone containing the reverse mapping for all addresses in the <literal>192.168.1.0/24</literal> range. <indexterm><primary>PTR, DNS record</primary></indexterm>"
2178 msgid "<literal>PTR</literal> (<emphasis>pointer</emphasis>): 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, <literal>1.168.192.in-addr.arpa</literal> is the zone containing the reverse mapping for all addresses in the <literal>192.168.1.0/24</literal> range."
2179 msgstr "<literal>PTR</literal> : 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 <literal>1.168.192.in-addr.arpa</literal> pour toutes les adresses du réseau <literal>192.168.1.0/24</literal>. <indexterm><primary>PTR, enregistrement DNS</primary></indexterm>"
2180
2181 #, fuzzy
2182 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2183 msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>PTR</literal></tertiary>"
2184 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2185
2186 msgid "<literal>AAAA</literal> (<emphasis>IPv6 address record</emphasis>): IPv6 address."
2187 msgstr ""
2188
2189 #, fuzzy
2190 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2191 msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>AAAA</literal></tertiary>"
2192 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2193
2194 #, fuzzy
2195 #| msgid "<literal>NS</literal>: 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 <literal>falcot.com</literal> zone can include an NS record for <literal>internal.falcot.com</literal>, which means that the <literal>internal.falcot.com</literal> zone is handled by another server. Of course, this server must declare an <literal>internal.falcot.com</literal> zone. <indexterm><primary>NS, DNS record</primary></indexterm>"
2196 msgid "<literal>NS</literal> (<emphasis>name server</emphasis>): 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 <literal>falcot.com</literal> zone can include an NS record for <literal>internal.falcot.com</literal>, which means that the <literal>internal.falcot.com</literal> zone is handled by another server. Of course, this server must declare an <literal>internal.falcot.com</literal> zone."
2197 msgstr "<literal>NS</literal> : 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 <literal>interne.falcot.com</literal> 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 <literal>interne.falcot.com</literal>. <indexterm><primary>NS, enregistrement DNS</primary></indexterm>"
2198
2199 #, fuzzy
2200 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2201 msgid "<primary>DNS</primary><secondary>resource record</secondary><tertiary><literal>NS</literal></tertiary>"
2202 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2203
2204 msgid "DNS software"
2205 msgstr ""
2206
2207 msgid "<primary>ISC</primary>"
2208 msgstr "<primary>ISC</primary>"
2209
2210 #, fuzzy
2211 #| msgid "<primary>Internet Software Consortium</primary>"
2212 msgid "<primary>Internet Software Consortium</primary><see>ISC</see>"
2213 msgstr "<primary><foreignphrase>Internet Software Consortium</foreignphrase></primary>"
2214
2215 msgid "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>"
2216 msgstr "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>"
2217
2218 #, fuzzy
2219 #| msgid "<primary>zone</primary><secondary>reverse</secondary>"
2220 msgid "<primary>DNS</primary><secondary><emphasis role=\"pkg\">bind9</emphasis></secondary><seealso><command>bind</command></seealso>"
2221 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
2222
2223 #, fuzzy
2224 #| msgid "The reference name server, Bind, was developed and is maintained by ISC (<emphasis>Internet Software Consortium</emphasis>). It is provided in Debian by the <emphasis role=\"pkg\">bind9</emphasis> 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)."
2225 msgid "The reference name server, Bind, was developed and is maintained by ISC (the <emphasis>Internet Software Consortium</emphasis>). It is provided in Debian by the <emphasis role=\"pkg\">bind9</emphasis> 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)."
2226 msgstr "Le logiciel serveur de noms de référence, Bind, est développé par l'ISC (<foreignphrase>Internet Software Consortium</foreignphrase>, ou consortium du logiciel Internet). Debian le fournit dans le paquet <emphasis role=\"pkg\">bind9</emphasis>. 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."
2227
2228 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."
2229 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."
2230
2231 msgid "<emphasis>CULTURE</emphasis> DNSSEC"
2232 msgstr "<emphasis>CULTURE</emphasis> DNSSEC"
2233
2234 msgid "<primary>DNSSEC</primary>"
2235 msgstr "<primary>DNSSEC</primary>"
2236
2237 msgid "<primary>Domain Name System Security Extensions</primary><see>DNSSEC</see>"
2238 msgstr ""
2239
2240 #, fuzzy
2241 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2242 msgid "<primary>DNS</primary><secondary>security extensions</secondary><see>DNSSEC</see>"
2243 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2244
2245 #, fuzzy
2246 #| 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. <ulink type=\"block\" url=\"http://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions\" />"
2247 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. <ulink type=\"block\" url=\"https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions\" />"
2248 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 <literal>.fr</literal>), 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). <ulink type=\"block\" url=\"https://www.afnic.fr/fr/produits-et-services/services/dnssec-1.html\" />"
2249
2250 #, fuzzy
2251 #| msgid "Configuring"
2252 msgid "Configuring bind"
2253 msgstr "Configuration"
2254
2255 #, fuzzy
2256 #| msgid "<primary>zone</primary><secondary>DNS</secondary>"
2257 msgid "<primary>daemon</primary><secondary>bind</secondary>"
2258 msgstr "<primary>zone</primary><secondary>DNS</secondary>"
2259
2260 #, fuzzy
2261 #| msgid "<primary>record</primary><secondary>DNS</secondary>"
2262 msgid "<primary>server</primary><secondary>DNS</secondary>"
2263 msgstr "<primary>enregistrement</primary><secondary>DNS</secondary>"
2264
2265 #, fuzzy
2266 #| msgid "<primary>network</primary><secondary>DHCP configuration</secondary>"
2267 msgid "<primary><command>bind</command></primary><secondary>configuration</secondary>"
2268 msgstr "<primary>réseau</primary><secondary>configuration DHCP</secondary>"
2269
2270 msgid "Configuration files for <command>bind</command>, irrespective of version, have the same structure."
2271 msgstr "Quelle que soit la version de <command>bind</command> employée, les fichiers de configuration ont la même structure."
2272
2273 msgid "The Falcot administrators created a primary <literal>falcot.com</literal> zone to store information related to this domain, and a <literal>168.192.in-addr.arpa</literal> zone for reverse mapping of IP addresses in the local networks."
2274 msgstr "Les administrateurs de Falcot ont créé une zone primaire <literal>falcot.com</literal> pour stocker les informations relatives à ce domaine et une zone <literal>168.192.in-addr.arpa</literal> pour les résolutions inverses des adresses IP des différents réseaux locaux."
2275
2276 msgid "<emphasis>CAUTION</emphasis> Names of reverse zones"
2277 msgstr "<emphasis>ATTENTION</emphasis> Noms des zones inverses"
2278
2279 msgid "<primary>zone</primary><secondary>reverse</secondary>"
2280 msgstr "<primary>zone</primary><secondary>inverse</secondary>"
2281
2282 msgid "<primary>reverse zone</primary>"
2283 msgstr "<primary>inverse, zone</primary>"
2284
2285 #, fuzzy
2286 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2287 msgid "<primary>DNS</primary><secondary>reverse zone</secondary>"
2288 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2289
2290 msgid "<primary><literal>in-addr.arpa</literal></primary>"
2291 msgstr "<primary><literal>in-addr.arpa</literal></primary>"
2292
2293 msgid "<primary><literal>ip6.arpa</literal></primary>"
2294 msgstr "<primary><literal>ip6.arpa</literal></primary>"
2295
2296 msgid "<primary>nibble format</primary>"
2297 msgstr "<primary>nibble, format</primary>"
2298
2299 msgid "Reverse zones have a particular name. The zone covering the <literal>192.168.0.0/16</literal> network needs to be named <literal>168.192.in-addr.arpa</literal>: the IP address components are reversed, and followed by the <literal>in-addr.arpa</literal> suffix."
2300 msgstr "Une zone inverse porte un nom particulier. La zone couvrant le réseau <literal>192.168.0.0/16</literal> s'appellera ainsi <literal>168.192.in-addr.arpa</literal> : les composants de l'adresse IP sont inversés et suivis du suffixe <literal>in-addr.arpa</literal>."
2301
2302 msgid "For IPv6 networks, the suffix is <literal>ip6.arpa</literal> and the IP address components which are reversed are each character in the full hexadecimal representation of the IP address. As such, the <literal>2001:0bc8:31a0::/48</literal> network would use a zone named <literal>0.a.1.3.8.c.b.0.1.0.0.2.ip6.arpa</literal>."
2303 msgstr "Pour les réseaux IPv6, le suffixe est <literal>ip6.arpa</literal> 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 <literal>2001:0bc8:31a0::/48</literal> utilise une zone nommée <literal>0.a.1.3.8.c.b.0.1.0.0.2.ip6.arpa</literal>."
2304
2305 msgid "<emphasis>TIP</emphasis> Testing the DNS server"
2306 msgstr "<emphasis>ASTUCE</emphasis> Tester le serveur DNS"
2307
2308 msgid "<primary><command>host</command></primary>"
2309 msgstr "<primary><command>host</command></primary>"
2310
2311 msgid "The <command>host</command> command (in the <emphasis role=\"pkg\">bind9-host</emphasis> package) queries a DNS server, and can be used to test the server configuration. For example, <command>host machine.falcot.com localhost</command> checks the local server's reply for the <literal>machine.falcot.com</literal> query. <command>host <replaceable>ipaddress</replaceable> localhost</command> tests the reverse resolution."
2312 msgstr "La commande <command>host</command> (du paquet <emphasis role=\"pkg\">bind9-host</emphasis>) interroge un serveur DNS, par exemple celui qu'on vient de configurer. La commande <command>host machine.falcot.com localhost</command> contrôlera donc la réponse du serveur DNS local pour la requête <literal>machine.falcot.com</literal>. La commande <command>host <replaceable>adresseip</replaceable> localhost</command> testera la résolution inverse."
2313
2314 #, fuzzy
2315 #| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>"
2316 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/bind/named.conf</filename></secondary>"
2317 msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>"
2318
2319 msgid "The following configuration excerpts, taken from the Falcot files, can serve as starting points to configure a DNS server:"
2320 msgstr "On pourra configurer un serveur DNS en s'inspirant des extraits suivants, issus des fichiers de configuration de la société Falcot:"
2321
2322 msgid "Excerpt of <filename>/etc/bind/named.conf.local</filename>"
2323 msgstr "Extrait du fichier <filename>/etc/bind/named.conf.local</filename>"
2324
2325 msgid ""
2326 "\n"
2327 "zone \"falcot.com\" {\n"
2328 " type master;\n"
2329 " file \"/etc/bind/db.falcot.com\";\n"
2330 " allow-query { any; };\n"
2331 " allow-transfer {\n"
2332 " 195.20.105.149/32 ; // ns0.xname.org\n"
2333 " 193.23.158.13/32 ; // ns1.xname.org\n"
2334 " };\n"
2335 "};\n"
2336 "\n"
2337 "zone \"internal.falcot.com\" {\n"
2338 " type master;\n"
2339 " file \"/etc/bind/db.internal.falcot.com\";\n"
2340 " allow-query { 192.168.0.0/16; };\n"
2341 "};\n"
2342 "\n"
2343 "zone \"168.192.in-addr.arpa\" {\n"
2344 " type master;\n"
2345 " file \"/etc/bind/db.192.168\";\n"
2346 " allow-query { 192.168.0.0/16; };\n"
2347 "};"
2348 msgstr ""
2349 "\n"
2350 "zone \"falcot.com\" {\n"
2351 " type master;\n"
2352 " file \"/etc/bind/db.falcot.com\";\n"
2353 " allow-query { any; };\n"
2354 " allow-transfer {\n"
2355 " 195.20.105.149/32 ; // ns0.xname.org\n"
2356 " 193.23.158.13/32 ; // ns1.xname.org\n"
2357 " };\n"
2358 "};\n"
2359 "\n"
2360 "zone \"interne.falcot.com\" {\n"
2361 " type master;\n"
2362 " file \"/etc/bind/db.interne.falcot.com\";\n"
2363 " allow-query { 192.168.0.0/16; };\n"
2364 "};\n"
2365 "\n"
2366 "zone \"168.192.in-addr.arpa\" {\n"
2367 " type master;\n"
2368 " file \"/etc/bind/db.192.168\";\n"
2369 " allow-query { 192.168.0.0/16; };\n"
2370 "};"
2371
2372 msgid "Excerpt of <filename>/etc/bind/db.falcot.com</filename>"
2373 msgstr "Extrait du fichier <filename>/etc/bind/db.falcot.com</filename>"
2374
2375 msgid ""
2376 "; falcot.com Zone \n"
2377 "; admin.falcot.com. =&gt; zone contact: [email protected]\n"
2378 "$TTL 604800\n"
2379 "@ IN SOA falcot.com. admin.falcot.com. (\n"
2380 " 20040121 ; Serial\n"
2381 " 604800 ; Refresh\n"
2382 " 86400 ; Retry\n"
2383 " 2419200 ; Expire\n"
2384 " 604800 ) ; Negative Cache TTL\n"
2385 ";\n"
2386 "; The @ refers to the zone name (\"falcot.com\" here)\n"
2387 "; or to $ORIGIN if that directive has been used\n"
2388 ";\n"
2389 "@ IN NS ns\n"
2390 "@ IN NS ns0.xname.org.\n"
2391 "\n"
2392 "internal IN NS 192.168.0.2\n"
2393 "\n"
2394 "@ IN A 212.94.201.10\n"
2395 "@ IN MX 5 mail\n"
2396 "@ IN MX 10 mail2\n"
2397 "\n"
2398 "ns IN A 212.94.201.10\n"
2399 "mail IN A 212.94.201.10\n"
2400 "mail2 IN A 212.94.201.11\n"
2401 "www IN A 212.94.201.11\n"
2402 "\n"
2403 "dns IN CNAME ns"
2404 msgstr ""
2405 "; Zone falcot.com\n"
2406 "; admin.falcot.com. =&gt; contact pour la zone: [email protected]\n"
2407 "$TTL 604800\n"
2408 "@ IN SOA falcot.com. admin.falcot.com. (\n"
2409 " 20040121 ; Serial\n"
2410 " 604800 ; Refresh\n"
2411 " 86400 ; Retry\n"
2412 " 2419200 ; Expire\n"
2413 " 604800 ) ; Negative Cache TTL\n"
2414 ";\n"
2415 "; Le @ fait référence au nom de la zone («falcot.com.» en l'occurrence)\n"
2416 "; ou à $ORIGIN si cette directive a été employée\n"
2417 ";\n"
2418 "@ IN NS ns\n"
2419 "@ IN NS ns0.xname.org.\n"
2420 "\n"
2421 "interne IN NS 192.168.0.2\n"
2422 "\n"
2423 "@ IN A 212.94.201.10\n"
2424 "@ IN MX 5 mail\n"
2425 "@ IN MX 10 mail2\n"
2426 "\n"
2427 "ns IN A 212.94.201.10\n"
2428 "mail IN A 212.94.201.10\n"
2429 "mail2 IN A 212.94.201.11\n"
2430 "www IN A 212.94.201.11\n"
2431 "\n"
2432 "dns IN CNAME ns"
2433
2434 msgid "<emphasis>CAUTION</emphasis> Syntax of a name"
2435 msgstr "<emphasis>ATTENTION</emphasis> Syntaxe d'un nom"
2436
2437 msgid "The syntax of machine names follows strict rules. For instance, <literal>machine</literal> implies <literal>machine.<replaceable>domain</replaceable></literal>. If the domain name should not be appended to a name, said name must be written as <literal>machine.</literal> (with a dot as suffix). Indicating a DNS name outside the current domain therefore requires a syntax such as <literal>machine.otherdomain.com.</literal> (with the final dot)."
2438 msgstr "La syntaxe désignant les noms de machines est particulière. <literal>machine</literal> sous-entend ainsi <literal>machine.<replaceable>domaine</replaceable></literal>. S'il ne faut pas ajouter automatiquement le nom du domaine, il convient d'écrire <literal>machine.</literal> (en suffixant ce nom d'un point). Pour indiquer un nom DNS extérieur au domaine géré, on écrira donc <literal>machine.autredomaine.com.</literal> avec un point."
2439
2440 msgid "Excerpt of <filename>/etc/bind/db.192.168</filename>"
2441 msgstr "Extrait du fichier <filename>/etc/bind/db.192.168</filename>"
2442
2443 msgid ""
2444 "; Reverse zone for 192.168.0.0/16\n"
2445 "; admin.falcot.com. =&gt; zone contact: [email protected]\n"
2446 "$TTL 604800\n"
2447 "@ IN SOA ns.internal.falcot.com. admin.falcot.com. (\n"
2448 " 20040121 ; Serial\n"
2449 " 604800 ; Refresh\n"
2450 " 86400 ; Retry\n"
2451 " 2419200 ; Expire\n"
2452 " 604800 ) ; Negative Cache TTL\n"
2453 "\n"
2454 " IN NS ns.internal.falcot.com.\n"
2455 "\n"
2456 "; 192.168.0.1 -&gt; arrakis\n"
2457 "1.0 IN PTR arrakis.internal.falcot.com.\n"
2458 "; 192.168.0.2 -&gt; neptune\n"
2459 "2.0 IN PTR neptune.internal.falcot.com.\n"
2460 "\n"
2461 "; 192.168.3.1 -&gt; pau\n"
2462 "1.3 IN PTR pau.internal.falcot.com."
2463 msgstr ""
2464 "; Zone inverse pour 192.168.0.0/16\n"
2465 "; admin.falcot.com. =&gt; contact pour la zone: [email protected]\n"
2466 "$TTL 604800\n"
2467 "@ IN SOA ns.interne.falcot.com. admin.falcot.com. (\n"
2468 " 20040121 ; Serial\n"
2469 " 604800 ; Refresh\n"
2470 " 86400 ; Retry\n"
2471 " 2419200 ; Expire\n"
2472 " 604800 ) ; Negative Cache TTL\n"
2473 "\n"
2474 " IN NS ns.interne.falcot.com.\n"
2475 "\n"
2476 "; 192.168.0.1 -&gt; arrakis\n"
2477 "1.0 IN PTR arrakis.interne.falcot.com.\n"
2478 "; 192.168.0.2 -&gt; neptune\n"
2479 "2.0 IN PTR neptune.interne.falcot.com.\n"
2480 "\n"
2481 "; 192.168.3.1 -&gt; pau\n"
2482 "1.3 IN PTR pau.interne.falcot.com."
2483
2484 #, fuzzy
2485 #| msgid "<primary>Dynamic Host Configuration Protocol</primary>"
2486 msgid "<primary>DHCP</primary><seealso>Dynamic Host Configuration Protocol</seealso>"
2487 msgstr "<primary><foreignphrase>Dynamic Host Configuration Protocol</foreignphrase></primary>"
2488
2489 #, fuzzy
2490 #| msgid "<primary>Dynamic Host Configuration Protocol</primary>"
2491 msgid "<primary>Dynamic Host Configuration Protocol</primary><seealso>DHCP</seealso>"
2492 msgstr "<primary><foreignphrase>Dynamic Host Configuration Protocol</foreignphrase></primary>"
2493
2494 msgid "<primary>network</primary><secondary>DHCP configuration</secondary>"
2495 msgstr "<primary>réseau</primary><secondary>configuration DHCP</secondary>"
2496
2497 #, fuzzy
2498 #| msgid "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>"
2499 msgid "<primary><emphasis role=\"pkg\">isc-dhcp-server</emphasis></primary>"
2500 msgstr "<primary><emphasis role=\"pkg\">bind9</emphasis></primary>"
2501
2502 msgid "DHCP (for <emphasis>Dynamic Host Configuration Protocol</emphasis>) 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."
2503 msgstr "DHCP (<foreignphrase>Dynamic Host Configuration Protocol</foreignphrase>, 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."
2504
2505 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."
2506 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."
2507
2508 msgid "The Internet Software Consortium (also involved in developing <command>bind</command>) is the main author of the DHCP server. The matching Debian package is <emphasis role=\"pkg\">isc-dhcp-server</emphasis>."
2509 msgstr "L'<foreignphrase>Internet Software Consortium</foreignphrase>, qui développe <command>bind</command>, s'occupe également du serveur DHCP. Le paquet Debian correspondant est <emphasis role=\"pkg\">isc-dhcp-server</emphasis>."
2510
2511 msgid "Configuring"
2512 msgstr "Configuration"
2513
2514 #, fuzzy
2515 #| msgid "<primary>DNS</primary><secondary>zone</secondary>"
2516 msgid "<primary>DHCP</primary><secondary></secondary>"
2517 msgstr "<primary>DNS</primary><secondary>zone</secondary>"
2518
2519 #, fuzzy
2520 #| msgid "<primary>server</primary><secondary>name</secondary>"
2521 msgid "<primary>server</primary><secondary>DHCP</secondary>"
2522 msgstr "<primary>serveur</primary><secondary>de noms</secondary>"
2523
2524 #, fuzzy
2525 #| msgid "<primary>zone</primary><secondary>DNS</secondary>"
2526 msgid "<primary>daemon</primary><secondary>dhcpd</secondary>"
2527 msgstr "<primary>zone</primary><secondary>DNS</secondary>"
2528
2529 #, fuzzy
2530 #| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>"
2531 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/dhcp/dhcpd.conf</filename></secondary>"
2532 msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>"
2533
2534 #, fuzzy
2535 #| msgid "<primary><filename>/etc/bind/named.conf</filename></primary>"
2536 msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/dhcp/dhcpd6.conf</filename></secondary>"
2537 msgstr "<primary><filename>/etc/bind/named.conf</filename></primary>"
2538
2539 #, fuzzy
2540 #| msgid "The first elements that need to be edited in the DHCP server configuration file (<filename>/etc/dhcp/dhcpd.conf</filename>) are the domain name and the DNS servers. If this server is alone on the local network (as defined by the broadcast propagation), the <literal>authoritative</literal> directive must also be enabled (or uncommented). One also needs to create a <literal>subnet</literal> section describing the local network and the configuration information to be provided. The following example fits a <literal>192.168.0.0/24</literal> local network with a router at <literal>192.168.0.1</literal> serving as the gateway. Available IP addresses are in the range <literal>192.168.0.128</literal> to <literal>192.168.0.254</literal>."
2541 msgid "The first elements that need to be edited in the DHCP server configuration files (<filename>/etc/dhcp/dhcpd.conf</filename>, and <filename>/etc/dhcp/dhcpd6.conf</filename> 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 <literal>authoritative</literal> directive must also be enabled (or uncommented). One also needs to create a <literal>subnet</literal> section describing the local network and the configuration information to be provided. The following example fits a <literal>192.168.0.0/24</literal> local network with a router at <literal>192.168.0.1</literal> serving as the gateway. Available IP addresses are in the range <literal>192.168.0.128</literal> to <literal>192.168.0.254</literal>."
2542 msgstr "Les premiers éléments à modifier dans le fichier de configuration du serveur DHCP, <filename>/etc/dhcp/dhcpd.conf</filename>, sont le nom de domaine et les serveurs DNS. Il faut aussi activer (en la décommentant) l'option <literal>authoritative</literal> si ce serveur est le seul sur le réseau local (tel que défini par la limite de propagation du <foreignphrase>broadcast</foreignphrase>, mécanisme employé pour joindre le serveur DHCP). On créera aussi une section <literal>subnet</literal> décrivant le réseau local et les informations de configuration diffusées. L'exemple ci-dessous convient pour le réseau local <literal>192.168.0.0/24</literal>, qui dispose d'un routeur (<literal>192.168.0.1</literal>) faisant office de passerelle externe. Les adresses IP disponibles sont comprises entre <literal>192.168.0.128</literal> et <literal>192.168.0.254</literal>."
2543
2544 msgid "Excerpt of <filename>/etc/dhcp/dhcpd.conf</filename>"
2545 msgstr "Extrait du fichier <filename>/etc/dhcp/dhcpd.conf</filename>"
2546
2547 msgid ""
2548 "\n"
2549 "#\n"
2550 "# Sample configuration file for ISC dhcpd for Debian\n"
2551 "#\n"
2552 "\n"
2553 "# The ddns-updates-style parameter controls whether or not the server will\n"
2554 "# attempt to do a DNS update when a lease is confirmed. We default to the\n"
2555 "# behavior of the version 2 packages ('none', since DHCP v2 didn't\n"
2556 "# have support for DDNS.)\n"
2557 "ddns-update-style interim;\n"
2558 "\n"
2559 "# option definitions common to all supported networks...\n"
2560 "option domain-name \"internal.falcot.com\";\n"
2561 "option domain-name-servers ns.internal.falcot.com;\n"
2562 "\n"
2563 "default-lease-time 600;\n"
2564 "max-lease-time 7200;\n"
2565 "\n"
2566 "# If this DHCP server is the official DHCP server for the local\n"
2567 "# network, the authoritative directive should be uncommented.\n"
2568 "authoritative;\n"
2569 "\n"
2570 "# Use this to send dhcp log messages to a different log file (you also\n"
2571 "# have to hack syslog.conf to complete the redirection).\n"
2572 "log-facility local7;\n"
2573 "\n"
2574 "# My subnet\n"
2575 "subnet 192.168.0.0 netmask 255.255.255.0 {\n"
2576 " option routers 192.168.0.1;\n"
2577 " option broadcast-address 192.168.0.255;\n"
2578 " range 192.168.0.128 192.168.0.254;\n"
2579 " ddns-domainname \"internal.falcot.com\";\n"
2580 "}"
2581 msgstr ""
2582 "\n"
2583 "#\n"
2584 "# Sample configuration file for ISC dhcpd for Debian\n"
2585 "#\n"
2586 "\n"
2587 "# The ddns-updates-style parameter controls whether or not the server will\n"
2588 "# attempt to do a DNS update when a lease is confirmed. We default to the\n"
2589 "# behavior of the version 2 packages ('none', since DHCP v2 didn't\n"
2590 "# have support for DDNS.)\n"
2591 "ddns-update-style interim;\n"
2592 "\n"
2593 "# option definitions common to all supported networks...\n"
2594 "option domain-name \"interne.falcot.com\";\n"
2595 "option domain-name-servers ns.interne.falcot.com;\n"
2596 "\n"
2597 "default-lease-time 600;\n"
2598 "max-lease-time 7200;\n"
2599 "\n"
2600 "# If this DHCP server is the official DHCP server for the local\n"
2601 "# network, the authoritative directive should be uncommented.\n"
2602 "authoritative;\n"
2603 "\n"
2604 "# Use this to send dhcp log messages to a different log file (you also\n"
2605 "# have to hack syslog.conf to complete the redirection).\n"
2606 "log-facility local7;\n"
2607 "\n"
2608 "# My subnet\n"
2609 "subnet 192.168.0.0 netmask 255.255.255.0 {\n"
2610 " option routers 192.168.0.1;\n"
2611 " option broadcast-address 192.168.0.255;\n"
2612 " range 192.168.0.128 192.168.0.254;\n"
2613 " ddns-domainname \"interne.falcot.com\";\n"
2614 "}"
2615
2616 msgid "DHCP and DNS"
2617 msgstr "DHCP et DNS"
2618
2619 msgid "<primary>DNS</primary><secondary>automated updates</secondary>"
2620 msgstr "<primary>DNS</primary><secondary>mise à jour automatique</secondary>"
2621
2622 #, fuzzy
2623 #| msgid "<primary><command>ripngd</command></primary>"
2624 msgid "<primary><command>bind</command></primary>"
2625 msgstr "<primary><command>ripngd</command></primary>"
2626
2627 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 <literal>machine-192-168-0-131.internal.falcot.com</literal>). Using this feature requires configuring the DNS server to accept updates to the <literal>internal.falcot.com</literal> DNS zone from the DHCP server, and configuring the latter to submit updates for each registration."
2628 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 <literal>machine-192-168-0-131.interne.falcot.com</literal>). Pour exploiter cette possibilité, il faut autoriser le serveur DHCP à mettre à jour la zone DNS <literal>interne.falcot.com</literal> et configurer celui-ci pour qu'il s'en charge."
2629
2630 #, fuzzy
2631 #| msgid "In the <command>bind</command> case, the <literal>allow-update</literal> directive needs to be added to each of the zones that the DHCP server is to edit (the one for the <literal>internal.falcot.com</literal> 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)."
2632 msgid "In the <command>bind</command> case (see <xref linkend=\"sect.dns-software\" />), the <literal>allow-update</literal> directive needs to be added to each of the zones that the DHCP server is to edit (the one for the <literal>internal.falcot.com</literal> 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)."
2633 msgstr "Dans le cas de <command>bind</command>, on ajoutera la directive <literal>allow-update</literal> aux deux zones que le serveur DHCP devra modifier (celle du domaine <literal>interne.falcot.com</literal> 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)."
2634
2635 msgid ""
2636 "\n"
2637 "allow-update { 127.0.0.1 192.168.0.1 212.94.201.10 !any };"
2638 msgstr ""
2639 "\n"
2640 "allow-update { 127.0.0.1 192.168.0.1 212.94.201.10 !any };"
2641
2642 msgid "Beware! A zone that can be modified <emphasis>will</emphasis> be changed by <command>bind</command>, 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 <literal>internal.falcot.com</literal> domain with a delegated DNS server; this means the <literal>falcot.com</literal> zone file stays firmly under their manual control."
2643 msgstr "Attention ! Une zone modifiable sera changée par <command>bind</command>, 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 <literal>interne.falcot.com</literal> à l'aide d'un serveur DNS délégué. Le fichier de la zone <literal>falcot.com</literal> reste ainsi entièrement sous leur contrôle."
2644
2645 #, fuzzy
2646 #| msgid "The DHCP server configuration excerpt above already includes the directives required for DNS zone updates: they are the <literal>ddns-update-style interim;</literal> and <literal>ddns-domain-name \"internal.falcot.com\";</literal> lines in the block describing the subnet."
2647 msgid "The DHCP server configuration excerpt above already includes the directives required for DNS zone updates: they are the <literal>ddns-update-style interim;</literal> and <literal>ddns-domain-name \"internal.falcot.com\";</literal> lines."
2648 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 <literal>ddns-update-style interim ;</literal> et <literal>ddns-domain-name \"interne.falcot.com\";</literal> dans le bloc décrivant le réseau."
2649
2650 msgid "Network Diagnosis Tools"
2651 msgstr "Outils de diagnostic réseau"
2652
2653 #, fuzzy
2654 #| msgid "<primary>network</primary><secondary>gateway</secondary>"
2655 msgid "<primary>network</primary><secondary>diagnosis</secondary>"
2656 msgstr "<primary>réseau</primary><secondary>passerelle</secondary>"
2657
2658 #, fuzzy
2659 #| 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."
2660 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."
2661 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."
2662
2663 msgid "Local Diagnosis: <command>netstat</command>"
2664 msgstr "Diagnostic local : <command>netstat</command>"
2665
2666 msgid "<primary><command>netstat</command></primary>"
2667 msgstr "<primary><command>netstat</command></primary>"
2668
2669 msgid "Let's first mention the <command>netstat</command> command (in the <emphasis role=\"pkg\">net-tools</emphasis> 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, <literal>dbus</literal> communication, <literal>X11</literal> traffic, and communications between virtual filesystems and the desktop)."
2670 msgstr "Citons tout d'abord la commande <command>netstat</command> (du paquet <emphasis role=\"pkg\">net-tools</emphasis>), 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."
2671
2672 msgid "Common invocations therefore use options that alter <command>netstat</command>'s behavior. The most frequently used options include:"
2673 msgstr "On utilise donc généralement des options, qui permettent de modifier le comportement de <command>netstat</command>. Parmi les options les plus courantes, on trouve :"
2674
2675 msgid "<literal>-t</literal>, which filters the results to only include TCP connections;"
2676 msgstr "<literal>-t</literal>, qui filtre les résultats renvoyés pour que seules les connexions TCP soient listées ;"
2677
2678 msgid "<literal>-u</literal>, which works similarly for UDP connections; these options are not mutually exclusive, and one of them is enough to stop displaying Unix-domain connections;"
2679 msgstr "<literal>-u</literal>, 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 ;"
2680
2681 msgid "<literal>-a</literal>, to also list listening sockets (waiting for incoming connections);"
2682 msgstr "<literal>-a</literal>, qui liste également les <foreignphrase>sockets</foreignphrase> en écoute (en attente de connexions entrantes) ;"
2683
2684 msgid "<literal>-n</literal>, to display the results numerically: IP addresses (no DNS resolution), port numbers (no aliases as defined in <filename>/etc/services</filename>) and user ids (no login names);"
2685 msgstr "<literal>-n</literal>, 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 <filename>/etc/services</filename>) et les numéros d'utilisateurs (et non leur nom de connexion) ;"
2686
2687 msgid "<literal>-p</literal>, to list the processes involved; this option is only useful when <command>netstat</command> is run as root, since normal users will only see their own processes;"
2688 msgstr "<literal>-p</literal>, qui affiche les processus mis en jeu ; cette option n'est réellement utile que lorsque <command>netstat</command> est invoqué par l'utilisateur root, faute de quoi seuls les processus appartenant au même utilisateur seront listés ;"
2689
2690 msgid "<literal>-c</literal>, to continuously refresh the list of connections."
2691 msgstr "<literal>-c</literal>, qui rafraîchit la liste des connexions en continu."
2692
2693 msgid "Other options, documented in the <citerefentry><refentrytitle>netstat</refentrytitle> <manvolnum>8</manvolnum></citerefentry> 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 <command>netstat -tupan</command> as a reflex. Typical results, on a lightly loaded machine, may look like the following:"
2694 msgstr "D'autres options (documentées dans la page de manuel <citerefentry><refentrytitle>netstat</refentrytitle> <manvolnum>8</manvolnum></citerefentry>) 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 <command>netstat -tupan</command> 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 :"
2695
2696 msgid ""
2697 "\n"
2698 "<computeroutput># </computeroutput><userinput>netstat -tupan</userinput>\n"
2699 "<computeroutput>Active Internet connections (servers and established)\n"
2700 "Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name\n"
2701 "tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 397/rpcbind \n"
2702 "tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 431/sshd \n"
2703 "tcp 0 0 0.0.0.0:36568 0.0.0.0:* LISTEN 407/rpc.statd \n"
2704 "tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 762/exim4 \n"
2705 "tcp 0 272 192.168.1.242:22 192.168.1.129:44452 ESTABLISHED 1172/sshd: roland [\n"
2706 "tcp6 0 0 :::111 :::* LISTEN 397/rpcbind \n"
2707 "tcp6 0 0 :::22 :::* LISTEN 431/sshd \n"
2708 "tcp6 0 0 ::1:25 :::* LISTEN 762/exim4 \n"
2709 "tcp6 0 0 :::35210 :::* LISTEN 407/rpc.statd \n"
2710 "udp 0 0 0.0.0.0:39376 0.0.0.0:* 916/dhclient \n"
2711 "udp 0 0 0.0.0.0:996 0.0.0.0:* 397/rpcbind \n"
2712 "udp 0 0 127.0.0.1:1007 0.0.0.0:* 407/rpc.statd \n"
2713 "udp 0 0 0.0.0.0:68 0.0.0.0:* 916/dhclient \n"
2714 "udp 0 0 0.0.0.0:48720 0.0.0.0:* 451/avahi-daemon: r\n"
2715 "udp 0 0 0.0.0.0:111 0.0.0.0:* 397/rpcbind \n"
2716 "udp 0 0 192.168.1.242:123 0.0.0.0:* 539/ntpd \n"
2717 "udp 0 0 127.0.0.1:123 0.0.0.0:* 539/ntpd \n"
2718 "udp 0 0 0.0.0.0:123 0.0.0.0:* 539/ntpd \n"
2719 "udp 0 0 0.0.0.0:5353 0.0.0.0:* 451/avahi-daemon: r\n"
2720 "udp 0 0 0.0.0.0:39172 0.0.0.0:* 407/rpc.statd \n"
2721 "udp6 0 0 :::996 :::* 397/rpcbind \n"
2722 "udp6 0 0 :::34277 :::* 407/rpc.statd \n"
2723 "udp6 0 0 :::54852 :::* 916/dhclient \n"
2724 "udp6 0 0 :::111 :::* 397/rpcbind \n"
2725 "udp6 0 0 :::38007 :::* 451/avahi-daemon: r\n"
2726 "udp6 0 0 fe80::5054:ff:fe99::123 :::* 539/ntpd \n"
2727 "udp6 0 0 2001:bc8:3a7e:210:a:123 :::* 539/ntpd \n"
2728 "udp6 0 0 2001:bc8:3a7e:210:5:123 :::* 539/ntpd \n"
2729 "udp6 0 0 ::1:123 :::* 539/ntpd \n"
2730 "udp6 0 0 :::123 :::* 539/ntpd \n"
2731 "udp6 0 0 :::5353 :::* 451/avahi-daemon: r\n"
2732 "</computeroutput>"
2733 msgstr ""
2734 "\n"
2735 "<computeroutput># </computeroutput><userinput>netstat -tupan</userinput>\n"
2736 "<computeroutput>Connexions Internet actives (serveurs et établies)\n"
2737 "Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name\n"
2738 "tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 397/rpcbind \n"
2739 "tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 431/sshd \n"
2740 "tcp 0 0 0.0.0.0:36568 0.0.0.0:* LISTEN 407/rpc.statd \n"
2741 "tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 762/exim4 \n"
2742 "tcp 0 272 192.168.1.242:22 192.168.1.129:44452 ESTABLISHED 1172/sshd: roland [\n"
2743 "tcp6 0 0 :::111 :::* LISTEN 397/rpcbind \n"
2744 "tcp6 0 0 :::22 :::* LISTEN 431/sshd \n"
2745 "tcp6 0 0 ::1:25 :::* LISTEN 762/exim4 \n"
2746 "tcp6 0 0 :::35210 :::* LISTEN 407/rpc.statd \n"
2747 "udp 0 0 0.0.0.0:39376 0.0.0.0:* 916/dhclient \n"
2748 "udp 0 0 0.0.0.0:996 0.0.0.0:* 397/rpcbind \n"
2749 "udp 0 0 127.0.0.1:1007 0.0.0.0:* 407/rpc.statd \n"
2750 "udp 0 0 0.0.0.0:68 0.0.0.0:* 916/dhclient \n"
2751 "udp 0 0 0.0.0.0:48720 0.0.0.0:* 451/avahi-daemon: r\n"
2752 "udp 0 0 0.0.0.0:111 0.0.0.0:* 397/rpcbind \n"
2753 "udp 0 0 192.168.1.242:123 0.0.0.0:* 539/ntpd \n"
2754 "udp 0 0 127.0.0.1:123 0.0.0.0:* 539/ntpd \n"
2755 "udp 0 0 0.0.0.0:123 0.0.0.0:* 539/ntpd \n"
2756 "udp 0 0 0.0.0.0:5353 0.0.0.0:* 451/avahi-daemon: r\n"
2757 "udp 0 0 0.0.0.0:39172 0.0.0.0:* 407/rpc.statd \n"
2758 "udp6 0 0 :::996 :::* 397/rpcbind \n"
2759 "udp6 0 0 :::34277 :::* 407/rpc.statd \n"
2760 "udp6 0 0 :::54852 :::* 916/dhclient \n"
2761 "udp6 0 0 :::111 :::* 397/rpcbind \n"
2762 "udp6 0 0 :::38007 :::* 451/avahi-daemon: r\n"
2763 "udp6 0 0 fe80::5054:ff:fe99::123 :::* 539/ntpd \n"
2764 "udp6 0 0 2001:bc8:3a7e:210:a:123 :::* 539/ntpd \n"
2765 "udp6 0 0 2001:bc8:3a7e:210:5:123 :::* 539/ntpd \n"
2766 "udp6 0 0 ::1:123 :::* 539/ntpd \n"
2767 "udp6 0 0 :::123 :::* 539/ntpd \n"
2768 "udp6 0 0 :::5353 :::* 451/avahi-daemon: r\n"
2769 "</computeroutput>"
2770
2771 msgid "As expected, this lists established connections, two SSH connections in this case, and applications waiting for incoming connections (listed as <literal>LISTEN</literal>), notably the Exim4 email server listening on port 25."
2772 msgstr "On y retrouve bien les connexions établies (<literal>ESTABLISHED</literal>), ici deux connexions SSH, et les applications en attente de connexion (<literal>LISTEN</literal>), notamment le serveur de messagerie Exim4 sur le port 25."
2773
2774 msgid "Remote Diagnosis: <command>nmap</command>"
2775 msgstr "Diagnostic distant : <command>nmap</command>"
2776
2777 msgid "<primary><command>nmap</command></primary>"
2778 msgstr "<primary><command>nmap</command></primary>"
2779
2780 msgid "<command>nmap</command> (in the similarly-named package) is, in a way, the remote equivalent for <command>netstat</command>. 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, <command>nmap</command> 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."
2781 msgstr "<command>nmap</command> (du paquet éponyme) est en quelque sorte l'équivalent de <command>netstat</command>, 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. <command>nmap</command> 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."
2782
2783 msgid "A typical <command>nmap</command> invocation only uses the <literal>-A</literal> option (so that <command>nmap</command> 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 <command>nmap</command>; please refer to the documentation in the <citerefentry> <refentrytitle>nmap</refentrytitle> <manvolnum>1</manvolnum> </citerefentry> manual page."
2784 msgstr "Une utilisation typique de <command>nmap</command> utilise simplement l'option <literal>-A</literal>, 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 <command>nmap</command> ; on se référera à la documentation, dans la page de manuel <citerefentry> <refentrytitle>nmap</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>."
2785
2786 #, fuzzy
2787 #| msgid ""
2788 #| "\n"
2789 #| "<computeroutput># </computeroutput><userinput>nmap mirtuel</userinput>\n"
2790 #| "<computeroutput>\n"
2791 #| "Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-09 16:46 CET\n"
2792 #| "Nmap scan report for mirtuel (192.168.1.242)\n"
2793 #| "Host is up (0.000013s latency).\n"
2794 #| "rDNS record for 192.168.1.242: mirtuel.internal.placard.fr.eu.org\n"
2795 #| "Not shown: 998 closed ports\n"
2796 #| "PORT STATE SERVICE\n"
2797 #| "22/tcp open ssh\n"
2798 #| "111/tcp open rpcbind\n"
2799 #| "\n"
2800 #| "Nmap done: 1 IP address (1 host up) scanned in 2.41 seconds\n"
2801 #| "# </computeroutput><userinput>nmap -A localhost</userinput>\n"
2802 #| "<computeroutput>\n"
2803 #| "Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-09 16:46 CET\n"
2804 #| "Nmap scan report for localhost (127.0.0.1)\n"
2805 #| "Host is up (0.000013s latency).\n"
2806 #| "Other addresses for localhost (not scanned): 127.0.0.1\n"
2807 #| "Not shown: 997 closed ports\n"
2808 #| "PORT STATE SERVICE VERSION\n"
2809 #| "22/tcp open ssh OpenSSH 6.7p1 Debian 3 (protocol 2.0)\n"
2810 #| "|_ssh-hostkey: ERROR: Script execution failed (use -d to debug)\n"
2811 #| "25/tcp open smtp Exim smtpd 4.84\n"
2812 #| "| smtp-commands: mirtuel Hello localhost [127.0.0.1], SIZE 52428800, 8BITMIME, PIPELINING, HELP, \n"
2813 #| "|_ Commands supported: AUTH HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP \n"
2814 #| "111/tcp open rpcbind 2-4 (RPC #100000)\n"
2815 #| "| rpcinfo: \n"
2816 #| "| program version port/proto service\n"
2817 #| "| 100000 2,3,4 111/tcp rpcbind\n"
2818 #| "| 100000 2,3,4 111/udp rpcbind\n"
2819 #| "| 100024 1 36568/tcp status\n"
2820 #| "|_ 100024 1 39172/udp status\n"
2821 #| "Device type: general purpose\n"
2822 #| "Running: Linux 3.X\n"
2823 #| "OS CPE: cpe:/o:linux:linux_kernel:3\n"
2824 #| "OS details: Linux 3.7 - 3.15\n"
2825 #| "Network Distance: 0 hops\n"
2826 #| "Service Info: Host: mirtuel; OS: Linux; CPE: cpe:/o:linux:linux_kernel\n"
2827 #| "\n"
2828 #| "OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .\n"
2829 #| "Nmap done: 1 IP address (1 host up) scanned in 11.54 seconds\n"
2830 #| "</computeroutput>"
2831 msgid ""
2832 "\n"
2833 "<computeroutput># </computeroutput><userinput>nmap debian</userinput>\n"
2834 "<computeroutput><![CDATA[Starting Nmap 7.80 ( https://nmap.org ) at 2022-02-22 20:58 CET\n"
2835 "Nmap scan report for debian (192.168.122.57)\n"
2836 "Host is up (0.000087s latency).\n"
2837 "Not shown: 996 closed ports\n"
2838 "PORT STATE SERVICE\n"
2839 "22/tcp open ssh\n"
2840 "79/tcp open finger\n"
2841 "80/tcp open http\n"
2842 "113/tcp open ident\n"
2843 "\n"
2844 "Nmap done: 1 IP address (1 host up) scanned in 0.07 seconds\n"
2845 "]]># </computeroutput><userinput>nmap -A localhost</userinput>\n"
2846 "<computeroutput><![CDATA[nmap -A localhost\n"
2847 "Starting Nmap 7.80 ( https://nmap.org ) at 2022-02-22 20:56 CET\n"
2848 "Stats: 0:01:16 elapsed; 0 hosts completed (1 up), 1 undergoing Service Scan\n"
2849 "Service scan Timing: About 83.33% done; ETC: 20:57 (0:00:15 remaining)\n"
2850 "Nmap scan report for localhost (127.0.0.1)\n"
2851 "Host is up (0.000086s latency).\n"
2852 "Other addresses for localhost (not scanned): ::1\n"
2853 "Not shown: 994 closed ports\n"
2854 "PORT STATE SERVICE VERSION\n"
2855 "22/tcp open ssh OpenSSH 8.4p1 Debian 5 (protocol 2.0)\n"
2856 "|_auth-owners: foobar\n"
2857 "25/tcp open smtp Postfix smtpd\n"
2858 "|_auth-owners: foobar\n"
2859 "|_smtp-commands: debian, PIPELINING, SIZE 10240000, VRFY, ETRN, STARTTLS, ENHANCEDSTATUSCODES, 8BITMIME, DSN, SMTPUTF8, CHUNKING, \n"
2860 "| ssl-cert: Subject: commonName=debian\n"
2861 "| Subject Alternative Name: DNS:debian\n"
2862 "| Not valid before: 2022-02-22T14:48:42\n"
2863 "|_Not valid after: 2032-02-20T14:48:42\n"
2864 "|_ssl-date: TLS randomness does not represent time\n"
2865 "79/tcp open finger?\n"
2866 "|_auth-owners: foobar\n"
2867 "|_finger: ERROR: Script execution failed (use -d to debug)\n"
2868 "80/tcp open http Apache httpd 2.4.52 ((Debian))\n"
2869 "|_auth-owners: foobar\n"
2870 "|_http-server-header: Apache/2.4.52 (Debian)\n"
2871 "|_http-title: Apache2 Debian Default Page: It works\n"
2872 "113/tcp open ident Liedentd (Claimed user: foobar)\n"
2873 "|_auth-owners: foobar\n"
2874 "631/tcp open ipp CUPS 2.3\n"
2875 "|_auth-owners: foobar\n"
2876 "| http-robots.txt: 1 disallowed entry \n"
2877 "|_/\n"
2878 "|_http-server-header: CUPS/2.3 IPP/2.1\n"
2879 "|_http-title: Home - CUPS 2.3.3op2\n"
2880 "Service Info: Host: debian; OS: Linux; CPE: cpe:/o:linux:linux_kernel\n"
2881 "\n"
2882 "Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .\n"
2883 "Nmap done: 1 IP address (1 host up) scanned in 87.91 seconds\n"
2884 "]]></computeroutput>"
2885 msgstr ""
2886 "\n"
2887 "<computeroutput># </computeroutput><userinput>nmap mirtuel</userinput>\n"
2888 "<computeroutput>\n"
2889 "Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-09 16:46 CET\n"
2890 "Nmap scan report for mirtuel (192.168.1.242)\n"
2891 "Host is up (0.000013s latency).\n"
2892 "rDNS record for 192.168.1.242: mirtuel.internal.placard.fr.eu.org\n"
2893 "Not shown: 998 closed ports\n"
2894 "PORT STATE SERVICE\n"
2895 "22/tcp open ssh\n"
2896 "111/tcp open rpcbind\n"
2897 "\n"
2898 "Nmap done: 1 IP address (1 host up) scanned in 2.41 seconds\n"
2899 "# </computeroutput><userinput>nmap -A localhost</userinput>\n"
2900 "<computeroutput>\n"
2901 "Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-09 16:46 CET\n"
2902 "Nmap scan report for localhost (127.0.0.1)\n"
2903 "Host is up (0.000013s latency).\n"
2904 "Other addresses for localhost (not scanned): 127.0.0.1\n"
2905 "Not shown: 997 closed ports\n"
2906 "PORT STATE SERVICE VERSION\n"
2907 "22/tcp open ssh OpenSSH 6.7p1 Debian 3 (protocol 2.0)\n"
2908 "|_ssh-hostkey: ERROR: Script execution failed (use -d to debug)\n"
2909 "25/tcp open smtp Exim smtpd 4.84\n"
2910 "| smtp-commands: mirtuel Hello localhost [127.0.0.1], SIZE 52428800, 8BITMIME, PIPELINING, HELP, \n"
2911 "|_ Commands supported: AUTH HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP \n"
2912 "111/tcp open rpcbind 2-4 (RPC #100000)\n"
2913 "| rpcinfo: \n"
2914 "| program version port/proto service\n"
2915 "| 100000 2,3,4 111/tcp rpcbind\n"
2916 "| 100000 2,3,4 111/udp rpcbind\n"
2917 "| 100024 1 36568/tcp status\n"
2918 "|_ 100024 1 39172/udp status\n"
2919 "Device type: general purpose\n"
2920 "Running: Linux 3.X\n"
2921 "OS CPE: cpe:/o:linux:linux_kernel:3\n"
2922 "OS details: Linux 3.7 - 3.15\n"
2923 "Network Distance: 0 hops\n"
2924 "Service Info: Host: mirtuel; OS: Linux; CPE: cpe:/o:linux:linux_kernel\n"
2925 "\n"
2926 "OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .\n"
2927 "Nmap done: 1 IP address (1 host up) scanned in 11.54 seconds\n"
2928 "</computeroutput>"
2929
2930 #, fuzzy
2931 #| 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 <literal>lo</literal> loopback interface, it only appears during an analysis of <literal>localhost</literal> and not when scanning <literal>mirtuel</literal> (which maps to the <literal>eth0</literal> interface on the same machine)."
2932 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 <literal>lo</literal> loopback interface, it only appears during an analysis of <literal>localhost</literal> and not when scanning <literal>debian</literal> (which maps to the <literal>enp1s0</literal> interface on the same machine)."
2933 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 <literal>lo</literal>, il n'apparaît que lors d'une analyse de <literal>localhost</literal> et non de <literal>mirtuel</literal> (l'interface réseau <literal>eth0</literal> de la même machine)."
2934
2935 msgid "Sniffers: <command>tcpdump</command> and <command>wireshark</command>"
2936 msgstr "Les <foreignphrase>sniffers</foreignphrase> : <command>tcpdump</command> et <command>wireshark</command>"
2937
2938 msgid "<primary><command>tcpdump</command></primary>"
2939 msgstr "<primary><command>tcpdump</command></primary>"
2940
2941 msgid "<primary><command>wireshark</command></primary>"
2942 msgstr "<primary><command>wireshark</command></primary>"
2943
2944 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 <emphasis>sniffer</emphasis>. Such a tool observes all the packets that reach a given network interface, and displays them in a user-friendly way."
2945 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 <foreignphrase>sniffer</foreignphrase> (renifleur). Cet outil scrute tous les paquets qui atteignent une interface réseau et les affiche de manière plus lisible à l'utilisateur."
2946
2947 msgid "The venerable tool in this domain is <command>tcpdump</command>, 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."
2948 msgstr "L'ancêtre dans ce domaine est sans conteste <command>tcpdump</command> (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."
2949
2950 msgid "A more recent (and more modern) tool, <command>wireshark</command> (in the <emphasis role=\"pkg\">wireshark</emphasis> 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, <command>wireshark</command> 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."
2951 msgstr "Plus récent et plus moderne, l'outil <command>wireshark</command> (paquet <emphasis role=\"pkg\">wireshark</emphasis>) 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."
2952
2953 msgid "The <command>wireshark</command> network traffic analyzer"
2954 msgstr "Analyseur de trafic réseau <command>wireshark</command>"
2955
2956 #, fuzzy
2957 #| msgid "In our example, the packets traveling over SSH are filtered out (with the <literal>!tcp.port == 22</literal> filter). The packet currently displayed was developed at the HTTP layer."
2958 msgid "In our example, the packets traveling over SSH are filtered out (with the <literal>!tcp.port == 22</literal> filter). The packet currently displayed was developed at the transport layer of the SSHv2 protocol."
2959 msgstr "Dans notre exemple, seuls les paquets n'ayant pas transité par SSH sont affichés (grâce au filtre <literal>!tcp.port == 22</literal>). Le paquet en cours d'analyse approfondie a été développé à la couche HTTP."
2960
2961 msgid "<emphasis>TIP</emphasis> <command>wireshark</command> with no graphical interface: <command>tshark</command>"
2962 msgstr "<emphasis>ASTUCE</emphasis> <command>wireshark</command> sans interface graphique : <command>tshark</command>"
2963
2964 msgid "<primary><command>tshark</command></primary>"
2965 msgstr "<primary><command>tshark</command></primary>"
2966
2967 msgid "When one cannot run a graphical interface, or does not wish to do so for whatever reason, a text-only version of <command>wireshark</command> also exists under the name <command>tshark</command> (in a separate <emphasis role=\"pkg\">tshark</emphasis> 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 <command>wireshark</command> running on another machine."
2968 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 <command>wireshark</command> appelée <command>tshark</command> (dans un paquet <emphasis role=\"pkg\">tshark</emphasis> 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 <command>wireshark</command> graphique sur une autre machine."
2969
2970 #, fuzzy
2971 #~| msgid "Barring a specific QoS configuration, the Linux kernel uses the <literal>pfifo_fast</literal> queue scheduler, which provides a few interesting features by itself. The priority of each processed IP packet is based on the ToS field (<emphasis>Type of Service</emphasis>) of this packet; modifying this field is enough to take advantage of the scheduling features. There are five possible values:"
2972 #~ msgid "Barring a specific QoS configuration, the Linux kernel uses the <literal>pfifo_fast</literal> queue scheduler, which provides a few interesting features by itself. The priority of each processed IP packet is based on the DSCP field (<emphasis>Differentiated of Services Code Point</emphasis>) of this packet; modifying this 6-bit field is enough to take advantage of the scheduling features. Refer to <ulink url=\"https://en.wikipedia.org/wiki/Differentiated_services#Class_Selector\" /> for more information."
2973 #~ msgstr "En l'absence d'une configuration particulière de QoS, le noyau Linux emploie la file d'attente <literal>pfifo_fast</literal>, qui propose déjà quelques fonctionnalités intéressantes. Pour établir les priorités des paquets IP, elle utilise leur champ ToS (<foreignphrase>Type of Service</foreignphrase>, ou type de service) — qu'il suffira donc de modifier pour bénéficier de cette file. Ce champ peut recevoir cinq valeurs :"
2974
2975 #~ msgid "<primary>TCP, port</primary>"
2976 #~ msgstr "<primary>TCP, port</primary>"
2977
2978 #~ msgid "<primary>UDP, port</primary>"
2979 #~ msgstr "<primary>UDP, port</primary>"
2980
2981 #~ msgid "<primary>SNAT</primary>"
2982 #~ msgstr "<primary>SNAT</primary>"
2983
2984 #~ msgid "<primary>DNAT</primary>"
2985 #~ msgstr "<primary>DNAT</primary>"
2986
2987 #, fuzzy
2988 #~| msgid "<primary>X.509, certificate</primary>"
2989 #~ msgid "<primary>certificates</primary>"
2990 #~ msgstr "<primary>X.509, certificat</primary>"
2991
2992 #~ msgid "<primary>X.509, certificate</primary>"
2993 #~ msgstr "<primary>X.509, certificat</primary>"
2994
2995 #~ msgid "<primary>SSH</primary>"
2996 #~ msgstr "<primary>SSH</primary>"
2997
2998 #~ msgid "<primary>Point-to-Point Tunneling Protocol</primary>"
2999 #~ msgstr "<primary><foreignphrase>Point-to-Point Tunneling Protocol</foreignphrase></primary>"
3000
3001 #, fuzzy
3002 #~| msgid "<primary>gateway</primary>"
3003 #~ msgid "<primary>net neutrality</primary>"
3004 #~ msgstr "<primary>passerelle</primary>"
3005
3006 #~ msgid "In the PPP case, creating a script that calls <command>wondershaper</command> in <filename>/etc/ppp/ip-up.d/</filename> will enable traffic control as soon as the connection is up."
3007 #~ msgstr "Dans le cas de PPP, la création d'un script appelant <command>wondershaper</command> dans <filename>/etc/ppp/ip-up.d/</filename> activera le contrôle de trafic dès le démarrage de la connexion."
3008
3009 #, fuzzy
3010 #~| msgid "<primary><command>route</command></primary>"
3011 #~ msgid "<primary><command>ip route</command></primary>"
3012 #~ msgstr "<primary><command>route</command></primary>"
3013
3014 #~ msgid "<primary>IPv6 firewall</primary>"
3015 #~ msgstr "<primary>pare-feu IPv6</primary>"
3016
3017 #~ msgid "<literal>A</literal>: IPv4 address. <indexterm><primary>A, DNS record</primary></indexterm>"
3018 #~ msgstr "<literal>A</literal> : attribution d'une adresse IPv4. <indexterm><primary>A, enregistrement DNS</primary></indexterm>"
3019
3020 #~ msgid "<literal>AAAA</literal>: IPv6 address. <indexterm><primary>AAAA, DNS record</primary></indexterm>"
3021 #~ msgstr "<literal>AAAA</literal> : correspondance nom vers adresse IPv6. <indexterm><primary>AAAA, enregistrement DNS</primary></indexterm>"
3022
3023 #~ msgid "<primary>DNS record</primary>"
3024 #~ msgstr "<primary>DNS</primary><secondary>enregistrement</secondary>"
3025
3026 #~ msgid "<primary>DHCP</primary>"
3027 #~ msgstr "<primary>DHCP</primary>"
3028
3029 #~ msgid "<emphasis>NOTE</emphasis> <emphasis>easy-rsa</emphasis> before <emphasis role=\"distribution\">Jessie</emphasis>"
3030 #~ msgstr "<emphasis>NOTE</emphasis> <emphasis>easy-rsa</emphasis> avant <emphasis role=\"distribution\">Jessie</emphasis>"
3031
3032 #~ msgid "In versions of Debian up to <emphasis role=\"distribution\">Wheezy</emphasis>, <emphasis>easy-rsa</emphasis> was distributed as part of the <emphasis role=\"pkg\">openvpn</emphasis> package, and its scripts were to be found under <filename>/usr/share/doc/openvpn/examples/easy-rsa/2.0/</filename>. Setting up a CA involved copying that directory, instead of using the <command>make-cadir</command> command as documented here."
3033 #~ msgstr "Jusqu'à <emphasis role=\"distribution\">Wheezy</emphasis>, <emphasis>easy-rsa</emphasis> faisait partie du paquet <emphasis role=\"pkg\">openvpn</emphasis> et les scripts se trouvaient dans <filename>/usr/share/doc/openvpn/examples/easy-rsa/2.0/</filename>. Pour mettre en place une autorité de certification il fallait copier ce répertoire, la commande <command>make-cadir</command> documentée ici n'existant pas encore."
3034
3035 #~ msgid ""
3036 #~ "\n"
3037 #~ "<computeroutput>$ </computeroutput><userinput>vim vars\n"
3038 #~ "</userinput><computeroutput>$ </computeroutput><userinput>grep KEY_ vars\n"
3039 #~ "</userinput><computeroutput>export KEY_CONFIG=`$EASY_RSA/whichopensslcnf $EASY_RSA`\n"
3040 #~ "export KEY_DIR=\"$EASY_RSA/keys\"\n"
3041 #~ "echo NOTE: If you run ./clean-all, I will be doing a rm -rf on $KEY_DIR\n"
3042 #~ "export KEY_SIZE=2048\n"
3043 #~ "export KEY_EXPIRE=3650\n"
3044 #~ "export KEY_COUNTRY=\"FR\"\n"
3045 #~ "export KEY_PROVINCE=\"Loire\"\n"
3046 #~ "export KEY_CITY=\"Saint-Étienne\"\n"
3047 #~ "export KEY_ORG=\"Falcot Corp\"\n"
3048 #~ "export KEY_EMAIL=\"[email protected]\"\n"
3049 #~ "export KEY_OU=\"Certificate authority\"\n"
3050 #~ "export KEY_NAME=\"Certificate authority for Falcot Corp\"\n"
3051 #~ "# If you'd like to sign all keys with the same Common Name, uncomment the KEY_CN export below\n"
3052 #~ "# export KEY_CN=\"CommonName\"\n"
3053 #~ "$ </computeroutput><userinput>. ./vars\n"
3054 #~ "</userinput><computeroutput>NOTE: If you run ./clean-all, I will be doing a rm -rf on /home/roland/pki-falcot/keys\n"
3055 #~ "$ </computeroutput><userinput>./clean-all\n"
3056 #~ "</userinput>"
3057 #~ msgstr ""
3058 #~ "\n"
3059 #~ "<computeroutput>$ </computeroutput><userinput>vim vars\n"
3060 #~ "</userinput><computeroutput>$ </computeroutput><userinput>grep KEY_ vars\n"
3061 #~ "</userinput><computeroutput>export KEY_CONFIG=`$EASY_RSA/whichopensslcnf $EASY_RSA`\n"
3062 #~ "export KEY_DIR=\"$EASY_RSA/keys\"\n"
3063 #~ "echo NOTE: If you run ./clean-all, I will be doing a rm -rf on $KEY_DIR\n"
3064 #~ "export KEY_SIZE=2048\n"
3065 #~ "export KEY_EXPIRE=3650\n"
3066 #~ "export KEY_COUNTRY=\"FR\"\n"
3067 #~ "export KEY_PROVINCE=\"Loire\"\n"
3068 #~ "export KEY_CITY=\"Saint-Étienne\"\n"
3069 #~ "export KEY_ORG=\"Falcot Corp\"\n"
3070 #~ "export KEY_EMAIL=\"[email protected]\"\n"
3071 #~ "export KEY_OU=\"Certificate authority\"\n"
3072 #~ "export KEY_NAME=\"Certificate authority for Falcot Corp\"\n"
3073 #~ "# If you'd like to sign all keys with the same Common Name, uncomment the KEY_CN export below\n"
3074 #~ "# export KEY_CN=\"CommonName\"\n"
3075 #~ "$ </computeroutput><userinput>. ./vars\n"
3076 #~ "</userinput><computeroutput>NOTE: If you run ./clean-all, I will be doing a rm -rf on /home/roland/pki-falcot/keys\n"
3077 #~ "$ </computeroutput><userinput>./clean-all\n"
3078 #~ "</userinput>"
3079
3080 #~ msgid ""
3081 #~ "\n"
3082 #~ "<computeroutput>$ </computeroutput><userinput>./build-key-server vpn.falcot.com\n"
3083 #~ "</userinput><computeroutput>Generating a 2048 bit RSA private key\n"
3084 #~ ".....................................................................................................................+++\n"
3085 #~ "...........+++\n"
3086 #~ "writing new private key to 'vpn.falcot.com.key'\n"
3087 #~ "-----\n"
3088 #~ "You are about to be asked to enter information that will be incorporated\n"
3089 #~ "into your certificate request.\n"
3090 #~ "What you are about to enter is what is called a Distinguished Name or a DN.\n"
3091 #~ "There are quite a few fields but you can leave some blank\n"
3092 #~ "For some fields there will be a default value,\n"
3093 #~ "If you enter '.', the field will be left blank.\n"
3094 #~ "-----\n"
3095 #~ "Country Name (2 letter code) [FR]:\n"
3096 #~ "State or Province Name (full name) [Loire]:\n"
3097 #~ "Locality Name (eg, city) [Saint-Étienne]:\n"
3098 #~ "Organization Name (eg, company) [Falcot Corp]:\n"
3099 #~ "Organizational Unit Name (eg, section) [Certificate authority]:\n"
3100 #~ "Common Name (eg, your name or your server's hostname) [vpn.falcot.com]:\n"
3101 #~ "Name [Certificate authority for Falcot Corp]:\n"
3102 #~ "Email Address [[email protected]]:\n"
3103 #~ "\n"
3104 #~ "Please enter the following 'extra' attributes\n"
3105 #~ "to be sent with your certificate request\n"
3106 #~ "A challenge password []:\n"
3107 #~ "An optional company name []:\n"
3108 #~ "Using configuration from /home/roland/pki-falcot/openssl-1.0.0.cnf\n"
3109 #~ "Check that the request matches the signature\n"
3110 #~ "Signature ok\n"
3111 #~ "The Subject's Distinguished Name is as follows\n"
3112 #~ "countryName :PRINTABLE:'FR'\n"
3113 #~ "stateOrProvinceName :PRINTABLE:'Loire'\n"
3114 #~ "localityName :T61STRING:'Saint-\\0xFFFFFFC3\\0xFFFFFF89tienne'\n"
3115 #~ "organizationName :PRINTABLE:'Falcot Corp'\n"
3116 #~ "organizationalUnitName:PRINTABLE:'Certificate authority'\n"
3117 #~ "commonName :PRINTABLE:'vpn.falcot.com'\n"
3118 #~ "name :PRINTABLE:'Certificate authority for Falcot Corp'\n"
3119 #~ "emailAddress :IA5STRING:'[email protected]'\n"
3120 #~ "Certificate is to be certified until Mar 6 14:54:56 2025 GMT (3650 days)\n"
3121 #~ "Sign the certificate? [y/n]:</computeroutput><userinput>y\n"
3122 #~ "</userinput><computeroutput>\n"
3123 #~ "\n"
3124 #~ "1 out of 1 certificate requests certified, commit? [y/n]</computeroutput><userinput>y\n"
3125 #~ "</userinput><computeroutput>Write out database with 1 new entries\n"
3126 #~ "Data Base Updated\n"
3127 #~ "$ </computeroutput><userinput>./build-dh\n"
3128 #~ "</userinput><computeroutput>Generating DH parameters, 2048 bit long safe prime, generator 2\n"
3129 #~ "This is going to take a long time\n"
3130 #~ "[…]\n"
3131 #~ "</computeroutput>"
3132 #~ msgstr ""
3133 #~ "\n"
3134 #~ "<computeroutput>$ </computeroutput><userinput>./build-key-server vpn.falcot.com\n"
3135 #~ "</userinput><computeroutput>Generating a 2048 bit RSA private key\n"
3136 #~ ".....................................................................................................................+++\n"
3137 #~ "...........+++\n"
3138 #~ "writing new private key to 'vpn.falcot.com.key'\n"
3139 #~ "-----\n"
3140 #~ "You are about to be asked to enter information that will be incorporated\n"
3141 #~ "into your certificate request.\n"
3142 #~ "What you are about to enter is what is called a Distinguished Name or a DN.\n"
3143 #~ "There are quite a few fields but you can leave some blank\n"
3144 #~ "For some fields there will be a default value,\n"
3145 #~ "If you enter '.', the field will be left blank.\n"
3146 #~ "-----\n"
3147 #~ "Country Name (2 letter code) [FR]:\n"
3148 #~ "State or Province Name (full name) [Loire]:\n"
3149 #~ "Locality Name (eg, city) [Saint-Étienne]:\n"
3150 #~ "Organization Name (eg, company) [Falcot Corp]:\n"
3151 #~ "Organizational Unit Name (eg, section) [Certificate authority]:\n"
3152 #~ "Common Name (eg, your name or your server's hostname) [vpn.falcot.com]:\n"
3153 #~ "Name [Certificate authority for Falcot Corp]:\n"
3154 #~ "Email Address [[email protected]]:\n"
3155 #~ "\n"
3156 #~ "Please enter the following 'extra' attributes\n"
3157 #~ "to be sent with your certificate request\n"
3158 #~ "A challenge password []:\n"
3159 #~ "An optional company name []:\n"
3160 #~ "Using configuration from /home/roland/pki-falcot/openssl-1.0.0.cnf\n"
3161 #~ "Check that the request matches the signature\n"
3162 #~ "Signature ok\n"
3163 #~ "The Subject's Distinguished Name is as follows\n"
3164 #~ "countryName :PRINTABLE:'FR'\n"
3165 #~ "stateOrProvinceName :PRINTABLE:'Loire'\n"
3166 #~ "localityName :T61STRING:'Saint-\\0xFFFFFFC3\\0xFFFFFF89tienne'\n"
3167 #~ "organizationName :PRINTABLE:'Falcot Corp'\n"
3168 #~ "organizationalUnitName:PRINTABLE:'Certificate authority'\n"
3169 #~ "commonName :PRINTABLE:'vpn.falcot.com'\n"
3170 #~ "name :PRINTABLE:'Certificate authority for Falcot Corp'\n"
3171 #~ "emailAddress :IA5STRING:'[email protected]'\n"
3172 #~ "Certificate is to be certified until Mar 6 14:54:56 2025 GMT (3650 days)\n"
3173 #~ "Sign the certificate? [y/n]:</computeroutput><userinput>y\n"
3174 #~ "</userinput><computeroutput>\n"
3175 #~ "\n"
3176 #~ "1 out of 1 certificate requests certified, commit? [y/n]</computeroutput><userinput>y\n"
3177 #~ "</userinput><computeroutput>Write out database with 1 new entries\n"
3178 #~ "Data Base Updated\n"
3179 #~ "$ </computeroutput><userinput>./build-dh\n"
3180 #~ "</userinput><computeroutput>Generating DH parameters, 2048 bit long safe prime, generator 2\n"
3181 #~ "This is going to take a long time\n"
3182 #~ "[…]\n"
3183 #~ "</computeroutput>"
3184
3185 #~ msgid ""
3186 #~ "\n"
3187 #~ "<computeroutput>$ </computeroutput><userinput>./build-key JoeSmith\n"
3188 #~ "</userinput><computeroutput>Generating a 2048 bit RSA private key\n"
3189 #~ "................................+++\n"
3190 #~ "..............................................+++\n"
3191 #~ "writing new private key to 'JoeSmith.key'\n"
3192 #~ "-----\n"
3193 #~ "You are about to be asked to enter information that will be incorporated\n"
3194 #~ "into your certificate request.\n"
3195 #~ "What you are about to enter is what is called a Distinguished Name or a DN.\n"
3196 #~ "There are quite a few fields but you can leave some blank\n"
3197 #~ "For some fields there will be a default value,\n"
3198 #~ "If you enter '.', the field will be left blank.\n"
3199 #~ "-----\n"
3200 #~ "Country Name (2 letter code) [FR]:\n"
3201 #~ "State or Province Name (full name) [Loire]:\n"
3202 #~ "Locality Name (eg, city) [Saint-Étienne]:\n"
3203 #~ "Organization Name (eg, company) [Falcot Corp]:\n"
3204 #~ "Organizational Unit Name (eg, section) [Certificate authority]:</computeroutput><userinput>Development unit\n"
3205 #~ "</userinput><computeroutput>Common Name (eg, your name or your server's hostname) [JoeSmith]:</computeroutput><userinput>Joe Smith\n"
3206 #~ "</userinput><computeroutput>[…]</computeroutput>"
3207 #~ msgstr ""
3208 #~ "\n"
3209 #~ "<computeroutput>$ </computeroutput><userinput>./build-key PierreDurand\n"
3210 #~ "</userinput><computeroutput>Generating a 2048 bit RSA private key\n"
3211 #~ "................................+++\n"
3212 #~ "..............................................+++\n"
3213 #~ "writing new private key to 'PierreDurand.key'\n"
3214 #~ "-----\n"
3215 #~ "You are about to be asked to enter information that will be incorporated\n"
3216 #~ "into your certificate request.\n"
3217 #~ "What you are about to enter is what is called a Distinguished Name or a DN.\n"
3218 #~ "There are quite a few fields but you can leave some blank\n"
3219 #~ "For some fields there will be a default value,\n"
3220 #~ "If you enter '.', the field will be left blank.\n"
3221 #~ "-----\n"
3222 #~ "Country Name (2 letter code) [FR]:\n"
3223 #~ "State or Province Name (full name) [Loire]:\n"
3224 #~ "Locality Name (eg, city) [Saint-Étienne]:\n"
3225 #~ "Organization Name (eg, company) [Falcot SA]:\n"
3226 #~ "Organizational Unit Name (eg, section) [Certificate authority]:</computeroutput><userinput>Development unit\n"
3227 #~ "</userinput><computeroutput>Common Name (eg, your name or your server's hostname) [PierreDurand]:</computeroutput><userinput>Pierre Durand\n"
3228 #~ "</userinput><computeroutput>[…]</computeroutput>"
3229
3230 #~ msgid "<primary><command>racoon</command></primary>"
3231 #~ msgstr "<primary><command>racoon</command></primary>"
3232
3233 #~ 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 <emphasis role=\"pkg\">ipsec-tools</emphasis> package. In concrete terms, each host's <filename>/etc/ipsec-tools.conf</filename> contains the parameters for <emphasis>IPsec tunnels</emphasis> (or <emphasis>Security Associations</emphasis>, in the IPsec terminology) that the host is concerned with; the <command>/etc/init.d/setkey</command> 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 <citerefentry><refentrytitle>setkey</refentrytitle> <manvolnum>8</manvolnum></citerefentry> 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 <emphasis>IPsec Key Exchange</emphasis>) such as <emphasis role=\"pkg\">racoon</emphasis> or <emphasis role=\"pkg\">strongswan</emphasis> makes the process much simpler by bringing administration together at a central point, and more secure by rotating the keys periodically."
3234 #~ 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 <emphasis role=\"pkg\">ipsec-tools</emphasis> recelant des outils complémentaires et de paramétrage. Sur le plan pratique, le fichier <filename>/etc/ipsec-tools.conf</filename> de chaque hôte abrite les paramètres de « tunnels <emphasis>IPsec</emphasis> » (ou <foreignphrase>Security Association</foreignphrase> dans le vocabulaire <emphasis>IPsec</emphasis>) le concernant et le script <command>/etc/init.d/setkey</command> offre le moyen d'établir (paramètre <literal>start</literal>) ou de stopper (<literal>stop</literal>) 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 <citerefentry><refentrytitle>setkey</refentrytitle><manvolnum>8</manvolnum></citerefentry>. 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 (<foreignphrase>IPsec Key Exchange</foreignphrase>, échange de clés IPsec) comme <emphasis role=\"pkg\">racoon</emphasis> ou <emphasis role=\"pkg\">strongswan</emphasis> simplifie tout cela en centralisant l'administration et améliore la sécurité en organisant une rotation des clés employées."
3235
3236 #~ msgid "Normal-Service (0);"
3237 #~ msgstr "<foreignphrase>Normal-Service</foreignphrase> (0) (service normal) ;"
3238
3239 #~ msgid "Minimize-Cost (2);"
3240 #~ msgstr "<foreignphrase>Minimize-Cost</foreignphrase> (2) (minimiser le coût) ;"
3241
3242 #~ msgid "Maximize-Reliability (4);"
3243 #~ msgstr "<foreignphrase>Maximize-Reliability</foreignphrase> (4) (maximiser la fiabilité) ;"
3244
3245 #~ msgid "Maximize-Throughput (8);"
3246 #~ msgstr "<foreignphrase>Maximize-Throughput</foreignphrase> (8) (maximiser le débit) ;"
3247
3248 #~ msgid "Minimize-Delay (16)."
3249 #~ msgstr "<foreignphrase>Minimize-Delay</foreignphrase> (16) (minimiser le délai)."
3250
3251 #~ msgid "<primary>ToS</primary>"
3252 #~ msgstr "<primary>ToS</primary>"
3253
3254 #~ msgid "<primary>Type of Service</primary>"
3255 #~ msgstr "<primary><foreignphrase>Type of Service</foreignphrase></primary>"
3256
3257 #~ msgid ""
3258 #~ "\n"
3259 #~ "iptables -t mangle -A PREROUTING -p tcp --sport ssh -j TOS --set-tos Minimize-Delay\n"
3260 #~ "iptables -t mangle -A PREROUTING -p tcp --dport ssh -j TOS --set-tos Minimize-Delay"
3261 #~ msgstr ""
3262 #~ "\n"
3263 #~ "iptables -t mangle -A PREROUTING -p tcp --sport ssh -j TOS --set-tos Minimize-Delay\n"
3264 #~ "iptables -t mangle -A PREROUTING -p tcp --dport ssh -j TOS --set-tos Minimize-Delay"
3265
3266 #~ msgid "<primary>BABEL wireless mesh routing</primary>"
3267 #~ msgstr "<primary>BABEL, routage de réseau maillé sans fil</primary>"
3268
3269 #~ msgid "<primary><command>babeld</command></primary>"
3270 #~ msgstr "<primary><command>babeld</command></primary>"
3271
3272 #~ msgid "Daemons are enabled by editing the <filename>/etc/quagga/daemons</filename> file and creating the appropriate configuration file in <filename>/etc/quagga/</filename>; this configuration file must be named after the daemon, with a <filename>.conf</filename> extension, and belong to the <literal>quagga</literal> user and the <literal>quaggavty</literal> group, in order for the <filename>/etc/init.d/quagga</filename> script to invoke the daemon."
3273 #~ msgstr "On active un démon en modifiant le fichier <filename>/etc/quagga/daemons</filename> et en créant dans le répertoire <filename>/etc/quagga/</filename> son fichier de configuration, qui doit porter son nom suivi de <filename>.conf</filename> et appartenir à l'utilisateur <literal>quagga</literal> et au groupe <literal>quaggavty</literal> — dans le cas contraire, le script <filename>/etc/init.d/quagga</filename> n'invoquera pas ce démon."
3274
3275 #~ msgid "IPv6 connections can be restricted, in the same fashion as for IPv4: the standard Debian kernels include an adaptation of <emphasis>netfilter</emphasis> for IPv6. This IPv6-enabled <emphasis>netfilter</emphasis> is configured in a similar fashion to its IPv4 counterpart, except the program to use is <command>ip6tables</command> instead of <command>iptables</command>."
3276 #~ msgstr "Les connexions IPv6 peuvent être filtrées et restreintes comme avec IPv4 : il existe une adaptation de <command>netfilter</command> pour l'IPv6 compilée dans les noyaux Debian. Elle se configure comme la version classique, mais avec le programme <command>ip6tables</command> en lieu et place d'<command>iptables</command>."
3277
3278 #~ msgid "<primary>Freenet6</primary>"
3279 #~ msgstr "<primary>Freenet6</primary>"
3280
3281 #~ msgid "<primary>Gogo6</primary>"
3282 #~ msgstr "<primary>Gogo6</primary>"
3283
3284 #~ msgid "To use a Freenet6 tunnel, you need to register for a Freenet6 Pro account on the website, then install the <emphasis role=\"pkg\">gogoc</emphasis> package and configure the tunnel. This requires editing the <filename>/etc/gogoc/gogoc.conf</filename> file: <literal>userid</literal> and <literal>password</literal> lines received by e-mail should be added, and <literal>server</literal> should be replaced with <literal>authenticated.freenet6.net</literal>."
3285 #~ 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 <emphasis role=\"pkg\">gogoc</emphasis> et configurer ce tunnel. On intégrera au fichier <filename>/etc/gogoc/gogoc.conf</filename> les lignes <literal>userid</literal> et <literal>password</literal> reçues par courrier électronique et on remplacera <literal>server</literal> par <literal>authenticated.freenet6.net</literal>."
3286
3287 #~ msgid "IPv6 connectivity is proposed to all machines on a local network by adding the three following directives to the <filename>/etc/gogoc/gogoc.conf</filename> file (assuming the local network is connected to the eth0 interface):"
3288 #~ msgstr "On proposera une connectivité IPv6 à toutes les machines du réseau local en modifiant dans le fichier <filename>/etc/gogoc/gogoc.conf</filename> les trois directives ci-dessous (le réseau local est supposé connecté à l'interface eth0) :"
3289
3290 #~ msgid ""
3291 #~ "\n"
3292 #~ "host_type=router\n"
3293 #~ "prefixlen=56\n"
3294 #~ "if_prefix=eth0"
3295 #~ msgstr ""
3296 #~ "\n"
3297 #~ "host_type=router\n"
3298 #~ "prefixlen=56\n"
3299 #~ "if_prefix=eth0"
3300
3301 #~ msgid "<emphasis>CULTURE</emphasis> <command>ethereal</command> and <command>wireshark</command>"
3302 #~ msgstr "<emphasis>CULTURE</emphasis> <command>ethereal</command> et <command>wireshark</command>"
3303
3304 #~ msgid "<primary><command>ethereal</command></primary>"
3305 #~ msgstr "<primary><command>ethereal</command></primary>"
3306
3307 #~ msgid "<primary><command>tethereal</command></primary>"
3308 #~ msgstr "<primary><command>tethereal</command></primary>"
3309
3310 #~ msgid "<command>wireshark</command> seems to be relatively young; however, it is only the new name for a software application previously known as <command>ethereal</command>. 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."
3311 #~ msgstr "<command>wireshark</command>, bien qu'apparu relativement récemment, est en réalité simplement le nouveau nom du logiciel <command>ethereal</command>. 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é."
3312
3313 #~ msgid "Presentation"
3314 #~ msgstr "Présentation"