Page MenuHomeFreeBSD

security: Inter-link between SA and EN pages for greater visibility
ClosedPublic

Authored by jrtc27 on Dec 5 2023, 7:09 PM.
Tags
None
Referenced Files
Unknown Object (File)
Jan 21 2024, 3:38 AM
Unknown Object (File)
Dec 24 2023, 2:02 PM
Unknown Object (File)
Dec 21 2023, 12:10 AM

Details

Summary

Both sets of announcements are important for administrators to be aware
of, so make it more obvious that ENs exist when looking at SAs, and make
it clear that SAs aren't included in the list of ENs.

Suggested by: brooks

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jrtc27 requested review of this revision.Dec 5 2023, 7:09 PM
jrtc27 created this revision.
This revision is now accepted and ready to land.Dec 5 2023, 7:15 PM

I tend to think that decoupling them is a bit of a failure given that our update mechanisms tend to be all or nothing, but this looks like a nice improvement.

jhb added inline comments.
website/content/en/security/_index.adoc
76

s/classed/classified/?

website/content/en/security/advisories.adoc
13

(If you change above, here as well)

website/content/en/security/_index.adoc
76

Is there a subtle distinction between the two that makes you want to use the latter over the former? To me they're synonymous.

As I said on IRC, what I think would be really useful is a unified table per release that also has "markers" for each pX so you can tell which fixes are included in each patch release. Something like:

EN-XX | --
EN-XY | --
--- | 14.0-p1
SA-NN | --
EA-XZ | --
--- | 14.0-p2

or something

website/content/en/security/_index.adoc
76

Might be American vs UK english. I generally only use "class" as a noun and "classify" for the verb.

unified table per release that also has "markers" for each pX

I agree that would make sense, and that we don't need to separate SAs and ENs as much as we do. But adding this cross-reference is a good small improvement for now.

website/content/en/security/_index.adoc
76

I probably would have written "classified as", but "classed as" reads fine to me (as a Canadian).

Other than that typo (and maybe using "classified": "classed" looks unfamiliar to me but readily understandable), LGTM.

website/content/en/security/notices.adoc
11