Source strings

13 Strings 100%
Browse Translate
441 Words 100%
3,355 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
13 441 3,355
All strings Browse Translate Zen
13 441 3,355
Read-only strings Browse Translate Zen

Overview

Project website www.linuxfromscratch.org
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@git.linuxfromscratch.org:fr-lfs
Repository branch trunk
Last remote commit Automatic BLFS commit based on 9166af53de96dd822e35386ef6a1929ac480970a d6d7f172dd
Julien Lepiller authored 11 hours ago
Last commit in Weblate Automatic BLFS commit based on 9166af53de96dd822e35386ef6a1929ac480970a d6d7f172dd
Julien Lepiller authored 11 hours ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask blfs/*/postlfs/security/vulnerabilities.po
Translation file Not available
Last change April 13, 2024, 4:19 a.m.
Last author None
8 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 13 441 3,355
Translated 100% 13 100% 441 100% 3,355
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 13 100% 441 100% 3,355
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 14 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

441
Hosted words
13
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Source string added
To keep track of what is being discovered, you may wish to follow the security announcements of one or more distributions. For example, Debian has <ulink url="https://www.debian.org/security">Debian security</ulink>. Fedora's links on security are at <ulink url="https://fedoraproject.org/wiki/category:Security">the Fedora wiki</ulink>. Details of Gentoo linux security announcements are discussed at <ulink url="https://security.gentoo.org">Gentoo security</ulink>. Finally, the Slackware archives of security announcements are at <ulink url="http://slackware.com/security/">Slackware security</ulink>.
8 months ago
User avatar None

Source string added
For some packages, subscribing to their &apos;announce&apos; lists will provide prompt news of newer versions.
a year ago
User avatar None

Source string added
The most general English source is perhaps <ulink url="https://seclists.org/fulldisclosure">the Full Disclosure Mailing List</ulink>, but please read the comment on that page. If you use other languages you may prefer other sites such as <ulink url="https://www.heise.de/security">heise.de</ulink> (German) or <ulink url="https://www.cert.hr">cert.hr</ulink> (Croatian). These are not linux-specific. There is also a daily update at lwn.net for subscribers (free access to the data after 2 weeks, but their vulnerabilities database at <ulink url="https://lwn.net/Alerts/">lwn.net/Alerts</ulink> is unrestricted).
a year ago
User avatar None

Source string added
The editors now issue Security Advisories for packages in BLFS (and LFS), which can be found at <ulink url="https://www.linuxfromscratch.org/blfs/advisories/">BLFS Security Advisories</ulink>, and grade the severity according to what upstream reports, or to what is shown at <ulink url="https://nvd.nist.gov/">nvd.nist.gov</ulink> if that has details.
a year ago
User avatar None

Source string added
The bottom line is that you are responsible for your own security, and for assessing the potential impact of any problems.
a year ago
User avatar None

Source string added
The normal way for BLFS to fix a vulnerability is, ideally, to update the book to a new fixed release of the package. Sometimes that happens even before the vulnerability is public knowledge, so there is no guarantee that it will be shown as a vulnerability fix in the Changelog. Alternatively, a <command>sed</command> command, or a patch taken from a distribution, may be appropriate.
a year ago
User avatar None

Source string added
BLFS differs from distributions&mdash;there is no BLFS security team, and the editors only become aware of vulnerabilities after they are public knowledge. Sometimes, a package with a vulnerability will not be updated in the book for a long time. Issues can be logged in the Trac system, which might speed up resolution.
a year ago
User avatar None

Source string added
The main place where vulnerabilities get logged is <ulink url="https://cve.mitre.org">cve.mitre.org</ulink>. Unfortunately, many vulnerability numbers (CVE-yyyy-nnnn) are initially only labelled as "reserved" when distributions start issuing fixes. Also, some vulnerabilities apply to particular combinations of <command>configure</command> options, or only apply to old versions of packages which have long since been updated in BLFS.
a year ago
User avatar None

Source string added
All software has bugs. Sometimes, a bug can be exploited, for example to allow users to gain enhanced privileges (perhaps gaining a root shell, or simply accessing or deleting other user&apos;s files), or to allow a remote site to crash an application (denial of service), or for theft of data. These bugs are labelled as vulnerabilities.
a year ago
User avatar None

Source string added
About vulnerabilities
a year ago
Browse all translation changes