Ignore:
Timestamp:
02/04/2021 02:56:49 AM (3 years ago)
Author:
Ken Moffat <ken@…>
Branches:
10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
6fbbe46
Parents:
d9a7451
Message:

Wireshark - for editors, note where their security advisories are, we have missed at least the items fixed in 3.4.0.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@24169 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • networking/netutils/wireshark.xml

    rd9a7451 rc8a095cb  
    1212  <!ENTITY wireshark-time          "2.4 SBU (with parallelism=4 and all optional dependencies available in the BLFS book)">
    1313]>
     14
     15<!-- Gentler reminder: many Wireshark releases contain vulnerability fixes,
     16 we have not always been aware of these. At https://www.wireshark.org/security/
     17 there is a list of advisories and the version in which they were fixed.
     18
     19 If you click on an advisory, after the bug number in the References:
     20 there may be a CVE number, although perhaps those get added some time after
     21 the release.  Perhaps as a general rule treat ALL their advisories for crashes
     22 etc as worthy of a security fix. -->
    1423
    1524<sect1 id="wireshark" xreflabel="Wireshark-&wireshark-version;">
Note: See TracChangeset for help on using the changeset viewer.