[nsp] To S or not to S?

From: Charles Sprickman (spork@inch.com)
Date: Tue Jul 02 2002 - 17:50:41 EDT

Next message: Gert Doering: "Re: [nsp] To S or not to S?"
Previous message: Cisco Systems Product Security Incident Response Team: "Security Advisory: Cisco Secure ACS Unix Acme.server Information Disclosure Vulnerability"
Next in thread: Gert Doering: "Re: [nsp] To S or not to S?"
Reply: Gert Doering: "Re: [nsp] To S or not to S?"
Maybe reply: Charles Sprickman: "[nsp] To S or not to S?"
Maybe reply: Charles Sprickman: "[nsp] To S or not to S?"
Maybe reply: Charles Sprickman: "[nsp] To S or not to S?"
Reply: Gert Doering: "Re: [nsp] To S or not to S?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mail actions: [ respond to this message ] [ mail a new topic ]

Hello All,

Is the S-train still recommended for an ISP not needing an abundance of
fancy features? I'm not convinced 12.2 is worth it yet as long as I can
still get security fixes... Just BGP, OSPF, 802.1q VLANs and ssh, that's
all we require.

Any opinions?

Thanks,

Charles

--
Charles Sprickman
spork@inch.com

Next message: Gert Doering: "Re: [nsp] To S or not to S?"
Previous message: Cisco Systems Product Security Incident Response Team: "Security Advisory: Cisco Secure ACS Unix Acme.server Information Disclosure Vulnerability"
Next in thread: Gert Doering: "Re: [nsp] To S or not to S?"
Reply: Gert Doering: "Re: [nsp] To S or not to S?"
Maybe reply: Charles Sprickman: "[nsp] To S or not to S?"
Maybe reply: Charles Sprickman: "[nsp] To S or not to S?"
Maybe reply: Charles Sprickman: "[nsp] To S or not to S?"
Reply: Gert Doering: "Re: [nsp] To S or not to S?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:02 EDT