how often?
that is irrelevant unless the site design is static for "long" periods of
time...
if they cant secure the darn machine it doesnt matter if it even
exists... unless..... :)
some of you people are true "experts" at security theory and
implementation... if the usgov or whomever wont hire you (and pay you) to
do it right and get the job done (security wize,etc) then the only issues
i see are that
the site(s) is/are insecure and really has no value based upon
content consistancy
taxpayer dollars are being wasted
it makes good food for security discussions
the site(s) was/were designed to be hacked for some reason(s)...
--->
Robert H. Hanson Cutting Edge Communications, Inc.
Otis Orchards, Wa. Regional Commercial Internet Service Provider
(509) 927-9541 email: roberth @
cet .
com - http://www.cet.com/
On Tue, 31 Dec 1996, Dave Kinchlea wrote:
> Not to disagree with anything Paul has said, because I don't, but the
> original premise was government web sites not high volume web sites. How
> often does the Air Force's web pages need to change? Not too often I
> would wager, they don't *need* re-visits, they don't have advertising
> (at least I would expect they don't, I haven't checked actually), they
> are there just to provide some mostly static information. Given that, I
> think there is merit to a write-once media approach. But not, as Paul
> and others point out, as a general solution.
>
> cheers, kinch
>
>
References:
|
|
