full-disclosure - Re: Patch tuesday debris

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <D1E2366271E85B44945134F3F3CA58CCB9358F@cptcorpmail01.capetown.fwslash.net>
Date: Mon, 20 Nov 2006 14:36:51 +0200
From: "Steven Scheffler" <steven@...wardslash.com>
To: "ASB" <abaker@...il.com>,
	"Aaron Howell" <aaron_howell@...nuity-is.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Patch tuesday debris

This happens sometimes. The (MSI3) installer doesn't clean up the
temporary folder. The syntax is something similar:

msxml4-KB927978-enu /q REBOOT=ReallySuppress /l*v c:\KB927978.log

Where the last part is the path to the log file

________________________________

From: full-disclosure-bounces@...ts.grok.org.uk
[mailto:full-disclosure-bounces@...ts.grok.org.uk] On Behalf Of ASB
Sent: Monday, November 20, 2006 1:08 PM
To: Aaron Howell
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: [Full-disclosure] Patch tuesday debris

Yes, there seems to have been some debris left from this one.   (Based
on a look at 5 systems)

No errors to speak of.

-ASB

On 11/20/06, Aaron Howell <aaron_howell@...nuity-is.com> wrote: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

My folder is named c:\6ad0c137abd5117c8e8326 , and my file is named 
msxml4-KB927978-enu.log

>   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.

I just checked 2 random machines at the office, and they both have
similar directories with the same log file. My assumption would be that
it's just sloppy installation leaving files rolling around... 

>     cheers,
>       DaveK

aaron

This e-mail message is confidential and intended solely for the person to whom or the entity to which it is addressed. All the contents and any attachments remain the property of VR Services (Pty) Ltd unless so stated by contract.
If you are not the intended recipient, you are prohibited from reading, copying, using or disclosing this message to others. 
If you received this message in error, please notify the sender immediately by replying to this e-mail or by telephoning +27 21 528 9300 and thereafter delete the message. VR Services (Pty) Ltd does not accept liability for any personal views expressed in this message.

Content of type "text/html" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/