Re: [Full-disclosure] Patch tuesday debris
- From: "Dave \"No, not that one\" Korn" <davek_throwaway@xxxxxxxxxxx>
- Date: Tue, 21 Nov 2006 14:27:51 -0000
Dave "No, not that one" Korn wrote:
Last tuesday's updates (which I deferred installing until yesterday)
left a folder on my HD, called "C:\c0772dab3463959f7c", containing a
log file, msxml6-KB927977-enu-x86.log, which contains install logging
details for the msxml patch.
Did everyone get this (or perhaps a similarly-named folder with a
different hex number)? If absolutely everyone ended up with this it's
probably just M$ being careless, but if not it might mean something
failed during install and that's why it didn't clean up properly.
Enough other people reported this, and there's been no sign of any
problems, that I think it can be safely ignored. Thanks for all the input,
folks.
cheers,
DaveK
--
Can't think of a witty .sigline today....
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
- References:
- [Full-disclosure] Patch tuesday debris
- From: Dave \"No, not that one\" Korn
- [Full-disclosure] Patch tuesday debris
- Prev by Date: Re: [Full-disclosure] Which is more secure? Oracle vs. Microsoft
- Next by Date: [Full-disclosure] [ GLSA 200611-15 ] qmailAdmin: Buffer overflow
- Previous by thread: Re: [Full-disclosure] Patch tuesday debris
- Next by thread: [Full-disclosure] [ MDKSA-2006:214 ] - Updated gv packages fix buffer overflow vulnerability
- Index(es):
Relevant Pages
|
