Re: Cisco Security Advisory: Cisco IOS Software SSL VPN Denial of Service Vulnerability
On 3/27/2014 4:07 PM, Matt Palmer wrote:
On Wed, Mar 26, 2014 at 10:52:42AM -0600, kendrick eastes wrote:
The Full-disclosure mailing list was recently... retired, I guess cisco thought NANOG was the next best place.
Nope, they've been sending these things here for as long as I can remember. I have NFI why -- probably hubris, thinking that everyone running a network *must* have some Cisco somewhere.
There used to be cisco 'wigs with well-known names on NANOG. One of them was probably asked to do it. -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)
I wonder if they should be invited to only post a single message with the titles and links to the alerts so that people can follow it up. They should also include a link to their own list that they send the full alerts to. That way there could be some headline alerting to people that there is something in that topic available but avoids sending each alert to the list every time. Depends on compliance with the charter for the list but I think it might be nice list etiquette. Regards Alexander On 28/03/2014, at 3:27 pm, Larry Sheldon <LarrySheldon@cox.net> wrote:
On 3/27/2014 4:07 PM, Matt Palmer wrote:
On Wed, Mar 26, 2014 at 10:52:42AM -0600, kendrick eastes wrote:
The Full-disclosure mailing list was recently... retired, I guess cisco thought NANOG was the next best place.
Nope, they've been sending these things here for as long as I can remember. I have NFI why -- probably hubris, thinking that everyone running a network *must* have some Cisco somewhere.
There used to be cisco 'wigs with well-known names on NANOG.
One of them was probably asked to do it.
-- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)
On 3/27/2014 7:44 PM, Alexander Neilson wrote:
I wonder if they should be invited to only post a single message with the titles and links to the alerts so that people can follow it up.
Why? Personally, I think it's fine. It only happens (at most) every six months (and sometimes more like a year).
Depends on compliance with the charter for the list but I think it might be nice list etiquette.
I'm surprised at the level of concern over this, considering it's an event that has been going on since before most of those posting about this were even on this list. I'm hoping (in vain, I'm sure) that my gently pointing out that those posts are useful to many people, and that their occurrence predates most of you, will make this non-issue die away (and you make me REALLY MISS srh). While I still worked (I don't now; I'm retired), it was nice to have those alerts, because it could be checked against the *things* *that* *should* *be* *patched* for sanity. Even now, there's still Cisco stuff on my toy network, and I *still* care. Could we just stick to the interesting issues of IPv6, and SMTP, and move on? Please? -- You've confused equality of opportunity for equality of outcomes, and have seriously confused justice with equality. (Woodchuck)
On Friday, March 28, 2014 05:48:29 AM Shrdlu wrote:
Why? Personally, I think it's fine. It only happens (at most) every six months (and sometimes more like a year).
I think it's fine too. As I'm sure you know, if you're a Cisco customer, you can subscribe to their internal notification services where you'll get this anyway. That they consolidate the most critical bug information and push it out to the typical operational mailing lists a couple of times a year is not such a problem, I'd say. For some, this could be the only way they find out. Mark.
Alexander Neilson <alexander@neilson.net.nz> wrote:
I wonder if they should be invited to only post a single message with the titles and links to the alerts so that people can follow it up.
i would prefer that the header be in blue, the titles in green, and the urls in magenta, in comic sans, of course randy
On 3/28/2014 12:57 AM, Randy Bush wrote:
Alexander Neilson <alexander@neilson.net.nz> wrote:
I wonder if they should be invited to only post a single message with the titles and links to the alerts so that people can follow it up. i would prefer that the header be in blue, the titles in green, and the urls in magenta, in comic sans, of course
randy
I disagree vehemently. That's far too simple of a system and doesn't convey the necessary information that should be in a summary document. Titles should be either cerise, amaranth or raspberry coloured, depending on the bug's severity, and the headers should be blue-gray, glaucous or steel blue depending on the day of the week the bug was discovered. Some people might whine that those colors are too close to each other, but they can just buy a colorimeter -- that's an operational problem anyways. I can agree to comic sans, as long as it blinks. Actually, we should probably just set up a committee for report styling. We really need an industry standard for this, and one that covers all possible reporting needs for at least the next 20 years. Shouldn't take more than a few weeks. I think I have a TPS report template around here that would be a great starting point.... :p
participants (6)
-
Alexander Neilson -
Larry Sheldon -
Mark Tinka -
Peter Kristolaitis -
Randy Bush -
Shrdlu