Timeline for Topicality of NIS when configuring new devices?

Current License: CC BY-SA 3.0

9 events

when toggle format	what		by	license	comment
Apr 13, 2017 at 12:14	history	edited	CommunityBot		replaced http://serverfault.com/ with https://serverfault.com/
Mar 25, 2015 at 0:39	vote	accept	Andrew B
Mar 22, 2015 at 19:26	comment	added	Michael Hampton Mod		By all means such people should be strongly warned that they have a problem that needs fixing. But I don't think that always means they should be turned away.
Mar 22, 2015 at 19:20	answer	added	Andrew B		timeline score: 3
Mar 22, 2015 at 19:12	comment	added	Andrew B		If I was, I wouldn't have bothered trying to put a finer point on it. I do see where you're coming from though. I'm probably taking too much of a hard line due to how we typically handle the case where people are trying to use root in insecure ways, in an effort to prevent people copycatting bad design in Google searches.
Mar 22, 2015 at 19:05	comment	added	Michael Hampton Mod		NIS was known to be insecure more than 15 years ago. But some people are still stuck with it because it's been in the environment forever with no sign of budget or political will to replace it. Are you suggesting we should not help people maintain their environments simply because they have security issues?
Mar 22, 2015 at 19:02	comment	added	Andrew B		@Michael I'm not sure that completely addresses the topic at hand, since the subject of security is never touched on. I don't consider the three bullets in the question to really address this case. (certainly not "The system can still perform well for its intended purpose") That said, I'm also fine with it if that's the stance the community wants to take.
Mar 22, 2015 at 18:59	comment	added	Michael Hampton Mod		Have you read When are legacy/unsupported systems still on-topic?
Mar 22, 2015 at 18:45	history	asked	Andrew B	CC BY-SA 3.0