How do you deploy?
Last night a question was put to us, "I wonder how many people use vendor-loads (on new machines) versus reformat/reload?" Therefore, in the interest of science (and general curiosity) I thought I would throw the question out for discussion today. Feel free to let us know via the "Contact" link at the top of this page how you, or your organization, choose to deploy.
/-- UPDATE --/
We have received a number of responses to this question, and the majority has been of the 'reformat/reload' variety. One of our readers, Ian, submitted some excellent thoughts I would like to share:
Dare I question Pros and Cons? I do... Pros: Nothing beats the familiarity and intimacy of a custom install... every file is accounted for and required, a blessing if trouble shooting is required in the future. Cons: Time, it can be time consuming performing a reformat/clean install depending on configuration but long term those hours appreciate to savings in the event of a catastrophe - A worthwhile trade off." (Thank you Ian, have a safe trip)
The final tally is an overwhelming 'reformat/reload' with some interesting thoughts on how to go about it. I will consolidate some of those thoughts, and add them to this write-up later in the week.
Many thanx go out to everybody who wrote in today. Thank you.
Veritas Exploit on the web
FrSIRT has notified the ISC that a new exploit has been released utilizing the Stack Overflow vulnerability in Veritas Netbackup Enterprise Server. As a reminder, a specifically crafted packet, sent to the Volume Manager via port 13701, will cause a stack overflow, allowing the attacker to run code of her/his choosing. Authentication by the attacker is not needed to take advantage of this vulnerability.
The vulnerability that this exploit takes advantage of is ~60 days old. The downside of this exploit is that, in one pass, an attacker would have the ability to create a disaster, and then destroy a company's ability to recover from said disaster.
The security packs that address this vulnerability, Symantec Advisory #SYM05-024, can be found here.
Thanx again to FrSIRT for providing the update.
Two-factor authentication Defense Mechanisms
With the growing use of two-factor authentication, users are finding it increasingly difficult to safely transport and, especially, store one of the more common devices used in this endeavor; the Smart Card. A device the size and shape of a common credit card, this is different from standard credit cards in that it has an embedded chip for the storage of information, particularly user information and certificates. Recent discussions brought about the point that an individual might be wise to protect the Smart Card with the same degree of protection as the other piece of two-factor authentication, the PIN.
Both devices, at a minimum, require protection from the greatest threat posed to date, and that is electromagnetic psychotronic hacking form mind control carriers (MCCs). In previous articles it was established that psychotronic hacking can be used to decrypt and read brain waves, so the process of hacking a Smart Card would be child's play for MCCs.
*PIN Protection unit (PPU)
http://zapatopi.net/afdb/
*Smart Card protection unit (SCPU)
http://www.rpi-polymath.com/ducttape/RFIDWallet.php
The regular practice, and combined use, of the PPU and SCPU will result in a little known heightened state of personal security, commonly referred to as Infosystems Defcon 10T (ID-10T)
WMF Generator
We received notification last night that a working exploit "MS Windows Metafile (WMF) Remote File Download Exploit Generator" has been released to the public. The code takes advantage of the "Vulnerability in Graphics Rendering Engine Could Allow Remote Code Execution", MS# MS06-001. The exploit code will generate a .wmf that downloads and executes a specified URL. The sad part to this story is that we have a set of 'plug & play' source code for evil-doers to spread their wares with. And only 10 days after a patch has been released.
Windows Vista security patches
(Thanks to EWeek for the link.)
-- Bill Stearns
Comments