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]

Date: Mon, 20 Nov 2006 00:04:27 -0800
From: Aaron Howell <aaron_howell@...nuity-is.com>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: Patch tuesday debris

-----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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

iD8DBQFFYWGL7MF9x9aUuGIRAnTzAKCOD8AjYY2gRCPOQ9dHjEobftVQfwCglmKM
p8DUMR+bh+4SwI0/S/J5Mh8=
=I36/
-----END PGP SIGNATURE-----

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