|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: Displacement of Blame[tm]
From: Garance A Drosihn (drosih
rpi.edu)Date: Fri Jul 14 2000 - 13:01:41 CDT
- Next message: Garance A Drosihn: "Re: Displacement of Blame[tm]"
- Previous message: Jeffrey J. Mountin: "Re: Displacement of Blame[tm]"
- In reply to: David Pick: "Re: Displacement of Blame[tm]"
- Next in thread: Narvi: "Re: Displacement of Blame[tm]"
- Next in thread: Brett Glass: "Re: Displacement of Blame[tm]"
- Reply: Garance A Drosihn: "Re: Displacement of Blame[tm]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At 10:53 AM +0100 7/14/00, David Pick wrote:
>
>A little shorter:
> <port> FreeBSD Port Security Advisory <advisory number>
>
>1) puts the package name first indicating it's *probably* a problem
> with the package itself, and in any case only matters if you are
> running that package
>
>2) says it contains *specific* advice for people running the FreeBSD
> port (as I hope the content would)!
>
>3) contains the advisory number at the end, when this is the least
> significant data in the header, but useful for indexing archives
For what it is worth, I think I like this suggestion the most. My
opinion is probably influenced by the fact that I sort my mailboxes
by subject name. My hope is that some other OS's might pick up on
this subject-format strategy, and thus all the security advisories
for a given <port> would sort together (for those of us who sort by
subject... :-).
If that did happen, then it would become much more obvious to the
casual onlooker that <port> was something that was not unique and
specific to a single operating system, while at the same time helping
freebsd users see which issues MAY be effecting them.
I also like having the <port> name at the start of the subject,
instead of at the end where it is more likely to be trimmed off.
I also want the words 'FreeBSD' and 'Port' to show up early in
the subject line.
>Alternatively:
> FreeBSD Port of <port>: Security Advisory <advisory number>
This would be fine with me too.
And in case I haven't explicitly mentioned it before, I do think
all these security advisories are a very excellent service to
FreeBSD users, and help to show freebsd is serious about security
issues. All I have been wondering about is if we could come up
with a slightly better format for the subject lines.
--- Garance Alistair Drosehn = gadeclipse.acs.rpi.edu Senior Systems Programmer or drosih
rpi.edu Rensselaer Polytechnic Institute
To Unsubscribe: send mail to majordomo
FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
- Next message: Garance A Drosihn: "Re: Displacement of Blame[tm]"
- Previous message: Jeffrey J. Mountin: "Re: Displacement of Blame[tm]"
- In reply to: David Pick: "Re: Displacement of Blame[tm]"
- Next in thread: Narvi: "Re: Displacement of Blame[tm]"
- Next in thread: Brett Glass: "Re: Displacement of Blame[tm]"
- Reply: Garance A Drosihn: "Re: Displacement of Blame[tm]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]