source: postlfs/security/vulnerabilities.xml@ 45ab6c7

11.0 ken/refactor-virt lazarus qt5new trunk
Last change on this file since 45ab6c7 was 45ab6c7, checked in by Xi Ruoyao <xry111@…>, 5 months ago

more SVN prop clean up

Remove "$LastChanged$" everywhere, and also some unused $Date$

  • Property mode set to 100644
File size: 4.1 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
8<sect1 id="vulnerabilities" xreflabel="vulnerabilities">
9 <?dbhtml filename="vulnerabilities.html"?>
11 <sect1info>
12 <date>$Date$</date>
13 </sect1info>
15 <title>Vulnerabilities</title>
17 <!-- section g : 'Others' in longindex.html -->
18 <indexterm zone="vulnerabilities">
19 <primary sortas="g-vulnerabilities">vulnerability links</primary>
20 </indexterm>
22 <sect2 role="package">
23 <title>About vulnerabilities</title>
25 <para>
26 All software has bugs. Sometimes, a bug can be exploited, for example to
27 allow users to gain enhanced privileges (perhaps gaining a root shell,
28 or simply accessing or deleting other user&apos;s files), or to allow a
29 remote site to crash an application (denial of service), or for theft of
30 data. These bugs are labelled as vulnerabilities.
31 </para>
33 <para>
34 The main place where vulnerabilities get logged is
35 <ulink url=""></ulink>. Unfortunately,
36 many vulnerability numbers (CVE-yyyy-nnnn) are initially only labelled
37 as "reserved" when distributions start issuing fixes. Also, some
38 vulnerabilities apply to particular combinations of
39 <command>configure</command> options, or only apply to old versions of
40 packages which have long since been updated in BLFS.
41 </para>
43 <para>
44 BLFS differs from distributions&mdash;there is no BLFS security team, and
45 the editors only become aware of vulnerabilities after they are public
46 knowledge. Sometimes, a package with a vulnerability will not be updated
47 in the book for a long time. Issues can be logged in the Trac system,
48 which might speed up resolution.
49 </para>
51 <para>
52 The normal way for BLFS to fix a vulnerability is, ideally, to update
53 the book to a new fixed release of the package. Sometimes that happens
54 even before the vulnerability is public knowledge, so there is no
55 guarantee that it will be shown as a vulnerability fix in the Changelog.
56 Alternatively, a <command>sed</command> command, or a patch taken from
57 a distribution, may be appropriate.
58 </para>
60 <para>
61 The bottom line is that you are responsible for your own security, and
62 for assessing the potential impact of any problems.
63 </para>
65 <para>
66 To keep track of what is being discovered, you may wish to follow the
67 security announcements of one or more distributions. For example, Debian
68 has <ulink url="">Debian security</ulink>.
69 Fedora's links on security are at <ulink
70 url="">the Fedora wiki</ulink>.
71 Details of Gentoo linux security announcements are discussed at
72 <ulink url="">Gentoo security</ulink>.
73 Finally, the Slackware archives of security announcements are at
74 <ulink url="">Slackware security</ulink>.
75 </para>
77 <para>
78 The most general English source is perhaps
79 <ulink url="">the Full Disclosure
80 Mailing List</ulink>, but please read the comment on that page. If you
81 use other languages you may prefer other sites such as <ulink
82 url=""></ulink> (German) or <ulink
83 url=""></ulink> (Croatian). These are not
84 linux-specific. There is also a daily update at for subscribers
85 (free access to the data after 2 weeks, but their vulnerabilities
86 database at <ulink
87 url=""></ulink>
88 is unrestricted).
89 </para>
91 <para>
92 For some packages, subscribing to their &apos;announce&apos; lists
93 will provide prompt news of newer versions.
94 </para>
96 <para condition="html" role="usernotes">User Notes:
97 <ulink url="&blfs-wiki;/vulnerabilities"/></para>
99 </sect2>
Note: See TracBrowser for help on using the repository browser.