Re: can't prevent root lockout under Tru64/C2 security
From: Darren Tucker (dtucker_at_gate.dodgy.net.au)
Date: 01/31/05
- Next message: Nico Kadel-Garcia: "Re: can't prevent root lockout under Tru64/C2 security"
- Previous message: Darren Tucker: "Re: can't prevent root lockout under Tru64/C2 security"
- In reply to: Nico Kadel-Garcia: "Re: can't prevent root lockout under Tru64/C2 security"
- Next in thread: Nico Kadel-Garcia: "Re: can't prevent root lockout under Tru64/C2 security"
- Reply: Nico Kadel-Garcia: "Re: can't prevent root lockout under Tru64/C2 security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 31 Jan 2005 03:44:14 GMT
Warning: topic drift ahead. For a potential solution see my other
post up-thread.
On 2005-01-30, Nico Kadel-Garcia <nkadel@comcast.net> wrote:
> Number 1: Tru64 support is basically dead as a doornail.
HP may be fitting it for a coffin but it's not dead yet.
> I strongly urge you
> to take the money for electricity used powering those older systems and
> invest it in a modest modern Opteron box running a decent Linux distro.
That's not always easy, cost effective or even possible.
In many environments, the new hardware cost is pocket change compared to
the the cost of time, effort, application upgrades, approvals, testing,
(re)certifications and contract renegotiations required to implement it.
An application may not even be available on a newer platform at all.
Contractual obligations, regulations and/or certifications may prevent.
> There just aren't enough of these systems left alive to constitute an open
> source community to keep them going.
Digression: as far as I'm concerned, OpenSSH support is alive on a given
platform as long as *someone* is prepared to do the work, and it can be
done without compromising the integrity of it.
For example, I still test releases on AIX 4.2.1 even though that version
has been EOLed for nearly half a decade. It's similar enough to modern
versions that the effort involved is small (and I get a kick out of the
occasional email I get telling me that it works on those systems or ones
even older).
For another example, until recently it built on NeXTs because one of the
other developers did the work (until finally running out of time to wait
for compiles on a 25MHz 68040 :-)
In the case of sshd's SIA support, it's pretty well written and the
author usually pops up when a pre-release call-for-testing goes out.
Even if he stops doing that, as long as someone steps up it'll still be
"supported". And if no one does and you still need support, drop me a
line, we might be able to work something out :-)
--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
- Next message: Nico Kadel-Garcia: "Re: can't prevent root lockout under Tru64/C2 security"
- Previous message: Darren Tucker: "Re: can't prevent root lockout under Tru64/C2 security"
- In reply to: Nico Kadel-Garcia: "Re: can't prevent root lockout under Tru64/C2 security"
- Next in thread: Nico Kadel-Garcia: "Re: can't prevent root lockout under Tru64/C2 security"
- Reply: Nico Kadel-Garcia: "Re: can't prevent root lockout under Tru64/C2 security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
