🚀 go-pugleaf

In article <lhx1x_k@rpi.edu>, fitzgb@mml0.meche.rpi.edu (Brian Fitzgerald) writes...
>:-)
> 
>>From: mcb@presto.ig.com (Michael C. Berch)
>>Organization: IntelliGenetics, Inc., Mountain View, California, USA
>writes:
>....
>>
>>        _____________________________________________________
>>             The Computer Incident Advisory Capability
>>                         ___  __ __    _     ___
>>                        /       |     / \   /
>>                        \___  __|__  /___\  \___
>>        _____________________________________________________
>>                           INFORMATION BULLETIN
>>
>>       18 New and Upgraded Security Patches Available For SunOS
>....
>[ Ken Pon's announcement to Sun Customers, renumbered and reformatted ]
>....
>>This document was prepared as an account of work sponsored by an agency
>>of the United States Government.  Neither the United States Government
> 
>.... man, I'm in the wrong line of work. :-)
> 
>Brian
>(future consultant :-))

It should be remembered that Ken Pon was hired away from CIAC by Sun.
Accordingly, CIAC has great respect for Ken's work and would never dream
of changing one little word! :^) (For a less tonge-in-cheek reason, see
items 2 and 3 below.)

It should also be noted that:
	1) The posting of this CIAC bulletin was not by CIAC - CIAC uses
		a surface mail list and an e-mail list for distribution.
		(I also have it on good authority that comp.security.announce
		is not currently available to CIAC as a distribution
		channal.)
	2) CIAC bulletins are prepared by the DOE's CIAC team for the
		benefit of DOE installations, many of which are not
		on the Internet or otherwise don't quickly see Ken's
		(Sun's) security announcements. Renumbering/reformatting
		is part of the administrative necessities of their
		business. The CERT/CC follows basically the same policy.
	3) Believe it or not, some information reaches security groups
		such as CIAC and the CERT/CC where the provider of that
		information requires particular wording. (While this may
		not be the case with this bulletin, it is often unwise to
		deviate too far from vendor wording. This helps avoid
		misunderstandings. (For fun, compare CIAC bulletins and
		CERT/CC advisories generated from the same Sun security
		dispatch!)
	4) Don't be put-off by the disclaimer. The US government uses that
		everywhere - its required basically everywhere! Given the
		state of governmental bureaucracy, are you surprised??

OK, yes, I've had some fun with this, but hopefully I provided some
insight/information also.
					Hal R. Brand
					(Another Ex-CIACer)
					LLNL
					brand@addvax.llnl.gov