View | Details | Raw Unified | Return to bug 277068 | Differences between
and this patch

Collapse All | Expand All

(-)b/documentation/content/en/books/developers-handbook/testing/_index.adoc (+1 lines)
Lines 72-77 It is not possible to use all of the suggestions below every single time, but th Link Here
72
* Remove all non-essential device drivers from the kernel. For instance if USB is not needed for the test, do not put USB in the kernel. Drivers which attach often have timeouts ticking away.
72
* Remove all non-essential device drivers from the kernel. For instance if USB is not needed for the test, do not put USB in the kernel. Drivers which attach often have timeouts ticking away.
73
* Unconfigure hardware that are not in use. Detach disks with man:atacontrol[8] and man:camcontrol[8] if the disks are not used for the test.
73
* Unconfigure hardware that are not in use. Detach disks with man:atacontrol[8] and man:camcontrol[8] if the disks are not used for the test.
74
* Do not configure the network unless it is being tested, or wait until after the test has been performed to ship the results off to another computer.
74
* Do not configure the network unless it is being tested, or wait until after the test has been performed to ship the results off to another computer.
75
* Disable "Turbo-modes" because they make the clock frequency explicitly depend on the environment.
75
+
76
+
76
If the system must be connected to a public network, watch out for spikes of broadcast traffic. Even though it is hardly noticeable, it will take up CPU cycles. Multicast has similar caveats.
77
If the system must be connected to a public network, watch out for spikes of broadcast traffic. Even though it is hardly noticeable, it will take up CPU cycles. Multicast has similar caveats.
77
* Put each file system on its own disk. This minimizes jitter from head-seek optimizations.
78
* Put each file system on its own disk. This minimizes jitter from head-seek optimizations.
(-)b/documentation/content/en/books/porters-handbook/security/_index.adoc (-13 / +3 lines)
Lines 168-179 Now consider a realistic VuXML entry: Link Here
168
  <references> <.>
168
  <references> <.>
169
    <freebsdsa>SA-10:75.foo</freebsdsa> <.>
169
    <freebsdsa>SA-10:75.foo</freebsdsa> <.>
170
    <freebsdpr>ports/987654</freebsdpr> <.>
170
    <freebsdpr>ports/987654</freebsdpr> <.>
171
    <cvename>CAN-2010-0201</cvename> <.>
171
    <cvename>CVE-2023-48795</cvename> <.>
172
    <cvename>CAN-2010-0466</cvename>
173
    <bid>96298</bid> <.>
174
    <certsa>CA-2010-99</certsa> <.>
175
    <certvu>740169</certvu> <.>
172
    <certvu>740169</certvu> <.>
176
    <uscertsa>SA10-99A</uscertsa> <.>
177
    <uscertta>SA10-99A</uscertta> <.>
173
    <uscertta>SA10-99A</uscertta> <.>
178
    <mlist msgid="201075606@hacker.com">http://marc.theaimsgroup.com/?l=bugtraq&amp;m=203886607825605</mlist> <.>
174
    <mlist msgid="201075606@hacker.com">http://marc.theaimsgroup.com/?l=bugtraq&amp;m=203886607825605</mlist> <.>
179
    <url>http://j.r.hacker.com/advisories/1</url> <.>
175
    <url>http://j.r.hacker.com/advisories/1</url> <.>
Lines 213-227 The above example specifies that affected are versions `1.6` and up to but not i Link Here
213
209
214
<.> This is a https://cve.mitre.org/[MITRE CVE] identifier.
210
<.> This is a https://cve.mitre.org/[MITRE CVE] identifier.
215
211
216
<.> This is a https://www.securityfocus.com/bid/[SecurityFocus Bug ID].
212
<.> This is a https://www.kb.cert.org/vuls/[US-CERT] vulnerability note.
217
213
218
<.> This is a https://www.cert.org/[US-CERT] security advisory.
214
<.> This is a https://www.cisa.gov/news-events/cybersecurity-advisories[US-CERT] Technical Cyber Security Alert.
219
220
<.> This is a https://www.cert.org/[US-CERT] vulnerability note.
221
222
<.> This is a https://www.cert.org/[US-CERT] Cyber Security Alert.
223
224
<.> This is a https://www.cert.org/[US-CERT] Technical Cyber Security Alert.
225
215
226
<.> This is a URL to an archived posting in a mailing list. The attribute `msgid` is optional and may specify the message ID of the posting.
216
<.> This is a URL to an archived posting in a mailing list. The attribute `msgid` is optional and may specify the message ID of the posting.
227
217

Return to bug 277068