Freebox Player (Revolution / V6)

cela sert a quoi tous ces trucs

@rcoupat : Pour faire simple, Dnsmasq est un serveur DNS/DHCP minimaliste, plus de détails sur Wikipedia : https://fr.wikipedia.org/wiki/Dnsmasq

Sur le site officiel, expliqué en une ligne par l’auteur : http://www.thekelleys.org.uk/

Plus d’un an après la sortie de la mise à jour, du neuf?
→ dnsmasq 2.78 → 2.80 (2018-10-18)

Dnsmasq 2.81 (2020-04-11)
- http://www.thekelleys.org.uk/dnsmasq/doc.html

- http://www.thekelleys.org.uk/dnsmasq/CHANGELOG

il y a jamais de mise à jour donc cela ne doit pas avoir trop d’importance

@rcoupat: Les mises à jour sont très importantes, il y a des améliorations et des corrections, et surtout quand il y a des failles de sécurité ;)

cela doit avoir peu d’importance car si cela était vraiment indispensable, les développeurs Free auraient fait ce qu’il faut

Dnsmasq 2.82 (2020-07-19) :
- http://www.thekelleys.org.uk/dnsmasq/doc.html

- http://www.thekelleys.org.uk/dnsmasq/CHANGELOG

version 2.82:
Improve behaviour in the face of network interfaces which come
and go and change index. Thanks to Petr Mensik for the patch.

Convert hard startup failure on NETLINK_NO_ENOBUFS under qemu-user
to a warning.

Allow IPv6 addresses ofthe form [::ffff:1.2.3.4] in –dhcp-option.

Fix crash under heavy TCP connection load introduced in 2.81.
Thanks to Frank for good work chasing this down.

Change default lease time for DHCPv6 to one day.

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.
Thanks to Martin-Éric Racine for suggestions on this.

Du neuf à propos de la version 2.82 sortie le 19 juillet 2020 ?

Correction de failles dans Dnsmasq 2.83 (2020-01-19) :
- http://www.thekelleys.org.uk/dnsmasq/doc.html
- http://www.thekelleys.org.uk/dnsmasq/CHANGELOG

version 2.83

Use the values of --min-port and --max-port in outgoing
TCP connections to upstream DNS servers.

Fix a remote buffer overflow problem in the DNSSEC code. Any
dnsmasq with DNSSEC compiled in and enabled is vulnerable to this,
referenced by CVE-2020-25681, CVE-2020-25682, CVE-2020-25683
CVE-2020-25687.

Be sure to only accept UDP DNS query replies at the address
from which the query was originated. This keeps as much entropy
in the {query-ID, random-port} tuple as possible, to help defeat
cache poisoning attacks. Refer: CVE-2020-25684.

Use the SHA-256 hash function to verify that DNS answers
received are for the questions originally asked. This replaces
the slightly insecure SHA-1 (when compiled with DNSSEC) or
the very insecure CRC32 (otherwise). Refer: CVE-2020-25685.

Handle multiple identical near simultaneous DNS queries better.
Previously, such queries would all be forwarded
independently. This is, in theory, inefficent but in practise
not a problem, _except_ that is means that an answer for any
of the forwarded queries will be accepted and cached.
An attacker can send a query multiple times, and for each repeat,
another {port, ID} becomes capable of accepting the answer he is
sending in the blind, to random IDs and ports. The chance of a
succesful attack is therefore multiplied by the number of repeats
of the query. The new behaviour detects repeated queries and
merely stores the clients sending repeats so that when the
first query completes, the answer can be sent to all the
clients who asked. Refer: CVE-2020-25686.

Sortie de : Dnsmasq 2.84 (2021-01-25) qui corrige un bug dans 2.83.

Dnsmasq 2.85 (2021-04-07) qui corrige des bugs de 2.83/2.84 + faille CVE-2021-3448.